The Ultimate Guide to GoHighLevel Database Reactivation (DBR) Workflows (2026) - GHL Logic

The Ultimate Guide to GoHighLevel Database Reactivation (DBR) Workflows (2026)

Quick answer: GoHighLevel database reactivation (DBR) is a campaign that texts and emails old leads and past customers to restart conversations. Only text contacts who gave consent, register A2P 10DLC, clean the list, send in small drip batches, use reply-based logic to sort interested contacts, and watch your opt-out rate after every batch.

Almost every business that has run for a year or two has a CRM full of people who went quiet. They asked for a quote, booked once, downloaded a guide, or bought two years ago and never came back. A database reactivation campaign, or DBR, is how you start those conversations again with a short text or email. It is one of the cheapest ways to fill a calendar, because you are not paying for new clicks.

It is also the fastest way we know to get a GoHighLevel sub-account restricted. Old lists are full of dead numbers, people who forgot they ever gave you their number, and people who will reply STOP the moment an unknown text lands. So this guide spends as much time on consent and opt-out safety as it does on the workflow itself. Honestly, the workflow is the easy part.

We updated this guide in November 2026 for three changes that matter for DBR: HighLevel’s new SMS safeguard thresholds, the FCC’s revised opt-out rules that take effect November 25, 2026, and the newer drip and split settings in workflows. Here is how we would build a DBR today, and where we think most tutorials cut corners.

What is a Database Reactivation (DBR)?

A database reactivation is a campaign that messages contacts already in your CRM who have gone quiet, such as old leads, unclosed quotes, no-shows, and past customers. You send a short, personal text or email that asks one simple question. People who reply move into a booking or sales path. Everyone else gets a few polite follow-ups, and then the campaign stops.

The idea is simple. The hard part is running it without breaking consent rules or burning your sender reputation, because a list that has been sitting for a year behaves very differently from fresh form leads.

Read this: The Ultimate Guide: GoHighLevel for Marketing Agencies (2026)

Before You Text Anyone: The Consent Check Most Guides Skip

Most DBR tutorials we found jump straight to the workflow builder. We start with one question for every segment: how did this person give us their number, and did they agree to get marketing texts from this business?

Under the US Telephone Consumer Protection Act (TCPA), marketing texts sent with automated tools generally need prior express written consent. Consent also belongs to the business that collected it. HighLevel’s own LC Phone messaging policy says consent can’t be bought, sold, or exchanged, so a purchased or borrowed list is off limits for SMS no matter how friendly the message is.

We are not lawyers and this is not legal advice. But this is the triage we run before any old list goes near a send button:

SegmentHow you got the numberOur call for SMS
Form leads who ticked an SMS consent boxOpt-in form with clear consent wordingUsually fine to text. Keep a record of the form and the date.
Past customers who gave a number for booking or billingA transaction, no marketing consentRisky for promo texts. Email first and ask if they want text updates.
Quote requests from a form with no SMS wordingForm without a consent checkboxEmail only until they opt in.
Contacts imported from an old CRM with no consent recordUnknownEmail only. No proof means no SMS.
Purchased, scraped, or shared listsA third partyDo not text them. Do not email them from your main domain either.
Anyone who replied STOP or is marked DNDConsent revokedNever. Not even for “one last offer.”

Federal law does not put an expiry date on consent, but old consent is weak in practice. A person who opted in three years ago and has not heard from you since is exactly the person most likely to hit “report junk.” Those reports and opt-outs feed the numbers that get accounts paused. When we are unsure about a segment, we send an email first that asks people to reply if they want texts, and we only text the people who say yes.

States can add their own rules on top of federal law. Florida’s telemarketing law, for example, limits these messages to 8 a.m. to 8 p.m. in the recipient’s time zone and to three on the same subject in 24 hours. If you text people in many states, ask your attorney which state rules apply to you.

What Changed in November 2026 for SMS Opt-Outs and Filtering

HighLevel’s new SMS safeguards

