Objective
Produce a CSV that fills every one of Ananya’s variables, and find and fix a row Ringg rejects.The scenario
Acme’s CRM exports the customers due on 15 October with its own headers:Customer, Phone, EMI, Due and Loan A/c. Nothing matches a variable name, so you map the columns by hand, and one phone number in the export is incomplete. Use your own and your colleagues’ numbers.
Phone numbers are ten digits without
+91; the amounts sit in double quotes because they contain a comma.
Hands-on
Uploading and mapping a calling list
1
Upload the export
Open Monitor → Campaigns → Create campaign. Name it
EMI reminders - 15 October, pick EMI reminder - Hindi, and drop the CSV on Upload calling list. The file must be .csv, up to 20 MB, with a header row.2
Map the columns
In Calling list settings, keep Country code +91. Under Map variables to CSV columns, every variable reads Select CSV column. Pick
Customer for callee_name, Phone for mobile_number, EMI for due_amount, Due for due_date and Loan A/c for loan_account; Next stays disabled until all five are mapped. Leave Remove invalid rows on and Transliterate variables off: it rewrites values into the agent’s primary language, English (India) for Ananya.3
Read the upload summary
Click Next. After “CSV verified successfully”, step 2 shows Total rows 3, Valid contacts 2, Successful upload
2/3 uploaded and Invalid rows 1 with Download invalid rows.4
Fix the row
Download the rejected rows (
invalid_entries.csv), complete the phone number and put the row back. While editing, rename the headers to the variable names so the next upload maps itself; matching is exact, including case.5
Upload again
Leave the page without launching: the campaign stays in the list as a Draft, where you can select it and click Terminate. Create a new campaign with the fixed file and click Next.
Checkpoint
Every variable is mapped before you touch a dropdown, and the summary reads Total rows 3, Valid contacts 3, Successful upload
3/3 uploaded, with no Invalid rows.Exercise
Upload the original export once more with Remove invalid rows switched off. Expected result: the upload still loads the two valid rows and sets the bad one aside, and Ringg also emails you the rejected rows. Keep the switch on for real lists to skip that email.What you learned
- A list needs one column per agent variable, always including
mobile_numberandcallee_name. Headers that equal the variable name map themselves; anything else you map by hand. - One Country code covers the whole list, numbers are national-format digits, and another country means another campaign.
- Rows Ringg can’t call are dropped and returned as
invalid_entries.csv; with Remove invalid rows off, they are also emailed to you. A campaign where every row fails ends as No Valid Contacts.