Build Failed Payment and Review Alerts in HighLevel
A failed payment, a new review, or a flagged contact only helps if a specific person sees it and knows what to check. This walkthrough builds 3 HighLevel workflows that each send 1 internal email to a named teammate and stop there.
Don't have a HighLevel account yet? Start a trial and build these alerts in your own account.
Paid link
Each workflow has an event that starts it, a person who receives the alert, and an action that person takes. None of them message the customer, reply in public, or delete a record. The automation's job ends when the right person has the signal, and the decision stays with your team.
Check what HighLevel can detect
Before building, the walkthrough searched the trigger list for an unfinished form. There isn't one. Form Submitted fires when someone finishes and submits a form, and Order Form Submission belongs to the order form process. Neither tells you someone opened a form and left, so the build skips form recovery and sticks to events the account supports.
Workflow 1: failed payment to a billing reviewer
- Create a workflow from scratch and give it a clear name, such as Leak: Payment Failed
- Add the Payment Received trigger, open Add filters, and set Payment Status to Failed1
- Leave the other filters, such as Source, unset unless you need to narrow the payments
- Add an Internal Notification action named Notify Billing Reviewer, with Email as the type
- Leave From Email blank so the account's default sending settings apply2
- Set To User Type to Particular User, pick the person who reviews billing, and leave contact followers off
- Write the subject and body, save, and end the path after this 1 alert
The trigger's name is misleading on its own. Payment Received covers successful and failed results, and the Payment Status filter is what makes this workflow respond to a failure.
The alert includes the contact's full name and email as merge fields so the reviewer can find the record. Then it tells them what to do: check the transaction and the related invoice, order, or subscription, confirm the current balance before contacting the customer, and log the outcome. The balance check matters because the event describes 1 failed attempt, not where the account stands now. Another payment may already have cleared it.
Workflow 2: new review to the review owner
Use the New Review Received trigger and leave its filters open to catch every new review, or filter by rating and review source to narrow it.3 It's a different trigger from Video Testimonial Received, which belongs to a separate submission process.
The review event is contactless. A reviewer's public name doesn't link to a CRM contact, and it doesn't give you permission to email them.3 So this workflow sends no thank-you email and guesses no address. The Internal Notification goes to a Particular User, the person responsible for reputation, because Assigned User depends on a contact this event doesn't supply.2
Keep contact merge fields out of the body. The message tells the reviewer to open Reputation, check the source, rating, and wording, and decide whether a public response or internal follow-up is needed. Its last line states that the workflow sends no customer message or public reply.
Workflow 3: flagged contact to a reviewer
Use the Contact Tag trigger with a Tag Added filter for 1 exact tag, chat_widget_high_volume_flag in the walkthrough. Search the tag library first and select the existing tag, so the signal isn't split across 2 spellings. A removed tag is a different event, and any tag change would be too broad.
Creating the tag doesn't turn on chat widget spam detection or apply the flag to anyone. Contacts that already carry the tag don't enter when you publish the workflow. Only a new application of the tag starts a run.
The alert names the tag and the contact, then asks the reviewer to read the contact record and the recent conversation before deciding anything, to avoid messaging or deleting the contact because of the flag alone, and to log the decision. High volume can have more than 1 explanation, and a tag doesn't prove fraud.
Where each workflow stops
Each path ends after its 1 internal notification. That limits what a run does. It doesn't:
- Charge a card, stop processor retries, or recover a payment
- Assign a task or track whether the review gets done
- Confirm that the alert email arrived
- Stop another qualifying event from starting a new run
- Pause other workflows or change messaging permission
Follow-through belongs in your team's routine: who reads these alerts, how fast, and where they log the outcome.
Who this is not for
- Businesses that want automated dunning emails sent to customers after a failed charge
- Teams without a named person for billing, reputation, or account review
- Accounts that need unfinished-form recovery, since no form trigger detects an abandoned form
- Reputation setups that want automatic public replies to reviews
Questions people ask about this
Answers from the build in this walkthrough, checked against HighLevel's help center. Last reviewed November 20, 2026.
- How do I get alerted when a payment fails in HighLevel?
- Build a workflow with the Payment Received trigger, filter Payment Status to Failed, and add an Internal Notification action that emails a Particular User. Have the alert tell them to confirm the current balance before contacting the customer.
- Why doesn't the review alert include the reviewer's contact details?
- The New Review Received trigger is contactless, so the review isn't linked to a CRM contact. Contact merge fields have nothing to fill, and a public name isn't permission to email someone.
- Should I send these alerts to the Assigned User?
- Not for contactless events. Assigned User sends only when the workflow has a contact with an assigned user. Particular User always reaches the teammate you pick.
- Can HighLevel start a workflow when someone abandons a form?
- Not with the form triggers checked in the walkthrough. Form Submitted fires only after a completed submission, so an unfinished form has no event to start a workflow.
- Will contacts who already have the flag tag enter the workflow?
- No. The Contact Tag trigger with Tag Added starts a run when the tag is newly applied. Contacts that carried it before the workflow was published don't enter.
- Does ending the workflow stop a failed payment from retrying?
- No. Ending the path only limits what this workflow does. Processor retries, other workflows, and other qualifying events are unaffected.
Ready to build this in HighLevel?
Every step in this walkthrough runs inside HighLevel
Paid link
We may earn a commission when you sign up through this link, at no cost to you. Full disclosure.
Try this and Sell More
The class, mapped
Original diagrams built from this session: the order the work runs in, what each stage owes the next, and the list to work against once the video ends.
The internal alert pattern
- 1HighLevel
Event fires
Payment Received filtered to Failed, New Review Received, or a specific tag added
- 2Workflow
Internal Notification
1 email to a Particular User, never to the customer
- 3Reviewer
Inspect the source
The transaction, review, or conversation, before any action
- 4Reviewer
Decide and log
Contact, reply, or follow up internally, then record the outcome
Internal alert build checklist
Build
- Payment Received filtered to Payment Status Failed
- New Review Received with no contact merge fields
- Contact Tag trigger set to 1 exact tag added
- Each alert sent to a Particular User with followers off
Before you publish
- Each alert tells the reviewer what to check first
- No customer email, public reply, or delete action on any path
- Each path ends after its 1 notification
- A named person owns each alert in your team's routine
Keep going
Related training
Same pillar, same problem, different angle
Share the library
Send it to the one person on your team who needs it
The training is free and open to all. Sharing is how the operator beside you stops guessing too.
Share the site
No login, no email gate. Watch, use it, pass it on.