HighLevel published a changelog entry called Fewer SMS Restrictions, More Confidence in Messaging that rewrites how messaging restrictions work for a selected group of sub-accounts. Other sub-accounts stay on the existing safeguards, and the rules for brand new sub-accounts did not change. So before you plan volume, find out which set your account is on. Here is how the two compare, based on the changelog and HighLevel’s Restriction History help article:

RuleExisting safeguardsNew safeguards (selected sub-accounts)
Healthy rangeOpt-outs 0 to 1%, delivery errors 0 to 6%Same advice applies
WarningAim to stay under 2 to 3% opt-outsOpt-out rate above 4%, or carrier filtering above 15%
PauseLockout at 3% opt-outs or a 10% delivery error rateMay pause above 6% opt-outs or 25% carrier filtering
What counts as filteringAll delivery errors count toward the error rateOnly messages flagged with error 30007
Time windowNot stated in the help articleRolling last 7 days
Pause length24 hours12 hours, and agency owners can resume when eligible
One to one chatsStill work during a suspensionStill work during a bulk restriction

The new rules are more forgiving, and HighLevel says its own testing showed 80% fewer restrictions. Do not read that as permission to blast an old list. The same entry says very high opt-out or filtering rates can still lead to more pauses or a manual review. The rolling 7-day window also cuts both ways: one bad batch on Monday is still dragging your rate up on Friday.

A quick way to picture it: if you send 500 reactivation texts in a week, roughly 20 opt-outs puts you past the 4% warning line and roughly 30 puts you past the 6% pause line. On a stale list, that can happen in a single afternoon. That is why we always pilot small first. You can see every warning and lockout under Settings > Phone System > Messaging > Restriction History. Check it after each batch, not after the campaign ends.

This worry is not new. In a 2023 post in the GoHighLevel Skool community, a builder running his second reactivation asked what happens if 10 people opt out in the first 10 messages of a 200-message day, because the rules did not say when the check starts. The new 7-day window answers part of that, but the lesson stands: early opt-outs on a small sample are your warning light.

The FCC opt-out rules that start November 25, 2026

Separately, the FCC adopted a revised order on consent revocation (FCC 26-67). Law firm summaries, including this one from Kelley Drye and this breakdown of the November 25 start date, point out the parts that matter for a DBR:

  • A marketing opt-out still revokes all marketing from your business. A STOP on your DBR means no promo texts from any of your other campaigns either.
  • You must honor opt-outs within a reasonable time, and 10 business days is the outer limit. In GoHighLevel it should be instant, so do not build any delay.
  • If you make a reply text the only way to opt out, you must accept seven standard words: stop, quit, end, revoke, opt out, cancel, and unsubscribe.
  • Opting out of informational messages (like appointment reminders) no longer has to stop every other category, but keep promos out of reminder texts or they count as marketing.

Here is a gap we noticed while researching this update. HighLevel’s SMS compliance settings article lists STOP, STOPALL, CANCEL, UNSUBSCRIBE, END, and QUIT as the carrier opt-out words. “Revoke” and “opt out” are not on that list. Before you launch, text each of the seven FCC words from a test phone to your number and check whether the contact gets marked DND. If any word is not handled, add a small safety workflow: trigger on Customer Replied, filter for that word, set DND for SMS, and remove the contact from all workflows.

Preparing and Cleaning Your Cold Data List

Never import a raw export and send to everyone in it. A list that has been sitting for a year will have dead numbers, landlines, people who changed jobs, and duplicates. Every bad number adds to your error or filtering rate before a single real person even reads your message.

Email and Phone Number Verification

Turn on HighLevel’s Number Intelligence before you send. HighLevel’s SMS deliverability guide says it checks numbers before sending and puts a temporary DND on contacts who can’t receive texts, such as landlines. For email, run old addresses through a verification tool and drop hard bounces first. If you plan big email batches, set up a dedicated sending domain with SPF, DKIM, and DMARC; our Mailgun email setup service covers that.

Segmenting Your Data for Maximum Relevancy

