CSV Import Guide
How to prepare and upload your customer list to Tadhkir
Required Columns
Your CSV file must include these three columns (header names are flexible):
| Data | Accepted Header Names | Required |
|---|---|---|
| Customer name | Name, name, Full Name |
✅ |
| Phone number | Phone, phone, Mobile |
✅ |
| Last visit date | Last Visit, last_visit, Visit |
✅ |
File Format
- File type:
.csv(comma-separated) - Encoding: UTF-8 (important for Arabic names)
- Max rows: No hard limit, but we recommend batches of 1,000 for large imports
Example CSV
Name,Phone,Last Visit
Fatima Al Rashidi,+966501234567,2024-08-15
Mohammed Al Harbi,0501112233,2024-06-01
Sarah Johnson,+447891234567,2024-09-20
Amina Musa,+2348012345678,2024-07-30
Phone Number Format
Tadhkir accepts multiple formats and auto-normalises them:
| Input | Normalised to | Notes |
|---|---|---|
+966501234567 |
+966501234567 |
✅ Preferred — international format, any country |
0501234567 |
+966501234567 |
✅ Local format, read using your market |
00966501234567 |
+966501234567 |
✅ IDD prefix read as + |
(080) 3123-4567 |
+2348031234567 |
✅ Spaces, brackets and dashes are ignored |
0803 1234 |
rejected | ❌ Too few digits — we will not guess the rest |
abc |
rejected | ❌ Not a number |
How the country is decided:
- If the number is written with a country code (
+44…,0044…), that country wins — always. A customer of a Lagos clinic who carries a UK number keeps their UK number. - Otherwise it is read as a local number in your business's market. The upload screen tells you which country that is before you import.
Numbers are checked against the real numbering plan for that country, not just a digit count, so a transposed or missing digit is caught instead of being stored as a number that silently never delivers.
If a number is the right length but not in a range we recognise, it is imported with a warning rather than rejected — new ranges open faster than any library's data ships, and refusing a real customer costs more than one failed message.
Date Format
Last Visit must be in YYYY-MM-DD format:
| Input | Valid? | Notes |
|---|---|---|
2024-08-15 |
✅ | ISO 8601 — preferred |
15/08/2024 |
❌ | Will fail validation |
Aug 15 2024 |
❌ | Will fail validation |
2024-13-45 |
❌ | Invalid month/day |
Tip: In Excel/Sheets, format the date column as
YYYY-MM-DDbefore exporting to CSV. In Google Sheets: Format → Number → More formats →yyyy-mm-dd.
Validation Rules
Tadhkir validates each row before importing:
| Check | Rule |
|---|---|
| Name | Must be present (not empty) |
| Phone | Must be a plausible number for its country (see above) |
| Date | Must be a valid date in YYYY-MM-DD format |
| Duplicate in file | The same name and number twice in one file — the second is skipped |
Rows that fail validation are shown in red during the review step. You can proceed with valid rows only, or fix the CSV and re-upload.
Step-by-Step Import
- Go to Dashboard → Customers → click Import CSV (Or complete during onboarding Step 2)
- Click Choose File and select your
.csvfile - Tadhkir parses the file and shows a Review screen:
- Green rows = valid, ready to import
- Red rows = validation errors — hover to see the reason
- Click Import to proceed
- Tadhkir adds new customers, updates existing ones, and calculates each
next_reminder_dateautomatically based on your business vertical - You get a summary of what actually happened — for example "47 added, 12 updated, 3 skipped" — and can download the skipped rows as a CSV to fix and re-upload
Common Errors & Fixes
| Error | Cause | Fix |
|---|---|---|
| "Date must be YYYY-MM-DD" | Date is in another format | Reformat the date column before export |
| "Too few digits" / "Too many digits" | A digit was dropped or added | Check the number against the customer record |
| "Not a phone number" | Letters, or a placeholder like n/a |
Remove the row or fill in a real number |
| "Appears earlier in this file" | The same person is listed twice | Keep one row — the one with the later visit date |
| "That person is already on your customer list with this number" | An exact re-add | Nothing to do; their record is already there |
| "Missing name" | Name column is blank | Fill in all name fields |
| "Column not found" | CSV headers don't match expected names | Rename headers to Name, Phone, Last Visit |
| Arabic text garbled | Wrong encoding | Save CSV as UTF-8 (not ANSI) |
Duplicates and Re-uploads
Re-uploading your list is safe and is the normal way to refresh it. Nothing is duplicated and nothing is lost.
A customer is identified by name and number together:
- Same name, same number → the existing record is updated. Only the visit date changes, and only if the one in your file is later. Uploading an older export can never drag a customer's recall date backwards.
- Same number, different name → added as a separate customer. Families share a handset, and both people should get their own reminders for their own appointments.
- Same name, different number → added as a separate customer. Change a number on an existing record in Dashboard → Customers rather than by re-uploading, otherwise you will have both.
One thing to know about shared numbers: reminders are per person, but unsubscribing is per number. If anyone sharing a handset replies STOP, messages stop for everyone on that number — WhatsApp delivers to the phone, not the person. Any of them can turn messages back on by sending START.
After Import
- Each customer's
next_reminder_dateis automatically calculated (last visit + vertical interval) - Customers with a
next_reminder_datein the past appear immediately in the Recall Engine as overdue - You can view all imported customers in Dashboard → Customers
- To edit a customer's details, click their record in the customer directory