Automation Merge Fields

Current V2 scope: The quote-follow-up editor accepts only the double-brace fields listed below. The broader V1 bracket-token catalog remains a parity reference and does not work in this current V2 editor.

Current V2 Safe Fields

Click a field pill to append it to the last email subject, email body, or SMS message selected in the editor. Preview and test replace fields with sample values without sending.

V2 does not yet persist a sequential estimate number. Both estimate-reference tokens therefore render a truthful stable reference derived from the estimate identity and proposal revision; they do not invent an EST-001234 number. Unknown fields fail closed when the draft is validated. The secure proposal link remains scoped to the exact issued revision. Do not paste private office notes or unsupported object paths into customer copy.

Broader Clean Estimate V1 Reference

Merge fields let you insert dynamic data into your automation messages. Instead of writing a generic message, you can address the customer by name, reference their estimate total, or include a payment link -- all automatically.

Syntax

Merge fields use the [field.name] format. For example:

Hi [customer.first_name], thanks for requesting an estimate!

When the workflow runs, the engine replaces [customer.first_name] with the actual customer name from the contact record.

Using the Merge Field Toolbar

When editing an SMS, email subject, email body, note, call whisper, or text-to-speech message in the Guided Editor or visual builder, an Insert live data field picker appears beside the form field. Its help text explains that the bracketed token is replaced with real record data when the automation runs. It has tabs for each category:

• Customer -- contact information
• Organization -- your company details
• Estimate -- estimate data
• Job -- job data
• Invoice -- retained V1 invoice data; current V2 invoice workflows do not

expose these tokens in the automation editor yet

• Appointment -- scheduling data

Click any field pill to insert it at your cursor position in the text area.

Available Fields

Customer

Organization

Estimate

Job

Invoice

V1 reference: These invoice merge fields belong to the retained V1 automation engine. The current V2 invoice workspace does not yet make them available in Guided Editor or visual-builder sends.

Appointment

Sales Rep

Preview

When editing SMS or email templates in the Guided Editor, a live preview shows the rendered message with example data filled in. Use this to verify your merge fields are correct and the message reads naturally before activating.

Tips

• Always include [customer.first_name] in your opening line. Personalized messages get higher response rates.
• Use [estimate.link] to make it easy for customers to act from a current V2

message. [invoice.payment_link] remains a V1-only automation merge field; current V2 invoices deliver their authorized link through Send invoice or Resend invoice instead.

• Keep SMS messages short. Merge fields expand to real data at send time, so account for longer names or addresses when estimating message length.
• If a merge field cannot be resolved (for example, the customer has no email on file), it is replaced with an empty string. Structure your sentences so they still make sense if a field is blank.