Tutorialthe whole build, step by step

Speed to lead: make sure every web form gets a call back

Every web form gets one rep and a deadline, then a second name, nights too, and a daily no-call list your manager reads. Any CRM, with HighLevel clicks.

By Eric Snyder, founder 16 min readChecked on Oct 25, 2026
Save this guidereceiptsgroup.com/guides/form-callback-rules
SetupAbout an hour: the rules on paper, then two workflows and a saved list
Running cost$0 for the rules. In HighLevel: your plan, plus about 1.2 cents per alert text with carrier fees and $0.0166 per call minute (checked 2026-10-25)
You needYour CRM, your reps' names, a second name who answers at night, and 10 minutes every morning
Works withAny CRM that logs calls; the exact clicks here are for HighLevel
In this guide
Start here
  1. Start here: paste this into ChatGPT or Claude
The two rules
  1. How the pieces connect
  2. The two rules, on paper (any CRM)
  3. The two rules in HighLevel
  4. Reading the list every morning
  5. Example (made up)
Copy and use
  1. First test: your own phone (a few cents)
  2. What it costs
  3. When it breaks
  4. Sources, checked Oct 25, 2026

This is the leak that bugs me most, because you already paid for the lead. A form comes in from your website at 4:55. The rep it went to is already in the parking lot. And it just sits there all night, like a package on the porch. I don't even think anyone's ignoring it. Everybody just thinks somebody else has it.

So it's two rules. Rule one: every new form gets one rep and a deadline. Let's say 15 minutes while the team's working, and if no call attempt is logged by then, it goes to a second name, after hours too. Rule two is the one I'd never skip, because it catches the form that slips through anyway: once a day, somebody pulls every form with no call logged onto a list your manager actually reads, and asks why.

This won't make a slow office fast. I wish it did. But it makes the slow part show up on a list instead of in a lost job. Here's all of it: the rules on paper for any CRM, the exact clicks in HighLevel, the question to send your CRM's support if you're on something else, a test with your own phone before it touches a real lead, how to read the list, and what it costs.

Checked on Oct 25, 2026

Start herepart 1

Start here: paste this into ChatGPT or Claude

Not technical? Start here. Copy this prompt into ChatGPT or Claude (the free versions work) and it walks you through the whole guide, one step at a time, in plain English. It asks before it assumes anything and checks with you before anything that costs money, reaches a real customer or deletes something. The rest of the page is the same guide, written out, if you'd rather do it yourself.

PromptThe walkthrough prompt (copy all of it)
Hi! Please be my patient guide for this step-by-step guide from Receipts Group: "Stop paying for website leads nobody calls back: two rules"
The guide is here: https://receiptsgroup.com/guides/form-callback-rules (open it if you can; if you can't, everything you need is below).

About me: I run a small business and I'm not technical. Use plain words and short sentences.

