Voice

SMS

Set up SMS on numbers from your own Twilio account, choose human or AI replies, and inspect receiving and routing through Copilot.

Octocom supports incoming SMS, replies from Help Desk agents and AI replies on numbers connected from your own Twilio account. Supported numbers can also carry MMS attachments. Octocom-provided purchased numbers are for calls and cannot be connected for SMS through custom Twilio tools.

Set up with Copilot

Ask: "Connect my Twilio number to this business for SMS handled by our agents." You need the Modify settings permission.

  1. Connect your custom account and list its numbers with create_twilio_account and list_twilio_phone_numbers. See Your Twilio account.
  2. Inspect the selected number with get_twilio_phone_number. Check SMS capability, current routing and any toll-free verification requirements.
  3. Use connect_twilio_phone_number with the business, explicit account ID, number SID and channels: ["sms"]. Leave voice out to preserve call routing. Use smsMode: "agent" for human replies or "bot" for AI replies. New configurations default to human agents.
  4. If a Messaging Service overrides the number's webhook, follow the service-specific instructions in Your Twilio account.
  5. Inspect again. Check sms.pointsToOctocom, sms.configuredInOctocom and sms.receivingEnabled. These confirm configuration, not delivery.

US/Canada messaging from US toll-free numbers needs approved toll-free verification. A number supporting SMS does not imply it is approved to send. The tools report verification when available; they do not submit registration. Other destinations and number types have their own provider requirements. See Twilio's toll-free verification guide.

Human or AI replies

In agent mode, incoming messages create or update an SMS conversation in the Help Desk for human agents. In bot mode, the AI handles the conversation using the business's configured behavior. Replies use the number the customer texted.

Use get_sms_settings to inspect the mode, connected numbers and enabled state. Use update_sms_settings to change mode or the complete disabledRecipientNumbers list. An empty list enables receiving on every connected number. Disabled numbers discard inbound messages before creating or updating a conversation.

In the dashboard, open Settings -> Voice & SMS -> SMS to inspect connected numbers, toggle receiving and manage blocked senders. Initial number connection and mode changes are available through Copilot/MCP or REST.

Bot-triggered outbound texts

For a bot to text a customer during another conversation, select a connected custom number with update_sms_settings and outboundPhoneNumber. This enables the bot's sendSms action. Setting the sender does not send a message. Configure the bot's workflow for when sending is appropriate.

Without your own Twilio number, ask Octocom to set up a bot sender for you, such as your brand name. Customers can't reply to a text sent from a name.

This action is separate from replying to an SMS thread. This setup does not add a bulk SMS campaign interface.

Texting customers from the Help Desk

Agents can text customers from connected numbers that receive texts, since that is where the reply arrives:

  • A new conversation: click + beside Help Desk and choose SMS. See Starting a new conversation.
  • A phone call conversation: choose Reply via SMS to text the caller, for example after a missed call. It goes from the number they called when that number can text. Their reply joins the same conversation. See Replying by text or email.

Troubleshooting

  • The number is in Twilio but absent from Octocom: list_twilio_phone_numbers is live account inventory; list_phone_numbers shows connected numbers. Connect it to a business.
  • The webhook is correct but messages do not appear: inspect effective routing, the local business mapping, receiving state and blocked senders. An application or Messaging Service can override the displayed number webhook.
  • Sending fails: inspect credentials, the selected sender, provider registration and Twilio's delivery errors. Changing receiving settings does not approve a sender with a carrier.
  • The business already uses Postscript or another account: the connection tool preserves that setup and refuses to replace it silently.
  • A credential rotation breaks receiving: Octocom uses the saved Auth Token to validate inbound webhook signatures. Update the saved token to match Twilio and re-test both directions.

The same settings are available through GET / PATCH /rest/v1/sms-settings?businessSlug=your-business. No inspection or configuration tool sends a test message automatically.

On this page