What B3 Voice connects to
Everything below is something the bots plug into on your side. Nothing here is a logo we have never dialed through.
B3 Voice bots run on the dialer you already operate: ViciDial, Convoso, Five9 or your own SIP trunk. They pull from your lists, dial on your caller ID, mark do-not-call requests, transfer into your existing queues and write outcomes back using your own disposition codes. Verifier bots also write captured details into your CRM and the ViciDial comments.
What we deliberately do not do
B3 Voice does not resell telephony, does not supply phone numbers and does not ask you to move dialer. Your carrier relationship, your caller-ID reputation and your call costs stay exactly where they are, which is the point, because that reputation took you years to build and is not ours to put at risk.
- You keep your own numbers and your own carrier. Telephony is billed to you, at cost, by them.
- You keep your dialer. The bots run against the list and queues you already operate.
- You keep your disposition codes and your reports. Nothing downstream has to be rebuilt.
What you connect, and what it does
Grouped by the job it does on a call. Everything here is yours, your account, your content, your data on the way back out.
Dialers
ViciDial
The bots pull from your ViciDial lists, dial on your caller ID, transfer into your queues and write dispositions back using your existing codes. No migration, and your reports keep working unchanged.
Convoso
Same hooks as ViciDial: list, caller ID, transfer queue and disposition write-back. If you already run Convoso's own virtual agent, the bots sit alongside it rather than replacing the platform.
Your own SIP trunk
Running a custom stack or an in-house dialer? Custom hooks connect the bots to your trunk directly. This is the path most centers with a bespoke setup take.
Call handling
Transfer to your closers
Transfers land in the queue or on the extension your ACD already routes to. Routing rules stay exactly where they are, the bots do not replace your call distribution.
Compliance
Do-not-call requests
When a caller asks to be removed, the bot confirms it, ends the call and marks the number as DNC, so the request is on record for your team and your dialer.
Call recordings and transcripts
Every call is recorded and transcribed, searchable by number, disposition or phrase, and retained for the period you specify. Exportable for a carrier audit.
Reporting
Disposition write-back
Outcomes are written using your existing disposition codes, so your current QA, payroll and campaign reports read bot calls the same way they read human ones.
CSV export
Every call, disposition and transcript exports as CSV from the client panel, the path most operators use to get data into a spreadsheet or their own warehouse.
Webhooks
Post each completed call to an endpoint you control, so a transfer can trigger something in your own systems the moment it happens.
Data out
Your CRM
Verifier bots write the details they capture on the call, such as name, date of birth, address and verification answers, straight into your CRM. We connect it during your trial.
ViciDial comments
Verifiers add a clear call summary to the ViciDial comments, so your closers and QA see what was captured without opening another system.