My goal: every lead form that comes in gets a call. Two rules.
Rule 1: every new form gets one rep and a deadline (for example, 15 minutes while the team's working). If no call attempt is logged by then, it goes to a second name, after hours too.
Rule 2: once a day, somebody pulls every form with no call logged onto a list my manager actually reads, and we ask why.
The catch: a call only counts if it's logged in my CRM. A call from a rep's own cell phone usually isn't.

How to help me:
1. One step at a time. For each step, tell me in a sentence what it's for and exactly what to do. Then stop and wait until I say "done" or tell you what I see.
2. Ask before you assume anything about my business, my CRM, my team or my forms. One question at a time.
3. If you use a technical word, explain it in plain English the first time (for example: CRM, workflow, trigger, tag, smart list, round robin, internal notification, logged call).
4. Stop and check with me before anything that costs money (a paid plan, a trial that bills when it ends, a phone number, text or call charges), anything that reaches a real customer or a real lead (publishing or turning on a workflow, calling or texting anyone), and anything that deletes something (deleting a contact, a tag or a workflow, or removing anyone from a workflow).
5. Use only what I tell you or show you. Never guess a menu name or a setting in my CRM. If you're not sure where something is, tell me to ask my CRM's support and give me the question to send.
6. If I paste anything, remind me first to take out customers' names, phone numbers and addresses.

The steps, from the guide:

Step 1. List every place a lead form lands.
My website form, Google, Facebook, anything else that sends me leads. For each: where does it show up, who sees it first, and does it land in my CRM? A form that only goes to someone's email can't be watched by anything, so it has to get into the CRM first.

Step 2. Give every form one name.
One rep, or a rotation (round robin: each new form goes to the next rep in line). Never "the team" or a shared inbox.

Step 3. Pick the deadline and the second name.
My deadline while we're working (the guide's example: 15 minutes). My second name during the day (a manager or another rep) and after hours (whoever's on call, or me). The after-hours name has to be someone who actually answers at night.

Step 4. Decide what counts as a call attempt.
Only a call that's logged in my CRM, made from the CRM's phone or app so it records itself. Answered, voicemail, no answer: all count as attempts.

Step 5. Pick who pulls the daily list, what time, and who reads it.
Fill in the rules sheet below with me.

Step 6. Set it up in my CRM.
If my CRM is HighLevel, walk me through it like this:
Workflow A, "New form: rep and deadline":
a. Automation, then Workflows, then + Create Workflow, then + Start from Scratch. Name it "New form: rep and deadline".
b. Add New Trigger, choose Form Submitted. Under Form Is, pick my form. This trigger works with forms built in HighLevel; for forms from other tools, tell me to ask HighLevel's support.
c. Click + and add Assign To User. Pick my reps (more than one means round robin). Split Traffic: Equally. Turn on Only Apply To Unassigned Contacts, so a repeat customer keeps their rep.
d. Click + and add Add Contact Tag. Type "no call yet" and click Add New Tag.
e. Click + and add Send Internal Notification. Type of Notification: SMS. To User Type: Assigned User. Paste alert 1 below. This step has to come after Assign To User.
f. Click + and add Wait. Choose "A set period of time", 15, minutes. Leave Advance Window off, so the clock runs after hours too.
g. Click + and add Send Internal Notification. SMS. To User Type: Particular Users, and pick my second name. Paste alert 2 below.
h. Settings tab: turn on Allow Re-entry, so a second form from the same person starts the clock again. Leave Time Window off: it pauses texts outside the hours you pick, and the after-hours alert is the point.
Workflow B, "Call made: off the list":
i. + Create Workflow, then + Start from Scratch. Add New Trigger, choose Call Details. Call Direction: outgoing. Call Status: select every status, because an attempt counts whether they answer or not.
j. Click + and add Remove Contact Tag: "no call yet".
k. Click + and add Remove from Workflow. Choose Another Workflow and pick "New form: rep and deadline". Not All Workflows.
l. Settings tab: turn on Allow Re-entry, so every call counts, not just the first call that contact ever got.
The list:
m. Logged in as the person who reads the list (HighLevel's smart lists belong to whoever makes them): Contacts, then Smart Lists, then + Add smart list. Under Advanced Filters, search for Tags, choose the "no call yet" tag, click Apply, then Create. Name it "No call yet".
n. Optional, a morning reminder: a third workflow with the Scheduler trigger set to Daily at a time I pick (Skip Weekends if we're closed), then Send Internal Notification, Email, Particular Users: the person who reads the list.
o. Save all of them. Before I turn on any Publish toggle, stop and check with me.
If my CRM is something else, don't guess the clicks. Give me the support question below to send them, then help me with their answer.

Step 7. First test with my own phone, before it touches a real lead.
For the test, put only me in Assign To User and as the second name (while it's published like that, real forms come to me too, so I call them). Then:
Test 1, no call: I fill in my form with my own name and cell number. Did alert 1 come? Am I on the "No call yet" list? Did alert 2 come 15 minutes later?
Test 2, a call in time: I fill in the form again and, within 15 minutes, call my own cell from HighLevel's dialer (the phone icon at the top). Did the tag come off? Did alert 2 stay away?
Test 3: if my reps use the HighLevel mobile app, do test 2 again calling from the app.
Optional test 4: one evening, fill in the form and don't call. Alert 2 should come 15 minutes later, not the next morning.
Then put my real reps and second name back, and take the test contact off the list (check with me before deleting anything).

Step 8. Every morning: read the list and ask why.
For each form on it: who had it, why no call is logged, and what changes so it doesn't happen again. Use the daily sheet and the reasons list below.

The rules sheet (fill it in with me):
---
THE CALLBACK RULES (print it, post it)

RULE 1: every new form gets a rep and a deadline.
Forms we watch: _______________
First name: _______________ (one rep, or the rotation)
Deadline while we're working: ___ minutes
Our working hours: _______________
Second name, daytime: _______________
Second name, nights and weekends: _______________
A call counts only if it's logged in our CRM:
answered, voicemail or no answer.

RULE 2: once a day, the no-call list.
Who pulls it: _______________
What time: _______________
Who reads it and asks why: _______________
---

The alert texts (fill in the brackets with me; {{contact.name}} is HighLevel's tag for the lead's name):
---
ALERT 1 (to the rep, right away)
New web form: {{contact.name}}. It's yours.
Call from [your CRM] in the next 15 minutes
so it logs, or it goes to [second name].

ALERT 2 (to the second name, at the deadline)
No call logged after 15 minutes:
{{contact.name}}, web form. It's yours now.
Call from [your CRM] so it logs.
---

The daily sheet:
---
THE NO-CALL LIST: [date]
(no customer phone numbers or addresses on paper)

Form came in (day, time): _______________
Who had it: _______________
Second name got the alert? Y / N
Why no call is logged: _______________
The fix: _______________
Called now? Y / N   By who: _______________
---

The reasons, and the fix for each:
- "I called from my cell." The call happened but isn't logged. Call from the CRM's phone or app next time. In HighLevel, the mobile app's SIM calling isn't logged either.
- "It came in after hours." That's what the second name is for. Check the after-hours name got the alert and knew it was theirs.
- "I thought someone else had it." Check the form had one name on it. In HighLevel, check the lead has an assigned user.
- "Wrong number, spam or a test." Take the tag off so tomorrow's list is clean. If spam is most of the list, fix the form.
- "They called us first." An incoming call doesn't take the tag off in this setup. Take it off by hand.
- "It went to a rep who was off, or who left." Fix the names in Assign To User.
- "We called and it's still on the list." The call didn't log, or the call workflow isn't published. Run test 2 again.

The support question (for any CRM that isn't HighLevel):
---
Hi, I'd like to set this up in [your CRM]:

1. When a new web form comes in, it's assigned to one rep (or the next rep in a rotation), and that rep gets a text alert right away.
2. If no outbound call to that lead is logged within 15 minutes, a second person gets a text alert. This has to work at night and on weekends too.
3. Every morning, I can open a list of every form lead with no call logged yet.

Four questions:
- Which forms can start this: only forms built in [your CRM], or my website's form too?
- Which calls count as logged: calls from your app, from your mobile app, from a rep's own cell phone?
- What do the alert texts cost?
- Does the 15-minute check run after hours, or does it wait for business hours?
---

Watch out for these:
- A rep calls from their own cell. The call happened, but it isn't logged, so the second name gets pinged and it lands on the list.
- A form that never reaches the CRM (it only emails someone). Nothing can watch it.
- An after-hours second name who doesn't answer. Then there's no rule at night.
- A Time Window on workflow A, or an Advance Window on its Wait, holds the after-hours alert until morning.
- Allow Re-entry off on workflow B: only the first call a contact ever gets would count.
- Alert texts that don't arrive: every user needs a phone number set in HighLevel, and ask HighLevel's support to check my texting setup, including my A2P 10DLC registration.
- Pasting customer details into an AI. Take out names, numbers and addresses first.

When we're done, give me a short recap: my rules sheet filled in, what each test showed, and who reads the list and when.

Start by asking me a few quick questions about my business, one at a time. Then begin with step 1.
The two rulesparts 2 to 6

How the pieces connect

  1. 1
    A new formYour website form lands in your CRM→ a new lead with nobody on it yet
  2. 2
    Rule 1: one nameAssigned to one rep (or the next in the rotation), with a text alert→ a rep who knows it's theirs
  3. 3
    The deadline15 minutes on the clock, day or night→ a call logged, or not
  4. 4
    The second nameNo call logged: the second name gets the alert→ a second shot before it goes cold
  5. 5
    Rule 2: the listEvery form with no call logged, every morning→ a manager asking why, and a fix

The catch is the word “logged.” A call from a rep's own cell happened, but your CRM never saw it. So the second name gets pinged and it lands on the list. That's fine the first time: it's how you find out who's calling from their cell.

Words you'll see

  • CRM: the system that holds your customer list and what happened with each one.
  • Round robin: each new lead goes to the next rep in line, so it's always one name.
  • Logged call: a call your CRM recorded by itself because it was made from the CRM's phone or app.
  • Workflow: HighLevel's word for an automation: something happens, then the CRM does these steps.
  • Trigger: the “something happens” that starts a workflow, like a form coming in or a call going out.
  • Tag: a label on a customer's record. Here, “no call yet” goes on when the form lands and comes off on the first logged call.
  • Smart list: HighLevel's saved filter of customers. It updates by itself as tags come and go.
  • Internal notification: an alert HighLevel sends to your team (text, email or the bell in the app), never to the customer.

The two rules, on paper (any CRM)

Do this part first, with a pen. It changes nothing in your software, and it's where you find out whether a form can even reach your CRM.

  1. List every place a form lands

    Your website form, Google, Facebook, anything else that sends you leads. For each one, write down where it shows up and who sees it first. Then the question that matters: does it land in your CRM? A form that only goes to somebody's email can't be watched by anything, so get it into the CRM first.

  2. Give every form one name

    One rep, or a rotation where each new form goes to the next rep in line. If a customer's already been working with a rep, I'd keep them on that rep.

  3. Set the deadline and the second name

    I'd say 15 minutes while the team's working. Pick yours and write it down. Then the second name: a manager or another rep during the day, and somebody who actually answers at night and on weekends, whoever's on call, or you. If the after-hours name doesn't pick up, the rule doesn't exist at night.

  4. Decide what counts as a call attempt

    A call that's logged in your CRM. Answered, voicemail, no answer: they all count, because the rule is about trying, not about reaching them. A call from a rep's own cell happened, but your CRM never saw it, so it doesn't count. I know that sounds strict. It's the only way the list means anything.

  5. Pick who pulls the list, when, and who reads it

    Once a day, same time. One person pulls it, your manager reads it, and for every form on it somebody asks why. Fill in the sheet and put it where the team sees it.

    The rules sheet
    THE CALLBACK RULES (print it, post it)
    
    RULE 1: every new form gets a rep and a deadline.
    Forms we watch: _______________
    First name: _______________ (one rep, or the rotation)
    Deadline while we're working: ___ minutes
    Our working hours: _______________
    Second name, daytime: _______________
    Second name, nights and weekends: _______________
    A call counts only if it's logged in our CRM:
    answered, voicemail or no answer.
    
    RULE 2: once a day, the no-call list.
    Who pulls it: _______________
    What time: _______________
    Who reads it and asks why: _______________
  6. Not on HighLevel? Send your CRM's support this

    Every CRM does this a little differently, so don't guess the clicks. Send this and set it up from their answer. The next section has the clicks for HighLevel.

    The question for your CRM's support
    Hi, I'd like to set this up in [your CRM]:
    
    1. When a new web form comes in, it's assigned to one rep (or the next rep in a rotation), and that rep gets a text alert right away.
    2. If no outbound call to that lead is logged within 15 minutes, a second person gets a text alert. This has to work at night and on weekends too.
    3. Every morning, I can open a list of every form lead with no call logged yet.
    
    Four questions:
    - Which forms can start this: only forms built in [your CRM], or my website's form too?
    - Which calls count as logged: calls from your app, from your mobile app, from a rep's own cell phone?
    - What do the alert texts cost?
    - Does the 15-minute check run after hours, or does it wait for business hours?

The two rules in HighLevel

HighLevel (also called GoHighLevel) does this with two workflows and a smart list. Workflow A starts the clock when a form comes in. Workflow B stops it the moment anyone calls that lead from HighLevel. The tag “no call yet” ties them together: it goes on when the form lands, comes off on the first logged call, and the smart list is everyone still wearing it. Every click here is from HighLevel's own help pages, checked 2026-10-25.

Workflow A: a rep and a deadline

  1. Make the workflow

    WhereAutomation → Workflows → + Create Workflow → + Start from Scratch

    Name it “New form: rep and deadline.”

  2. Trigger: Form Submitted

    WhereAdd New Trigger → Form Submitted → Form Is

    Pick your form. Got more than one? Add a filter for each. HighLevel's help says this trigger works with forms built in HighLevel and fires on every submission. If your website form comes from another tool, it needs an integration or a webhook first: ask HighLevel's support or whoever built your site.

  3. Action: Assign To User

    WhereClick + → Assign To User

    Pick your reps. With more than one, HighLevel rotates them (round robin). Leave Split Traffic on Equally, or choose Unevenly to give somebody more. Turn on Only Apply To Unassigned Contacts, so a customer who already has a rep keeps them.

  4. Action: tag it “no call yet”

    WhereClick + → Add Contact Tag

    Type no call yet and click Add New Tag. Tags are case-sensitive, so type it the same way everywhere.

  5. Action: alert the rep

    WhereClick + → Send Internal Notification → Type of Notification: SMS → To User Type: Assigned User

    Paste alert 1. It has to sit after Assign To User (HighLevel's help says so), or it doesn't know who the rep is. Each rep needs a phone number set in HighLevel to get the text.

    Alert 1 (to the rep, right away)
    New web form: {{contact.name}}. It's yours.
    Call from [your CRM] in the next 15 minutes
    so it logs, or it goes to [second name].
  6. Action: the deadline

    WhereClick + → Wait → A set period of time → 15, minutes

    Leave Advance Window off. That setting makes the wait resume only on the days and hours you pick, and this clock has to run at night too.

  7. Action: alert the second name

    WhereClick + → Send Internal Notification → SMS → To User Type: Particular Users

    Pick your second name and paste alert 2. If the rep calls before the deadline, workflow B pulls the lead out of this workflow and this text never goes out.

    Alert 2 (to the second name, at the deadline)
    No call logged after 15 minutes:
    {{contact.name}}, web form. It's yours now.
    Call from [your CRM] so it logs.
  8. Settings: re-entry on, no time window

    WhereSettings tab → Allow Re-entry

    Turn on Allow Re-entry, so the same person filling in a second form starts the clock again. Leave Time Window off: HighLevel's help says it pauses texts and emails outside the hours you pick, and the after-hours alert is the whole point.

Workflow B: a logged call takes it off

  1. Trigger: Call Details, outgoing

    Where+ Create Workflow → + Start from Scratch → Add New Trigger → Call Details

    Name it “Call made: off the list.” Add the filter Call Direction: outgoing. Under Call Status, select every status in the list (busy, voicemail, no answer, completed and the rest), because an attempt counts whether they pick up or not.

  2. Action: take the tag off

    WhereClick + → Remove Contact Tag

    Pick no call yet. Leave Remove All Tags off.

  3. Action: stop the clock

    WhereClick + → Remove from Workflow → Another Workflow

    Pick “New form: rep and deadline.” Don't pick All Workflows: that pulls the lead out of every workflow it's in, including your follow-up.

    PermissionsHighLevel's help: a removal can't be undone automatically. To put someone back, you enroll them by hand.
  4. Settings: re-entry on

    WhereSettings tab → Allow Re-entry

    Turn it on. Without it, only the first call a contact ever got would count, so a customer you called once before who fills in a new form later would never come off the list.

Rule 2: the list

  1. Save the smart list

    WhereContacts → Smart Lists → + Add smart list

    Do this logged in as the person who reads the list: HighLevel's smart lists belong to whoever makes them (or share it later from Manage Smart List, in the ⋮ menu next to Add Contact). Under Advanced Filters, search for Tags, choose the no call yet tag, click Apply, then Create. Name it “No call yet.” It updates by itself: a lead joins when the tag goes on and drops off when it comes off.

  2. Optional: a morning reminder

    Where+ Create Workflow → + Start from Scratch → Add New Trigger → Scheduler → Daily

    Pick the time, and Skip Weekends under Advanced Settings if you're closed. Then Send Internal Notification → Email → Particular Users: the person who reads the list, with a line like “Open the No call yet list and write the why next to each one.” HighLevel's help says the Scheduler runs without a customer and can send internal emails and texts to your team.

  3. Save, then test before you publish

    Save all of them. Run the first test below before you turn on the Publish toggle with your real reps in it.

Reading the list every morning

The list is only worth something if somebody reads it out loud and asks why. Not to chew anybody out. The why is how you find the leak: the cell-phone caller, the rep who left but is still in the rotation, the after-hours name who never knew it was them. If the same why shows up three days running, that's a process to fix.

Every why gets a fix, and the fix goes in the process, not on a person.
The whyThe fix
“I called from my cell.”The call happened, it just isn't logged. Call from the CRM's phone or app next time. In HighLevel, the mobile app's SIM calling isn't logged either.
“It came in after hours.”That's what the second name is for. Check the after-hours name got the alert and knew it was theirs.
“I thought someone else had it.”Check the form had one name on it. In HighLevel, check the lead has an assigned user.
“Wrong number, spam or a test.”Take the tag off so tomorrow's list is clean. If spam is most of the list, fix the form.
“They called us first.”An incoming call doesn't take the tag off in this setup. Take it off by hand.
“It went to a rep who was off, or who left.”Fix the names in Assign To User. Somebody who's gone shouldn't be in the rotation.
“We called and it's still on the list.”The call didn't log, or workflow B isn't published. Run test 2 below again.
The daily sheet (one block per form on the list)
THE NO-CALL LIST: [date]
(no customer phone numbers or addresses on paper)

Form came in (day, time): _______________
Who had it: _______________
Second name got the alert? Y / N
Why no call is logged: _______________
The fix: _______________
Called now? Y / N   By who: _______________

Example (made up)

Everything here is made up: a fictional roofing company, one form, one night. Same form, before and after the two rules.

Made up, just to show where each rule catches it. The rules can't make a homeowner pick up. They make sure somebody tried, and that you can see it when nobody did.
WhenBefore: no rulesAfter: the two rules
Tuesday, 4:55 PMA roof repair form comes in. It lands in a shared inbox and in Rep A's emailSame form. It's assigned to Rep A, who gets a text alert
5:02 PMRep A is already in the parking lotSame
5:10 PMNothingNo call logged. The second name, this week's on-call rep, gets the alert
5:14 PMNothingThe on-call rep calls from the HighLevel app. No answer, leaves a voicemail. It's logged, so it's off the list
Wednesday, 8:30 AMRep A thinks the office has it. The office thinks Rep A has itThe manager opens the no-call list. This one isn't on it. Two others are: “called from my cell” and a spam form
10:00 AMRep A finally calls. The homeowner already booked somebody elseThe cell-phone one gets called again from the app. The spam one gets its tag taken off
Copy and useparts 7 to 9

First test: your own phone (a few cents)

Before a real lead goes through it, be the lead. This costs a few alert texts and a short call through HighLevel's phone.

  1. Put yourself in as both names

    In workflow A, set Assign To User to just you, and the second alert to just you, so no rep gets a test text. Publish both workflows. While it's set up like that, real forms come to you too, so call them.

  2. Test 1: no call

    Fill in your own form with your name and your cell number, and don't call. Good: alert 1 lands on your phone, you show up on the “No call yet” list, and alert 2 lands about 15 minutes later. Bad: no alert 1. Check that Assign To User comes before the notification and that your user has a phone number set.

  3. Test 2: a call in time

    Fill in the form again. Within 15 minutes, call your own cell from HighLevel's dialer (the phone icon at the top). Answer it or don't, it doesn't matter. Good: the tag comes off, you drop off the list, and alert 2 never comes. Bad: alert 2 comes anyway. Check that workflow B is published, Call Direction is outgoing, and Allow Re-entry is on in both workflows.

  4. Test 3: the mobile app

    If your reps call from the HighLevel mobile app, do test 2 again calling from the app. If the tag stays on, those calls aren't logging, and every one of them is going to land on the list. Fix that before you go live.

  5. Optional test 4: after hours

    One evening, fill in the form and don't call. Alert 2 should come about 15 minutes later, not the next morning. If it waits for morning, there's a Time Window or an Advance Window somewhere in workflow A.

  6. Put the real names back and clean up

    Set Assign To User back to your reps and the second alert to your second name. Take the tag off your test contact (or remove the contact) so it isn't on tomorrow's list.

After a week, paste the week's list into this prompt and let it find the pattern. Before you paste: take out customers' names, phone numbers and addresses. In Claude you can also choose whether your chats help improve its models: Settings → Privacy → Help Improve our AI models.

PromptThe weekly list prompt
Below is a week of my business's no-call list: every web form lead that had no call logged by the next morning, with who had it and the reason my team gave. There are no customer names or numbers in it.

Please:
1. Group the reasons. For example: called from a personal cell, came in after hours, nobody knew it was theirs, wrong number or spam, went to someone who was off or gone.
2. Count each group, and tell me which rep or which time of day shows up the most.
3. For the biggest group, give me one change to my process that would stop it. Aim it at the process, not at a person.
4. Keep it short: a small table, then three lines in plain words.

Rules: use only what's in my list. Never guess what my software does or make up a setting. If something's missing, list it under "Questions for me".

My list:
[paste it here: day and time, who had it, the reason; no customer names, phone numbers or addresses]

Good: a short table of reasons and one process change. Bad: it tells you what a setting in your CRM does. It can't see your CRM, so check that with your CRM's support.

What it costs

Checked 2026-10-25 on gohighlevel.com/pricing, HighLevel's help pages and claude.com/pricing. Prices change, so check before you buy.
WhatPlanPrice
The rules, the list, the morning readNone$0
HighLevelStarter$97 a month, or $970 a year. 14-day free trial; billing starts automatically when it ends unless you cancel, and usage fees can apply during the trial
HighLevelUnlimited$297 a month, or $2,970 a year
A HighLevel phone number (US local)Usage$1.15 a month
Calls out through HighLevel's phone system (US)Usage$0.0166 a minute ($0.0126 for the call plus $0.004 client minutes; $0.0180 before HighLevel's listed discount)
Alert texts to your teamUsage$0.00747 per outgoing US text segment, plus carrier fees (HighLevel's own estimate: about $0.005). A segment is 160 plain characters, or 70 once there's an emoji
Texting registration (A2P 10DLC), if you don't have it yetOne time$22.50 for sole proprietor or low-volume standard, $64.00 for high-volume standard
Texting registration, monthlyPer active campaign$1.50 (low-volume mixed), $2.00 (sole proprietor) or $10.00 (standard)
Claude (the prompts)Free$0
Claude, if you want more usePro$20 a month billed monthly, or $17 a month billed yearly ($200 up front)
ChatGPTSee OpenAI's pricing pageNot checked: OpenAI's pricing page didn't load for us on 2026-10-25

What one form costs to watch: let's say both alerts go out and each is one segment. That's two texts at about 1.2 cents each with the carrier fee, so about 2.5 cents, plus the call minutes you'd spend calling the lead anyway. Already on another CRM? The rules cost nothing extra there either; ask its support what its alert texts cost.

When it breaks

A rep swears they called, and it's still on the list
They called from their own cell, or with the mobile app's SIM calling. HighLevel's help says SIM-based calls aren't logged automatically. Call from the dialer (the phone icon at the top), or from the mobile app once the account has a HighLevel number (test 3 below checks those log).
Nobody gets alert 1
The notification has to come after Assign To User; if there's no assigned user, HighLevel skips that step and keeps going. And each user needs a phone number set in HighLevel for SMS alerts.
No alert texts arrive at all
Ask HighLevel's support to check your texting setup, including your business texting registration (A2P 10DLC). HighLevel lists its fees on its A2P fees page (in the sources).
The after-hours alert shows up at 8 AM
There's a Time Window on workflow A's Settings tab, or an Advance Window on its Wait. Turn both off for this workflow.
The second name gets pinged even though the rep called in time
Workflow B didn't fire. Check it's published, Call Direction is outgoing, every Call Status is selected, Allow Re-entry is on, and the call went out through HighLevel.
Your website form doesn't start anything
Form Submitted works with forms built in HighLevel. A form from another tool needs an integration or a webhook first; ask HighLevel's support or whoever built your site.
The same person fills in the form twice and the second one isn't watched
Turn on Allow Re-entry in workflow A. HighLevel's help says a contact who's still in a workflow can't enter it again, so the second form inside the first 15 minutes rides on the first clock.
A repeat customer gets handed to a new rep
Turn on Only Apply To Unassigned Contacts in Assign To User.
Your team calls from a separate dialer
Those calls aren't in HighLevel unless they're brought in. HighLevel's Log External Call action can log them through a webhook, but its help doesn't say whether those logged calls fire the Call Details trigger, so test it before you count on it.
The list is full of spam and test forms
Take the tag off those so the real misses stand out. If spam is most of the list, fix the form.
The manager can't see the list
Smart lists belong to the user who made them. Make it under the manager's login, or share it from Manage Smart List.
The list gets long and nobody reads it
Then rule 2 isn't running. Put one name on reading it and a time on the rules sheet, and turn on the morning reminder.
The AI tells you where a setting is in your CRM
It can't see your CRM and may be guessing. Check with your CRM's support or its help pages before you click.
ChatGPT or Claude can't open the guide link
That's fine. Everything it needs is in the walkthrough prompt. Tell it to keep going without the link.

One name, one deadline, one list

“I thought you had it” is two people shrugging while your lead books somebody else. With one name on every form, a deadline and a list somebody actually reads, the miss shows up the next morning instead of in a lost job.

If you'd rather have a phone floor built around this, that's our call center buildout.

Checked on Oct 25, 2026 against

Every claim about a third-party tool in this guide (plans, prices, menu paths, commands, limits) was checked against these official pages on Oct 25, 2026. These screens change often: if something looks different, trust the page over this guide.

Rather skip the setup?

Want help setting this up?

Receipts Group builds these systems. Thirty minutes with Eric tells you which piece is worth building first, or that none of them are. The guides stay free either way.

Keep going

more free guides