An order confirmation can reuse its wording while changing the order number for each recipient. That keeps the workflow consistent while the data changes.
What does a template contain?
A template contains fixed text, variable definitions and the message category, which classifies why you are sending the message. A destination can apply that content classification to its registration rules.
Each variable names a value that changes between sends, such as an order number. The template defines its accepted type, whether it is required and any constraint on its value.
Campaign content and templates combine reusable wording with recipient-specific values. Bird's template catalog includes system templates for authentication and transactional messages. Workspace templates let you publish your own text in multiple languages. Authoring is available through the template management API.
Read the variables before choosing a template. A familiar-looking preview does not establish that its required values match the data your application has.
Do SMS templates need approval?
Built-in templates are ready to send. Publishing a workspace template validates its text and variables. The published version becomes available immediately, without Meta approval. Destination rules can still require content registration.
These are separate processes. A provider's reusable message body does not itself establish compliance with a destination's rules.
For example, TRAI's guidance for senders requires registration of content templates for communications through registered sender identities in India. That requirement concerns the message structure, including fixed and variable parts.
Check the destination before choosing the sending workflow. Sender registration concerns the sending identity and can coexist with a content requirement.
How does Bird choose the category and sender?
The template supplies the category, the content classification for why you are sending the message. Built-in templates select a sender for the destination; workspace templates use the sender you provide.
A template send rejects text, category and media_urls alongside template. Omit from for a built-in template and supply it for a workspace template. The template-send contract documents these requirements.
Use a workspace template or free text when your application must choose a particular sender.
Inspect from and category in the response. Those fields tell you which sender and content classification Bird selected for that message.
How do I send a template in Bird?
Identify a published template and supply its variable values in the send's template object.
Use slug or id to identify it. Read GET /v1/sms/templates/{template_ref} for its live_version_id, then read GET /v1/sms/templates/{template_ref}/versions/{version_id} for its content and variable definitions.
Put values in parameters, keyed by variable name. Missing required values, undeclared keys or invalid formats return 422, so validate the values before releasing the send.
The serialized parameters object must fit within 16 KB. Bird rejects a request that exceeds that limit, so keep it to the template's declared values.
Choose language when needed. The template's language settings determine the default and any fallback, so inspect those settings instead of assuming every requested language exists.
Do templates change how SMS is billed?
The rendered text is counted like any other SMS body.
Insert the real values before estimating segments. A long order reference or a name outside the compact alphabet can increase the count.
A template reference is not a fixed price for every recipient. The response's segments.count reports the billable parts for that rendered message.
When should I choose a template?
Choose a catalog template when its body, variables and sender-selection behavior fit your workflow.
- Use a template when the supplied body matches the message and you have its required values.
- Publish a workspace template for reusable wording with your own sender, or use free text for an individual message.
- Apply the destination's registration requirements to either choice.
In short
Templates contain reusable text and variable definitions.
Choose a built-in template or use a published workspace template, then supply its required values.
Sender selection depends on the template scope.
Built-in templates use a sender selected by Bird. Workspace templates require a sender you own. The template supplies the category.
Workspace publication needs no Meta review.
Publishing a workspace template validates its draft. The published version is immediately available for sending. Destination content-registration rules remain separate.
Substituted values still affect segment count.
Check the rendered message because longer values can increase billable segments.