Text agent onboarding
Step-by-step guide to registering your Twilio messaging campaign and setting up Spara Text agents.
This page walks you through the onboarding process for Spara Text agents. Spara uses Twilio to send and receive SMS messages on your behalf. Before your text agent can go live, Twilio requires that your brand and messaging campaign are registered and approved — this is an industry-wide compliance requirement to protect consumers from unwanted messages.
For a refresher on how Text agents work, see Agent Overview and Text Agents.
Overview
Twilio's A2P 10DLC (Application-to-Person 10-Digit Long Code) registration process ensures that businesses sending text messages through standard US phone numbers are verified and compliant. The process has three parts:
Brand registration — Twilio verifies your business identity.
Campaign registration — Twilio reviews how you plan to use messaging.
Phone number assignment — Once approved, Spara provisions a phone number for your text agent.
Your Spara CSM handles the registration on your behalf, but you'll need to provide the information below.
The registration and approval process typically takes 3–7 business days depending on Twilio and carrier review times. Plan accordingly when scheduling your text agent launch.
What you need to provide
Send the following information to your Spara CSM to begin the registration process.
1. Campaign description
A clear explanation of how your organization will use Spara to send text messages. This is reviewed by Twilio and mobile carriers to ensure compliance.
Your description should cover:
Who receives texts — e.g., inbound leads who submit a form on your website, existing customers who opt in to text communication
What texts contain — e.g., follow-up messages encouraging leads to schedule a meeting, answers to product questions, appointment confirmations
How contacts opt in — e.g., by submitting a web form that includes SMS consent language, by texting your number first
Example campaign description:
We use Spara's AI text agent to engage inbound sales leads who opt in through our website contact form. Texts include follow-up messages encouraging leads to schedule a meeting, responses to product questions, and appointment confirmations. Contacts opt in by submitting a form that includes explicit SMS consent.
2. Terms of Service and Privacy Policy
Provide public URLs to:
Terms of Service — Must be publicly accessible on your website.
Privacy Policy — Must be publicly accessible on your website.
Both documents must include:
Explicit SMS opt-in language — A clear statement that users consent to receive text messages by taking a specific action (e.g., submitting a form, checking a box). The opt-in must not be buried in unrelated terms.
Message frequency disclosure — e.g., "Message frequency varies" or "You may receive up to X messages per month."
Opt-out instructions — e.g., "Reply STOP to unsubscribe from text messages at any time."
"Message and data rates may apply" — This standard carrier disclosure is required.
Contact information — A way for recipients to reach you with questions about your messaging program (email or phone number).
Your Terms of Service and Privacy Policy must not authorize the following use cases, which are prohibited by Twilio and mobile carriers:
Third-party or affiliate marketing messages
Messages on behalf of another company or brand
High-risk financial services (payday loans, debt collection)
Cannabis or CBD-related messaging
Gambling-related messaging
Messages containing links to age-gated content
If your documents include language that could be interpreted as authorizing these use cases, your campaign may be rejected.
Example opt-in language for your website form:
By submitting this form, you consent to receive automated text messages from [Your Company] at the phone number provided. Message frequency varies. Message and data rates may apply. Reply STOP to opt out at any time. View our [Privacy Policy] and [Terms of Service].
3. Sample text messages
Provide 3 example text messages that represent the types of texts your agent will send. These help Twilio and carriers understand your messaging content.
Examples:
Hi [First Name], thanks for reaching out! I'd love to help you learn more about [Product]. Do you have a few minutes to chat, or would you prefer to schedule a call? Reply STOP to opt out.
Hey [First Name], just following up on your inquiry about [Product]. We have availability this week if you'd like to set up a quick demo. Here's a link to book a time: [calendar link]. Reply STOP to opt out.
Hi [First Name], thanks for booking a demo with us! You're confirmed for [Date] at [Time]. We'll send a reminder before the call. Let me know if you have any questions. Reply STOP to opt out.
Every text message must include opt-out language (e.g., "Reply STOP to opt out"). Spara automatically appends this to outgoing messages if it is not already present in the message body.
After approval
Once your brand and campaign are approved by Twilio:
Your Spara CSM will provision a phone number and assign it to your organization.
Configure your text agent in the Agent Editor with instructions for how it should respond to incoming texts.
Build Workflows using the Send Text Step step to automate outgoing texts.
FAQ
How long does approval take? Typically 3–7 business days, depending on Twilio and carrier review times.
Can I use a toll-free number instead of a local number? Yes — toll-free numbers have a separate verification process. Ask your Spara CSM about toll-free options if you prefer a toll-free number.
What happens if my campaign is rejected? Your Spara CSM will share the rejection reason and help you update your campaign description or policy documents to address the issue. Most rejections are resolved by updating opt-in language or clarifying the campaign use case.
Do I need a separate campaign for each phone number? Not typically. A single campaign registration can cover multiple phone numbers as long as they are used for the same messaging purpose.
Last updated