Variable Mapping
Match contact-list columns to the fields your AI employee already uses in a campaign.
Variable Mapping
Variable mapping connects the columns in your contact list to the fields used during a campaign. Your job here is not to write new placeholders; it is to map the existing employee fields to the correct CSV columns.
The fields your AI employee uses are configured during setup and listed automatically in the campaign wizard. You only need to match them to the right columns from your contact list.
How the Mapping Step Works
Keep each piece of information in its own CSV column, such as name, company, order number, or appointment date.
During campaign creation, the Variable Mapping step shows employee fields on one side and your CSV columns on the other.
Fonify often matches similar names automatically. Still, double-check every critical field before moving on.
Use the preview to see how the first few contacts will resolve. This helps you catch empty or incorrect mappings before launch.
Example Mapping
For a real-estate campaign, your mapping might look like this:
customer_name -> full_name
preferred_area -> district
budget_range -> budget
last_contact_date -> last_contacted_atThat allows the employee to personalize the call with the right customer context.
Most Common Mistakes
| Mistake | What happens | What to do |
|---|---|---|
| Empty column values | The employee cannot use that information | Keep critical fields complete |
| Wrong column mapped | The employee says the wrong customer detail | Recheck names, dates, and amounts carefully |
| Format mismatch | Dates or numbers appear wrong | Keep CSV formatting simple and consistent |
Missing required mappings can block the campaign from starting.