Message templates and variables

Text templates (CRUD)

Fulreach persists account-scoped text templates (name, body, language en|fr|es|it server validation). Create/list/update/delete via API routes the web app calls with accountId.

Templates help you standardise intros and follow-ups; keep them short and human.

Variable interpolation in automation

Sequence workers render template bodies using prospect fields (examples from domain integration: {first_name}, {last_name}, headline tokens). Both {var} and {{var}} styles appear historically—consistency helps reduce missed merges.

Missing data typically substitutes empty string rather than hard failing step.

Audio / video template tabs

The product UI may show multiple template modes; only text template CRUD is confirmed wired to backend storage in current internal spec audit—treat non-text tabs as experimental unless your tenant release notes state otherwise.

Best practices

• Draft for one person reading on mobile—short lines, clear CTA.
• Avoid hyper-personalisation tokens you don’t consistently enrich.
• Localise (language field) when operating multi-region seats.