Caveats
API key secrets are shown once
Section titled “API key secrets are shown once”Twilio shows the API Key Secret when the key is created. If you lose it before saving Twilio in TracsConnect, create a new key.
Sender setup must be complete in Twilio
Section titled “Sender setup must be complete in Twilio”The sender phone number or messaging service must be ready in Twilio before TracsConnect can send customer texts. Registration, compliance, and number ownership all stay in Twilio.
Messaging service behavior is controlled in Twilio
Section titled “Messaging service behavior is controlled in Twilio”If you enter a Messaging Service SID, Twilio’s messaging service settings decide how senders are selected and how fallback behaves. Review those settings in Twilio before relying on them for customer communication.
RCS requires a Messaging Service SID
Section titled “RCS requires a Messaging Service SID”Twilio routes RCS messaging through a Messaging Service, not a plain phone number. If you want TracsConnect to send RCS messages (richer messages with branding and read receipts), paste a Messaging Service SID into the setup window. Without it, TracsConnect sends standard SMS only.
Twilio handles the fallback automatically — if a customer’s device does not support RCS, the message goes out as SMS instead.
Usage is billed by Twilio
Section titled “Usage is billed by Twilio”Messages sent through TracsConnect use your Twilio account. Review Twilio billing, rate limits, and compliance requirements before expanding usage.