Compliance

SMS safeguards built into the daily workflow.

Permission, approved sending numbers and respectful follow-up matter before you press start. Text Blast Pro adds sending-hour controls, opt-outs and pacing to help you manage that work.

Why this page exists

Sent is not the same as delivered.

A provider accepting a text does not prove it reached the recipient. Review confirmed delivery and failure information separately, and keep your sending setup and list permissions current.

Wait for delivery evidence

Delivery callbacks update message status when the provider supplies them. Missing confirmation stays distinct from confirmed delivery.

Review the whole workflow

An approved number is only one part of sending. Account readiness, list permission, opt-outs and sending limits still apply.

Keep responsibility visible

Platform controls support your process. They do not replace your responsibility to contact people lawfully.

10DLC

Registered before you send anything

The TBP team handles the supported 10DLC setup using your business and messaging information. Live sending requires messaging approval and eligible paid billing. Approval times can vary.

  • Brand and campaign, both

    Registering the business is only half of it. The campaign — what you are sending and why — is registered too.

  • Done during onboarding

    We file it with the information you give us at signup. You never open a carrier portal.

  • Numbers attached to the registration

    Every number we provision for you sends under your registered campaign, not a shared pool.

Quiet hours

Sending windows that account for the seller's timezone

Campaign and nurture sends use the recipient timezone inferred from contact data. A send that falls outside the configured window waits for an eligible time instead of following your office clock.

  • Inferred from contact data

    The system uses the mailing state, then property state, to infer a timezone. If neither is available, it falls back to the workspace timezone. Check your list data before sending.

  • Held, not dropped

    A message that would land outside the window waits until the window opens rather than being discarded.

  • Nurture obeys it too

    Scheduled follow-ups use the same window, so an automated sequence cannot text somebody at 3am on your behalf.

Opt-outs

Opt-outs apply across the workspace

Standard opt-out keywords are processed when incoming messages reach TBP. The number is added to your workspace suppression records so future campaigns and follow-ups can exclude it.

  • Three things happen at once

    The conversation is marked, it leaves your unread queue, and the number is suppressed.

  • Across every campaign, not just that one

    The suppression applies to your whole account and every list you upload afterwards.

  • Kept even if you delete the thread

    Removing a conversation does not remove the opt-out. That record is what stops the number ever being texted again.

  • Respect requests beyond keywords

    Review what a seller actually says. If they ask not to be contacted, block further messaging rather than treating the absence of a keyword as permission.

Pacing and rotation

Controlled sending across approved numbers

Campaigns use eligible sending numbers and configured capacity limits. Pacing and rotation organize delivery attempts; they do not guarantee delivery or bypass provider filtering.

  • Spread across every number

    Traffic rotates automatically. No single number carries the whole campaign.

  • Paced by the minute

    Each number sends at a steady rate rather than emptying a queue as fast as the provider will accept it.

  • Sticky per seller

    A seller always hears from the number that first texted them, so you look like a consistent contact rather than a rotating cast.

  • A daily ceiling if you want one

    Off by default, available per number if a carrier ever asks you to throttle.

Message variety

Write useful variations, not duplicate work

Create up to four full-message variations and personalize supported fields. Review each version for accuracy, sender identification and opt-out wording.

  • Separate messages to review

    Write complete message options in the campaign editor so each variation makes sense on its own.

  • Consistent per person

    Variation selection stays consistent for a recipient within the campaign. A new campaign still needs its own review.

  • Merge fields on top

    Name, street and city vary the body further without you writing anything twice.

List screening

Checked before a single message leaves

The cheapest compliance problem to fix is the one you never send. Every import is screened against your suppression list, and the report tells you exactly what was dropped.

  • Opt-outs removed at import

    Anyone who has ever opted out is taken off the list before the campaign is even built.

  • Invalid numbers dropped

    Phone-format validation flags unusable entries. This is not a guarantee that a number is mobile, reachable or owned by the expected seller.

  • Record permission and screening

    Keep permission evidence and a recent screening date for your list. TBP records your attestation; it does not query the National DNC Registry for you.

  • Duplicates collapsed

    One person is one thread, even if they appear on three lists you bought separately.

Ready when you are

Deliverability is a feature, not an afterthought.

Use the setup trial to prepare your workspace. Live texting begins after paid activation and messaging approval.

10DLC registration handled7-day setup trialCancel anytime