Fieldcraft
Fieldcraft systemTested reference implementation

Lead qualification, built as a governed calling system.

A configurable blueprint connects campaign control, conversation state, qualification, outcomes, and operator review without hiding the work behind a voice API.

AI Phone SDR demo dashboard showing synthetic leads with queued, in-progress, completed, failed, callback, and no-answer states
Real dashboard capture in demo mode. Every lead, number, status, outcome, duration, and cost shown is synthetic test data.Demo data

At a glance.

Operating layer
Revenue Systems
Users
Sales operator and configured phone agent
System boundary
Reference workflow and simulator
Current status
Tested implementation
Evidence type
Source, tests, and demo capture

The operating problem.

Lead lists, scripts, calls, qualification notes, follow-up rules, and bookings often sit in separate systems with no shared operating logic.

The operator needs to know what the agent is doing, which rule produced the outcome, what exception needs attention, and how to pause or adjust the workflow.

Before

Lists, calls, scripts, and notes in separate tools

Qualification and follow-up depend on a person reconstructing context after each conversation.

After

One configurable calling workflow with visible state

Campaigns, leads, calls, transcripts, qualification, outcomes, and exceptions share one control surface.

How the system works.

The blueprint defines the operating rules before a campaign starts.

  1. Configure the client blueprintSet persona, offer, objections, qualification, compliance, calling rules, and provider choices.
  2. Import or select leadsPlace synthetic demo records or approved live records into the campaign queue.
  3. Start or pause the campaignThe operator controls campaign state from the dashboard.
  4. Watch call stateQueued, dialing, in-progress, completed, failed, and no-answer states remain visible.
  5. Inspect conversation and qualificationTranscript events and BANT fields are stored with the call detail.
  6. Record the outcomeQualification, callback, meeting, voicemail, or no-answer state can drive the configured next step.
  7. Review and adjustUse history and exceptions to change the blueprint instead of hiding logic inside prompts.

The dashboard is a control surface.

The agent sits inside an operator-owned workflow with inspectable state and explicit campaign controls.

Outbound qualification campaignDemo mode, campaign paused, no external calls
Start campaignPause

Campaign and lead queue

BlueprintPersona, offer, objections, qualification, compliance
QueueSelected leads and next attempt state
Calling rulesHours, caps, retries, consent, DNC, blocked regions

Active call workspace

Call stateIn progress, demo
Transcript eventsAgent and lead turns
QualificationBudget, authority, need, timeline
OutcomeWaiting for completion

Important decisions.

Configuration over hard-coding

One per-client file holds the persona, offer, objections, qualification, campaign, compliance, and integration choices.

Demo mode uses the real state path

Synthetic events write through the database and dashboard without spending telephony or model credits.

Compliance is visible

Disclosure, recording, DNC, calling hours, blocked regions, and retention are explicit fields instead of hidden assumptions.

Provider boundaries remain replaceable

Telephony, speech, language model, CRM, and calendar choices are represented in the blueprint architecture.

Evidence gallery.

The capture documents the implemented dashboard. Synthetic outcomes are interface evidence, not commercial results.

AI Phone SDR calls table with synthetic demo records in multiple call states
The real calls view makes queue and outcome states visible. The selected-call drawer exists in source, but a current runtime defect prevents it from being used as public visual proof.Demo data

What Fieldcraft delivered.

Calling blueprint

Client configuration, phone-agent pipeline, campaign engine, demo simulator, compliance fields, and replaceable provider boundaries.

Operator system

FastAPI endpoints, SQLite state, lead and campaign controls, call history, transcript and qualification structures, dashboard, and smoke tests.

Proof boundary.

Verified

  • The reference implementation includes a blueprint, pipeline, simulator, API, SQLite state, and monitoring dashboard.
  • Demo mode renders synthetic call state without contacting anyone.
  • Campaign, lead, call, transcript, qualification, and outcome models exist.

Not claimed

  • No call volume, booking, conversion, saving, ROI, or employee-replacement results.
  • No synthetic outcome is presented as a client result.
  • No claim is made that every configured integration is live or that the build is production-ready.
Back to indexAll Fieldcraft workNext case studyFieldcraft Agent Swarm

Make qualification inspectable

Map the rules around your next lead conversation.

Define the queue, qualification, exceptions, approvals, and operator control before choosing a voice provider.

Map My Lead-Qualification Workflow