> 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/conditional-qualifiers.md).

# Conditional qualifiers (follow-ups)

A qualifier doesn't have to show up every time. You can have it appear only *after* another qualifier gets a particular answer — so a rep sees a short list that grows based on what they're actually hearing, instead of a wall of questions that mostly don't apply.

A qualifier revealed this way is a **follow-up**.

> *Interested in a demo?* → **Yes** reveals *When are you looking to evaluate?* and *Who else is involved?* Answer **No** and neither one appears.

This article covers setting up and troubleshooting follow-ups. For qualifier basics — types, required mode, scope, CRM mapping — see [Configuring qualifiers](https://help.getmobly.com/help-center/the-hub/working-with-leads/configuring-qualifiers.md).

## Two ways to set it up

The relationship is the same either way — pick whichever direction you're already thinking in.

### From the triggering qualifier (usually easier)

Open the qualifier that asks the branching question. On the **Details** tab you'll see a follow-up pill:

* **Picklist** — one pill per value, in the Values table. Each value gets its own follow-ups, so *Hot* can reveal different questions than *Cold*.
* **Boolean** — one pill per label (True / False).
* **Open Text / Numeric** — a single **Once answered** pill, since there are no values to branch on.

Click a pill to link an existing qualifier, or **Create new follow-up** to build one on the spot. The popover lists what's already attached; the **×** next to a name stops showing it for that answer.

{% hint style="info" %}
**Save the qualifier before adding follow-ups.** The pills are inactive while you're still creating it — you'll see *"Save to add follow-ups."* Save once, reopen, then attach.
{% endhint %}

### From the follow-up itself

Open the qualifier you want to hide. On the **Settings** tab, under **Display Conditions**, turn on **Only show after a specific answer**, then:

1. **Choose the qualifier** whose answer should reveal this one. The picker is searchable, and qualifiers still in Draft are tagged so you know they aren't live yet.
2. **Choose which answers trigger it** — tap one or more values from the parent. For an Open Text or Numeric parent you'll see a fixed **Any answer** chip instead, because there's no value list to pick from.

The toggle is greyed out if you don't have an eligible qualifier to point at yet. **Note Activity qualifiers can't trigger a follow-up** — every other type can.

## Rules worth knowing

* **One trigger per qualifier.** A follow-up depends on exactly one parent, not several.
* **Chains work.** A reveals B, B reveals C. Each link is its own condition.
* **Loops are blocked.** Mobly rejects a condition that would make two qualifiers depend on each other and names the pair causing it.
* **The edit modal lists dependents.** If other qualifiers are revealed by the one you're editing, you'll see them called out — check this before you archive or rework it.

## What reps see

On mobile, a parent and its revealed follow-ups group together in a tinted band, and follow-ups animate in as the trigger answer is given. Reps don't have to hunt for what just appeared.

{% hint style="info" %}
**Hidden follow-ups never block a save.** A follow-up marked **Require** only blocks saving when it's actually visible. If the trigger answer isn't given, the follow-up stays hidden and the rep can save normally — a required follow-up won't trap them on a question that doesn't apply.
{% endhint %}

{% hint style="warning" %}
**Changing the trigger answer clears the follow-up's answer.** If a rep answers the follow-up and then goes back and changes the parent so the follow-up no longer applies, Mobly clears the follow-up's answer rather than keeping an orphaned response to a question that's no longer being asked.
{% endhint %}

## If a follow-up is always showing

Four causes, all fixable in settings:

* **Its trigger value was deleted.** If someone deleted the picklist value this follow-up keyed on and chose to clear it rather than move those leads to a replacement, the follow-up loses its only trigger and starts showing on every lead. Point it at a different value. See [Deleting a qualifier value](https://help.getmobly.com/help-center/the-hub/working-with-leads/configuring-qualifiers.md#deleting-a-qualifier-value).
* **The trigger isn't assigned to that event.** A follow-up whose parent isn't present at an event has nothing to wait for, so it shows unconditionally. If the parent is scoped to **Specific Events**, make sure every event using the follow-up also has the parent. See the Scope section in [Configuring qualifiers](https://help.getmobly.com/help-center/the-hub/working-with-leads/configuring-qualifiers.md).
* **The trigger was converted to an activity.** Activities can't reveal follow-ups. If you turn on **Send as activity** for a qualifier that other qualifiers depend on, Mobly warns you by name and those follow-ups become always shown.
* **The trigger was archived.** Archiving clears the display conditions pointing at it, which releases its follow-ups. Re-link them to a new trigger, or archive them too.

## Checking your work before you publish

The [Mobile Preview](https://help.getmobly.com/help-center/the-hub/working-with-leads/configuring-qualifiers.md#the-mobile-preview-panel) panel honors display conditions. Answer a qualifier in the preview and its follow-ups appear, grouped and labeled, exactly as a rep would see them — the fastest way to walk a branch before reps do.

Filter the preview to a specific event while you're there. That catches the most common setup mistake: a follow-up assigned to an event its trigger isn't on.

## Designing a good follow-up set

* **Lead with the branching question.** The qualifier that routes the conversation should come first in your order — reps answer top to bottom.
* **Keep chains shallow.** Two levels is usually plenty. Three or more gets hard to reason about when you're auditing why a qualifier didn't appear.
* **Require the parent, not the follow-up.** If the branch itself is mandatory, put **Require** on the parent. Marking a follow-up required only matters once it's visible.
* **Use follow-ups instead of a long flat list.** If half your qualifiers only apply to some conversations, put them behind a condition. Reps see a short list that grows only when it's relevant, and your data gets cleaner because nobody's guessing at questions that don't apply.

## Related articles

* [Configuring qualifiers](https://help.getmobly.com/help-center/the-hub/working-with-leads/configuring-qualifiers.md) — types, required mode, scope, and the rest of qualifier setup
* [How to configure qualifiers by event](https://help.getmobly.com/help-center/the-hub/managing-events/how-to-configure-qualifiers-by-event.md) — per-event assignment at scale
* [How to use qualifiers to manage leads](https://help.getmobly.com/help-center/the-hub/working-with-leads/how-to-use-qualifiers-to-manage-leads.md) — filtering and acting on qualifier answers
* [Qualifiers (CRM)](https://help.getmobly.com/help-center/integrations/crm/qualifiers.md) — mapping qualifier values into your CRM