Split the list by what the person actually did with you, because the message should change with it:

  • Past customers who have not bought in 6 months or more.
  • Quote requests that went silent after the estimate.
  • Lead magnet downloads who never booked a call.
  • No-shows who booked and then missed the appointment.

Before you import, add a consent column to the spreadsheet, for example “sms-consent-yes” or “email-only.” It takes an hour in a spreadsheet and saves you from texting the wrong segment later. Skip it and you end up guessing who said yes to texts.

Importing Cold Lists Safely into GoHighLevel

Go to Contacts, open the Import option, and upload your cleaned CSV. Map name, email, phone, and your consent column to the right fields. If you have notes from an old CRM, map them to a custom field so whoever answers a reply can see the history.

The Power of the Batch Tag

During import, add a unique tag such as dbr-2026-11-batch1. That tag is your undo button. If something goes wrong, you filter by it and pull everyone out of the workflow with one bulk action. Also tag the consent group, then build a smart list that shows only SMS-consented contacts who are not on DND. That smart list, not your whole CRM, is what you send from.

Building the Core DBR Workflow Architecture

Create a new workflow from scratch under Automation > Workflows and give it a clear name with the batch date. If you are new to the builder, our advanced workflow builder guide explains the newer actions.

Setting Up the Trigger Point

We still prefer no automatic trigger on the main DBR workflow. You add contacts with a bulk action from your smart list, so nothing fires until you decide. A Contact Tag Added trigger also works, and several popular guides use it. If you go that way, make sure no other automation can add the same tag by accident, and add a Drip action right after the trigger so pacing still applies. If your workflow does not fire when you expect, see our guide on GoHighLevel workflows not triggering.

Drafting the First SMS Step

Keep it short, personal, link-free, and say who you are. Here is the kind of first text we would write for a home services client:

Hi {{contact.first_name}}, it's Sam at [Business Name]. You asked us about a roof quote last spring. Is that still on your list this year? Reply STOP to opt out.

Why it is written that way:

  • It names the business. HighLevel’s deliverability guide recommends sender ID in the first text to each new contact.
  • It mentions the real past interaction, so it feels expected instead of random.
  • It asks a yes or no question, which is easy to answer from a lock screen.
  • It has no link. HighLevel’s guide says public shorteners like bit.ly are high risk and that AT&T blocks them outright.

If your SMS compliance toggles are on, HighLevel adds sender info and opt-out text to the first message of a conversation by itself, and skips it when your message already has complete opt-out wording. Test one message to your own phone so you do not end up with the opt-out line twice.

Picking a Low-Friction Offer

Asking a cold contact to buy a $5,000 package in the first text does not work. Good DBR offers are small, real, and easy to say yes to. A few patterns that fit different businesses:

  • A spare slot: “We had a cancellation for an AC tune-up Thursday afternoon. Want it?”
  • A useful update: “We put together updated pricing for kitchen remodels this year. Want me to email it over?”
  • A credit for past customers: “We are giving past customers a $50 credit on their next visit this month. Want me to add it to your account?”

Only use scarcity that is true. If you say “3 slots left,” have 3 slots. People on old lists are already skeptical, and a fake deadline is a quick way to earn a spam report.

Technical Delivery Control: The Drip Mode Action

HighLevel rebuilt Drip Mode for bulk actions. When you add contacts to the workflow in bulk, the drip settings are Start On, Batch Quantity (1 to 10,000), Repeat After, Send On (weekdays), Process Between (allowed hours), and End At. Progress is saved after every batch, and you can pause a running drip from Contacts > Bulk Actions.

Configuring Drip Schedules

Two details that most guides miss:

  • Process Between uses the account time zone, not each contact’s. If your account is on Eastern time and you allow 10 a.m. to 4 p.m., a West Coast contact gets your text at 7 a.m. Split batches by region or narrow the window.
  • Bulk drip and the workflow Drip action are different tools. The Drip action inside a workflow releases contacts in batches of 1 to 10,000 every 1 to 60 minutes, 1 to 24 hours, or 1 to 7 days. Use it when contacts enter by tag, so pacing holds even if someone tags 3,000 people at once.

