Hi {{ first_name | default("there") }},
Your quote {{ quotes[0].name }} for {{ quotes[0].total_incl_tax | number_format(2) }} is attached.
It's valid until {{ quotes[0].valid_until | date("d M Y") }}.
``` The "current record" is whatever the template is being rendered against: the contact you clicked **Compose** from, the lead a workflow is running on, etc. Related records are arrays (`contacts[0]`, `accounts[0]`, `quotes[0]`, …). See [Flexie Scripting → Language basics](https://flexie.io/resources/flexie-scripting/language-basics) for the full rules. ### Tracking: opens and clicks If **Track all links** is on: * Every link in the email is rewritten to go through Flexie's click-tracker first, then on to the original URL. * A tiny invisible image is inserted in the HTML for **open tracking**. Each click is logged on the recipient's record; opens become the trigger for the [Email opened workflow trigger](https://flexie.io/resources/inbox/email#email-opened). Open any email template to see its per-message **Stats** (opens, clicks, delivery counts) and its **Clicks** breakdown (which links were clicked, by whom, when). ### A/B testing For broadcast-type emails, the template form has a **Variant** tab. You can: * Define one or more variant subjects/bodies/HTML. * Set the split weight (e.g. A/B 50/50, or A/B/C/D). * Pick a winner by open-rate or click-rate after a chosen window. ### Personal signatures vs templates A user's email signature is part of their **mailbox account** profile (set on the mailbox itself), not a template. Signatures are appended to the body of every outbound email; templates are inserted into the body. Both work together: your template provides the message; your signature finishes it. ## SMS templates ### Creating an SMS template The form fields: | Field | What it does | | --------------- | ------------------------------------------------------------------ | | **Name** | Internal label, shown in the template picker. | | **Text** | The message body, accepts variables. | | **Record type** | Which record type variables resolve against (lead, contact, etc.). | | **Category** | Optional folder for grouping templates. | | **Owner** | Who created it (visible in the list). | | **Access list** | Who can use this template. | ### Variables: same rules as email ``` Hi {{ first_name }}, your appointment is on {{ next_appointment | date("D d M, H:i") }} at {{ accounts[0].address }}. Reply YES to confirm, NO to reschedule. ``` Be mindful of length. The compose form shows live character plus segment counts; templates with long variable expansions (e.g. a full street address) can push a one-segment template into three. Test the template against a real customer before saving. ### SMS templates feed WhatsApp compose Both the SMS compose form and the WhatsApp compose form share the **SMS template** picker. A "We received your invoice" template you wrote for SMS is also available when replying on WhatsApp. There's no separate "WhatsApp template" library today; if you need a WhatsApp-only template, either prefix it (`[WA]`) or limit its access list to people who only work in WhatsApp. > The other direction also matters: WhatsApp lets you attach media, while SMS can only attach a link. If your template assumes an image is attached, that works in WhatsApp but not in SMS. Keep the template's text self-contained, and add media on the compose form for WhatsApp. ## Using a template ### From compose In the email or SMS compose form, **Templates** opens a picker. You'll see templates filtered by: * the current record type (only templates whose **Record type** matches), * your access (templates you're allowed to use), * your language preference (when the template has a **Language** set). Click a template → its content is inserted into the compose body (replacing or appending depending on the picker). Variables aren't expanded until **Send**, that way you can edit the populated text first. ### From a workflow The **Send email** workflow action has a **Template** picker, pick one, and the action uses its subject, body, from/reply-to addresses. The **Send SMS** and **Send WhatsApp** actions accept the SMS template via the same picker. You can still override individual fields (subject, body, recipient) on the action; the template gives you a starting point. ## Gotchas * **A template set to the wrong record type won't show up.** If your template's **Record type** is _Lead_ and you're composing from a _Contact_'s page, it won't appear in the picker. Either change it to the right record type, or duplicate it. * **Variables on send-from-inbox.** When you compose from the inbox (without picking a customer first), variables that reference customer fields render as blanks. Compose from a customer's page if you want variables to resolve. * **The "language" field is opt-in.** Setting it filters the picker for users whose preference matches. Leaving it blank means the template shows up for everyone, usually what you want. * **CC/BCC at the template level.** These apply to _every_ send from the template. Don't put a personal address here; use the **Reply-to** field for a shared support inbox instead. * **Tracking only works for HTML sends.** A plain-text-only email doesn't carry click trackers or open pixels. ## Next * [Workflows & automation](https://flexie.io/resources/inbox/workflows-and-automation): using templates from the send-message workflow actions. * [Flexie Scripting → Language basics](https://flexie.io/resources/flexie-scripting/language-basics): the variables you can use inside the template body.