Start with a small, permissioned list you understand. A clean import matters more than a large one.
1. Make the file easy to check
Keep an untouched copy of your original export, then prepare a CSV with one contact per row and a clear header row. Text Blast Pro accepts up to 5,000 contact rows in a single import. Split larger exports into separate files before uploading, and give each part a name your team will recognize later.
Separate the seller's name, phone number and property fields into their own columns. Keep phone numbers and ZIP codes as text in your spreadsheet so formatting does not remove leading digits. A property address and a seller's mailing address are different fields; check that you are mapping the one you actually intend to use in your message.
- Remove blank contact rows and obvious duplicates before uploading.
- Check a few records against the source, especially phone numbers and addresses.
- Use a descriptive list name, such as the source, market and export date.
2. Keep permission records with the list
Possessing a phone number is not the same as having permission to send a marketing text. Before importing, confirm that your intended use is appropriate and that you can document the permission behind it. Keep the original evidence, not just a note saying the list was purchased or exported.
The import flow asks you to attach compliance evidence and confirm that it applies to the contacts being imported. Read those fields carefully and provide accurate information. Text Blast Pro records your certification and excludes invalid, duplicate and previously opted-out numbers; those controls do not turn an unsuitable list into a suitable one or replace your own screening responsibilities.
3. Review the mapping, not just the row count
Upload the CSV in Marketing Lists and review the suggested column mapping. The seller phone field is required. Map the name and property fields you need, and leave irrelevant columns unimported. Use the sample values beside each column to catch mistakes before confirming the import.
For campaign personalization, the supported merge fields are {{first_name}}, {{last_name}}, {{property_address}}, {{property_city}}, {{property_state}}, {{property_zip}} and {{apn_id}}. Choose fields that are populated in your list. If many records have no property address, rewrite the message so that a missing address will not leave an awkward or misleading sentence.
4. Check the message and sending setup
Create a campaign draft, select your list and review the message preview. Read it as the recipient would: who is contacting them, why are they being contacted, and what response are you asking for? Identify your actual business, use only accurate details and include the required opt-out wording. Check every wording variation, not only the first one.
Review the character and SMS segment estimate. A longer message or some characters can use more than one segment, so a single visible message is not always a single unit of SMS usage. Start with a small test using numbers you control and are allowed to message, then confirm that replies appear in the inbox.
5. Launch only when the workspace is ready
The seven-day trial is for workspace setup, not live SMS sending. Sending requires an eligible paid subscription and approved messaging setup. Confirm your sending number, available usage and team responsibilities before launching. Recipient sending hours, suppression checks and capacity limits still apply, even to a small campaign.
After launch, watch the campaign's progress and review any waiting or failure details. A completed campaign means processing has finished; it is not a promise that every carrier delivered every message. Keep the original CSV and permission evidence so you can investigate a specific record without guessing.
See where this fits in your workflow.
Explore the features, or bring your list and follow-up questions to a product walkthrough.