How many per day? HighLevel does not publish a safe DBR volume, and anyone who quotes you an exact number is guessing. Published examples vary. CloseBot described its own DBR campaign as 50 contacts a day, one message every two minutes, 9 a.m. to 5 p.m. Monday to Saturday. A Skool community member shared that new reactivation batches did best for him at 10:30 to 11:00 a.m. on Tuesday to Thursday. That is one person’s experience, not a rule, but it is a sensible window to test.

Our own approach: start with a pilot of about 50 contacts, wait 48 hours, then check opt-outs, 30007 errors, and Restriction History. If everything looks clean, raise the batch size step by step. If opt-outs jump, stop and fix the message or the segment before you send another batch.

Implementing Real-Time Reply Capture and If/Else Logic

After the first SMS, add a Wait step set to wait for a contact reply, with a timeout of about two days. Then add an If/Else branch that splits people who replied from people who did not.

Read this: The Complete Guide to GoHighLevel CRM Setup (2026)

Designing the Intent Branch

  1. Step 1: Send the DBR text.
  2. Step 2: Wait for a reply, up to 2 days.
  3. Step 3, replied: tag dbr-replied, stop the follow-ups, alert a rep or hand off to an AI agent, and move the opportunity to an “Engaged” stage.
  4. Step 4, no reply: one follow-up text, then an email two to three days later, then end the workflow and tag dbr-no-response so the same people are not hit again next month.

Keep total touches low. Two to four is plenty for an old list. Every extra text to someone who did not reply is another chance for an opt-out.

Advanced Intent Filtering

Keyword filters (“yes,” “sure,” “interested”) handle the easy replies. Real replies are messier: “who is this?”, “maybe next month,” “wrong number.” We send anything that is not a clear yes to a person or an AI agent rather than trying to catch every phrase with filters. CloseBot’s write-up takes a similar approach: its AI agent answers questions, books demos, and tags angry contacts with “ai off” and “not interested” so it stops replying. If you want to try this, our GHL AI Employee guide covers the setup. Whatever you use, a “wrong number” reply should set DND right away.

Test Two Openers With the Split Action

HighLevel’s November 13, 2026 changelog added Even split and Weighted split to the Split action. For a DBR, put an Even split in front of the first SMS and test two openers on your pilot batch. Even split rotates contacts evenly, which a Random split does not promise. One catch: split settings lock once contacts enter, so decide before you publish.

Maximizing Deliverability: Compliance and Carrier Guidelines

Register A2P 10DLC First

If you text US numbers from a local 10DLC number, your brand and campaign need A2P registration, and US carriers block unregistered 10DLC traffic. Register before you build the DBR, because HighLevel says verification can take up to a week. Make sure your campaign use case covers marketing if your DBR includes offers. Our A2P 10DLC registration guide walks through it, and this guide covers rejected A2P campaigns. If you would rather hand it off, see our A2P 10DLC and Twilio setup service.

The Mandatory Opt-Out Safe Guard

Under Settings > Phone System > Messaging, turn on the opt-out message and sender information toggles. If your DBR runs for weeks, also turn on periodic opt-out and sender info, which re-adds them every 1 to 60 days. Then run the seven-word STOP test from the FCC section above. HighLevel stops future texts to anyone it marks as opted out, so the main job is making sure every opt-out word is caught.

Avoiding Filtering Red Flags

  • No public link shorteners. Use your own branded domain and no more than one redirect.
  • No link at all in the first text. Send it after the person replies and asks.
  • Avoid all caps, lots of exclamation marks, and spammy words like “FREE” or “ACT NOW.”
  • Do not rotate the same message across many numbers to dodge limits. Carriers treat that as snowshoeing.
  • Watch for error 30007. Under the new safeguards, these are the messages that count toward your filtering rate.

If you see a cluster of 30007 errors in one batch, pause the drip and rewrite the message. Sending more of the same text rarely fixes filtering.

