Message templates
Create reusable message templates for dashboard and automation workflows.
Template fields
Templates store a name, content, optional source system, workspace ownership, and timestamps.
Template content supports placeholders such as `{{display_name}}`, `{{phone_number}}`, `{{email}}`, and metadata keys when rendered by template-aware workflows.
Templates are dashboard/customer-session resources. They are managed through `/api/customer/templates`, not through public `x-api-key` integration endpoints.
- Create: use the dashboard Templates page or the authenticated customer portal template route.
- Update: PATCH the template route.
- Archive/restore/delete: available through customer portal template routes.
- Preview/test-send: available through customer portal template routes.
Template API routes
Use these routes from the authenticated customer dashboard or trusted server-side customer portal code. They require the customer session for the workspace.
/api/customer/templatesList templates in the current workspace.
/api/customer/templatesCreate a template.
{
"name": "Appointment reminder",
"content": "Hi {{display_name}}, your appointment is tomorrow at {{time}}.",
"source_system": "appointments"
}/api/customer/templates/{template_id}/test-sendSend a template test through a workspace sender.
Recommended usage
Use templates for repeatable customer messages such as appointment reminders, payment notices, status updates, and support responses.
Keep dynamic values explicit and review template copy before attaching it to automations.
Need help?
Use Book Integration Help if you want setup help for OTP or automated customer messaging.
Continue building
Next steps
Start here
A plain-language map of Free Sandbox, paid sender modes, credentials, and the first successful request.
Free Sandbox quickstart
The shortest beginner path from a verified account to a queued Free Sandbox OTP.
Glossary
Understand workspaces, keys, senders, receivers, queue states, webhooks, and idempotency.
Authentication and access
HookMessage separates customer API keys, dashboard sessions, and internal platform access.