> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/the-hub/working-with-leads/configuring-qualifiers.md).

# Configuring qualifiers

Qualifiers are how reps capture structured data about leads at events — lead type, follow-up intent, budget, raffle entries, products of interest, quick notes, anything you want a rep to record in a single tap. You define **what qualifiers exist**, what type they are, and how they behave in **Lead Settings**.

This article covers configuring qualifiers. For applying qualifier values to leads during capture, see [How to use qualifiers to manage leads](/help-center/the-hub/working-with-leads/how-to-use-qualifiers-to-manage-leads.md). For mapping qualifier values to your CRM or Marketing Automation tool, see the per-integration Qualifiers tab.

## Where qualifiers live

In the Hub, **Lead Settings → General → Qualifiers**.

The Qualifiers section shows every qualifier in your organization with these properties at a glance: name, type, value count (for picklist-style qualifiers), scope, status, and an Actions menu. A **Mobile Preview** panel on the right shows what the current set of qualifiers looks like in the Mobly mobile app.

## The five qualifier types

Qualifiers come in five types. Pick the one that matches the shape of the data you need reps to capture.

* **Picklist** — a fixed set of options a rep picks from (e.g., Lead Type: Hot / Warm / Cold). Supports single- or multiple-select.
* **Open Text** — a free-text response (e.g., "What are they most interested in?"). Character limit is configurable.
* **Numeric** — a number, integer-only. Supports min/max bounds and a unit label like `$`, `%`, `mi`, or `seats`.
* **Boolean** — a yes/no answer. Renders as a two-choice picker (True/False by default, auto-adjusts to Yes/No if mapped to a CRM Yes/No field).
* **Note Activity** — a timestamped note attached to the lead's activity history for the current event or activation. Not stored as a field — it becomes an entry in the lead's activity feed.

{% hint style="warning" %}
**Type is set once and can't be changed.** Pick carefully at creation. If you need a different type later, create a new qualifier and archive the old one.
{% endhint %}

## Anatomy of a qualifier

Each qualifier has:

* **Name** — what the rep sees in the Mobly app (e.g., "Lead Type," "Budget," "Business Interest")
* **Type** — one of the five above
* **Values** (Picklist and Boolean only) — the discrete options
* **Character limit** (Open Text only) — how long a rep's response can be
* **Min / Max / Unit label** (Numeric only) — bounds and the label rendered next to the number
* **Required mode** — how strict the qualifier is (see below)
* **Scope** — **All Events** or **Specific Events**
* **Status** — **Active** or **Archived**

## Creating a qualifier

Two paths from **+ Add Qualifier**:

### Start from scratch

Pick a type, name it, configure values or bounds, set the required mode and scope, and save.

### Auto Create from CRM

If you have a supported CRM connected (Salesforce, HubSpot, Zoho, Marketo), pick **Auto Create** on the type-picker screen. You choose an object and a field in your CRM, and Mobly reads that field's type and pre-fills everything for you:

* Picklist fields → Picklist qualifier with the CRM's picklist options pre-loaded
* Number / currency / percent fields → Numeric qualifier
* Boolean fields → Boolean qualifier
* Text fields → Open Text qualifier (with the option to convert to Picklist or Boolean before saving)

This is a **one-time fast-path**, not a background sync. If the CRM field's options change later, you'll need to update the qualifier's values in Mobly manually. To match up with a different field later, use **Change field** from the modal footer.

Auto Create is per-qualifier — different qualifiers can be tied to different CRM fields (or none at all).

## The three tabs

When you create or edit a qualifier, the modal has three tabs:

* **Details** — name, values, character limit, numeric bounds. The "what does it capture" part.
* **Settings** — required mode, default value, event assignment. The "how does it behave" part.
* **Integration** — how the qualifier maps into your CRM. Send-as-activity toggle, multi-select separator, boolean label mapping. See [Qualifiers (CRM)](/help-center/integrations/crm/qualifiers.md) for the mapping details.

## Required mode — Off, Important, Require

A three-way control on the Settings tab:

* **Off** (default) — fully optional. No prompts. Reps fill in only when relevant.
* **Important** — a soft nudge. When a rep tries to save the lead without a value, they get a prompt asking if they want to add one. They can skip. The qualifier shows an orange **Important** badge in the mobile app.
* **Require** — hard requirement. Reps can't save the lead until they've picked a value. The qualifier shows a red **Required** badge.

Use **Require** sparingly — over-using it slows reps down and encourages arbitrary picks just to save the scan. **Important** is the middle ground for qualifiers you want reps to notice but not block on.

## Default value

Each type (except Note Activity) has an optional **Default value** on the Settings tab:

* **Picklist / Boolean** — pick which option is the default
* **Open Text** — a pre-filled string
* **Numeric** — a starting number, clamped to your min/max

Default values apply **on ingest and when syncing to your CRM** — they fill in for leads whose reps didn't pick a value. They **do not** pre-select the value on the mobile app. Reps still see the qualifier as unset until they interact with it.

## Single-select vs multiple-select (Picklist only)

For Picklist qualifiers, you pick a selection mode:

* **Single** — one value per lead. Forces clean data, easy to report on.
* **Multiple** — reps can pick more than one. Sends to your CRM as a delimited list.

