Skip to content
AskVault Docs
Try Free →

The Leads page

Written by , Founder, AskVault · Reviewed by Aashiq
Last updated: · 4 min read

What makes a contact a lead

A lead is a contact with two attributes:

  1. Captured contact info. At minimum email; ideally email plus phone or company.
  2. Buying-intent signal. Triggered the collect_lead skill (asked about pricing, requested a demo, downloaded gated content).

Distinct from a general contact, which may be a support case or an anonymous visitor. Every lead is a contact; not every contact is a lead.

What the Leads page shows

A table with these columns by default:

  • Name and email.
  • Lead score (0-100). Calculated by sdr_lead_qualifier.
  • Stage. New, contacted, qualified, demo-booked, opportunity, closed.
  • Source channel. Widget, WhatsApp, email, etc.
  • CRM sync. Synced to HubSpot/Salesforce, pending, error.
  • Captured at. Timestamp.
  • Last activity. Most recent conversation update.

Customize columns under Leads > View Options.

Lead scoring (BANT)

The sdr_lead_qualifier skill scores each lead 0-100 based on BANT:

  • Budget. Did they reveal a budget range that fits your ICP?
  • Authority. Are they the decision-maker?
  • Need. Did they describe a real problem your product solves?
  • Timing. Buying within 90 days?

Each dimension scores 0-25; total 0-100. Configure the rubric under AI Agents > Skills > sdr_lead_qualifier.

Score interpretation:

  • 80-100. Hot. Route to sales immediately.
  • 60-79. Warm. Nurture aggressively.
  • 40-59. Lukewarm. Marketing nurture.
  • 0-39. Cold. Drip into long-term email sequence.

Lead detail view

Click any lead to see:

  • Profile. Name, email, phone, company.
  • BANT breakdown. Score per dimension with the conversation quote that drove it.
  • Conversation history. Full transcript.
  • Notes. Agent-only notes on the lead.
  • CRM links. Direct link to the HubSpot/Salesforce record.
  • Activity timeline. Stage changes, agent actions, system events.

Useful before a sales rep reaches out.

Auto-routing hot leads

For leads above a configurable threshold (default 80), automation rules can:

  • Tag the lead hot.
  • Push to CRM with a "hot lead" flag for the CRM workflow to pick up.
  • Notify a sales channel in Slack within 60 seconds.
  • Trigger demo_scheduler to offer a Calendly slot immediately.

Speed to lead matters: industry research finds hot leads converted within 5 minutes are about 8x more likely to close than those contacted after 30 minutes.

Configure under Dashboard > Automation Rules > Hot Lead Routing.

Stage progression

Leads move through stages:

  1. New. Captured but not yet evaluated.
  2. Contacted. A human reached out (or bot followed up with demo_scheduler).
  3. Qualified. Sales engineer confirmed BANT.
  4. Demo-booked. Calendly slot booked.
  5. Opportunity. Linked to a CRM deal.
  6. Closed. Won or lost.

Stages can advance manually (drag-drop in Kanban view) or via rules (e.g., "demo booked" auto-advances on calendly.event_scheduled webhook).

CRM sync state

Leads sync to CRM when:

  • CRM integration enabled (HubSpot, Salesforce).
  • Lead score above sync threshold (default 50).
  • Required fields present (email at minimum).

Sync status:

  • Synced. Lead mirrors to CRM. Includes the CRM contact ID.
  • Pending. Sync queued; typically completes within 60 seconds.
  • Error. Sync failed (rate limit, validation, etc.). Click for the specific reason.
  • Below threshold. Lead score below sync cutoff. Sync skipped.

Force a manual sync from the lead detail.

Source channel breakdown

Where leads come from:

  • Widget. Most common for marketing-site traffic.
  • WhatsApp. Common for India and Latin America.
  • Hosted page. Standalone chat page (e.g., chat.yoursite.co).
  • Email assistant. Inbound email triggering capture.
  • Slack, Telegram, Discord. Community-driven.

Channel mix per workspace tells you where your funnel is strong. Analytics > Lead Source breakdown.

Bulk operations on leads

