Messaging (SMS)
Send SMS to contacts on one of two lanes. Bring your own carrier - your Twilio, Telnyx or Plivo account, or a custom HTTP provider - and your credentials stay encrypted and are never shown back. Or text from a WorkBOS number on our carrier account, which needs a one-off carrier registration first: see Texting registration below, because in the United States that registration is not optional and volume texting will not start without it. Either way every message is logged, consent is respected, and a monthly spend cap protects you.
- 1
1. Connect a provider
People > Messaging. Pick Twilio / Telnyx / Plivo / Custom, paste the account id + auth token and your from-number, set a monthly spend cap, and enable it. Leave the token blank later to keep the saved one.
- 2
2. Send
Type a destination number + message and Send. It queues and the dispatcher delivers it through your provider in seconds; the result (sent/failed) shows in the log.
- 3
3. Consent & caps
Numbers on the suppression list are never messaged. The monthly USD cap blocks sends once reached. Both are enforced server-side.
Security: provider secrets live in a table no client can read - they are reachable only by the secure server dispatcher. Configuration is owner/admin only; sending is staff-gated; the public never touches it.
Send, reply to and read every SMS conversation in one place under Communication > SMS - a two-way conversation view per contact, with New message and provider setup (Configure) on the same page. Unread inbound replies raise a count badge on the SMS nav item and a red dot on each conversation; opening a conversation marks it read. Booking + appointment reminders (email + SMS) send automatically. To receive replies, point your provider inbound-SMS webhook at the sms-inbound function URL. Automations can send an SMS as an action, and drip sequences can carry SMS steps.