Main site

Real Estate AI agent · Voice follow-up

Lead-Qualification & Follow-Up Voice AI Agent

Call and text only numbers the supervising broker has released from a consent-verified list, speak the identification, callback number and AI disclosure on connecting, and hand the conversation to the named licensed agent.

Typical delivery
4–6 weeks
Deployment
Your stack
Broker approval
Consent-gated
After launch
Agent Care

What this agent does

Dials the list, never builds it

In

  1. 01

    Check that the campaign, list and script carry the supervising broker's release before a number enters the run.

  2. 02

    Verify each number against the internal do-not-call record and the suppression services the brokerage subscribes to.

Reason

  1. 03

    Resolve the recipient's local calling window and attempt cap to the stricter of the federal and state rule.

  2. 04

    Check that a consent artefact is attached to the record and is the one the broker marked in scope for this campaign.

  3. 05

    Speak the responsible entity, a callback number and the AI disclosure the brokerage configured for that jurisdiction.

Decide

  1. 06

    Qualify against the questions on the approved script, and nothing outside it.

  2. 07

    Resolve a clear stop, remove-me or equivalent request to the suppression queue, and end the call.

Out

  1. 08

    Retain the consent reference, the recording state, the script version and the disposition against the lead record.

  2. 09

    Execute write actions only inside the approval boundaries agreed during implementation.

Product statement

An AI voice is an artificial voice under the FCC's February 2024 ruling, so the agent sits inside 47 USC §227 by construction; the brokerage is the caller and the supervising broker releases a campaign.

Example workflow

One attempt, list to disposition

  1. 1Released campaign receivedBroker-approved list, script, cadence and calling-hour rules
  2. 2Consent state assembledConsent artefact, suppression status, recipient state and prior attempt history
  3. 3Attempt preparedDialling window, script path, recording state and confidence
  4. 4Controls appliedSuppression checks, calling-hour and frequency rules, recording-state gate and confidence threshold

No human action required

Stages 1 to 4 run unaided and dial nothing — a placed call cannot be unplaced, so the broker's lane opens at the confidence gate, ahead of the dial.

5DecisionSplits at the confidence threshold
High confidence

Waits for the supervising broker.

Low confidence

Adds a compliance-officer read first.

Broker approval

The attempt is held with its consent artefact, its state rules and the confidence.

Approve · Amend · Send to compliance

Approved — the call is placed

  1. 6Dialer and CRM updatedOnly where write access and approval policy allow it
  2. 7Outcome evaluatedConsent evidence, disclosure delivery, opt-out handling and complaints after the call

Amendments

Each broker amendment is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required

8 items

  • Adding a number to a dialling list.
    • Deciding that a consent record is valid or in scope.
    • Launching or resuming a campaign.
    • Turning on call recording or transcription.

  • Automation boundary

    Agent acts unaided

    • ✓Speak the responsible entity's identity and callback number.
    • ✓Speak the AI disclosure configured for the recipient's jurisdiction.
    • ✓Capture a clear stop request and write it to the suppression queue.
    • ✓Transfer the call to the named licensed agent.

    Writes happen inside the boundaries agreed at implementation; only a stop request goes without waiting.

    • Deciding that a message is not telemarketing.
    • Interpreting an ambiguous revocation.
    • Setting or overriding calling-hour and frequency rules.
  • Approving script or voice-persona changes.

Example output

One attempt, annotated

Everything the agent prepares is attached to the record it was drawn from.

Voice-agent output · single lead

Illustrative example
Lead
Warm inbound enquiry
Planned opener
Automated assistant for the brokerage, callback number spoken first
Local dial time
2:40 pm local
Consent on file
Signed written consent
Confidence
91%
Recording
Off — not captured on this call

As received

Taken from the lead record and the consent artefact on file — nothing on this side is decided by the agent.

Consent evidence used

  • Signed consent record
  • Broker-released list
  • Suppression check

Why this call now

The window, the cap and the suppression state cleared before the broker saw it.

What the score decides

Below the threshold the attempt picks up a compliance read before the broker sees it.

Action

ApproveAmendSend to compliance

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value lands

Value 01 – 04

All released leads

From the broker's list

03Qualification

Call from the approved script

Work from the consent artefact on file and the calling rules configured for the recipient's state.

01Approved path

Reach the leads that consent covers

Routine first-contact and follow-up attempts run on the approved script.

02Human review

Point review at the doubtful attempts

Attempts with thin consent provenance or an unresolved state rule are held, so the broker's read starts where exposure concentrates.

04

Build an evidence trail

