Messaging

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.

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.

GET/api/customer/templates

List templates in the current workspace.

POST/api/customer/templates

Create a template.

Create template

json

{
  "name": "Appointment reminder",
  "content": "Hi {{display_name}}, your appointment is tomorrow at {{time}}.",
  "source_system": "appointments"
}

POST/api/customer/templates/{template_id}/test-send

Send 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.

Next steps

Quickstart

A practical path from empty workspace to a working server-side integration.

Authentication and access

HookMessage separates customer API keys, dashboard sessions, and internal platform access.

Workspaces

A workspace is the tenant boundary for every customer resource.

Senders and sessions

A sender is the WhatsApp number used to deliver messages for a workspace.