Skip to main content
Use Phone numbers as your shared number inventory. Settings → Channels → SMS & RCS turns an eligible number into a conversation channel. The same number can handle voice and SMS with different assistants.

Set up your number

  1. Open Settings → Channels → SMS & RCS. Buy an SMS number or import an existing one through Phone numbers.
  2. Choose Set up SMS, name the channel and select an assistant.
  3. Save to connect incoming SMS. Automatic replies start off; enable Allow outbound SMS and AI auto-replies when ready.
  4. Set the response delay, inactivity timeout and optional conversation-ended webhook.
Platform numbers and imported Twilio BYOC numbers are supported when the number has SMS capability. A SIP trunk alone does not provide SMS. Some destinations require carrier registration; see SMS registration. For a BYOC Messaging Service, let incoming messages use the phone number’s webhook before connecting. Disabling the SMS channel preserves the number and voice routing. Removing or releasing the phone number disables its SMS channel. Saving an SMS channel applies its settings and the Allow outbound SMS choice together. Editing an already active channel does not reconnect it to the carrier. If another editor changes the channel, reload its settings before saving again.

Replies and History

Open History, filter by SMS, and select a conversation. You can inspect messages, assistant actions, analysis, delivery status and charged credits, pause the assistant and reply manually. An unconfirmed delivery must be checked before retrying. SMS-only channel replies fit one segment: 160 GSM-7 units or 70 UTF-16 units for Unicode. GSM-7 extension symbols such as ^, {, } and € count as two units; most emoji use two UTF-16 units. The composer shows the applicable limit. RCS-enabled delivery uses its own text and content validation. Long assistant drafts are never silently truncated. SMS uses the existing SMS credit rate, including any applicable carrier component. There is no additional general chat-message charge. An estimated charge can change once the final carrier price arrives. Incoming STOP messages suppress further sending; restarting depends on the carrier’s supported opt-in flow.

Customer memory

In Settings → Data → Memory, enable SMS for the workspace. In the assistant’s Memory settings, also select SMS for reading and writing. New assistants require this explicit selection. SMS uses the authenticated sender’s phone number to recognize the same contact across phone calls and text conversations. Workspace and assistant scope, consent, retention and selected memory categories still apply. SMS memory is currently available in root workspaces, including a reseller’s own workspace; reseller customer workspaces can use SMS conversations without SMS memory. See Customer memory.

API, MCP and command line

Use POST /api/v1/messaging-connectors or MCP create_messaging_connector to connect the number. Use PATCH /api/v1/messaging-connectors/{id} or update_messaging_connector to enable, pause or configure it. List with GET /api/v1/messaging-connectors?platform=sms or list_messaging_connectors.
The SDK supports the same update. After reading the channel, pass its last update time to detect concurrent edits:
When importing a Twilio number, select Enable SMS conversations to continue directly to SMS setup. This is optional and does not turn on automatic replies.

SMS charges

Outgoing SMS includes a sending fee and delivery usage with the applicable markup. Incoming SMS on platform numbers is charged in credits for its actual network cost plus the receiving markup, even when AI replies are paused or no SMS channel is connected. Final charges may arrive later; repeated delivery notifications do not create duplicate charges. For BYOC numbers, your carrier bills delivery and receipt directly. General chat-message fees do not apply to SMS. Review the rates in Usage, through GET /api/v1/usage/rates, MCP get_usage_rates, or famulor get-workspace-usage-rates.

Company senders and RCS

