Skip to main content

​
RCS Templates Tab: Approval and Deliverability Per Template

The RCS channel page in the dashboard has three views behind one switcher: Messages, Templates, and Analytics. The Templates view is the per-template home — approval status, per-template deliverability, and the edit/delete actions — that the RCS channel page previously only exposed through the REST contract. This guide walks the tab end to end.

​
Where the tab sits

Open the dashboard and go to Messages → RCS. The Messages / Templates / Analytics switcher at the top of the page now includes a Templates value. The active view is synced to the ?tab= query parameter, so you can deep-link directly to the template roster with ?tab=templates — handy for linking row-level work from a runbook or chat.

​
Pick the agent first

Templates are registered against a specific RCS agent (bot), so the tab scopes to one agent at a time. If your tenant has more than one agent, use the agent picker at the top of the view to switch between them; the header shows the selected agent’s registration status (for example launched or pending launch) alongside a link into the Rich Card Studio. If no agent exists yet, the tab routes you to the RCS setup flow instead of showing an empty picker.

​
What each template row shows

Each template renders as a card with:
  • Approval badge — Approved, Pending review, Rejected, or Draft, with the carrier’s rejection_reason shown inline when a review failed.
  • Message type — whether the template is a rich card or a carousel.
  • Deliverability inline — Sent, Delivered, Read, and Taps counts pulled from the same template analytics aggregation the Analytics tab uses, so the two surfaces always agree. A template with no sends yet says so explicitly instead of showing zeros forever.

​
Actions per row

  • Edit in Rich Card Studio — opens the shipped Rich Card Studio builder on that template, replacing the old “dedicated editor coming soon” hint the create-template dialog used to show. The Studio is the same builder the tab’s header links to.
  • Delete — removes the template after a confirmation dialog. Deleting is destructive for live traffic: any campaign or flow still sending the template starts failing once it is removed from the carrier directory, so check campaign references before you confirm.

​
Approval lifecycle

A template starts as pending and must reach an approved status before a campaign can send it. The lifecycle detail that bites most teams: an update resets approval. Editing a template — through the Studio or a PUT /api/v1/rcs/bots/:id/templates/:name call — re-submits the definition and moves it back to pending. Publish template edits before a dependent campaign goes live, not while it is running, or the campaign sends against a definition that is back in review. This mirrors the lifecycle the RCS channel page Templates section documents; the tab just makes each template’s current state readable at a glance.

​
If the list fails to load

The tab renders explicit zero states — skeletons while loading, an error card on failure, and setup/Studio CTAs when there is nothing to show. The Retry button on the error state re-requests both the template roster and the parent agent roster together, so a failed agent list recovers fully instead of retrying only the templates call against a still-broken roster.
  • RCS channel page — message shapes, the template REST contract, and the template-analytics endpoint the tab visualizes.
  • RCS onboarding guide — brand, agent, verification, and launch; the path to reach-sizing before your first campaign.