Integrating with Textlocal (Legacy)
Textlocal is no longer available to new customers
As of April 2025, following their acquisition by WebEx, Textlocal are no longer accepting new customers. It is also no longer possible to buy Textlocal credits.
Existing Textlocal customers can continue to use their integrated account to send SMS messages through ChurchSuite until Textlocal credits have been used up, or WebEx communicate the closure of your TextLocal account - expected Q4 2025. If you choose to migrate from Textlocal to WebEx, you will no longer be able to send SMS messages through ChurchSuite using the Textlocal integration - there is no WebEx integration.
As an alternative to Textlocal, integrations with Twilio and BulkSMS are provided - see our related articles for more information. We recommend that customers using the Textlocal integration move to using one of these alternative providers as soon as their Textlocal credits are used and before WebEx close the Textlocal API. When you are ready, Reset the TextLocal integration to remove it from your ChurchSuite account and to begin sending messages using your chosen alternative service provider.
Which SMS provider is for me?
We provide integrations with two SMS service providers - BulkSMS and Twilio. Here's a brief comparison to help you decide which is best for you.
| Service | BulkSMS | Twilio |
| Scheduled SMS support | ✅
|
❌
|
| View SMS replies in the ChurchSuite communication logs | ❌
|
✅ |
| Use a personal mobile number as the Sender ID, and receive replies to that number* | ✅
|
❌
|
| Register a church, organisation or personal name as an alphanumeric Sender ID for broadcast messages where replies are not needed* | ✅
|
❌
|
| Specify an alphanumeric SenderID when composing a message (no pre-registration)* | ❌
|
✅ |
| Pricing benefits for organisations supporting communities or causes/non-profits* | ✅ | ✅ |
*in supported countries