Consent capture
We write the sign-up wording for your booking form, tablet and phone script, name your business, say what the texts are for and how to stop them, and store when and where each customer agreed. You receive: the form wording in place, and a consent field layout for the contact record.
Carrier registration
We prepare the brand details and the campaign description from your records, with sample messages, and submit them once you approve. If a registrar asks for a fix, we read the reason and resubmit. You receive: the registration pack, and the status of the brand and the campaign.
Message flows
We build each text from its trigger to its end: a confirmation, a reminder, a ready notice, a follow-up. Each flow lists its wait times and what stops it. You receive: a message map with the wording, the trigger and the exit for each text.
Reply handling
A reply of C cancels the booking, R offers new times, and a question goes to a named person at your business with the thread attached. The test log shows each reply run on sample numbers. You receive: a reply table listing each kind of reply and what the workflow does.
Send window
We set the hours texts can go out, inside the federal and state limits we identified for your customer base, and hold a text that is due overnight until the window opens. The customer’s time zone comes from the ZIP code on the booking. You receive: a send-window rule with the hours, the states it covers and the hold behavior.
Opt-out and suppression list
A STOP, or any other clear request to stop, moves the number to a suppression list that each text workflow reads before it sends. The customer gets one confirmation, and the list stays in your account. You receive: the suppression list, the confirmation wording and a short guide for staff who hear a request by phone or in person.