Documentation

Variables you can use in messages

Documentation

A template can carry placeholders in double braces. When the message is sent they are replaced with this job's own details.

Hi {{client_name}}, your inspection at {{property_address}} is
scheduled for {{scheduled_date}}.

An unrecognised placeholder renders as nothing at all. Not an error, not the literal text — an empty string. That is worth knowing because it is how a typo reaches a client: {{client_nmae}} produces Hi ,. Use the preview.

Available everywhere

Variable	Renders
`{{client_name}}`	The client's name on the inspection. Blank where none is recorded
`{{property_address}}`	The property address
`{{scheduled_date}}`	The appointment's date and time
`{{report_url}}`	A link to this inspection's report
`{{company_name}}`	Your company's trading name
`{{summary}}`	The amendment note from the latest publish. Only meaningful on an amended-report message; blank elsewhere

Email only

Variable	Renders
`{{inspector_name}}`	The assigned inspector
`{{invoice_url}}`	A link to invoices
`{{payment_url}}`	A link to pay
`{{agreement_sign_url}}`	This recipient's own signing link
`{{event_type_name}}`	The kind of visit, on visit-triggered messages
`{{event_scheduled_at}}`	When that visit is
`{{event_inspector_name}}`	Who is attending it

{{agreement_sign_url}} is resolved only when a template actually mentions it. Referencing it in a message that has no outstanding agreement produces nothing, which is the correct outcome: there is no link to give.

The three event_* variables are populated only for messages triggered by a visit. On any other trigger they are blank.

Text messages only

Variable	Renders
`{{company_phone}}`	Your call-back number, from your workspace settings
`{{review_url}}`	A review link, where one is configured

{{company_phone}} is not decoration. A text from an unfamiliar number with no way to reply to a human is the one most likely to be reported as spam, and the compliance disclosure your workspace sends refers to it.

Two template systems, two vocabularies

The placeholders above are for the automation templates — the messages rules send.

The product also sends transactional email that is not rule-driven: a portal sign-in link, a shared repair request, an agent share. Those templates are edited on their own pages and each one lists the variables it accepts, beside the editor. Their names are not the same as the ones on this page, and they are not interchangeable.

Rule of thumb: use the list shown next to the editor you are typing in. This page is the automation list; a per-trigger page shows its own.

Preview before you save

Every template editor renders a preview with sample values. It is the only way to catch a variable that comes out blank, because a blank one looks like a sentence that was always meant to read that way.