For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configuring Data Requirements

Data Requirements is an advanced Lead Settings tab that lets you set enrichment-side expectations on a small set of contact fields. When enrichment can't meet what you've configured, affected leads are held from your CRM and land in Reconciliation.

Find it under Lead Settings → Data Requirements.

What the tab controls, at a high level

The tab exposes controls for a small set of contact fields (state, country, phone, email, personal address). For each, you can choose whether enrichment must produce a value and what should happen when it can't.

The settings apply during enrichment on every new lead — not at capture time. A rep in the mobile app won't see anything change; the effect shows up downstream, either as a lead syncing to your CRM as usual, or as a lead landing in Reconciliation for review.

When leads land in Reconciliation

If a configured requirement can't be met — for example, enrichment doesn't find a phone number and the setting demands one — the lead is held back from the CRM and appears in Reconciliation. Fix or override from there on a per-lead basis.

How this differs from Required qualifiers

Two different gates:

  • Required qualifiers (Lead Settings → General → Qualifiers) govern what a rep must fill in on a lead in the mobile app.

  • Data Requirements governs what enrichment must produce before a lead syncs to your CRM.

They work independently.

Last updated

Was this helpful?