Skip to main content
Notification rules decide what Liftify tells you about — a new review, a task assigned to you, a customer replying in the inbox — and whether you hear about it straight away or in a digest.
This form has caught up with the rename from Tickets to Tasks. The category that used to read Ticketing now reads Tasks, and its event names say “Task” instead of “Ticket”. Nothing about how the rules behave changed with the renaming. Rules you created before keep whatever name you gave them, so a rule of yours may still say “Ticket” — rename it if it bothers you. See Work a task.

​
Personal rules versus account defaults

There are two notification pages in settings, and they do different jobs. This page is about the first one. For the second, see Set default notifications for new users.

​
Open your notifications

  1. In the left sidebar, click the circle with your initials, then Settings.
  2. Under User, click Notifications.
The Setup my notifications tile in the Settings group on your dashboard is a shortcut to the same page. It used to open a page most people were not allowed to see, and refused them; it now opens your own rules. Your existing rules are grouped by category. Once you have rules, a filter bar appears above them so you can narrow by category or frequency. With none at all you’ll see No notifications yet.

​
Create a rule

Click Create Notification and work down the form.

​
Event Category

Which part of Liftify the rule listens to — Reviews, Tasks, Inbox, Surveys and so on. You only see categories for areas your role lets you see, so this list is shorter for some people than others. If only one category is available, the field is fixed on it.

​
Event Type

The specific thing that happens. Some of the options: A short description of the selected event appears under the dropdown.

​
How many internal notes you hear about

Internal Note Added is new, and it brings its own Notify me for field — separate from the Notify me about field the Task events use, described below. It decides how many of your team’s notes reach you: The event only sends Instantly — there is no digest for notes. You are never emailed about a note you wrote yourself, and you get one email per note however many of your rules it matched. Editing a note sends nothing. See Add an internal note to a conversation.

​
Notify me about

This field decides whose tasks the rule tells you about. It appears on five Task events — Task Assigned, Task Status Changed, New Comment on Task, Task Not Resolved In Time and Task Stuck In Status — and on nothing else. Each event starts on its own sensible default — Task Assigned on Tasks I own, the rest on Tasks I own or watch — and switching the Event Type resets it to that event’s default.
This used to be called Notify me for and offered two options, on two events only. There was also an Assignee filter further down the form, which did an overlapping job; it has been removed. If you had a rule using it, it now says Tasks I own here instead.All tasks never widens what you can see: someone whose role limits them to tasks assigned to or watched by them still only hears about those.

​
Whose work

This field decides whose jobs the feedback has to belong to. It appears on New Review Received and New Survey Response, and on nothing else. A specific employee’s jobs is a group of names at the bottom of the list. Someone who is no longer active is shown as (inactive). With more than eight people to choose from, a Search employees… box appears, and an empty search says No employees found. Past 50 employees the list no longer loads everybody up front — it would take too long to open on a large roster. Instead the box reads Type a name to find an employee… and looks people up as you type:
  • Type at least two letters. Below that it says Type at least 2 letters of a name.
  • While it looks, it says Searching…
  • If the lookup fails, it says Couldn’t load employees. Try again. Type again to retry.
The person a rule already follows is always listed, whether or not you have searched for them, so opening an existing rule shows you who it points at.
My jobs only appears once your login is linked to an employee record. Until it is, the field explains why: ““My jobs” needs this notification’s owner linked to an employee record. An admin can link one in Settings → Employees.”Picking somebody else’s jobs needs permission to see employees. Without it you get All jobs and My jobs only. You can still edit the rest of a rule that already follows someone — you just can’t point it at a different person.
A rule narrowed this way waits for the review or response to be matched to a job, because until then nobody is credited and there is nothing to compare against. Feedback that arrives already matched notifies you straight away. Feedback matched later notifies you when the match is made — including when somebody confirms it by hand on the match screen.Credit that lands on old feedback does not notify anyone. Adding a person to a job’s crew credits them on every review already matched to that job, so anything older than a week is passed over rather than arriving as a pile of alerts about months-old feedback. A match confirmed by hand is exempt from that cut-off.
On the rules list, a narrowed rule carries its scope — My jobs, or Dana Whitfield’s jobs. If the scope stops resolving, because your login was unlinked or the person you followed was deactivated or merged away, the rule says so — My jobs (not sending — no linked employee), or Dana Whitfield’s jobs (not sending — employee unavailable). A rule in that state sends nothing; it deliberately does not fall back to All jobs, which would quietly widen it. Fix the link, or set the rule to All jobs yourself.

​
Frequency

Choose Instantly, Daily digest, Weekly digest or Monthly digest. Some events only support one option, in which case the field is locked to it. New Message Received now takes Instantly, Daily digest or Weekly digest. Pick a digest and you get one email listing every inbound message since the last one, rather than an email per message — useful if your inbox is busy and you are not the person watching it minute to minute. Pick anything other than Instantly and a panel opens: “Configure when your digest will be delivered:”
  • Delivery Time — on the hour, and it’s (your local time), so it follows the timezone set on your profile.
  • Day of Week — weekly digests only.
  • Day of Month — monthly digests only, 1st through 28th.
