Missed calls and SMS: keep permission separate
When a customer calls while your crew is on a roof or under a sink, a quick reply sounds useful. But a missed call is a signal to follow up, not blanket permission to start an automated text conversation. The operational question is: what permission did this person actually give, for which messages, to which business?
This guide is a workflow checklist for contractors considering customer text-back. It does not determine your legal obligations or guarantee carrier approval. Confirm current requirements with your messaging provider and qualified counsel before turning on automated customer texts.
1. Separate events that often get confused
A caller might contact your shop, hear a recorded disclosure, choose whether to receive texts, and later ask for help or opt out. Each event has a different meaning. A call or voicemail tells you someone tried to reach you; it does not document agreement to automated SMS. Paying an invoice or accepting general service terms is also a separate choice.
A contractor owner opting into JE Horizon account and owner alerts cannot consent on behalf of all their customers. The public Line SMS program covers account, support, and owner notifications; it does not enroll a shop's callers in contractor-to-customer messaging. Treat that distinction as a boundary in forms and staff training.
- Call received: capture the callback number and service request through normal intake.
- SMS permission: record an affirmative choice for a defined sender and purpose.
- Program activation: verify number, brand, campaign, and carrier status before sending.
- Later preference: honor an opt-out and keep its suppression record.
2. Write the program before wiring the automation
Start with one narrow use case, such as intake questions and appointment updates for a current service request. Write down the sender name a customer will recognize, the sending number, types of messages, recipients, and when the conversation ends. Avoid folding promotions into a service-request program; promotional messaging can require different consent and registration.
Make the sender and scope understandable before the person agrees. Include expected or variable frequency, notice that message and data rates may apply, instructions to stop or get help, and the fact that texting is optional. The actual terms and sample messages should match the registered use case. A sentence buried in checkout is a poor substitute for a clear SMS choice.
For Line's proposed caller flow, the published caller-consent script describes a complete spoken disclosure followed by pressing 1 to agree. It says pressing 2, silence, hangup, invalid digits, or an incomplete prompt means no texts. That page distinguishes a proposed managed receptionist program from an optional dedicated line using a shop's own brand and number. Publication of the script is not a statement of carrier approval.
3. Keep a permission record you can review
A consent record should let you reconstruct the customer's choice without relying on memory. For a web form, retain the form version, disclosure text, submitted number, timestamp, and affirmative action. For an in-call choice, retain the script version, number presented, completed disclosure event, and digit selected. Limit access to these records and follow your privacy policy for retention and deletion.
Test the negative paths deliberately. If a call disconnects halfway through the prompt, no customer text should be sent. The same applies to silence or refusal. If a customer says STOP later, suppression should prevent another automated message. A staff member still needs a non-SMS route, such as a callback, to handle the service request.
- Place a test call and decline SMS. Confirm no customer text leaves the system.
- Place a test call, hear the complete disclosure, and affirmatively agree. Inspect the stored event.
- Send STOP from the test handset and verify suppression before attempting another automation.
- Send HELP and confirm the response points to a working support path.
- Repeat after changing scripts, numbers, or providers; old tests do not cover a new configuration.
4. Treat 10DLC registration as a separate launch gate
In the United States, application-to-person messages from a ten-digit long-code number generally run through business messaging registration. Your provider will specify what brand and campaign information to submit for your use case. Expect to align the legal business identity, website, opt-in path, message examples, and opt-out and help handling. Conflicting descriptions can delay review.
Registration and customer permission solve different problems. A registered campaign does not create consent for an individual caller. A valid opt-in does not mean a number is provisioned for business texting. Even with both in place, carriers can filter messages; delivery is never guaranteed. Keep automation disabled until your provider confirms the necessary approval and activation status for the sender and program.
5. Use a restrained first reply
Once the applicable program is active and this customer has agreed, keep the first text tied to the request. An illustrative draft is: “Acme Plumbing: We received your request about a leak. What address should we use for the appointment? Reply STOP to stop, HELP for help.” Replace the placeholder with the registered sender and adapt wording to the approved campaign. This example is not a preapproved template.
Do not promise a technician, arrival time, estimate, or emergency response until a person has checked availability and scope. If the caller does not opt into texts, follow the shop's normal phone or voicemail process. Review the current caller disclosure and SMS program page whenever the workflow changes.
Check the current primary guidance
Messaging rules and provider review practices can change. Before launch, compare your exact opt-in flow and campaign application with Telnyx's current 10DLC campaign requirements, and review the FCC order on revoking consent. These sources do not replace a review of your particular business, provider account, or applicable law.