Platform
Calling, qualifying, messaging and recording are usually four purchases. Here they are one line, so the context a customer gives you on the phone is still there in the chat an hour later.
The four jobs, in order
the four jobs
Where a campaign starts
Upload a file, connect a form, or point at the portal your enquiries already land in. Numbers are cleaned, de-duplicated, checked against your opt-in status and assigned to seats and calling windows.
The calling itself
Outbound and inbound on your own number. The agent opens with who it is and why it called, asks the qualification questions your best closer uses, handles interruptions, and adapts language mid-call.
WhatsApp follow-through
The conversation continues in chat with the call attached to it: documents, prices, booking links, reminders, and a two-way reply path that the agent can answer or route.
What you can audit
Every interaction becomes a row: disposition, recording, transcript, messages, outcome. You get a daily report and a live board, and the same data can be pushed into your CRM.
what it plugs into
A campaign that ends in a screenshot is a campaign your team has to re-enter. PitchX writes the call and the chat back into the system you already run, on the fields you already report on, so the pipeline looks the same the week after we switch on as it did the week before.
Contact, activity and stage written back. Your owner, your fields, your duplicate rules.
Connected with the owner’s own sign-in, so the agent sends and books as your team, not as a stranger.
The threads and numbers your customers already have you on.
If it takes a POST request, the write-back works on day one. We will point it at your endpoint.
Connections are approved by an account owner on your side, scoped to what the campaign needs, and revoked the same way. We do not ask for a mailbox password, and we do not keep access after the campaign ends.
when the line breaks
A calling system fails in four places. These are ours, and what the platform does before the failure reaches your customer or your brand. If a campaign cannot answer these four, we do not run it.
They ask for a person
The call transfers with the transcript so far attached, and the agent stays silent until a human joins. If nobody can pick up inside the window you set, it books a callback rather than improvising an answer.
The number is dead
Dead, duplicate and DND numbers leave the list at intake, and the reason is written back to the row, so you can see what was never dialled and why.
The line drops
The record is marked incomplete. The agent does not redial outside your calling window, and the next attempt reads the transcript before it says hello again.
The script runs out
Anything past the agreed boundary is refused and escalated. The agent cannot invent a promise, a deadline or a policy, and every refusal sits in the transcript for you to hear.
The recording is the test. Listen to the calls that went badly, not the demo, before you scale a campaign.
what is on the wire
Voice is the worst place to run a shared API: every millisecond of round trip is a pause the customer notices, and every recording is something you would rather not hand a stranger.
Speech
Emotional synthesis and zero-shot voice cloning, tuned per language
Understanding
Real-time intent detection with script boundaries enforced by the platform
Inference
Triton serving on bare-metal GPU nodes, isolated per deployment
Telephony
Dedicated VoIP numbers, one per seat, KYC completed at activation
Data
In-region storage, no shared third-party API path for your audio
Bare-metal GPU clusters (L40S / H100 class) with Triton serving, run in-region on Indian soil.
Your voice models, weights and knowledge base are containerised per deployment. No shared pipeline with another client.
Around 350 ms voice response, so nobody waits for the agent to think.
A dedicated VoIP number per seat, KYC’d and yours for the life of the campaign.
Recording, transcript, disposition and message log on every interaction, exportable.
Script boundaries, forbidden claims, escalation rules and quiet hours enforced by the platform.
getting live
Day 0
You describe the list, the outcome and the language mix. We tell you honestly if voice is the wrong tool.
Day 1
We build the agent from your product sheet, price list and the questions your best closer actually asks.
Day 2
Company GST certificate, company PAN and the authorised signatory’s Aadhaar. A dedicated VoIP number takes 2 to 3 working days to activate.
Day 3
A small slice of your list, live, with you listening to every call and us tightening the script against it.
Day 4-5
Full batch, WhatsApp follow-ups switched on, CRM write-back verified, daily report in your inbox.
Timeline assumes your documents are ready. The number lead time is the carrier’s, not ours.
next
No rate card. A plan against your campaign.
Talk to an expertGesture control is off.
Skeleton only. Frames stay on this device.
Frames are processed on this device. They never leave the browser and nothing is recorded.
j next k prev l activate , . pan or step Esc off
This control needs a camera. It is optional: touch, scroll and keyboard already do every command.