Analyzing DBR Performance Metrics

Once the drip is running, open the workflow and check its execution logs to see who got each step. Pair that with Restriction History under your messaging settings. The numbers we track for every batch:

  • Delivery rate: how many texts actually arrived. Falling delivery usually means dirty data or filtering.
  • Opt-out rate: HighLevel calls 0 to 1% good. Watch this more than anything else.
  • 30007 count: carrier filtering, the number the new safeguards measure.
  • Reply rate: the share of contacts who texted back.
  • Booked calls or sales: the only number that pays the bills.

We do not give a target reply rate, because it swings a lot by industry, list age, and offer. Compare batch to batch inside your own account. If opt-outs climb, pause, fix the message or the segment, and restart with a fresh small batch.

Common DBR Mistakes We See

  • Texting the whole CRM, including email-only and no-consent contacts.
  • Forgetting to exclude DND contacts from the smart list.
  • Putting a link, especially a bit.ly link, in the first message.
  • Leaving “Stop on Response” off, so follow-ups go out after someone already replied.
  • Using a tag trigger that another automation also adds, which sends the DBR to people you never meant to reach.
  • Setting the drip window without checking the account time zone.
  • Running the same DBR on the same list every month. Give people a few months between attempts.

Aaron Beadles’ YouTube video Ultimate Guide: Database Reactivation + A2P, Email, and Domain Setup in GoHighLevel pairs DBR with A2P, email, and domain setup in a single tutorial, and that pairing is right. A reactivation is only as safe as the messaging setup underneath it.

Related guides: GoHighLevel Services and GoHighLevel for Industries.

Frequently Asked Questions (FAQ)

What is the best offer format for a GoHighLevel database reactivation?

The most effective offer format is a short, conversational question that promises high immediate value with zero friction. Avoid sales pitches. Instead, ask a simple question about a free voucher, an educational PDF guide, or a last-minute open booking slot.

How many text messages should I send per day in a DBR campaign?

For cold databases, you should limit your delivery speed to 10 to 15 text messages per hour using GoHighLevel’s drip mode. Sending more than 150 to 200 messages per day from a single unverified standard number increases the risk of carrier filtering.

How does GoHighLevel’s “Stop on Response” feature work in a DBR workflow?

When you enable “Stop on Response” in the workflow settings panel, the system will instantly freeze the automation sequence for an individual contact the moment they reply. This prevents the system from sending follow-up automated prompts after a lead has already engaged.

Can I run a database reactivation campaign entirely over email?

Yes. While text messaging yields higher open and reply rates, you can execute DBR campaigns via email. Ensure your sending domain has perfect SPF, DKIM, and DMARC authentication records in place before blasting a large historical database list.

What should I do if a contact replies with an angry message during a DBR?

Your workflow should include negative intent logic. If a lead replies with negative phrases, GoHighLevel can automatically remove them from marketing funnels, apply a “Do Not Contact” tag, and archive the chat thread to keep your database clean.

Final Summary: Opening up Your Hidden Capital

A database reactivation can turn an idle CRM into booked calls without new ad spend, but on an old list the risk sits mostly in compliance, not in the workflow. Check consent by segment, register A2P, clean and tag the list, test all seven opt-out words, pilot 50 contacts, then scale slowly while watching opt-outs and 30007 errors. Do that, and HighLevel’s trigger, wait, and branch tools do the rest.

Ready to Launch Your Database Reactivation Campaign?

If you would rather not risk your phone numbers on a first attempt, our certified team can clean and segment your list, set up A2P and compliance settings, and build the DBR workflow with reply handling. See our GoHighLevel expert cost guide for typical pricing, or book a free 30 minute consultation and we will look at your list with you.

Want this done for you?

Our certified GoHighLevel experts can set it up for you, usually in 2 to 4 weeks with 30 days of free support. See our GoHighLevel workflow automation service.

Book a Free Consultation

Similar Posts

One Comment

Leave a Reply

Your email address will not be published. Required fields are marked *