For editable consent examples and practical handset recording steps, see the RCS company sender setup guide. RCS is an optional addition to the SMS channel. Existing SMS channels keep working. Settings → Channels → SMS & RCS has two views: SMS lists your numbers, RCS lists your company names. In RCS, choose Add company name to apply for a branded sender without purchasing another number. Each company name has Company profile for the application and Settings for its connection. To send RCS from a number, choose an approved company sender in that number’s Settings. A company sender can receive RCS replies. A phone number is required for SMS delivery and SMS fallback, but not for an RCS-only company sender. Campaigns can send under a company name too: choose it as the sender of an SMS campaign, or of an SMS & RCS step in a sequence. Complete Company, Branding, Consent and Verification with truthful business details, support contacts, your website, privacy policy, terms, at least two message examples, a demonstration video and the actual opt-in and opt-out process. Upload a square 224 × 224 PNG/JPEG logo (up to 50,000 bytes) and a 1440 × 448 banner (up to 200,000 bytes). These brand images become publicly accessible to display your company profile. For a new application, saved workspace name and website and your personal name and email are editable suggestions. Review the representative’s authority; no legal identity or consent is inferred. Existing applications keep their saved values. Website fields accept a public domain and add HTTPS; the phone picker stores an international number. In Branding, choose, replace or remove images, or expand Use an image URL. The phone preview shows the current profile and first sample message; switch to SMS fallback to compare the plain-text appearance. The preview does not prove approval or delivery. Choose Review and book RCS and confirm the displayed credit amount. The standard setup is 500 credits once per company sender. Linking more eligible numbers to that sender does not repeat the setup charge. Message delivery and receipt are charged separately in credits. Check the current workspace quote before booking; booking pays for the application and does not guarantee approval. Saving a draft is free. The verification timeline shows application review, network review, requested corrections and approval. Approval alone is insufficient: sending becomes available after activation. Follow the correction guidance in the existing application instead of booking a duplicate. Choose the countries where your recipients use RCS. A new draft suggests your workspace country when it is open for setup. Existing drafts keep their saved selection. Countries awaiting setup availability are shown separately. Availability for an application does not guarantee every device or network can receive RCS. While the sender is in network review, its status is checked automatically. When it is approved for the first time, its RCS-only connections without a number turn on by themselves and the person who submitted the application receives an email. Reply settings stay as you saved them. After a later pause, switch the connection back on yourself. Under Message delivery, choose:
  • SMS only: keep using SMS, even when a company sender is attached.
  • RCS with SMS fallback: try RCS and use the linked eligible SMS number when RCS is unavailable. Rich content requires an explicit plain-text fallback message. A company sender without a fallback number cannot use this mode.
  • RCS only: use the company sender without falling back to SMS. An unsupported destination or unavailable sender returns an error.
Test before approval: while a booked company sender is in review, add up to five personal mobile numbers in the company name’s Settings under Test numbers. Your support team registers each number as a test device; accept the invitation on that phone. Messages between the company sender and these numbers then use RCS only, without SMS fallback. They reach the sender’s default connection and its assistant and are charged like other RCS messages. All other recipients stay blocked until approval. Workspace phone numbers cannot be test numbers. The assistant answers only when automatic replies are on for that connection. History keeps both transports under SMS and shows the actual delivery transport, status and credits. Recipient consent and STOP suppression apply to both. Do not retry an uncertain send with a new request key until its delivery state has been checked. RCS text of up to 160 UTF-8 bytes uses the basic text class; longer text and rich media use the single-message class. Accents and emoji can use several bytes. SMS fallback has its own GSM-7/Unicode segment count and may cost more than the RCS text. Actual network usage and later corrections are reflected in the final credits; a send estimate is not a guaranteed price.

RCS API, MCP, command line and SDK

Use the same SMS platform when creating or editing a messaging connector. List company senders to read availability and the current setup quote. Submission requires explicit acceptance of that quote. Scope requirements and workspace roles still apply.
RCS conversation text allows up to 1,600 Unicode characters. With SMS fallback, the complete fallback text can require several charged SMS segments. For plain-text messages, SMS fallback sends the same text. A separate fallback message is accepted only for rich cards, carousels or media. The send response includes the known transport and whether SMS fallback was used, when available; History remains the source for later delivery updates. To select which connection receives new incoming RCS contacts for a shared company sender, update that SMS connection with the incoming-default option. Existing conversations retain their connection. Read the company sender to check the selected connection.