Placeholders that fill in the real values

Eleven insertable values — customer name and contact details, project and stage names, estimate total, event amount, your company name, the standard title and the open link — grouped and explained.

What it is

Chips inserted at the cursor of whichever field was last focused. Each carries a hint saying where the value comes from. Resolution is best-effort: values come from the event's structured data first, then the estimate link the event points at, then org identity.

Also called: merge fields · {{customer name}} · template variables · personalised alerts

See it
Placeholders that fill in the real values
CustomerBuildingAmountStatus
Sutter Kline40×64 Shop$11,080Approved
Ronan PetschBarndominium$2,720Sent
Ivy BrubakerRiding Arena$17,730Paid
Delia Yoder40×64 Shop$17,920Open
Ronan Petsch30×40 Garage$5,380Draft
The token chip rail grouped Customer / Project / Money / Company / Message above the message field. NotificationMessageComposer.tsx. Sample data — no customer information appears here.
How it works
  1. 1A token the event cannot supply renders as empty rather than printing the placeholder.
  2. 2If the whole rendered body ends up blank, dispatch falls back to the standard message rather than sending an empty text.
Why we built it

The file states the purpose: 'A token names a per-project value that exists across projects… so a builder can write the message they actually want to receive ("{{customer.name}} approved {{project.name}} for {{estimate.total}}") and the dispatcher fills the live values when the event fires.'

The problem
  • Custom wording that could not reference live values
  • Blank messages when a value was missing
Sound familiar?
What you get
Personalised alerts without per-event editing
A missing value degrades gracefully

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →