Skip to main content
Every time something happens on a customer’s account (a lead assigned, a bid outbid, a return approved), Juiced tells them by email, text, or in-app notification. The default copy works, but it sounds like Juiced. This guide makes it sound like you. For the full list of events and variables, see Notifications.

​
Prerequisites

  • The Admin role.
  • SendGrid set up for email templates, and Twilio for SMS. Without them, those channels don’t appear.
  • A sense of your voice (friendly, brisk, formal, whatever matches the rest of your customer communication).

​
1. Open Notification Templates

Click the gear in the rail and choose Notification Templates under Application.
Notification Templates list with one row per notification type and Visible and Default columns for each channelNotification Templates list with one row per notification type and Visible and Default columns for each channel
Each row is a notification type with a short description of when it’s sent. For each channel (Email, SMS, In-App), two columns show its settings.
  • Visible means customers can see and change this notification in their preferences.
  • Default means it’s turned on for new contacts.
A type that doesn’t support a channel shows a dash there. Payment emails, for example, are email-only.

​
2. Open a template

Click a notification type. The top of the page lists its Available variables, and below that is a card per channel (Email Template, SMS Template, and In-App Template).
Edit Lead Assigned Template page listing available variables such as lead.full_name and customer.name, followed by the Email Template card with Visible to customers and Enabled by default switchesEdit Lead Assigned Template page listing available variables such as lead.full_name and customer.name, followed by the Email Template card with Visible to customers and Enabled by default switches

​
3. Write the copy

Each card has two fields.
  • Subject is the email subject, or the in-app notification’s title. SMS has no subject.
  • Body is the message. Drop in variables from the list at the top, for example {{ lead.full_name }} or {{ customer.name }}.
A Lead Assigned email might use the subject New {{ lead.leadType.name }} lead in {{ lead.city }} and this body.
A few things to know about how messages come out.
  • Emails keep basic formatting (bold, italic, underline, strikethrough), and each line becomes its own paragraph. Lines written as Label: value, like the phone line above, are laid out as a tidy details list.
  • Emails get a button to the relevant page automatically, so you don’t need to paste the link in.
  • SMS should be short. Put the important detail first.
Only use variables listed for that notification type. Juiced checks when you save, and a variable that doesn’t exist for this type (say, a lead field on Customer Paused, which has no lead) shows an error.

​
4. Decide who can turn it off

Each card also has two switches.
  • Visible to customers hides the notification from customers’ preferences when it’s off, so they can’t change it.
  • Enabled by default sets whether new contacts start with it on.
They work together. Visible and on by default is the usual setup. Hidden and on makes a must-send message. Visible and off makes it opt-in, which suits chatty notifications like Bid Matched.

​
5. Save

Click Save all in the floating save bar. Every channel saves together. If you get it wrong, Reset to Default on a card restores that channel’s default template, and Reset All to Default at the top restores every channel for this type. Both ask you to confirm, and there’s no undo, so copy anything you want to keep first.

​
6. Test it

Add yourself as a contact on a test customer, then use the contact’s Test action to send a test notification. Or wait for the real thing by posting a test lead through one of your sources and watching it arrive.

​
Good to know

  • Branding carries through, so your logo and colors appear in emails without extra setup.
  • Customers manage which notifications each contact gets under Notifications → Contacts in their portal. See Notifications in the customer portal.
  • In-app notifications land in the bell of every user on the customer’s account.
  • Sending lead data to a CRM is a different job. Use webhooks for that.