What Automatic Alerts Should a Small Business Set Up for Its Team?

By Bill Stilwell · Last reviewed October 17, 2026

The short answer

Set your systems to alert one named person when something needs action: a new lead, a booking, an accepted or declined estimate, a payment received or failed, a complaint, an overdue task, an approval, or a broken system. Send urgent and high-value items to the owner too. Keep alerts few and specific so nobody starts ignoring them.

Why it matters

Most dropped leads and late fixes happen because nobody knew something needed attention. An alert that goes to a shared inbox nobody owns is almost as bad as no alert. Good alerts go to one person, say what to do, and come through a channel that person checks.

18.9.1 New lead

What it means: telling the assigned owner a new lead came in.

How to do it: send the alert by text or app notification to the person who owns lead response (see 16.2.1 Lead Response Ownership). Include the name, service, source, and a link to the record.

Common mistake: form leads go to an email inbox that gets checked once a day.

18.9.2 New booking

What it means: telling the delivery team about a new booking.

How to do it: send the date, address, service, and special notes to whoever schedules and does the work (see 17.1 Scheduling).

Common mistake: an online booking nobody sees until the customer calls asking where the crew is.

18.9.3 Payment received

What it means: telling the right person a payment came in.

How to do it: alert whoever handles bookkeeping or releases the next step, like ordering materials after a deposit.

Common mistake: materials aren’t ordered because nobody noticed the deposit cleared.

18.9.4 Complaint

What it means: telling the escalation owner about a complaint.

How to do it: any complaint, bad review, or refund request goes to the person named in your complaint process, right away (see 17.8 Complaint Handling).

Common mistake: a one-star review sits for two weeks before anyone sees it.

18.9.5 Task overdue

What it means: reminding the responsible person when a task is late.

How to do it: set due dates on tasks like callbacks, estimates, and follow-ups. Alert the owner when one passes. If it’s still open a day later, alert their manager.

Common mistake: due dates with no alerts, so overdue tasks just pile up.

18.9.6 Approval needed

What it means: telling the reviewer something is waiting for their okay.

How to do it: use alerts for discounts over a set amount, refunds, change orders, and AI-written content that needs human review (see 25.3 Human Review of AI Output).

Common mistake: a change order waits three days for approval while the crew stands around.

18.9.7 System failure

What it means: telling the administrator when a system breaks.

How to do it: turn on failure alerts for forms, payments, automations, and website uptime. Send them to whoever can fix the problem, plus a backup person (see 18.11 Monitoring Automation and 13.2.6 Uptime Monitoring).

Common mistake: the website form breaks on a Friday and nobody finds out until Tuesday.

16.8.1 New lead (sales notifications)

Same as 18.9.1. Notify the person responsible for responding.

16.8.2 High-value lead

Set a rule, like “estimated job over $10,000,” and also alert the owner or manager so they can step in.

16.8.3 Urgent lead

Follow your urgency procedure. For example, a burst pipe or no-heat call alerts the on-call person by phone, not just email (see 16.2.5 Lead Escalation).

16.8.4 Estimate accepted

Notify the delivery and billing people so they can schedule the job and send the deposit request.

16.8.5 Estimate declined

Record the reason in the customer record and notify the salesperson so they can follow up if it makes sense (see 16.7 Follow-Up Procedures).

16.8.6 Payment received

Same as 18.9.3. Notify the team that handles the next step.

16.8.7 Payment failed

Notify the owner and the customer service owner, so someone contacts the customer quickly and kindly (see 16.6.4 Failed Payments).

16.2.5 note: Lead escalation

The Page Map places the alert setup for lead escalation here. The rules for when and how a lead gets escalated live in 16.2.5 Lead Escalation. Build the alerts in this section to match those rules.

When to get help from a pro

A customer relationship management (CRM) or automation specialist can set up alerts across your tools. Questions to ask:

Which of my tools can send alerts, and to which channels?
How do I add a backup person when the main owner is off?
How do I keep alerts from piling up and being ignored?

Bill’s note

[Bill: add a short note. For example, the alerts SiteSmarty uses for new client leads, or a client who lost jobs because form leads went to an unchecked inbox.]

How I did this for SiteSmarty

[Date I did this:]
[What I actually did, step by step: each SiteSmarty alert, who gets it, and how]
[What it cost and how long it took:]
[What surprised me or what I’d do differently:]
[Screenshot or photo to add, with private info blurred: the notification settings list]
[Result so far:]

Questions people ask

Who should get a new lead alert? The one person who owns lead response, by a channel they check all day, like a text or app alert.

How do I alert the owner about a big lead? Set a rule based on job size or type that sends a second alert to the owner.

What should happen when a payment fails? Alert the owner and the customer service owner so someone reaches out to the customer quickly.

How do I know when an automation breaks? Turn on failure alerts in each tool and send them to the person who can fix it, plus a backup.

Audit check

Outline line	Question	Pass looks like	Fail looks like	Evidence to collect
18.9.1 New lead	Does every new lead alert its owner fast?	Instant alert to one person	Unowned inbox	Alert settings
18.9.2 New booking	Does the delivery team get booking alerts?	Booking details sent	Bookings missed	Alert settings
18.9.3 Payment received	Do payment alerts reach the right person?	Next step triggered	Payments unnoticed	Alert settings
18.9.4 Complaint	Do complaints and bad reviews alert the escalation owner?	Same-day alert	Found weeks later	Alert settings
18.9.5 Task overdue	Do overdue tasks alert the owner and then a manager?	Two-step alerts	No alerts	Task tool settings
18.9.6 Approval needed	Do approvals alert the reviewer?	Alerts for set items	Approvals stall	Alert settings
18.9.7 System failure	Do failures alert an admin and a backup?	Alerts on forms, payments, uptime	Silent failures	Monitoring settings
16.8.1 New lead	Same as 18.9.1	Same	Same	Same
16.8.2 High-value lead	Does the owner get alerts for big leads?	Rule in place	No rule	Alert rule
16.8.3 Urgent lead	Do urgent leads follow the urgency procedure?	Phone alert to on-call	Email only	Escalation settings
16.8.4 Estimate accepted	Are delivery and billing alerted?	Both notified	Job stalls	Alert settings
16.8.5 Estimate declined	Is the reason recorded and the salesperson alerted?	Reason field filled	No reason	Sample records
16.8.6 Payment received	Same as 18.9.3	Same	Same	Same
16.8.7 Payment failed	Are the owner and service owner alerted?	Both notified	Nobody follows up	Alert settings
16.2.5 note	Do escalation alerts match the 16.2.5 rules?	Alerts match rules	Mismatch	Rules and settings

Where this fits

Do this first: 16.2.1 Lead Response Ownership, 16.2.5 Lead Escalation

Do this next: 18.10 Testing Automation

Sources

Google Business Profile Help, "Tips to improve your local ranking on Google" (checked October 17, 2026)

This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.