Notifications

Notification templates let you customize the messaging customers receive when events happen in the system. You control the verbiage, formatting, and what details are included in each notification. Find them under Settings → Application → Notification Templates. Each row is a notification type, with columns for each channel showing whether it’s Visible to customers and turned on by Default for new contacts.

​

Channels

Notifications can be delivered through three channels, but channel availability varies by event. Each channel has its own template, so you can tailor the message format and length appropriately, such as detailed HTML emails, concise text messages, and quick in-app alerts. The Email channel only appears once SendGrid is configured, and SMS only once Twilio is. Some events don’t support every channel. Account Archived, Account Restored, Payment Failed, Payment Successful, and the two checkout emails are email-only, and Subscription Payment Failed goes out by email and in-app.

​

Notification events

Templates are available for the following events. The two checkout emails only appear when checkout pages are enabled for your account.

​

Template variables

Templates support merge fields using double curly braces, like {{ variable_name }}. Available variables depend on the notification type.

​

Common variables

These are available in all templates.

• {{ actionLink }} is the URL to the relevant page.
• {{ defaultActionText }} is the default text for the action button.
• {{ supportEmail }} is your tenant’s support email.

​

Lead variables

These are available for lead-related notifications (Lead Assigned, Outbid, Bid Matched, Return Approved).

• {{ lead.public_id }}, {{ lead.uuid }}
• {{ lead.full_name }}, {{ lead.first_name }}, {{ lead.last_name }}
• {{ lead.email }}, {{ lead.phone }}
• {{ lead.address_1 }}, {{ lead.address_2 }}, {{ lead.city }}
• {{ lead.leadType.name }}
• {{ lead.details.field_name }} for any custom field on the lead category

​

Customer variables

These are available for customer-related notifications.

• {{ customer.name }}, {{ customer.email }}, {{ customer.phone }}
• {{ customer.address }}, {{ customer.city }}, {{ customer.state }}, {{ customer.zip }}
• {{ customer.leads_count }} for batch notifications

​

Other variables

• Buy order notifications can use {{ buyOrder.amount }}, {{ buyOrder.scope }}, {{ buyOrder.status }}
• Return tier notifications can use {{ disputeTier.name }}, {{ disputeTier.discount_percentage }}, {{ disputeTier.penalty_percentage }}

​

Editing templates

Click a notification type to open its editor. The top of the page lists the Available variables for that type; copy any of them into your templates. Below that is one card per channel (Email Template, SMS Template, In-App Template), each with four settings.

• Visible to customers hides this notification type from customers’ notification preferences when it’s off.
• Enabled by default sets the initial preference when a new contact is created.
• Subject is the email subject or the in-app notification’s title. It’s required for email, and SMS has no subject.
• Body takes {{ variable }} placeholders. Emails keep basic formatting (bold, italic, underline, strikethrough) and put each line in its own paragraph; lines written as Label: value are laid out as a tidy details list. Keep SMS bodies short.

Emails get a button to the relevant page automatically, labeled with the type’s default action text, so you don’t need to add the link yourself. Changes to every channel are saved together with Save all in the floating save bar. Templates are validated when you save, so referencing a variable that doesn’t exist for that notification type shows an error. Each card has Reset to Default to restore that channel’s template, and Reset All to Default at the top restores every channel for the type. To check how a message lands, add yourself as a contact on a test customer and use the contact’s Test action.

​

Related guides