Hold the consent reference, the recording state, the script version and the disposition together.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

  • Telephony and CPaaS

    • Twilio
    • Bandwidth
    • Voice APIs
    • SIP trunking

  • Contact centre and dialer

    • Five9
    • Genesys Cloud CX
    • Campaign and cadence tooling

  • Brokerage CRM and leads

    • BoldTrail
    • Lofty
    • Zillow Premier Agent
    • Realtor.com

Agent

Lead-qualification voice

  • Reads the consent state
  • Places the released call
  • Hands to the licensed agent

  • Consent and DNC services

    • PossibleNOW
    • Gryphon.ai
    • Internal DNC
    • registry access

  • Observability & evaluation

    • OpenTelemetry
    • Langfuse
    • Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six layers between the model and the dial

Each control wraps the one inside it. What a layer misses is named in the failure-mode map that follows it.

L6 · Outermost — last line of defence

Inward → L1 · closest to the model

L6Rollback / safe modePull the agent back to preparing attempts only when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, voice, prompt, script and calling-rule configuration changes.Track
L4TraceabilityRecord the consent reference, the disclosure spoken, the disposition and the suppression writes.Record
L3Broker approvalHold attempts for the supervising broker; it governs whether a call is placed, not whether the consent behind it is good.Gate
L2Policy guardrailsTest attempts against configured suppression, calling-hour and recording-state rules; a failure returns the attempt.Restrict
L1Confidence thresholdsRoute low-confidence attempts to a compliance read before the broker sees them.Require review
Model coreAttempt prepared — dialling window, script path, recording state and confidence
L1 – L2
Test whether an attempt may stand
L3
Puts the dial in the broker's hands
L4 – L5
Keep the record and the version honest
L6
Pulls calling back when signals degrade

How Nestack evaluates it

Evaluate the calling workflow — not only the words on the call.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the call the recipient answers

  1. E1Final-output evaluationDid the opener carry the identity, the callback number and the AI disclosure?
  2. E2Step-level evaluationDid the agent use the right consent artefact, state rules and script version?
  3. E3Tool evaluationDid the opt-out reach the brokerage-wide do-not-call record, not just the campaign?
  4. E4Confidence calibrationDo low-confidence attempts actually attract more broker amendments?
  5. E5Slice evaluationHow does performance change across specific recipient cohorts?
  6. E6Business outcomeHow many attempts could not produce a consent artefact, or drew a complaint afterwards?

Floor — the outcome the brokerage answers for

Failure modes

Where each failure originates in the agent

Seven failure modes, each shown at the stage where it starts.

Agent lifecycle

Direction of processing →

  1. 01 · Retrieval

    1 mode

    • VO-01

      Co-registration artefact

      A checkbox on a shared form is read as consent for this caller.

    Stage gathers

    Consent artefact, suppression status and campaign rules

  2. 02 · Reasoning

    2 modes

    • VO-02

      Area-code time inference

      Calling time is taken from the area code, not the recipient.

    • VO-03

      Revocation read narrowly

      A stop request is treated as an objection to one property.

    Stage proposes

    Dialling window, script path and confidence

  3. 03 · Tool / write

    2 modes

    • VO-04

      Partial suppression write

      The opt-out reaches the campaign table, not the internal list.

    • VO-05

      Recording on by default

      Transcription starts on a call resolving to an all-party state.

    Stage writes

    Only where write access and approval policy allow it

  4. 04 · Output

    1 mode

    • VO-06

      Identification omitted

      The opener drops the responsible entity and the callback number.

    Stage returns

    The opener the recipient hears and what it collects

  5. 05 · Change / Version

    1 mode

    • VO-07

      Silent disclosure regression

      A voice-model swap drops the AI disclosure as redundant.

    Stage tracks

    Model, voice, script and calling-rule config

  • Sev-1 · a call placed outside the boundary
  • Sev-2 · the opener or the recording state is wrong
  • Sev-3 · consent evidence degrades, attempt held
See the complete Real Estate failure-mode catalogue

Affected slices

A safe-looking total, one exposed cohort

The unconsented-contact rate counts attempts placed where a valid, in-scope, unrevoked consent artefact cannot be produced at the moment of dialling. Nestack reports it by slice and by recipient state.

Slice performance — reported separately, not only in aggregate

Illustrative example
SliceFailure rateLiftLift vs. thresholdStatus
Aged or purchased leads, strict states9.1%3.8×Review
Ported and reassigned numbers7.2%3.0×Review
Recipients in all-party states3.6%1.5×Watch
Warm inbound leads1.2%0.5×Normal

Bar: unconsented-contact-rate lift vs. the all-attempts baseline · scale 0–4.0× · tick marks the 2.0× review threshold

2 of 4 slices over threshold

Evidence-linked improvement