Up to 200 leads at a time:

  • Apply tag.
  • Change stage.
  • Bulk-sync to CRM.
  • Export to CSV.
  • Bulk-notify the sales team.

See bulk operations.

CSV export

Export leads for offline analysis or CRM import:

  1. Filter the leads you want.
  2. Click "Export to CSV".
  3. Download. Includes name, email, phone, score, stage, channel, BANT breakdown, conversation summary.

Up to 10,000 rows per export. Larger exports paginate via API.

Lead API

For automation:

Terminal window
curl "https://api.askvault.co/v1/leads?score_min=80&stage=new" \
  -H "Authorization: Bearer ak_xxx"

Fetch a single lead:

Terminal window
curl "https://api.askvault.co/v1/leads/lead_xxx" \
  -H "Authorization: Bearer ak_xxx"

Update lead stage:

Terminal window
curl -X PATCH https://api.askvault.co/v1/leads/lead_xxx \
  -H "Authorization: Bearer ak_xxx" \
  -H "Content-Type: application/json" \
  -d '{"stage": "qualified"}'

Useful for syncing stage changes from your CRM back to AskVault.

Notifications

Subscribe to lead events under Settings > Notifications:

  • lead.captured. Fires when collect_lead succeeds.
  • lead.qualified. Score crosses 80.
  • lead.demo_booked. Calendly slot scheduled.
  • lead.opportunity. Linked to a CRM deal.

Notifications can go to email, Slack, or your own webhook endpoint.

Privacy and GDPR

Leads are personal data. Compliance:

  • Capture consent. collect_lead asks explicitly; consent logged.
  • Storage. Encrypted at rest. Retention follows workspace retention policy.
  • Deletion. Per-lead delete under Leads > [lead] > Danger Zone > Delete. API endpoint DELETE /v1/leads/lead_xxx.
  • Sub-processor handling. CRM sync sends to HubSpot/Salesforce per your sub-processor agreement.

See GDPR compliance.

Plan availability

  • Free. Basic lead capture, no scoring, no CRM sync.
  • Starter. Lead capture plus basic export. Starter+
  • Growth. Adds BANT scoring, CRM sync, hot-lead routing. Growth+
  • Business. Adds custom scoring rubrics, bulk operations, advanced filters. Business+
  • Enterprise. Custom integrations, SSO, dedicated infra.

Planned features (on the roadmap)

Documented for accuracy:

  • Custom scoring rubrics. Today, BANT-only. Custom rubric definition (e.g., MEDDIC, GPCT) planned for Business.
  • Predictive scoring. Today, rule-based. ML-based predictive scoring from past closed-won/lost outcomes planned.
  • Lead nurture sequences. Today, route to CRM and let CRM workflow handle. Native nurture sequences planned.

Limits

  • Leads per workspace. No hard cap. Practical limit varies by query workload.
  • Bulk operation cap. 200 leads per action.
  • CSV export rows. 10,000 per export.
  • Score range. 0-100.

Common pitfalls

Hot leads not routing to sales. Automation rule not configured. Set up the rule under Dashboard > Automation Rules.

Lead score seems low for high-intent visitor. BANT questions weren't fully answered. Tune sdr_lead_qualifier triggers to capture more.

Duplicate leads. Same person captured via two channels. Auto-merge happens on email match; manually merge if email differs.

CRM sync errors. Usually a missing required CRM property. Add the property in your CRM and re-sync.

FAQ

Can I capture leads without a CRM?

Yes. Leads live in AskVault. CRM sync is optional. Export to CSV any time.

What's the difference between a Contact and a Lead?

Contacts is everyone you've interacted with. Leads is the subset with captured email plus buying-intent signal. Every lead is a contact; not vice versa.

Can I change the BANT rubric?

Yes under AI Agents > Skills > sdr_lead_qualifier. Tune each dimension's weight or replace with your own questions.

Does this work for B2C use cases?

Yes. BANT is B2B-flavored; for B2C, customize the qualifier skill to ask about purchase intent, urgency, fit.

How long does a lead stay "New"?

Until manually advanced or until automation rules move it. No auto-aging today.

Was this page helpful?