Do you sell directly to my clients?

No. Partner-sourced accounts are yours. We don't market to them, we don't contact them, and inbound leads that identify an existing partner relationship get routed back to you.

How does billing work?

You're billed at partner rates on aggregate usage across your tenants. You set your own client pricing and keep the spread. Per-tenant usage is broken out so you can rebill accurately.

Can I build my own connectors?

Yes. The connector schema is published and auditable. Anything you build stays yours; anything you contribute back gets reviewed and listed with attribution.

What happens to my clients if I leave?

Workflow definitions, connector configs, call records, and transcripts export in full. We don't hold your client data hostage as a retention mechanic.

Who handles support when a client's agent breaks?

You own the client relationship and the first response. You get a direct escalation path with execution traces attached, so you're not relaying symptoms through a ticket queue.

For agencies, voice AI developers & white-label partners

The half of the voice stack you were going to build anyway.

Keep the voice, the model and the telephony you already chose. Your agent calls Voicent as a tool mid-conversation, and it executes connector calls while the caller is still on the line, carries real memory of who it is talking to, leaves an execution trace when something goes wrong, and starts from a connector library instead of the first ten integrations you write yourself.

Book a partner call See the template library

Why this exists

The voice was never the hard part.

Whatever you built on, the conversation works. It will hold a fluent call and hand you a transcript. What breaks is everything behind it: integration code rewritten per client, state that has to survive between calls, and the part where you work out what actually happened on call 400 without listening to it.

So that half moves into a graph you author, version and diff, and your agent invokes it as a tool call — four of the templates in the library run exactly that way. Nodes are triggers, lookups, branches and connector calls; the connectors execute while the caller is still on the line; memory persists across calls in a knowledge graph rather than a context window; and every run leaves a trace of which node fired and what came back. A connector we do not carry is declarative YAML you can write yourself, so your roadmap stops waiting on ours.

What you get

DEPLOY

Build the workflow once. Ship it to every client.

A workflow is a portable graph definition, not a per-client integration project. Build it once in your own workspace, then deploy it across client tenants with their own credentials, numbers, and calendars bound at run time. Update the template, push the change to the accounts you choose.

Browse deployable templates →

ORCHESTRATE

The tool layer your agent calls, not a second agent.

Your voice platform runs the conversation. Voicent runs what the conversation needs: look the caller up, check real availability, create the opportunity, take the payment, send the text. A graph of third-party API calls that branches on what they return — fired by the agent mid-call or by the call ending, and handed back fast enough for the agent to say the answer out loud. It versions and diffs like the integration code it replaces.

Read a complex workflow →

ISOLATION

Client credentials stay client-scoped.

Every integration resolves per workspace — cached credential, then the workspace's own connection, then a platform fallback only where you've allowed one. Memory sessions are keyed per caller and per workspace. One client's CRM is never reachable from another client's agent.

How the knowledge base is scoped →

CONNECTORS

Integrations you don't have to build.

Connectors are declarative schema, not bespoke code, so a new client tool is hours of work rather than a quarter of roadmap. When a prospect names software you have never heard of, the answer is yes and the timeline is this week.

22 connectors89 actions

Explore the connector directory →

MOAT

One capability wins deals the rest of the pitch can't.

Most voice AI resellers lose the receivables and subscription deals at the same question: can it actually take the payment? Payment movement is regulated and slow to build, which is why the platforms your prospects are also evaluating answer it with a text-message link. You can answer it with a posted transaction.

How VoicePay works →

PROOF

Reporting that survives client scrutiny.

Cost per resolution. Outcome-verified resolution, confirmed against CRM state rather than assumed from a transcript. Recovered revenue. These are the numbers a client's finance person will accept — and the ones a competing agency pitching containment rate cannot produce.

See what we report →

BRAND

Your brand, your pricing, your client relationship.

Custom domain, your logo, your markup. Voicent does not appear in your client's interface and does not contact your clients. The account, the billing relationship, and the renewal are yours.

VISIBILITY

When a call goes wrong, you can see why.

Every execution leaves a trace: which node ran, what the connector returned, where the branch went, what timed out. You debug a client escalation by reading the graph, not by re-listening to the recording and guessing at a prompt.

Read a workflow graph →

The numbers

Numbers here stay blank until they're verified against real partner accounts. Placeholder beats invented.

not yet verifiedMedian time to provision a new client workspace
22Connectors available at deploy, no build required
not yet verifiedPartner accounts running 5+ client tenants

Deploy from a library, not from scratch

22 prebuilt connectors and a workflow library your clients can be running on this week. Every connector is a declarative schema, so a client tool that isn't in the directory yet is hours of work, not a roadmap item.

Explore the connector directory

The integration project you'd otherwise quote for

Every client wants the same six systems wired to their agent, plus one nobody has heard of. Voicent workflows are third-party API calls composed as a graph: built once, deployed across tenants with each client's own credentials bound at run time. Every integration resolves per workspace, so one client's CRM is never reachable from another client's agent.

Open a workflow and read it

Evaluating Voicent for your own business?See what it does on a live call

Questions we get asked

Do you sell directly to my clients?: No. Partner-sourced accounts are yours. We don't market to them, we don't contact them, and inbound leads that identify an existing partner relationship get routed back to you.
How does billing work?: You're billed at partner rates on aggregate usage across your tenants. You set your own client pricing and keep the spread. Per-tenant usage is broken out so you can rebill accurately.
Can I build my own connectors?: Yes. The connector schema is published and auditable. Anything you build stays yours; anything you contribute back gets reviewed and listed with attribution.
What happens to my clients if I leave?: Workflow definitions, connector configs, call records, and transcripts export in full. We don't hold your client data hostage as a retention mechanic.
Who handles support when a client's agent breaks?: You own the client relationship and the first response. You get a direct escalation path with execution traces attached, so you're not relaying symptoms through a ticket queue.

Stop rebuilding the same integration for every client.

Bring one client workflow to a partner call. We'll build it as a template, deploy it to a test tenant, and show you what the second client costs you to launch.

Book a partner call