What did this failure not test for?

That is the question a cycle answers, and it answers it by leaving a regression case the next release must pass. Detection runs against that suite.

Improvement cycle · five stages

Switchback — the path turns at Improve and returns at Learn

  1. 01

    Detect

    Unconsented-contact rate rises in a recipient cohort.

  2. 02

    Diagnose

    The broker replays the attempts and the consent records behind them until the cause narrows to one.

  3. 03

    Improve

    Version-stamp the change, and attach the attempts that exposed it.

  4. 04

    Verify

    Nothing ships until the affected cases pass a second time.

  5. 05

    Learn

    The suite grows by one case; so does the calling policy.

  6. Learn → Detect

    The return edge. The next cycle is measured against a suite one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, calling workflow, evaluation, integration, then production validation and handover.

Workstream

Week 1Week 2Week 3Week 4Week 5Week 6

  1. 01Calling workflow discovery and boundary definition.Week 1
  2. 02Telephony, CRM and consent-source review.Week 1, Week 2
  3. 03Consent, suppression and state calling-rule mapping.Week 1, Week 2
  4. 04Lead-record ingestion and consent linking.Week 2
  5. 05Script logic and disclosure sequencing.Week 2, Week 3
  6. 06Confidence scoring and compliance routing.Week 3
  7. 07Broker approval workflow.Week 3, Week 4
  8. 08Telephony, dialer and CRM integration.Week 5
  9. 09Evaluation suite and regression cases.Week 4, Week 5
  10. 10Suppression guardrails and release controls.Week 4
  11. 11Call-record retention and tracing.Week 5, Week 6
  12. 12Deployment, documentation and Agent Care handover.Week 6

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel

Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tierPilotOne campaign, one officeProductionProduction telephonyAdvancedMulti-office campaigns
Introduced at Pilot
Calling to your consent rules✓✓✓
Broker approval✓✓✓
Call-level tracing and baseline✓✓✓
Introduced at Production
Per-state contact reporting—✓✓
Approval workflow in your systems—✓✓
Write-back into your dialer and CRM—✓✓
Trace export to your stack—✓✓
Introduced at Advanced
Multi-brand and multi-office rollout——✓
Multi-stage brokerage approvals——✓
High call volume——✓
Enterprise call controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build price
Confirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from build
Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

  1. 01Your lead sources and consent artefacts

    Lead-record ingestion and consent linking

    Week 1

  2. 02Representative approved scripts and cadences

    Calling baseline, script mapping and disclosure sequencing

    Week 2

  3. 03Your written do-not-call policy and calling rules

    Consent, suppression and state calling-rule mapping

    Week 1

  4. 04Access to relevant APIs, feeds or exports

    Telephony, CRM and consent-source assessment, then integration setup

    Week 2

  5. 05Attempts that drew complaints

    Evaluation suite, regression cases and failure-mode testing

    Week 4

  6. 06The rules that decide when a number may be dialled

    Confidence scoring, compliance routing, guardrails and approval controls

    Week 3

  7. 07A named supervising broker to release campaigns

    Broker approval workflow, then pilot and production validation

    Weeks 5–6

Nothing else is required

Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

Phases occupy the weeks they actually run. Week 5 carries two bars because evaluation and pilot overlap.

Phase

W1

W2

W3

W4

W5

W6

  1. DiscoveryW1
  2. BuildW2 – W3
  3. EvaluateW4 – W5
  4. Pilot & LaunchW5 – W6

Week focus

W1Consent provenance, calling rules and where the boundary sits

W2Consent, suppression and telephony data in place

W3Calling workflow, confidence logic and approval controls

W4Consent-artefact tests, recording-state checks and failure modes

W5Telephony connected, one campaign run under supervision, nothing autonomous

W6One campaign completed under broker release, then monitoring passes to Agent Care

Reading the band
Nothing is padded to fill a week. Evaluation and pilot both land in week 5, which is why it doubles.
At the end of W6
The last checks clear and monitoring moves to Agent Care.
Duration
Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Real Estate AI agent

Build a voice follow-up agent around your brokerage's consent record.

Show us your lead sources, your consent records and your calling rules. Whoever owns consent at your brokerage keeps the approval, and we map the calling workflow around them.

Typical delivery
4–6 weeks
Deployment
Your telephony and CRM
Broker approval
Consent-gated
After launch
Agent Care available

Nestack Agents · Lead-qualification voice

AGT-RE-06 · Agent Care available after launch

Build a voice follow-up agent

Four questions so the call starts from your actual setup — then pick a time that suits you.

About you
Your calling

No obligation. We’ll map the workflow, name the automation boundary and tell you if an agent is the wrong answer.