The two threshold-based inbox events set their own timing, so they don’t show a frequency at all.

​
What a digest email contains

A digest leads with a summary of the whole period, then lists the individual reviews or responses underneath. The summary covers everything that matched your rule, not just the handful the email shows, so the numbers at the top are trustworthy even when the list below is cut short. A review digest is headed “Daily Review Digest” (or Weekly, or Monthly) with the count of “new reviews matching your criteria” and the dates it covers. Under that, a Rating Breakdown gives you the average across the rated reviews and a bar per star band — 5 Stars down to 1 Star, plus Not Rated if any came in without a rating — each with its own count. Then Recent Reviews, showing up to ten, with a link to the rest. A survey digest carries the response count, the average rating out of 100, and, when the responses answered an NPS question, the NPS score beside it. Below that an NPS Breakdown names the score, how many responses were scored, and a bar per band: Promoters (9–10), Passives (7–8) and Detractors (0–6). A digest where nobody answered an NPS question has no NPS section at all.
The summary describes exactly what your rule matched, so it moves with your Scope, Rating and Sources filters. A rule narrowed to one location’s 1- and 2-star reviews gives you an average of those reviews, not of your account.

​
What a review email contains

Every email about a review — a new one, an edited one, a flagged or reported one, and any email about a reply — now carries a View Review button. It opens that one review on the Reviews page, filtered down to it, so you do not have to hunt for it in the list. In a digest, each review listed gets its own button. If you are not signed in when you click it, Liftify asks you to sign in and then takes you straight to the review rather than dropping you on the dashboard.
If the review has been deleted from Liftify since the email went out, the button lands on This review is no longer available — “It was deleted from Liftify after this link was sent. You can still find every other review on the Reviews page.” — with a View all reviews button.

​
What an instant survey response email contains

A New Survey Response rule set to Instantly emails you one response at a time, with the context behind it as well as the answers. It leads with who answered, the Overall Score, and the NPS Score where the survey asked for one. Then come up to four labelled blocks:
  • Customer — Name, Phone and Email, with the phone and email as links you can tap from your phone
  • Job — Name (a link into the job), Type, Job # and Service date
  • Team — the crew on that job, each listed under their role on it, or Technician where the job records no role
  • Service Site — Site and Address
Under those, the Answers list every question they answered, with their answer in full, in the order the survey asked — written comments included, line breaks and all. Questions they skipped are left out, and a View Full Response link at the end opens the response in Liftify. This is enough to ring the customer back without opening Liftify first, which is the point of an instant alert. The email used to show the first two answers only, each cut off at 150 characters, so the written comment you actually needed was usually the part that got trimmed. If your team has been treating the alert as a nudge to go and look, it is now worth reading on its own — and worth forwarding.
You only get the blocks your permissions allow: Job and Team need permission to see jobs, Service Site needs permission to see sites. Anything blank is left out, and a block with nothing in it is dropped entirely — so a response with no job behind it arrives with the Customer block alone.Your own filled-in custom fields ride along in the block they belong to. Customer fields need permission to see contacts.

​
Filters

Below the timing, a Filters section appears when the chosen event supports narrowing. Which filters show depends on the event. The ones you may see:
  • Scope — restrict the rule to particular locations. Leave it on All Locations to cover everything. The list offers your active locations, plus any location this rule already names that has since been made inactive, marked (inactive). Leave that one selected or deselect it deliberately — it is kept on purpose so an unrelated edit can’t empty the rule’s location list and quietly widen it to your whole account.
  • Rating — an operator (equals, less than, greater than or equal to, and so on) plus a star value, so you can be told about 1- and 2-star reviews only.
  • Sources — which review sites count: Google, Facebook, Yelp, BBB, HomeAdvisor or Angi. Angi is new to this list.
  • Status(es) — Task Stuck In Status only. Choose which statuses count as “stuck”, so you are only told about the ones that matter. It starts on All Statuses, and the list offers your open statuses with their colour dots. Statuses in the Done group are never counted as stuck, whatever you pick here.
  • Channel, Campaign, Source, Survey(s) and score-based filters, depending on the event.
Click Save when you’re done, or Cancel to back out.
Status(es) is the fix for a Task Stuck In Status rule that emails too much. Rather than raising the hour threshold for everything, name the one or two statuses where sitting still is actually a problem — Waiting on Customer, say, but not In Progress.

​
Change or delete a rule

Click a rule to open it, adjust it, then click Save. To remove it, click the trash icon at the top of the rule and confirm — you’re asked “Are you sure you want to delete this notification rule?”

​
Stop hearing about your own actions

At the top of the Notifications page is a switch: Don’t notify me about my own actions, described as “Skip inbox notifications triggered by things you do yourself, like assigning a conversation to yourself.” It applies across your rules rather than to any one of them, and it saves the moment you flip it.