Twilio Content Template Builder and RCS Campaigns
Twilio's builder creates RCS and WhatsApp templates in your Twilio account. RCS Campaigns is a campaign app for marketing teams that can send through that same account. Here is what each one does, taken from the official docs.
Twilio docs checked November 10, 2026. Twilio updates its docs often, so check the linked page before you rely on a detail.
In short
- Twilio's Content Template Builder is where templates are made and managed in a Twilio account: a no-code Console UI built on the Content API, for SMS, MMS, RCS, WhatsApp, and Facebook Messenger (Content Template Builder overview).
- RCS Campaigns is a campaign app for marketing teams: ready-made templates and flows, audiences, sending and scheduling, approvals, analytics, and reports.
- They work together. RCS Campaigns submits templates to Twilio, and on Pro you can connect your own Twilio account so templates are submitted from it and messages leave from a number it holds (Connect your own Twilio account).
What Twilio's Content Template Builder does
Twilio describes the Content Template Builder as a product that “lets you create both templated messages and rich-content messages.” It is a graphical interface on top of the Content API, and templates created in either one show up in the other (overview). You send the templates with the Programmable Messaging API, Studio, or Conversations, and Twilio says they are also available in Engage (Content Template Builder).
In the Console you give a template a name and a language, pick a content type, and add variables. A template can hold up to 100 variables. Samples are required for templates with media and for templates that need WhatsApp approval (Create templates). One template can carry several content types: Twilio sends the most complex one the channel supports, so a template with text and quick replies can send buttons on WhatsApp and plain text over SMS (Content types overview, overview).
Content types and RCS
Twilio's channel table lists four content types for RCS. The quick-reply and call-to-action types are listed for WhatsApp and Facebook Messenger, not RCS (Content types overview).
| Content type | RCS | Notes | |
|---|---|---|---|
| twilio/text | Yes | Yes | Plain text. Also SMS and Facebook Messenger. |
| twilio/media | Yes | Yes | Images, video, and documents. Also MMS and Facebook Messenger. |
| twilio/card | Yes | Yes | Title, body, media, and buttons. On RCS the buttons can be quick reply, URL, or phone number. With more than four buttons, the first four appear in the rich card and the rest in a chip list, which holds up to 11 (twilio/card). |
| twilio/carousel | Yes | Yes | A horizontally scrolling set of cards, each with media and one or two buttons. Twilio notes that carousels sent over RCS don't support body text (twilio/carousel). |
| twilio/quick-reply | Not listed | Yes | Up to ten quick-reply buttons, documented for WhatsApp and Facebook Messenger (twilio/quick-reply). On RCS, quick replies go inside a card or carousel. |
| twilio/call-to-action | Not listed | Yes | URL, phone, and other buttons, documented for WhatsApp and Facebook Messenger (twilio/call-to-action). On RCS, URL and phone buttons go inside a card or carousel. |
Twilio also lists WhatsApp-only types such as twilio/list-picker, twilio/catalog, twilio/flows, and whatsapp/authentication (Content types overview).
Approval
WhatsApp: “Save and submit for WhatsApp approval” creates the template, assigns an HX SID, and submits it for review with the category you choose. Twilio says Meta typically processes approvals within an hour, though some take up to one business day (Create templates). Statuses run from Unsubmitted, Received, and Pending to Approved, Rejected, Paused, or Disabled (Content types overview).
RCS: Twilio's onboarding guide describes approval of the sender rather than of each template. You can test with phone numbers added as test devices, but before you message anyone else, carriers must approve the RCS Sender. The guide says all countries require Google RCS registration, and to “allow four to six weeks or longer if you plan to launch in multiple regions” (RCS onboarding).
SMS fallback on Twilio
When an RCS sender is in a Messaging Service's sender pool, Twilio tries RCS first. Messages that can't be delivered over RCS fall back to SMS or MMS, using another sender in the pool or one you name with the FallbackFrom parameter (Send an RCS message).
What RCS Campaigns adds for a marketing team
The builder covers templates. A marketing team running campaigns also needs something to start from, a list to send to, a way to send and schedule, and numbers afterwards. That is the part RCS Campaigns covers.
A template library to start from
500+ ready-to-use templates across 80+ categories. In the app, Marketplace lets you preview a ready-made template for your industry and clone it, and Studio lets you build your own with text, images, buttons, and cards (Your first campaign).
Industry conversation flows
100+ multi-step conversation flows, such as check-in, bookings, reminders, claims, and renewals, each shown as the full two-way thread.
Audiences
Import contacts from a CSV or JSON file. Every number gets a reachability score at import, a tags column becomes tags you can segment on, and a STOP reply opts a contact out across your whole organization (Create an audience).
Campaign sending
A wizard walks through name, template, audiences, schedule, and review, and warns you if a contact is missing data the template needs. Send now, send a trial batch first, or schedule for later. Members save drafts and Admins send (Send or schedule a campaign).
Approvals
Pick a category and press Submit to Twilio in the editor; Studio lists every template's status (Submit a template). Agencies can also ask a client to sign off, and the campaign can't send until they do (Approve a campaign).
Analytics and reports
A dashboard per channel (WhatsApp or RCS) with the funnel from submitted to sent, delivered, read, and failed, with provider declines split from real failures (Analytics dashboard). Campaign reports add replies grouped by topic, an AI-written summary, and a spreadsheet of every message (Campaign report).
Replies
Replies land in the Inbox. On Pro, an AI assistant grounded in your own knowledge base can answer them and hand off to a person when a conversation gets complex.
SMS fallback
On channels that support it, a message that can't be delivered as a rich message falls back to SMS automatically. WhatsApp has no SMS fallback (Send or schedule a campaign, Message not delivered).
Side by side
| Topic | Twilio Content Template Builder | RCS Campaigns |
|---|---|---|
| What it is | A template tool: a no-code Console UI built on the Content API | A campaign app for marketing teams that sends through providers, Twilio included |
| Channels | SMS, MMS, RCS, WhatsApp, and Facebook Messenger | RCS and WhatsApp campaigns, with SMS fallback where the channel supports it |
| Starting point | A new template: name, language, and content type | 500+ ready-made templates, 100+ conversation flows, or your own in Studio |
| Rich RCS content | twilio/text, twilio/media, twilio/card, and twilio/carousel | Templates with text, images, buttons, and cards |
| Personalization | Up to 100 variables per template, filled in at send time | Contact fields from your audience imports |
| Approval | Submit for WhatsApp approval from the builder; carriers approve the RCS sender | Submit to Twilio from the editor; optional client sign-off for agencies |
| Audiences | Not covered by the builder | CSV or JSON import, reachability scores, tags, and organization-wide opt-outs |
| Sending | Programmable Messaging API, Studio, or Conversations; also available in Engage | Campaign wizard: send now, send a trial batch, or schedule |
| Reporting | Not covered by the builder | Analytics dashboard per channel and saved campaign reports |
| Who works in it | Teams working in the Twilio Console or with Twilio's APIs | Marketing and ops teams, with no code required |
“Not covered by the builder” means the Content Template Builder docs don't cover it. Twilio has other products, so check with Twilio for what fits your account.
Using both together
You don't have to pick one. RCS Campaigns sends through Twilio, and its template editor's button reads Submit to Twilio (Submit a template). On the Pro plan, an Admin can connect your own Twilio account with its Account SID, Auth Token, an API key and secret, the Messaging Service SID that owns your sender, and an RCS sender id if you send RCS. After that, “your templates are then submitted from that account, and your messages leave from a number it holds” (Connect your own Twilio account).
Per-message sending charges come from the provider you connect, separate from your RCS Campaigns plan (see pricing).
Which one to use
Use Twilio's builder directly if…
- Your developers send from your own code, Twilio Studio, or Conversations, and you only need the templates.
- You already have your own tools for contact lists, scheduling, and reporting, and want templates that plug into them.
- You want to set Content API fields yourself, such as RCS card orientation or which buttons go in a chip list.
- You need Facebook Messenger or plain SMS campaigns. The RCS Campaigns help center covers RCS and WhatsApp campaigns, with SMS as a fallback.
Use RCS Campaigns if…
- Your marketing team wants to start from ready-made templates and conversation flows instead of a blank template.
- You want audiences, scheduling, approvals, and reports in one app, without writing code.
- You already use Twilio: on Pro, connect your own account so templates are submitted from it and messages leave from your number.
- You run campaigns for clients and need their sign-off before a campaign sends.
FAQ
Does RCS Campaigns replace Twilio's Content Template Builder?
No. They do different jobs. Twilio's Content Template Builder creates and manages message templates in a Twilio account, in the Console or through the Content API. RCS Campaigns is a campaign app for marketing teams: ready-made templates, audiences, sending and scheduling, approvals, and reports. Its editor submits templates to Twilio, and on the Pro plan you can connect your own Twilio account so templates are submitted from that account and messages leave from a number it holds.
Can I send Twilio's quick-reply and call-to-action templates over RCS?
Not as separate content types. Twilio's docs list twilio/quick-reply and twilio/call-to-action for WhatsApp and Facebook Messenger. On RCS, quick-reply, URL, and phone-number buttons go inside a twilio/card or a twilio/carousel. Twilio's twilio/card page says that with more than four buttons, the first four appear in the rich card and the rest in a chip list, and that a chip list holds up to 11 buttons. Each carousel needs at least one button and no more than two.
Do RCS templates on Twilio need approval?
The approval step in Twilio's Content Template Builder is WhatsApp's review: you pick a category and submit, and Twilio says Meta typically processes approvals within an hour, though some take up to one business day. For RCS, Twilio's onboarding guide describes approval of the sender: carriers must approve the RCS Sender before you can message phone numbers that are not test devices, and every country requires Google RCS registration.
Is there SMS fallback when RCS can't be delivered?
On Twilio, when an RCS sender is in a Messaging Service's sender pool, messages that can't be delivered over RCS fall back to SMS or MMS using other senders in that pool. The RCS Campaigns help center says that on channels that support it, a message that cannot be delivered as a rich message falls back to SMS automatically, and that WhatsApp has no SMS fallback.
Sources
Twilio docs checked November 10, 2026.
- Content Template Builder (Twilio docs)
- Content Template Builder overview (Twilio docs)
- Content types overview (Twilio docs)
- Create templates with the Content Template Builder (Twilio docs)
- twilio/card (Twilio docs)
- twilio/carousel (Twilio docs)
- twilio/quick-reply (Twilio docs)
- twilio/call-to-action (Twilio docs)
- Send an RCS message (Twilio docs)
- RCS onboarding (Twilio docs)
- Connect your own Twilio account (RCS Campaigns help)
- Your first campaign in 15 minutes (RCS Campaigns help)
- Submit a template for approval (RCS Campaigns help)
- Create an audience and import contacts (RCS Campaigns help)
- Send or schedule a campaign (RCS Campaigns help)
- Approve a campaign (RCS Campaigns help)
- Read the Analytics dashboard (RCS Campaigns help)
- Generate and read a campaign report (RCS Campaigns help)
- Message not delivered (RCS Campaigns help)
Already on Twilio? Start from a ready-made template and send through your own account.