Jinja templates for voice campaign messages: examples and preview checks

A template substitutes contact data into text. It does not verify that the data is current, establish permission to call or guarantee what a language model will say later. Keep campaign templates small enough to inspect with representative records.

A greeting with an optional name

Hello {{ name | default('there', true) }}. This is the automated assistant for {{ company | default('our company', true) }}.

For name = "Sam" and company = "Example Repairs", the rendered text is:

Hello Sam. This is the automated assistant for Example Repairs.

The second argument to default also handles false-like values such as an empty string. Without it, an empty value can remain empty. See the official Jinja template reference for syntax and the default filter.

Use a condition for genuinely optional context

{% if service_name %}
I am calling about your request for {{ service_name }}.
{% else %}
I am calling about your recent service request.
{% endif %}

Use this only when there actually is a permitted recent request. A fallback must not invent a relationship with the recipient. If a required fact is missing, correct the record or block that workflow instead of replacing it with persuasive filler.

Burki's rendering boundary

Burki's campaign template engine uses Jinja expressions and supplies default values for assistant_name, company and name when those keys are absent. It also exposes formatting filters including phone_format and title_case. This describes template rendering, not verified campaign delivery or an unlimited template execution environment.

A template preview shows text. It does not prove that a telephone route works, that a recipient is eligible or that an external action will succeed. Do not depend on an undocumented campaign “Test Mode” button.

Preview the failure cases

Check a populated record, a missing key, an empty string, a null value, punctuation and unusual names. Invalid syntax or error-marked output must be fixed before a live run. Review whitespace and read the result aloud; a syntactically valid paragraph can still make a poor greeting.

Treat inserted contact values as data, not trusted model instructions. Avoid unnecessary personal information in the greeting. Use contact preparation and a bounded campaign run after the text has been checked.