Global Clinic ConnectGuides
← All screen guides
CRMAvailable

Templates

Message, WhatsApp, and prescription templates in one place, switched with the control at the top. Message templates hold reusable copy, WhatsApp templates are reviewed provider messages, and prescription templates control the final layout clinicians issue after a visit.

01

What you can do here

Switch between template types

The segmented control moves between message, WhatsApp, and prescription templates, and remembers the section you used last. The retired WhatsApp templates menu item now opens here.

Message templates: channel-aware

Mark a message template for email, SMS, WhatsApp, web chat, or any channel, and give it a category so the team finds the right one quickly. Email templates can carry a subject line. Search by name or wording and filter by channel to manage a long list.

Message templates: tokens and live preview

Drop tokens like {{first_name}}, {{name}}, {{email}}, {{phone}}, and {{clinic}} into the body, or click a token to insert it at the cursor. A live preview beside the editor fills the tokens with sample values as you type, so you see the finished message without sending anything. Unknown tokens are blanked so a raw placeholder never goes out.

WhatsApp templates: the builder

Choose the exact WhatsApp-supported language from the searchable catalog, then compose the parts WhatsApp understands: an optional header, the body, an optional footer, and up to ten buttons. A phone-frame preview shows exactly what the patient receives. Each variable needs a sample for review, a fallback for missing values, and optionally the contact field it auto-fills from.

WhatsApp templates: review lifecycle

Drafts are yours to edit. Submitting sends the template to WhatsApp and locks it while in review. Approved templates become sendable but can no longer be edited, so duplicate one as a draft to change the copy. The checks panel flags problems before you submit, and a rejection shows WhatsApp's reason.

Prescription templates: final layouts

Preview the code-backed prescription layouts and choose your default for the active clinic. The preference follows you across devices, and you can still choose another layout for one prescription. Templates format the final patient copy; they never fill clinical dosage or directions.

02

Follow these steps

Create a message template

  1. Select New template, pick a channel and category, and write the body with tokens.
  2. Watch the live preview fill the tokens with sample values as you type.
  3. Save it, and disable a template later to retire it without deleting its history.

Create and submit a WhatsApp template

  1. Switch to WhatsApp templates, select New template, and name it in lowercase with underscores.
  2. Choose the language variant that exactly matches the template copy.
  3. Write the body, declare each variable with a sample and fallback, and clear the checks panel.
  4. Confirm the phone-frame preview, then Submit for review and track approval in the status column.

Choose a prescription default

  1. Switch to Prescription templates and select a layout to preview it.
  2. Choose Make my default to use it automatically for this clinic.
  3. Review or change the layout again when issuing an individual prescription.
03

Helpful habits

  • Use tokens rather than typing names, so a message is always addressed correctly.
  • Keep transactional and marketing copy clearly named; consent rules differ by message type.
  • For WhatsApp, pick the honest category and never put medical details in template copy, which WhatsApp sees during review.
  • Give every WhatsApp variable a realistic sample, since vague samples cause rejections.
04

Tips

  • Only admins can create or edit templates; everyone with chat access can read and use them.
  • The message-template preview uses sample values; the contact-filled render happens when a message is prepared to send.
  • WhatsApp template names use lowercase letters, numbers, and underscores only.
  • Approved WhatsApp templates appear in the Conversations composer once a thread's reply window closes.
Next