Default to **Single** unless you have a clear reason to allow multiple. Multi values usually make sense for genuinely list-shaped data — Interests (product A, B, C), Content Requested, Follow-up Channels.

### What happens if a single-select qualifier gets two answers

The same lead can get scanned twice — by different reps, or the same rep at different moments. For **Single** picklists, you pick which value wins:

* **Last Value Wins** (the default) — the most recent answer overwrites. Use for "current status" qualifiers where the freshest read matters most.
* **First Value Wins** — the first answer is preserved; later ones are ignored. Use when the initial impression matters most.
* **Send All Values** — both answers are preserved and sent as a list. Rare — mostly when you want to capture disagreement between reps.

Set this per-qualifier on the Settings tab.

## Scope — All Events vs Specific Events

* **All Events** — the qualifier shows up at every event in your org. Use for org-wide qualifiers (Lead Type, Approval Status).
* **Specific Events** — the qualifier only shows up at events you assign it to. Use for event-specific qualifiers (Pickleball Raffle, ConfX Booth Demo). When the event is over, archive the qualifier without affecting others.

For per-event overrides at scale, see [How to configure qualifiers by event](/help-center/the-hub/managing-events/how-to-configure-qualifiers-by-event.md).

## Editing, duplicating, archiving, deleting

From the **Actions** menu on any qualifier row:

* **Edit** — opens the modal. Name, values, required mode, scope, integration mapping can all change. Type cannot.
* **Duplicate** — makes a copy named `<Name> (copy)`. Useful for spinning up event-specific variants of an org-wide qualifier.
* **Archive** — hides the qualifier from the Mobly app without deleting. Toggle the **Archived** filter at the top to see archived qualifiers; you can restore them.
* **Delete** — permanent. Individual **values** already applied to leads are locked from deletion (you'll see a lock icon and tooltip) — archive is usually safer than delete.

**Publishing**: newly-added qualifiers start as **Draft** so you can preview and tweak them before reps see them. Click **Publish** when ready. Once published, editing capability is more limited (you can't change the type, and you can't delete values that are already in use).

Reordering: drag the handle on any qualifier row (or any value row inside a qualifier) to change display order. Reps see qualifiers in this order on the mobile app.

## The Mobile Preview panel

The **Mobile Preview** on the right side of the Qualifiers table shows what your current qualifier set looks like inside the mobile app, rendered in a phone frame. It's live — as you add, edit, or reorder qualifiers, the preview updates.

Filter the preview to a specific event using the dropdown above the phone frame — useful for confirming that event-scoped qualifiers only show up where you intend them to.

The preview is **interactive**: you can tap picklist chips, use the numeric stepper, and open the Note Activity editor. Nothing you do in the preview persists — it's for visualizing the mobile UX only.

## Mapping qualifier values to your CRM or MA tool

After configuring a qualifier, the next step (if you sync to a CRM or MA tool) is mapping it. That's a per-integration step:

* For CRM mapping: [Qualifiers (CRM)](/help-center/integrations/crm/qualifiers.md) — also covers the Auto Create wizard, boolean label handling, and multi-select separators
* For MA mapping: [Qualifiers (Marketing Automation)](/help-center/integrations/marketing-automation/qualifiers.md)

Unmapped values trigger sync errors in the integration's Reconciliation tab — see [Reconciliation (CRM)](/help-center/integrations/crm/reconciliation.md) or [Reconciliation (MA)](/help-center/integrations/marketing-automation/reconciliation.md).

## Best practices

* **Pick the right type up front.** Type can't be changed. If you're not sure whether something should be Picklist or Open Text, ask what reporting you want downstream — Picklist wins for clean segmentation, Open Text wins for verbatim detail.
* **Keep picklists short.** 4–8 values. More than that and reps slow down.
* **Use Numeric for things you'll want to aggregate** — deal size, guest count, budget. Not for phone-like identifiers (use Open Text or map to a phone field instead).
* **Use Note Activity for context that changes** — objections raised, next steps, what the rep observed. Timestamped, event-scoped, lives in the activity feed.
* **Prefer Important over Require** for most nudges. Require is a real cost to rep speed; save it for the qualifiers your reporting truly can't tolerate empties on.
* **Match CRM picklists 1:1 where you can** — easier mapping, fewer surprises. Auto Create from CRM is the fastest way to guarantee alignment.
* **Archive obsolete qualifiers instead of deleting.** Lets you recover historical values if a customer asks "what did this lead get tagged with at SaaStr 2024?"
* **Review qualifiers quarterly.** Field marketing teams accumulate qualifiers quickly. A periodic clean-up keeps the rep experience tight.

## Related articles

* [How to use qualifiers to manage leads](/help-center/the-hub/working-with-leads/how-to-use-qualifiers-to-manage-leads.md) — applying qualifier values during capture, downstream use cases
* [How to add a qualifier to a lead](/help-center/the-mobly-app/working-with-a-lead/how-to-add-a-qualifier-to-a-lead.md) — the mobile rep flow
* [How to configure qualifiers by event](/help-center/the-hub/managing-events/how-to-configure-qualifiers-by-event.md) — per-event qualifier setup
* Per-integration qualifier mapping: [CRM](/help-center/integrations/crm/qualifiers.md) · [Marketing Automation](/help-center/integrations/marketing-automation/qualifiers.md)