VOICEB.ai
AI Reactivation Module
Your CRM is full of revenue you already paid for
Dormant opportunities. Deals marked lost. Customers who churned on price or timing. Leads that went quiet before anyone warmed them up. The AI Reactivation Module connects an LLM to your CRM, finds — or predicts — the signal that makes each record worth contacting now, proposes the plan, and runs it with autonomous agents across calls, WhatsApp, SMS, iMessage and email.
Running the module today: Proclinic · EU Leads
AI Orchestration Workflow
Turn dormant CRM leads into revenue, automatically.
VoiceB continuously analyzes your CRM, detects reactivation opportunities and autonomously orchestrates the next best action across email and AI voice until the lead converts or the opportunity is exhausted.
Step 01 / 12
Signal detected
Previous contract approaching renewal
Example lead
Laura — Energy lead
Last interaction: 6 months ago
Your CRM
Dormant, lost, churned
AI Reactivation Engine
Reads every record
Next Best Action
Decided per lead
Open the door
Wait
Evaluate response
AI Voice Call
Conversation
AI evaluates
Decides what is next
Outcome
Exactly one per lead
InvalidValid LeadTalk to AgentSold
CRM updated
Written back
The AI re-evaluates after every touch and chooses the next action — the loop runs until the lead converts or the opportunity is exhausted.
01 — The Missed Revenue
Four kinds of record nobody is working
Dormant opportunities
Open deals with no activity for months. Nobody closed them; nobody is calling them either. They sit in a stage, counted in the pipeline, worth nothing.
Lost deals
Marked lost on price, timing or a competitor. The reason that killed the deal is written in the record — and most of those reasons expire.
Churned customers
They left, and their contract anniversary, financing end or tariff change is coming round again. A churned customer knows the product; the sale is shorter.
Leads that need a warm-up
Inbound that never answered, forms completed and never followed, trials that lapsed. Not cold — just never contacted with a reason.
Acquisition budget goes to buying new names while these records sit in a database you already paid for. The module works that base instead.
02 — The Signals
An LLM reads your CRM and finds the reason to call
Agent Studio connects to your CRM — HubSpot and Salesforce natively, others through MCP — and an LLM reads every record: structured fields with rules, notes, emails and past transcripts with language understanding. It detects signals that already exist and predicts the ones we can trigger. Each signal is stored with its evidence, confidence and expiry, and can be written back to your CRM as a property. No signal, no contact.
Signal family
Examples
Lifecycle and contract
Contract or permanence end date, renewal window, financing or lease end, warranty expiry, tariff or plan expiry, promotion ending
Relationship history
Lost reason, last stage reached, product held, previous objection, NPS, past VoiceB conversations and outcomes
Correspondence
A stated reason for leaving, a deferred intent ("call me in Q1"), a competitor mentioned, a life event, a complaint, an explicit do-not-contact
Behaviour
Opens and clicks on your own emails, web or landing visits, a quote started and abandoned, an inbound call that didn't convert
Predicted
Records with no explicit signal, where the pattern of similar records that did reactivate says a counteroffer, a timing revisit or a content touch is likely to land
Suppression
Opt-out, open complaint or dispute, collections, fraud flag, missing or expired consent — these override everything
03 — The Plan
A proposed plan per segment — approved by your team before anything goes out
Score
Every record gets a reactivation score from its active signals, their freshness and any negative signals. The score decides who is worked first and who is not worked at all.
Play
The signal picks the play — the reason the cadence exists: Renewal window · Price-lost counteroffer · Timing revisit · Competitor switch-back · Life event · Re-engaged with content · Service recovery. The play fixes channel order, tone, offer policy, voice-entry rule and maximum touches.
Preview and approve
The play, the evidence and the CRM context produce the actual steps: message copy, WhatsApp template variables, SMS, email, and the briefing the voice agent reads before it dials. Your team previews the composed cadences per segment and approves them. Every message names the reason — never "just checking in".
04 — The Cadence
Messaging opens the door. The voice agent walks through it.
01
Connect
Dormant, lost and churned records come in from your CRM. Segment by last interaction, lost reason, deal stage, product held, value band and consent flag. Records without a verifiable lawful basis are blocked before the first step. A 5–10 % holdout is drawn.
02
Warm up
WhatsApp, SMS or iMessage open the conversation at low cost and low intrusion, naming the signal. Email joins the cadence where the base has it.
03
Call when it is earned
The autonomous voice agent calls once the customer engages — a reply, a tap, a click, an inbound call — or, for B2B bases, on the schedule you set. Every call attempt is followed within two minutes by a message that says who called, why, and gives a number the customer can call back right now.
04
Converse and close
The agent opens by naming the signal and the previous conversation, checks eligibility through your API, and closes, books, or transfers to a human with the full summary. A reply on any channel pauses the schedule and the agent takes over.
05
Write the outcome back
Every record leaves the cadence with exactly one outcome: Reactivated sale, Pre-sale, Qualified & transferred, Re-engaged, Opted out, or Unreachable. Outcomes land in your CRM against the record, not the touch.
Channels available today: voice, WhatsApp and SMS. Email and iMessage are being added to the cadence engine; ask us for dates for your base.
05 — Two Agents, One Persona
The customer meets one person on every channel
A1 — Messaging
Handles WhatsApp, SMS, iMessage and email replies. Turns a reply or a tap into confirmed interest and a call slot, or into an accepted offer through a secure link.
A2 — Voice
Makes the calls and answers the callback line. Opens with the signal, handles objections from your library, closes or books — or transfers to a human with the full summary.
Same name, same voice, same offer table, same objection library, same timeline on the record. QA and compliance review one persona. Both are configured in Agent Studio with the same Goal / Script / Guardrails / Objections blocks as any other VoiceB agent.
06 — The Rules
Enforced on every cadence, not left to the script
Voice entry policy. Set per cadence. "Signal required" — the default for consumer bases — allows a call only after a reply, a tap, a click or an inbound call. "No signal required" runs the calls after the messaging steps and is used for B2B bases, or for consumer bases where you have accepted responsibility for the list at activation.
Global stop. An opt-out on any channel — STOP by SMS, "No, thanks" on WhatsApp, an unsubscribe link, a verbal request on a call — stops every channel at once and updates the consent field in your CRM.
One cadence per contact. A reply pauses the schedule; the agent handles the conversation; the outcome decides whether the schedule resumes or closes.
Caps and windows. Frequency caps, quiet hours and working days apply per record across all channels. Never two call attempts in the same part of the day.
Holdout. Five to ten percent of every activated base never enters the cadence. Lift is reported against it, never as a gross number.
Lawful basis. Each base is reviewed for a lawful basis before activation — your assertion alone is not enough. AI disclosure on the voice leg and on conversational WhatsApp as required by the EU AI Act. In Spain, consumer calls go out from the mandatory 400 outbound range, with a geographic callback line in every message.
07 — Where It Fits
Any base with history and a reason
Consumer win-back
Telco, energy, insurance, automotive, health and dental: churned customers whose contract anniversary, tariff change or financing end gives the agent a reason to call.
B2B win-back and lead warm-up
Software, services and lead-generation operations: lost accounts and never-contacted leads worked by messaging first, with the voice agent reaching the switchboard, the mobile or the secondary contact.
Expansion on live triggers
Accounts already running VoiceB inbound add triggered contacts on the active base — a completed purchase, an expiring contract, an abandoned form — on the same agent, same persona, same outcomes.
Running the module today: Proclinic (dental and clinical supplies) and EU Leads (lead generation).
08 — Commercial Model
You pay for outcomes, not attempts
Enterprise plan
The module requires a CRM integration, a lawful-basis review of each base and enough volume to measure lift, so it is available on the Enterprise plan and inherits its minimum commitment.
A data-activation fee per base
We carry the messaging, telephony and speech cost on every record we work; the activation fee keeps the list clean, recent and consented. It is a commitment filter, not a margin line.
Per outcome, on the standard Enterprise card
Unreachable, invalid or no engagement: no charge. A recovered lead qualified and transferred, a pre-sale, or a reactivated sale confirmed in your system of record: priced per outcome, same taxonomy and same invoice as your inbound line. Revenue-share is available where sale value is reliably reported back through integration.
Attribution, agreed before launch
Any conversion in your system of record within the agreed window after a VoiceB touch (14 days proposed) is a reactivated outcome. With several channels running, this rule is written into the contract, not inferred from the CRM.
Telephony, WhatsApp conversation fees and speech processing remain pass-through at cost, itemised separately.
See pricing09 — The Pilot
One client, one base, one holdout
01
Lawful-basis review
Consent mapping, retention and the DPA amendment covering outbound channels — per base, before a single record is activated.
02
Connect, read, score
CRM connected through Agent Studio, segment defined, signals detected and predicted, reactivation scores reviewed with your team. Holdout drawn.
03
Approve the cadences
Composed cadences previewed and approved per segment; WhatsApp templates registered; numbers and senders configured.
04
Run and measure
Cadences run with outcomes written back. The headline number is lift versus holdout; the second is cost per reactivated customer against your blended CAC. Expansion to further bases and plays follows the first result.
Success is a statistically significant lift on reactivated customers, a cost per reactivated customer materially below your blended CAC, and zero compliance incidents.
10 — Get Started
Show us the base. We'll show you the signals.
Book a demo and we'll map your dormant, lost and churned records, the signals we can detect or predict in them, and the outcomes the module should write back.