Outbound, from the research to the phone call
Research the prospect, score the fit, write the sequence, hold the conversation in their own language, and log what was actually said. Five stages, one workflow, and nobody on your team dialling a number.
5
stages, from first research to logged outcome
2
scores per prospect: intent, and fit
0
numbers dialled by a person
Outbound does not scale with headcount
Every part of it is bounded by how many people you employ and how long they have been there.
The research is the first thing dropped
Twenty minutes of reading before a call is what makes the call good, and it is the first thing that goes when the target is dials rather than conversations.
Ramp takes months
A new rep is not productive for a quarter, and the list does not wait for them. Lists go stale faster than a team can work them.
The hundredth dial is not like the first
The opening call is scripted work done inconsistently, because consistency at that volume is not something people are built for.
Five stages, and each one feeds the next
The reason the call lands is the research three stages earlier. Buy the voice on its own and you have bought a robot reading a script.
Research
The prospect's professional record is read first: role, company, work history, recent posts and what they engage with. Everything a good salesperson would spend twenty minutes finding before dialling, and nobody has twenty minutes per name.
Two scores, not one
Buying intent and product fit are scored separately, because they are different questions and a single blended number hides which one is failing. The scoring reads company research alongside the profile and works against your own product playbook.
The sequence gets written
A multi-step sequence built from what the research actually found, each email with its own job — the cold open, the value-add, the problem-solution — and its tone set by the persona rather than by a house style. The personalisation is the research; the template is just the shape it arrives in.
The call happens
An AI voice conversation that adapts to what the prospect says, handles an objection, and speaks their language, adjusting tone to the sentiment it hears. It knows the product well enough to answer rather than deflect, it books the meeting straight into the calendar with availability checked, and it does not get tired at the hundredth dial.
Evidence-based action points
The transcript becomes prioritised follow-up tasks, each one carrying the thing that was said to justify it — a budget mentioned, a timeline discussed, a blocker named — and the whole outcome syncs to the CRM you already run.
What you get back is evidence, not a call log
A dialler tells you a call happened. The useful artefact is what the prospect said and what it means for the next move.
The signals
Budget mentioned, timeline discussed, blocker raised, deal stage assessed — pulled from the transcript with the words that produced them.
The next actions
Prioritised follow-ups, each one justified by something in the conversation rather than by a rule about what usually comes next.
The record
The full transcript and recording, and the whole outcome written to the CRM your team already opens every morning.
Calling people is regulated, and it should be
Built for the rules rather than around them. This is the part most tools in the category leave for you to discover.
Before the call
Do-not-call checking runs before a number is dialled, not after a complaint arrives.
During the call
Recording disclosure in the greeting, and consent tracked for every recorded conversation.
After the call
An opt-out that actually removes somebody, from the sequence as well as the dialling list.
On email
Unsubscribe links, and sender authentication configured properly — so the sequence is deliverable rather than merely sent.
What your obligations are for your jurisdiction and your list is a conversation for your own counsel, and worth having before the first campaign rather than after it.
The connect rate on this page is ours, not yours
ProspectVox runs our own outbound campaigns at a 47% connect rate, against an industry norm usually quoted at ten to fifteen percent.
Read that as exactly what it is: this product's number, on our list, in our market, for our offer. It is a reason to take voice seriously rather than a forecast about your pipeline, and anyone quoting you their connect rate as though it were yours is selling you something. The figures that used to sit beside it — a quarterly pipeline number, a leads-analysed count, an active-user count and a return multiple — are gone, along with the testimonial that was invented to support them.
What a sales leader asks first
Answers in the page source rather than behind a click, because the systems that summarise this page never click anything.
What does ProspectVox actually do, end to end?
Five stages in one workflow: it researches the prospect's professional record, scores buying intent and product fit as two separate numbers, generates a multi-step email sequence from what the research found, holds an AI phone conversation that adapts to the prospect's answers, and turns the transcript into evidence-backed follow-up tasks that sync to your CRM. Orchestration runs the stages; a person never has to dial.
Is this the same product as ProProspect?
Yes. It is one system that carried two names internally for too long, and the site used both — which is exactly the confusion this page ends. ProspectVox is the name in our own record, so it is the name here, and the old ProProspect page now redirects to this one.
How well does it actually connect?
Our own outbound campaigns run at a 47% connect rate, against an industry norm usually quoted at ten to fifteen percent. Read that as what it is: this product's number on our list, our market and our offer. It is a reason to take voice seriously, not a forecast about your pipeline, and anyone quoting you their connect rate as your connect rate is selling you something.
How should we work out whether it pays for itself?
Do the arithmetic on your own numbers rather than ours. The three costs it displaces are lead research time, sequence writing time and call-prep time — measure your current minutes per lead on each, multiply by your lead volume, and compare that against what this costs you. The comparison set is usually an SDR salary plus tooling, a per-lead research service, or a freelance copywriter per sequence. We do not publish blended customer return figures: every one we could quote would be self-reported and unverifiable, and the inputs that decide the answer — your lead volume, your deal size, your current process — are yours, not ours.
How does it handle the rules around calling people?
It is built for them rather than around them. Do-not-call checking before a number is dialled, recording disclosure in the greeting, consent tracked for recorded calls, and an opt-out that works. On email: unsubscribe links, and sender authentication configured properly so the sequences are deliverable rather than merely sent. Outbound calling is genuinely regulated, and the specifics for your jurisdiction and your list are a conversation to have with your counsel before the first campaign, not after it.
Does it work with our CRM?
It syncs outcomes to the CRM you already run rather than asking you to move, through APIs and webhooks. The design assumption is that your CRM is the system of record and this is one more thing writing to it — the same position VectorHire takes with an applicant tracking system.
What if a prospect asks something the AI cannot answer?
It is built to hand over rather than to improvise, the same way our support product is. The valuable output of an outbound call is rarely the answer anyway; it is the qualified conversation and the evidence of what the prospect actually cares about, and both survive a handover intact.
Can you name a company running this?
Not one we can name, and we will not invent one. ProspectVox is our own product and our own outbound runs on it, which is where the connect rate above comes from. The offer we can make is a demo against your own list and your own script, which in this category tells you more than a reference would.
The same outreach workflow can be built into your own stack as an engagement rather than bought as a product: see how that is scoped.