(EN) How to complete the employee file for SFTP

Creada por Iara Candela Vicente, Modificado el Vie., 31 Jul. a las 11:14 A. M. por Jesica Melo

⭐ Objetivo

Provide the English field-by-field guide to complete the employee file that is uploaded to the SFTP server.

⏰ Cuándo aplica esta guía

Before the first upload, and whenever employees are added or the structure changes.

⚙️ Paso a paso

If you are using integration through SFTP, you must generate a csv file which must keep the following updated employees' data:

Field	Details	Example
ID	Employee's identification code.	123
Nickname	Employee's nickname that Lara will use in their conversations. (If it is blank, Lara will use the Name field)	Mike
Name	Employee's name	Michael
Surname	Employee's surname	Scott
Email	Employee's email	michael.scott@dundermifflin.com
WhatsApp* (necessary when it will be the communication channel)	Phone number with a WhatsApp account (including the callsign)	52 45896523
Start date	Date of joining the company (in YYYY-MM-DD format)	2005-03-24
Manager (email)	Employee's manager's email	david.wallace@dundermifflin.com
HR on charge (email)	Employee's HR on charge's email	toby.flenderson@dundermifflin.com
Country	Geographic location of the employee. Use the two identifying letters of the country.	MX
Language	Language that Lara will use to speak to the employee.	Spanish: es Argentinian Spanish: es-ar Portuguese: pt English: en
Area	Area or department to which the employee belongs. Used for metrics.	Commercial
Team	Team to which the employee belongs. Used for metrics.	Sales
Role	Employee's position in the organization.	Regional Manager
End date	Only complete in case the employee is no longer part of the company, or they are about to leave it.	2021-03-24
Reason for leaving	Indicates what type of exit survey Lara should send to the employee.	Voluntary / Involuntary
Do not contact	Binary value to indicate if we want Lara NOT to contact the employee.	TRUE / X
Cohorte	[Leave blank, do not modify or complete]	-

To encourage a high response rate, it is suggested that you complete the Nickname field. Note that if the nickname field is empty, Lara will use the “Name” field, which for some people is a set of 2 or more names, and may feel unfriendly. E.g. “Hello John Michael, my name is Lara…”

Important data to take into account

How to upload the exit of an employee?

The “leaving date” field must be completed with the date of the person's last day in the company. This will automatically cause Lara to stop contacting the person from that date.

How can I temporarily pause Lara from contacting a person?

The “Do not contact” column must be completed with "TRUE". When you want to resume contact, simply delete the “TRUE” value.

Is the information automatically updated?

Yes, when you make a change to the file, the change will automatically be reflected on the platform the next day in the morning.

✅ Buenas prácticas

Always fill in ID, a contact channel (email or WhatsApp), leader and hire date. Without those four, the person does not enter the flow.

Use the AAAA-MM-DD format for every date.

Keep the ID stable over time: it is the key Lara uses to recognise a person.

⚠️ Errores frecuentes

Renaming or reordering the columns.

Using personal email when a corporate one exists.

Adding sensitive columns Lara does not need, such as compensation or health data.

❓ Preguntas frecuentes

Which fields are mandatory? ID, a contact channel, leader and hire date.

How do I flag someone who must not be contacted? With the do-not-contact field. There is no need to delete them.

Is the Spanish version identical? Yes. Keep both aligned.