Reselling a voice AI agent puts your name on every call it answers. Including the ones it gets wrong.
So the vendor you pick matters more than the price on their rate card. A cheap agent that needs a support ticket per customer costs more than it earns.
The short answer: ask where it lives, who does the PBX work, whose name callers hear, who sets the price, and what happens when it gets a call wrong. Below are all twelve questions, why each one matters and what a good answer sounds like. We've added our own answers, so you have one to compare against.
(Searchers call this an AI receptionist. We call it a voice AI agent, because it does more than answer.)
Last reviewed: November 19, 2026.
Where does it fit?
1. Does it live inside the portal my customers already use?
Why it matters. Every new login is a support ticket. Every new app is a reason not to use it.
A good answer. It shows up in the portal they already use, with the login they already have, and their roles carry over.
Ours. One script line adds it to your NetSapiens portal under a name you choose. Users sign in with their portal login. Office Managers set the agent up, and staff work the inbox.
2. Who does the PBX work to go live?
Why it matters. If each launch needs your engineers, you can't launch many.
A good answer. Going live creates what the PBX needs on its own, and your answering rules stay yours.
Ours. Three clicks. It creates the agent's NetSapiens user, sets its answering rule and assigns a number from the domain's own inventory. Each agent gets its own extension, starting at 40000. Hours, auto attendants and voicemail stay in the PBX.
3. Can it hand calls to real people on my PBX?
Why it matters. "My customers want a real person" is the first objection you'll hear. The answer is a good transfer.
A good answer. It transfers to the real users, queues and auto attendants in the customer's directory, and it can brief the person before connecting.
Ours. Users, call queues, auto attendants or voicemail, from the domain's own directory. Callers can ask for someone by name. With warm transfer, the agent briefs the staff member first, and the caller comes back to the agent if nobody picks up.
Whose business is it?
4. Whose name do my customers and their callers see?
Why it matters. If your customers see the vendor's name, they can go to the vendor.
A good answer. Yours, everywhere they look: the portal, the agent's name and voice, the emails.
Ours. Fully white-label. Your name on the portal, your logo and colors, the agent's name and voice you choose, and emails sent from your own domain. We set up your portal domain. Your customers never see our name.
5. Who sets the price, and can I see what I bill each customer?
Why it matters. Your margin is the point. You need to set it, and see it customer by customer.
A good answer. You set the price, and the vendor shows usage per customer at your price, ready for billing.
Ours. You set the price. We suggest $45–$95 a month plus $0.35–$0.55 a minute, and you can go anywhere you like. Your partner portal shows each customer's calls, minutes and what you bill them, with a CSV export. You package it in your own plans.
6. How do my customers find out it exists?
Why it matters. A product nobody sees doesn't sell. You can't call every customer.
A good answer. The product sells itself to your base, with your offer and your prices, and you can still provision customers yourself.
Ours. Every customer who hasn't switched it on sees an activation screen in their portal: their own missed calls from the last 30 days, their busiest times, and your headline and prices. Office Managers switch it on themselves, or you provision them through the API. More in turn missed calls into activations.
What happens after launch?
7. What stops a bad change from reaching callers?
Why it matters. Customers will edit their agent. Sooner or later, someone breaks it.
A good answer. Changes are drafts until someone publishes them, you can test before publishing, and you can undo in one click.
Ours. Every edit is a draft until someone presses Publish. Test it by voice or typed chat first. The last 10 published versions can be restored in one click.
8. How will I know when it gets a call wrong?
Why it matters. If your customer finds the problem first, it's a complaint. If you find it first, it's service.
A good answer. Every call has a summary, transcript and recording, the bad ones are flagged with a reason, and urgent calls reach someone right away.
Ours. Insights shows what the agent did, why calls didn't resolve and a short list of calls worth a look. Each call in the inbox has its summary, transcript and recording. Set a message alert, and it arrives by email or text while the caller is still on the line. Our weekly review routine shows how to use it.
9. How does it sound on a real call?
Why it matters. Callers decide in a few seconds whether it can help them.
A good answer. Natural turn-taking, no dead air, and it copes with background noise, spam and callers who switch languages.
Ours. It answers right away and handles interruptions. It follows callers between English and Spanish mid-call, filters spam calls, and cancels background voices. If a voice or transcription service has a problem, it fails over to another.
10. Can it do more than take messages?
Why it matters. Message-taking is a commodity. Booking, texting and looking things up is what customers pay more for.
A good answer. It takes real actions, through tools your customers already use, and you can add more.
Ours. It books appointments and texts links during the call through your own messaging account. It works in the tools your customers already run: it looks up and opens support tickets in HubSpot, reads tickets and scheduled visits in ConnectWise, finds invoices and balances in QuickBooks, and looks up online-store orders. It answers from documents a business uploads, links or syncs from Google Drive. Scenarios let a business script its playbooks step by step. Integrations live in a white-label marketplace, and customers can request the ones they need.
11. What happens to call recordings and customer data?
Why it matters. Your customers will ask you, and you need a straight answer.
A good answer. Specific facts, not a badge on a slide.
Ours. Recording links expire after an hour. Credentials for connected tools are encrypted at rest. Order and billing lookups are read-only. Before it shares account details, the agent can verify the caller, with a code texted to their phone or details from their own records. Have specific requirements? Talk to us.
12. Who supports me, and will you ever sell around me?
Why it matters. You're putting your name on someone else's product. You need a partner who answers quickly and stays out of your customer relationships.
A good answer. A named way to reach them, a steady release pace, and a clear no on selling to your customers.
Ours. Email, phone and a private Slack channel for each partner. We ship weekly, and the portal always runs the latest release. We don't sell to a provider's customers directly.
The vendor checklist
| # | Ask | A good answer |
|---|---|---|
| 1 | Does it live in the portal my customers use? | Same portal, same login, roles carry over |
| 2 | Who does the PBX work to go live? | The product does, in a few clicks |
| 3 | Can it hand calls to real people? | Users, queues, attendants, with a warm option |
| 4 | Whose name do callers see? | Yours, everywhere |
| 5 | Who sets the price? | You, with usage per customer at your price |
| 6 | How do customers find out it exists? | It pitches itself, with your offer |
| 7 | What stops a bad change? | Drafts, testing, one-click undo |
| 8 | How will I know it got a call wrong? | Flagged calls with reasons, alerts in real time |
| 9 | How does it sound? | Natural, bilingual, spam filtered |
| 10 | Can it do more than take messages? | Booking, texts, tickets, billing lookups, playbooks |
| 11 | What happens to the data? | Specific facts you can repeat |
| 12 | Who supports me? | A direct line, weekly releases, no selling around you |
Want to ask us these on a call? Book a demo.
FAQ
What's the most important question to ask a voice AI vendor?
Whose name your customers see. If the vendor's brand shows up anywhere your customers look, you're building their business, not yours.
How do I compare vendors' prices?
Compare what you can charge and what you keep, not the rate card alone. Ask who sets the price, and whether you can see usage per customer at your price.
Should I ask for a test before I sign?
Yes. Call a live agent yourself, ask it something it shouldn't know, and ask for a person. How it handles those three calls tells you more than a demo.
How long should it take to launch my first customer?
Ask what your team has to do for each new customer, not just the first one. With us, setting you up takes one to two weeks, and after that each customer goes live in three clicks.