How qualification works

SalesMarketing

Before someone lands on a host's calendar, Preb can check who they are and what they answered on your booking form — then decide whether to let them book and, if so, who should take the call. This page explains how that decision is made so the rest of the routing section makes sense.

The qualification model

Qualification in Preb is built from simple if-this, then-that rules that look at what a person enters in the first step of your booking form. There are two kinds of rule, and they do opposite jobs:

  • Disqualification rules turn people away — a lead who matches one is stopped before they can pick a time. See Disqualification rules.
  • Routing rules point people at the right host — a lead who matches one only sees availability for the hosts you chose. See Conditional routing.

There is no separate "qualified" list to maintain. A lead qualifies by default — they're allowed through unless a disqualification rule says otherwise. You only ever write rules for the exceptions you care about.

What a rule looks at

Rules read the details a visitor gives you in step one of the booking form — their name, email, and phone number, plus any custom questions you've added — along with their email domain, the country of their phone number, and where they came from (your UTM tracking). They never need anything you have to look up by hand.

Where rules run

Both kinds of rule are checked when the visitor finishes step one and clicks Continue — the moment they hand over their details and ask to see times. They are not checked while someone is still typing, so a half-finished email never trips a rule by accident.

Everything is decided on Preb's servers, not in the visitor's browser. That matters most for routing: even though the booking page only shows the times for the hosts a lead was routed to, Preb re-checks the routing rules again when the booking is actually submitted, so the booking can only land with a host the rules allow. (Disqualification, by contrast, shapes the booking experience but isn't a hard lock at submission — treat it as a filter that turns the right people away, not a security gate.)

Contacts created along the way

As soon as someone completes step one, Preb saves them as a contact in your pipeline — even if they're about to be disqualified. Nothing is lost.

  • A lead who is disqualified is recorded with a Disqualified status, and (if you wrote one) an internal reason you can see in the pipeline. That reason is for your team only — the visitor never sees it.
  • A lead who is blocked by your email rules (for example, a personal Gmail address when you only allow work emails) is turned away too, but is not marked Disqualified — those addresses don't clutter your pipeline with a disqualified label.

For more on contact statuses, see Statuses & stages.

Order of evaluation

When a visitor clicks Continue, Preb works through the checks in a fixed order and stops at the first one that applies:

Disqualification rules run first

Your disqualification rules are checked top to bottom. The first rule the lead matches wins, and they're turned away — no further checks happen.

Routing rules run next

If the lead wasn't disqualified, routing rules are checked (on team events that use Conversion Routing). Again, the first matching rule wins and decides which hosts they'll see. If no routing rule matches, the whole host pool is considered.

The lead sees their times

A qualified lead moves on to step two and picks a slot from the hosts they're eligible for.

First match wins — so order matters

Within each list, rules are read from the top down and the first one that matches is the only one that fires — matches don't stack. Put your most specific rules at the top and your broad catch-alls at the bottom. You can drag rules to reorder them on both the Disqualification and Routing screens.