Disqualification on Shield signals is available if Shield is turned ON in the Event – Data Intelligence section, and applies once Shield returns a result for the visitor (or, if you've enabled it, when Shield is unavailable).

All visitors that meet your criteria will be disqualified as per the Disqualification rules set in your event. Because Shield screens the visitor on page load, it can block a suspicious visitor before they ever take a slot on your calendar — which is the whole point of the feature: keeping bots, spammers, and fraudulent bookers off your closers' schedules.

Disqualification is available on all plans, including Startup and Growth.

Think of Shield disqualification in three tiers of severity:

These signals almost never come from a real buyer, so a single "Yes" is usually enough to disqualify:

These are better used in combination (see Best Practices) or to redirect rather than hard-block, since legitimate people sometimes trip them:

Use the "Disqualify when Shield is unavailable" checkbox if you'd rather fail closed than let unscreened visitors book (remember an empty wallet counts as unavailable).

Conditional routing on Shield signals is available if Shield is turned ON in the Event – Data Intelligence section, and applies once Shield returns a result for the visitor.

All visitors that meet your criteria will be routed to specific closers as per the Conditional Routing rules set in your event. Routing is the softer companion to disqualification: instead of blocking a flagged-but-allowed visitor, you send them somewhere appropriate.

Conditional routing on Shield fields requires the Business plan. On Startup and Growth, Shield signals are available for disqualification but not for routing.

Common ways teams route on Shield signals:

No single signal tells the whole story. Real buyers occasionally trip one flag (a privacy-conscious user on a VPN, someone in incognito mode), while sophisticated bad actors try to look clean on the surface.

The reliable approach is to cross-check signals — look for a risk flag confirmed by a second, independent one before you block.

The rule of thumb:

Hard signals (emulator, Frida, cloned app, MITM, anti-detect browser) can stand alone.

These pairings rarely occur together for a genuine buyer, so they make strong disqualification rules:

These are strong enough that a single "Yes" justifies a hard block, because they almost never appear for legitimate visitors:

These are common enough among real people that blocking on them alone will cost you good leads. Use them to confirm another flag, or to route rather than disqualify:

A sensible starting configuration for a high-ticket scheduler:

Shield does not change the logic of the Multi-Booking feature.

The event's Disqualification or Conditional Routing conditions take priority when turned on.

Shield usage appears as its own line in the tokens/credits usage breakdown, and clicking it opens the Shield logs with per-check results, credits/tokens consumed, and timestamps.

An empty wallet counts as Shield being unavailable. If "Disqualify when Shield is unavailable" is off, bookings still complete (without a Shield result); if it's on, visitors are disqualified until the wallet is topped up.

Turn on auto-recharge in Settings → Billing to avoid interruptions.

No. Shield charges once per visitor and caches the result for 7 days.

Within that window a returning visitor reuses the cached result at no additional charge. A re-check (and new charge) only happens if the 7-day window lapses, the cache is cleared, or the visitor's device changes.

Shield screens visitors on your public booking page, including Lift.

It runs when enabled at both the account and event level.

Bots, spammers, and fraudulent bookers.

Shield fingerprints each visitor's device and network to spot the tools bad actors use to fake being a real prospect — automated bots, emulators and virtual machines, VPNs/proxies and Tor, spoofed locations, tampered or jailbroken devices, and known-bad IPs.

You can then block those sessions before they take a slot on your closers' calendars.

It's Shield's overall internal health-scoring system. Behind the scenes it weighs many device and network factors together to judge how likely the visitor is to be genuine.

It's expressed as Low (< 0.5), Medium (0.5 to < 0.8), or High (≥ 0.8) — higher means more trustworthy.

Use it as a quick summary signal, ideally cross-checked with Suspect score or Bot result.

Almost always this is a single "soft" signal being used as a standalone block — most often VPN detected, Incognito, or Privacy settings, all of which privacy-conscious real people trigger routinely.

Open that contact's Fingerprint tab to see which signal fired. The fix is to require a second, confirming signal before disqualifying (see Best Practices — Combining Signals) rather than blocking on one soft flag alone.

For the Yes/No flags, Yes means the risk condition is present (e.g. VPN detected = Yes means a VPN is in use).

For the confidence-style levels it depends on the signal: for VPN confidence / Proxy confidence, High means Shield is very sure that VPN/proxy is present (riskier).

But for the overall Confidence score, High means the visitor is very likely genuine (safer).

When in doubt, check the Shield Signals table above.

The five to watch:

example case: VPN + Country
You're a US business and your ICP is US based only - spam isolated to VPN-on bookings from a specific set of countries → they blocked VPN + those countries together.