Short answer
Prepare phone numbers as text with international prefixes and a field map before importing them into a dialler. Separate uncertain data, validate a sample and reconcile created, updated and rejected rows; importing does not establish ownership or permission to call.
Key verification: Keep the original and verify names, numbers and identifiers in the sample.
Sources and limitationsBefore importing contacts to a dialer, prepare the phones as text, preserve the international prefix, and separate the records that you cannot validate. A number that looks correct may still be wrong or not belong to the right person. The import also does not certify permission to call.
Work on a copy, not on the original file
Save an export intact and assigns an identifier to each row. In a working copy, identify the country, phone, email, and fields that the team needs. Keep the phone as text in the spreadsheet to prevent the + sign from disappearing or turning into scientific notation.
CloudTalk requires CSV for import from file and provides a downloadable template. Document valid identifiers, including phone in E.164 format, and a limit of 8 MB. The actual template should be your reference for the headers. Official import requirements .
Cleaning and decision table
| Entry | Proposed Treatment | Reason |
|---|---|---|
| Telephone with spaces and known country | Normalize to the supported international format | Avoid different formats for the same destination |
| Telephone without country and dubious origin | Send for review | Do not invent a prefix for the location of the company |
| Extension written next to the number | Separate in the field supported by the system | The extension is not part of the international number |
| Two lines with the same telephone | Review identity and update rules | It can be a repeated contact or a shared line |
| Record that asked not to be contacted | Exclude from marking batch | Preserve contact restrictions |
It is not enough to remove spaces from all cells. A national or international exit prefix must be interpreted according to the country of origin. If that information is missing, human review is preferable to correcting by guesswork.
Preparation example
The following diagram is illustrative; It is not the CloudTalk template nor does it contain phones to call. Replace field names with supported ones and use your own test numbers.
registro_origen,nombre,telefono,pais,estado_revision
prueba-01,Contacto de ensayo,[numero propio en formato internacional],ES,validado
prueba-02,Registro pendiente,[pais sin confirmar],,revisarPreserve the source identifier if the importer allows an appropriate field. It will help you relate rejected or updated rows to the original copy, without depending on names that may match.
Import a representative sample first
- Download the current template and try encoding with accented names.
- Includes a few fictional records: new, existing, and one deliberately invalid.
- Review how the supplier identifies and updates contacts before accepting the batch.
- Check phones, additional fields, and error reporting.
- Corrects the work file and repeats only the pending records.
- Import the rest when you can reconcile new, updated, and rejected rows.
CloudTalk publishes merge rules that reach CSV imports. Review those rules before uploading data to an existing notebook; a shared phone can influence the partnership. Official Combination Rules .
Close and reconcile the import batch
Document number of rows, date, configuration used and unresolved errors. An import of 100 rows with 95 accepted is not complete until we know what happened to the other five. This preparation does not replace the historical merge in HubSpot : it validates a batch that enters the system.
Consider CloudTalk if you need to convert verified lists into operational team contacts. For few records, manual entry can avoid unnecessary import; for a continuous flow, commit a connector or API before repeating full uploads.
Sources and limitations
Documentary review: . Content type: Documentation-based guide.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- Official import requirementshelp.cloudtalk.io
- Official Combination Ruleshelp.cloudtalk.io
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
CloudTalkAffiliate linkThe labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.