Skip to content

Buyer’s guide

Before you choose a voice agent.

A practical guide for teams considering an AI voice agent for inbound or outbound calls: what it does, where it fits, what to ask any vendor and what to prepare before setup.

General guidance, not legal advice. Calling and data rules differ by country; check them with your own counsel.

  1. 01

    What an AI voice agent does

    An AI voice agent holds a phone conversation in natural speech. It listens, works out what the other person needs, answers from information you have approved and ends the call with a recorded outcome: what was asked, what was learned and what happens next.

    Unlike an IVR menu, callers don’t press keys or repeat set phrases; they explain in their own words. Unlike a voicemail or a missed call, the conversation ends with the details captured.

    • Inbound: it answers your line, including at night, at weekends and on public holidays, takes appointment and callback requests and routes the rest to your team.
    • Outbound: it calls people on a campaign list built around your ideal customer profile, qualifies their interest against your criteria and passes interested prospects to your team as meeting requests.
  2. 02

    Where it fits, and where it doesn’t

    Voice agents work best on calls that repeat: the same kinds of questions, the same details to collect, the same next steps.

    • Good fit: first conversations with prospects, calls outside office hours, appointment and callback requests, request intake and routing.
    • Keep with people: decisions, exceptions, complaints and anything sensitive. A good setup passes these to your team with the context attached.
    • Not a fit: medical, legal or financial advice, or anything outside the scope you approve.
    • Bookings: Neva AI agents capture meetings and appointments as requests for your team to confirm; they don’t confirm bookings themselves.
  3. 03

    Questions to ask any vendor

    • Which calls will the agent make or answer, and what exactly may it say or do?
    • Where do its answers come from, and what happens when it doesn’t know?
    • When does a call reach a person: live while the caller is on the line, after the call, or both? Who receives it, with what context?
    • What does each call leave behind, and how does it reach your systems, for example your CRM?
    • Where are recordings and transcripts kept, for how long, and who can access them? Is this agreed in writing before the first call?
    • For outbound: where does the contact list come from, who may be called and on what basis, at which hours, and how are opt-out requests handled?
    • How does each call open, and how is telling callers they are speaking with an AI handled where you operate?
    • Can you listen to test conversations before anything goes live?
    • Is it tested on real calls in your language, with real accents and background noise, rather than only on a scripted demo?
  4. 04

    What to prepare before setup

    • One workflow to start with: the calls that repeat most and cost your team the most time.
    • The questions callers ask, with the answers you approve.
    • For outbound: your ideal customer profile and the criteria that make a prospect worth a meeting.
    • Your handoff rules: which requests go to whom after the call, and with what information.
    • Calling hours, and where outcomes should land.
    • Your decisions on recordings, transcripts, retention and access, and a check of the calling and data rules that apply where you call: in Türkiye, for example, KVKK for personal data and the İYS commercial-message rules, which also cover phone calls; in the EU, the GDPR.
  5. 05

    How a deployment works with Neva AI

    • Before an agent takes a call, we agree in writing which calls it handles, the information it can use, where records are kept, for how long, who can access them, and which requests it passes to your team.
    • Its opening wording is agreed with you before launch.
    • Outbound lists are built around your ideal customer profile, from contacts you provide or that Neva sources. Having someone’s contact details doesn’t by itself mean they may be called; that is agreed before a campaign starts.
    • You review test conversations before anything goes live.
    • Outcomes can be passed on to your systems, for example your CRM; the connections are scoped with you during setup.
    • We don’t publish prices; cost depends on volume and scope and is discussed after the demo.

Buyer’s guide

Bring one real workflow to a demo.