Last updated: 16 April 2026
Templates and snippets help you send consistent, professional messages without typing the same content repeatedly. Templates are full pre-written messages; snippets are shorter reusable text blocks you can insert while composing.
Open Communications > Message Templates or Communications > Message Snippets from the configuration sidebar.
A template is a complete message with a subject line and body, ready to use when composing an email or SMS.
Templates support merge fields that are replaced with real data when the message is sent. Common merge fields include:
| Merge Field | Replaced With |
|---|---|
{{patient.first_name}} |
Patient's first name |
{{patient.last_name}} |
Patient's last name |
{{appointment.start_time}} |
Appointment date and time |
{{organization.name}} |
Your practice name |
Merge fields are automatically populated from the patient and appointment context when the template is used.
When composing a message, click the template selector to browse available templates. Select one to populate the subject and body. You can then edit the content before sending.
Jump includes built-in system templates for common scenarios. These cannot be edited directly, but you can duplicate them to create your own version.
Snippets are shorter pieces of reusable text -- a paragraph, a sentence, or a standard sign-off. They are designed for quick insertion while you are composing a message.
While composing a message, type # followed by the snippet name, or use the / command menu to browse and insert snippets. The snippet text is inserted at your cursor position.
You can:
Tip: Create templates for your most common messages -- appointment reminders, normal result notifications, and follow-up requests. This saves time and ensures patients receive consistent, well-written communications.
appointment.clinician_name) now resolve correctly in the message composer, and the merge-field overlay no longer closes unexpectedly while you are entering a value.{{user_signature}}) — you can now include {{user_signature}} in a template body. When inserted, it resolves to the signature configured on your user profile. Templates that don't include it no longer get a signature silently appended.