A client texts you asking about their event, and you want to reply from Check Cherry instead of your personal phone. Text messaging through Twilio or Quo keeps all your communication in one place.
Why use text messaging?
Text messages have much higher open rates than email. They're great for time-sensitive communication like day-of reminders, payment confirmations, and quick follow-ups. Many clients prefer a text over an email, especially for short updates.
Connect a provider
Start by navigating to Integrations, then follow the steps for whichever provider you're using.
To Connect Twilio
Finding your Twilio credentials
Your Account SID and Auth Token are on the main dashboard of your Twilio Console. To find your Phone Number SID:
Set up webhooks to receive Twilio replies
To see incoming replies from clients inside Check Cherry, configure a messaging webhook on your Twilio phone number. In your Twilio phone number settings:
- Under A Message Comes In, choose Webhook.
- Set the URL to
https://yourcompanyurl.checkcherry.com/webhooks/twilio/message_received— replaceyourcompanyurlwith your actual Check Cherry subdomain. - Set the method to
HTTP POST.
To Connect Quo
Your Quo API key is available in your Quo dashboard under account or developer settings.
Set up webhooks to receive Quo replies
To receive incoming replies from clients in Check Cherry, configure an inbound webhook in your Quo account settings:
- Log in to your Quo dashboard and go to Settings or Developer settings.
- Find the Inbound Webhook or Message Received URL field.
- Set the URL to
https://yourcompanyurl.checkcherry.com/webhooks/quo/message_received— replaceyourcompanyurlwith your actual Check Cherry subdomain. - Save your changes in Quo.
Quiet hours
Quiet hours prevent automated text messages from going out during nights and weekends, so clients don't receive Check Cherry notifications at odd hours. Any message that would have sent during a quiet period is held and delivered once quiet hours end.
A2P 10DLC registration (required for US numbers)
If you send text messages to US phone numbers using Twilio, carriers require you to register for A2P 10DLC (Application-to-Person 10-Digit Long Code). Without this registration, your messages will not be delivered.
A2P 10DLC is a carrier-mandated system that verifies your business identity and the type of messages you send. It provides better delivery rates and lower filtering risk than unregistered numbers. Registration is done through the Twilio Console — follow Twilio's guide: How do I register to use A2P 10DLC messaging?
Prepare your business information
- Legal business name: must match exactly with IRS or Secretary of State records.
- EIN / Tax ID: use your company's EIN, not your SSN (unless you're a sole proprietorship).
- Business type: accurately select LLC, Corporation, Sole Proprietor, etc.
- Website: provide a live, professional-looking site. Carriers often check it.
- Contact info: make sure your phone number and email are valid and monitored.
Describe your campaign clearly
- Use case: describe exactly what you'll send — for example: 'Booking confirmations, payment reminders, and customer service updates for event services.'
- Message samples: write samples that reflect real-world usage, including opt-out language ('Reply STOP to unsubscribe').
- Opt-in process: document how clients consent to receive texts (booking flow, contract checkbox, website forms, etc.).
Follow compliance rules
- Always provide clear instructions for STOP and HELP responses.
- Link to your Terms of Service and Privacy Policy where clients opt in.
- Avoid high-risk wording like 'Free $$$' or 'click here' in your messages.
Common reasons for rejection
- Using a DBA name instead of the official legal entity name.
- Submitting placeholder or non-functional websites.
- Copy/pasting generic message samples that don't reflect your real use cases.
- Forgetting to explain your opt-in process.
Troubleshooting undelivered messages
If your text messages show as undelivered, check your Twilio Console for error details. Go to the Monitor tab in Twilio and look at the Error Logs to see what went wrong.
Common causes include:
- Missing A2P 10DLC registration (messages to US numbers will be blocked).
- Invalid or disconnected recipient phone numbers.
- Twilio account balance is depleted.
- Message content flagged by carrier filters.
You can look up specific error codes in Twilio's error code reference to understand what each code means and how to resolve it.
Getting help
For questions about your Check Cherry integration, reach out through the chat bubble in the lower right corner of the app.
For provider-specific issues like account setup, registration, or billing, visit the Twilio Help Center or the Quo support site.