Qualification Rules

Qualification determines whether a contact meets a playbook's requirements before delivery. There are two layers: disqualification conditionals (playbook-level business rules) and field qualification (delivery endpoint-level value mapping).

Disqualification Conditionals

DQ conditionals are playbook-level rules that immediately disqualify a contact if matched. These represent business logic decisions — for example, rejecting contacts under 18 or contacts with a bankruptcy on record.

Adding DQ Rules

Navigate to the Qualification tab on a playbook and add rules using the conditional rules builder.

Each rule has:

• Active — Toggle individual rules on or off
• Conditions — Field, operator, and value (same conditional system as routing rules)
• Logic — Combine multiple conditions with AND/OR operators

If any active DQ rule matches, the contact is disqualified with a reason indicating which rule matched.

Supported Operators

Field Qualification

Field qualification happens at the delivery endpoint level, not the playbook level. When building a payload for delivery, each field can specify:

• Accepted Values — Values the client accepts. The LLM maps free-text contact answers to the closest match.
• Value Sets — A shared set of accepted values for large lists
• Formatting Instructions — LLM formatting guidance (e.g., "Add 1 to front of phone number if missing")
• Required — If enabled, a missing field disqualifies the contact

See Delivery Endpoints for details on payload configuration.

Qualification Modes

Full Qualification (Default)

Used when no first submission action is configured, or for manual delivery and repost flows:

1. Check all required fields — missing required fields disqualify
2. Qualify each field against accepted values using AI
3. Evaluate DQ conditionals
4. Build the delivery payload

Soft Qualification

Used when a First Submission Action is enabled:

1. Only DQ conditionals are checked (hard stops)
2. Missing fields are allowed — they will be collected during the first submission action
3. The contact proceeds to the AI agent, webhook, or review step to gather remaining data

Qualification Flow

Contact Submitted
    |
    v
Routing Rules (if Auto Routing enabled)
    |
    v
DQ Conditionals --- Match? ---> Disqualified
    |
    No match
    |
    v
First Submission Action? --- Yes ---> Soft qualified, proceed to action
    |
    No
    |
    v
Required Fields Check --- Missing? ---> Disqualified
    |
    All present
    |
    v
Field Qualification (AI) --- Unmappable? ---> Disqualified
    |
    All mapped
    |
    v
Build Payload ---> Check Delivery Settings ---> Deliver