Database Reactivation: Win Back Dead Leads in GoHighLevel

Database reactivation in GoHighLevel turns the contacts already sitting in your CRM into booked appointments, without spending a cent on new ad traffic. This guide covers what a reactivation campaign is, how to segment the list so you only message the right people, the exact workflow to build, the SMS compliance rules that keep you safe, and how to measure replies and booked calls.

What is a database reactivation campaign and why is it the cheapest lead source?

A database reactivation, often shortened to DBR, is a campaign that re-engages leads and customers you already have in your GoHighLevel account but who have gone quiet. These are old form fills, quote requests that never closed, lapsed customers, and no-shows. They already raised their hand once, so they are warmer than a stranger seeing your ad for the first time.

The reason the existing list is the cheapest lead source is that you have already paid to acquire it. The ad spend, the referral, or the walk-in that first put those contacts in your CRM is a sunk cost. A reactivation campaign spends only a few cents in SMS and email fees to reach hundreds or thousands of those contacts at once, which is why agencies run DBR as a fast win for a new client before any new lead generation is even switched on.

The mechanics are close cousins of two systems we cover elsewhere: our speed to lead workflow handles brand-new inbound leads in seconds, and our missed call text-back setup catches calls you cannot answer. Database reactivation applies the same conversational SMS logic to the leads already on the books.

How do you segment your list for a reactivation campaign?

Segmentation is the step that separates a professional DBR from a spray-and-pray blast that gets you spam complaints. In GoHighLevel you build a Smart List under Contacts, then apply filters so only genuine, contactable people enter the campaign. The goal is to include people who opted in and have gone cold, and to exclude anyone you should not message.

Use filters on Last Activity date, Tags, and Pipeline Stage, and always exclude DND contacts and anyone currently in an active opportunity so you do not text a live deal. The table below shows a practical segment definition you can copy.

Save the Smart List with a clear name such as DBR July 2026. Review the count before you send. If the list is large, message it in smaller batches over a few days so replies stay manageable and your sending number is not flagged for a sudden volume spike.

How do you build the reactivation workflow in GoHighLevel?

The build is one workflow that opens a conversation, listens for a reply, and branches based on whether the contact answers. Here is the step-by-step in the workflow builder.

1. Go to Automations > Workflows and click + Create Workflow, then Start from Scratch.
2. Add the trigger. The two reliable methods are a Contact Tag trigger that fires when you add a tag such as dbr-active in bulk, or leaving the trigger open and using bulk add to workflow from your Smart List. Both let you control exactly who enters and when.
3. Add a Send SMS action as the first step. Write a short, conversational opener with a merge field like {{contact.first_name}} that invites a reply instead of pitching. The aim is a human question, not an offer.
4. Add a Wait action set to wait for a reply event, or an If/Else with the condition Customer Replied. This is the fork in the road.
5. On the replied branch, hand the conversation off. Either route it to Conversation AI to qualify and book automatically, or assign the contact to a rep and create a task or opportunity so a human follows up fast.
6. On the no reply branch, add a Wait of two to three days, then a second, softer SMS nudge. Wait again, then send a final check-in that makes opting out easy.
7. Add an If/Else early in the workflow on whether a mobile number exists. Contacts without a mobile go down an email variant branch that carries the same message in a Send Email action.
8. Publish the workflow, then run one test contact through it end to end before you bulk-add the real list.

A conversational opener that earns replies looks like a text from a person, not a broadcast:

Hi {{contact.first_name}}, it is [Your Name] over at [Business Name]. We spoke a while back about [service]. Are you still looking for help with that, or should I close out your file?

That last line gives an easy out, which keeps complaints down and actually lifts reply rates because it reads as genuine. The whole system sits inside the broader patterns in our GoHighLevel automation workflows guide, and the reply handling is covered in depth in our Conversation AI guide.

A simple day-by-day cadence keeps the campaign polite and effective:

What are the SMS compliance rules for a reactivation campaign?

This is the part that protects your account and your client, so treat it as non-negotiable. A reactivation campaign only messages people who previously opted in to hear from that business. You cannot legally text a purchased or scraped list, and doing so risks carrier bans and complaints that can get a sending number shut down.

• Only message opted-in contacts. Reactivate people who gave the business their number for a reason. Never import and text a bought list.
• Honor DND and unsubscribe. Exclude DND contacts in your Smart List, and make sure any reply that asks to stop immediately marks the contact DND. GoHighLevel handles standard opt-out keywords, but confirm they are working.
• Register for A2P 10DLC. US application-to-person SMS must be registered so carriers deliver your messages. If you have not done this, follow our GoHighLevel A2P registration guide before you send a single reactivation text.
• Respect quiet hours. Send during normal daytime hours in the contact's local time zone, commonly between 8 in the morning and 9 at night. Use the workflow's window or wait steps so no text lands at 2am.
• Identify the business. Say who you are in the first message. A vague text from an unknown number reads as spam and gets reported.

Getting this right is not just legal hygiene, it is what keeps your delivery rates high. Carriers reward senders with clean opt-in practices and low complaint rates, so compliance and results point in the same direction.

How do you measure replies and booked appointments?

The two numbers that matter for a DBR are how many people replied and how many booked. Everything else is noise. GoHighLevel gives you the data to track both without guessing.

• Workflow history: open the workflow and check the execution log to confirm how many contacts entered, how many hit the replied branch, and where people dropped off.
• Conversations view: the inbox shows every reply thread, so you can see live conversations and jump in when Conversation AI or a rep hands one over.
• Opportunities and calendar: count booked appointments by watching new opportunities created from the campaign and confirmed calendar bookings tied to those contacts.

Rather than chase invented benchmarks, judge the campaign against its own baseline. Track reply count and booked count per batch, then compare batches as you refine the opener and the cadence. The table below frames what to watch at each stage.

For where this fits in the wider platform and what it costs to run, see our GoHighLevel review and the current pricing page.

GoHighLevel's 30-day extended trial gives full access to Smart Lists, the workflow builder, SMS and email sending, and Conversation AI, so you can build and test an entire reactivation campaign before you pay. Start with one clean, opted-in segment, send a genuine conversational opener, and turn contacts you already own into booked appointments.