Phone Number Formatting
Dialora parses and normalizes phone numbers, so a range of formats will work. But a number without a country code is genuinely ambiguous, and those get rejected rather than dialed incorrectly.
Standardize on E.164 and the problem goes away.
The format
+[country code][area code][subscriber number]No spaces, hyphens, parentheses, or leading zeros after the country code.
| Country | Example |
|---|---|
| US | +12345678901 |
| UK | +447123456789 |
| Australia | +61412345678 |
| India | +919876543210 |
What to avoid
| Format | Problem |
|---|---|
(123) 456-7890 | No country code — ambiguous |
123-456-7890 | No country code |
0412 345 678 | National format with a trunk prefix; the leading 0 is wrong in E.164 |
+1 (234) 567-8901 | Usually parses, but don’t rely on it — strip the punctuation |
Contacts uploaded by CSV with no country code are skipped at import, which is why a group’s contact count sometimes comes out lower than the row count in your file. See How to Upload Contacts.
Fix your data at the source
If your CRM stores national-format numbers, convert them once on export rather than fixing each upload:
- Strip spaces, hyphens, and parentheses
- Remove any leading trunk
0 - Prefix the country code with
+
Doing this in your own database means every campaign, webhook, and API call downstream just works.