Create and send a message template
Use this workflow when customer-facing copy should be reviewed once and reused safely. Drafting, publishing, and delivery remain separate actions.
Create an SMS template named “Order ready” for order updates. Its exact copy
should be “Hi {{customer_name}}, order {{order_number}} is ready for
pickup.” Declare both variables as required strings. Preview it for customer
Ama and order WEB-1042, let me approve the rendered message, publish it, then
send it to customer <CUSTOMER_ID>. Confirm creation, publication, and
delivery separately.
The agent uses create_message_template to create a draft, then preview_message_template with representative values. Only after you approve the rendered copy does it use publish_message_template. send_customer_template renders the published template again and shows the exact message before making one delivery attempt.
Sample response
Published template sent
The reviewed published version was sent once to the saved customer by SMS.
- Template
- Order ready tmpl_example_ready
- Channel
- SMS
- Published version
- 1
- Delivery
- Initialized chime_example_ready
| Step | Reviewed result |
|---|---|
| Draft | Created with 2 required string variables |
| Preview | Hi Ama, order WEB-1042 is ready for pickup. |
| Publish | Version 1 published |
| Send | One SMS initialized for cus_example_01 |
Illustrative values. The exact presentation depends on the MCP client.
An updated template becomes a new draft. If it differs from the published version, the send tool refuses delivery until that draft is previewed and published. The tool accepts a saved customer ID, not a raw phone number, and cannot broadcast or schedule messages.