An insurance carrier is ready for Agentforce Voice when four things are in place: Salesforce voice telephony that can hand calls to people, clean policy and claim data the agent can read, one rule-based call type to start with, and written controls for disclosure, recording and AI oversight. Most carriers have one or two of these. This guide covers how to check all four before you buy licenses or pick a partner.
It is written for service, operations and CRM leaders at carriers and MGAs running Salesforce. For a list of implementation partners, see our earlier post on who implements Agentforce Voice for insurance teams. Vantage Point is one of them, and we say so where it matters.
What is Agentforce Voice?
Agentforce Voice is Salesforce's AI agent for phone calls, announced at Dreamforce in October 2025. It answers calls in natural language, works from the data and actions you give it in Salesforce, logs the transcript to the customer's record and hands the call to a person through your telephony provider when it should. Salesforce lists out-of-the-box telephony integrations with Amazon Connect, Five9, Genesys, NICE and Vonage, among others.
The person who picks up a handed-off call sees the conversation so far, the customer's record and open cases. For a policyholder, that means not repeating a policy number three times.
Readiness area 1: telephony and Service Cloud
Agentforce Voice sits on top of Salesforce's voice stack. Before anything else, confirm:
- Which telephony provider runs your contact center today, and whether it is one Salesforce integrates with natively.
- Whether your service team works in the Service Cloud console, or in another tool with Salesforce in the background.
- Whether you are on Open CTI. Salesforce is retiring Open CTI on February 28, 2028 and steering customers to Service Cloud Voice, so a voice agent project is a good moment to plan that move. Our Service Cloud Voice page covers the migration.
- Which phone numbers, queues and routing rules the pilot would touch.
A carrier on a supported provider with Service Cloud in place can usually go straight to a pilot. A carrier on a legacy phone system should budget for the voice foundation first.
Readiness area 2: policy, claim and customer data
A voice agent can only answer what Salesforce knows. For each call type you want to automate, list the fields the agent needs and check where they live.
| Call type | Data the agent needs | Common gap |
|---|---|---|
| Claim status | Claim number, status, adjuster, last update, next step | Claims live in a separate claims system with no feed into Salesforce |
| Billing and payments | Balance, due date, payment history, payment link | Billing data is a day or more old |
| ID cards and documents | Policy, insured, vehicles or locations, document templates | Documents generated outside Salesforce |
| First notice of loss | Policy lookup, coverage in force, intake questions | Intake form not modeled in Salesforce |
| Caller identification | Phone number, policy number, date of birth or other verifiers | Duplicate contacts and outdated phone numbers |
Duplicate policyholder records are the most common problem we see. If the agent finds two contacts for one caller, it either guesses or hands off, and both hurt the pilot. Clean identity data before you measure anything.
Readiness area 3: choosing the first call type
Pick one call type that is frequent, rule-based and safe to hand off. Claim status and billing questions are the usual first choices. Avoid anything that requires judgment about coverage. Explaining what a policy covers, recommending a change or quoting a premium belongs with a licensed person, and your handoff rules should route those calls to one.
Before the pilot, record a baseline for the chosen call type: weekly volume, average handle time, transfer rate, abandonment and repeat calls within seven days. Without a baseline, nobody can say whether the agent helped.
Readiness area 4: compliance and AI oversight
Insurance regulators have been clear that existing rules apply to AI. The NAIC adopted its Model Bulletin on the Use of Artificial Intelligence Systems by Insurers in December 2023, and roughly half the states had adopted it by mid-2026. It expects insurers to maintain a written AI program covering governance, risk management, testing, monitoring and oversight of third-party AI vendors. A voice agent that talks to policyholders belongs in that program.
| Requirement | What to have in place before go-live |
|---|---|
| AI program (NAIC bulletin) | A description of the agent, its data, its testing results, who owns it and how it is monitored |
| AI disclosure | A greeting that tells callers they are speaking with an AI agent and how to reach a person |
| Recording consent | Disclosures at the start of the call, with all-party consent handling for callers in states that require it |
| Producer licensing | Handoff rules for coverage advice, quotes and policy changes |
| Privacy | Masking of sensitive fields in transcripts, retention periods per record type, access by role |
| Payments | Card capture outside the recorded leg, or recording paused, to keep PCI DSS scope small |
| Outbound calls | Documented consent under the TCPA before any AI agent places a call |
| Vendor oversight | Salesforce, the telephony provider and your implementation partner on your third-party register |
Your compliance team decides how each rule applies. Bring them in at the start of discovery, not the week before launch.
How should a carrier choose an implementation partner?
Look for three kinds of experience in the same team: Salesforce Service Cloud and voice, Agentforce configuration, and insurance operations. Ask each partner:
- Which Agentforce or voice projects have you delivered for insurers, and can we speak to a reference?
- Will you build a working agent in our sandbox before we commit to a full project?
- How do you design handoff rules for licensed activities?
- What will you document for our NAIC AI program and our vendor register?
- How will you measure the pilot, and against what baseline?
- Who supports the agent after go-live, and how are changes approved?
Vantage Point offers a free Agentforce Discovery and POC Accelerator: three working sessions over two weeks that score your use cases, check org readiness and walk through a configured agent in your sandbox. Our insurance Agentforce Voice pilot page describes the full pilot. We are not the right fit if you need a 24/7 support desk or a global systems integrator.
A readiness checklist
- Telephony provider confirmed and supported, Service Cloud console in use, Open CTI plan agreed.
- First call type chosen, with a baseline for volume, handle time, transfers and repeat calls.
- Fields for that call type available in Salesforce and current.
- Duplicate policyholder records cleaned for the pilot population.
- Handoff rules written for licensed activities, complaints and vulnerable callers.
- Disclosure, recording consent and retention settings approved by compliance.
- The agent described in your AI program, with an owner and monitoring plan.
- Licenses sized with your Salesforce account team.
Frequently asked questions
Who implements Agentforce Voice for insurance carriers?
Salesforce consulting partners with Service Cloud, voice and Agentforce experience. Vantage Point runs Agentforce Voice pilots for carriers, starting with a free two-week discovery and sandbox proof of concept.
Do we need Service Cloud Voice before Agentforce Voice?
You need Salesforce voice telephony that can route calls to people, through Amazon Connect or a supported partner provider. Carriers on Open CTI should plan a move, since Salesforce is retiring Open CTI on February 28, 2028.
Which insurance calls should a voice agent handle first?
Claim status, billing and payment questions, ID card requests, first notice of loss intake and caller identification. They are frequent and rule-based, and the agent can hand off cleanly when a call needs a person.
Does the NAIC Model Bulletin apply to a voice agent?
In states that adopted it, the bulletin expects insurers to govern, test and monitor AI systems used in insurance practices, including those from vendors. A policyholder-facing voice agent should be part of your written AI program.
Can an AI voice agent take payments?
It can route callers to a payment flow, but card details should be captured outside the recorded leg of the call, or recording paused, to keep PCI DSS scope small.
How long does a pilot take?
Discovery and a sandbox proof of concept take two weeks with our accelerator. The build and a controlled launch on one call type follow, with timing set by telephony and data readiness.
Start with a readiness check
If you are weighing Agentforce Voice, book a free CRM assessment or start the Agentforce Discovery and POC Accelerator. See also our insurance industry page.
