Hopper Drop-Run Trigger explained

When a predictive campaign abandons a call — connects to a person but has no agent free — that lead gets a DROP status. Those are often your warmest misses: real people who answered. The Hopper Drop-Run Trigger is a one-shot button that says "forget the usual queue rules for one minute and go straight after the drops." Used right, it's a fast way to recover abandoned contacts. Used carelessly, it can re-dial people you just called.

What one run actually does

Turn it on and save the campaign, and the very next Hopper run ignores all your normal loading criteria. Instead of pulling by your usual dial statuses and order, it loads only DROP-status leads from the active lists — and it puts them in at the highest hopper priority, so they jump to the front of the line. It will also bump any DROP leads already in the queue up to that top priority.

The key word is single. After that one run, the setting flips itself back to N automatically. The next minute, hopper loading returns to normal and your regular rules take over. You don't have to remember to turn it off — it's a momentary override, not a mode you have to manage.

The -All Drops- checkbox

By itself the trigger targets the standard DROP status. If you also tick the -All Drops- checkbox, it widens the net to any Status (lead status) with "DROP" in the status code or name — system statuses and your own custom ones, inbound or outbound. That's handy if you've created drop-flavored dispositions and want them all swept up in the same run.

The warning you have to read

Here's the catch: this run does not check whether your lists have been reset. So if those DROP leads were called recently, you can end up calling them back sooner than you intended. For compliance and for the person on the other end, that matters — some regions limit how quickly you can re-attempt an abandoned call.

The safeguard is the Drop Lockout Time. If you've set that — say, a 72-hour cooldown after a drop — the trigger will honor it and skip leads still inside the window. So before you fire a drop run, make sure your lockout time reflects your rules. Pushing your drop rate down in the first place beats chasing drops after the fact, so treat this trigger as cleanup, not a strategy.

When to reach for it

It shines when a brief staffing crunch caused a cluster of drops and you've now got agents free to clean them up promptly — within your lockout rules. It's the wrong tool for routine work; for that, set up proper Lead recycling so re-attempts follow a schedule instead of a manual scramble. The bigger picture on pacing and abandonment lives in the VICIdial dialing strategies guide. If you'd rather have a platform that keeps drops low without manual interventions, our managed hosting is tuned for it — see pricing.