8 Things to Check Before Buying AI Outbound Calling Software
Published · Last updated
If you run a Farmers Insurance franchise, you have probably asked an AI assistant some version of this question: what should I look for in AI outbound calling software? Demos are polished, but they tell you almost nothing about whether the software will hold up under TCPA consent rules for insurance calls, whether it can pull contacts out of your agency CRM, or whether your results will write back to the system you already use.
That gap between a convincing sales call and real due diligence is what this checklist is built to close. At Aidan, we build AI outbound calling for database reactivation and lead qualification campaigns that sync with Ricochet 360. We have seen how quickly a campaign can go sideways when compliance setup and workflow fit get treated as afterthoughts. So we start with why a strong demo is not the same as due diligence, then walk through eight checks that matter before you sign: consent setup for insurance calls, disclosure and recording notices, caller ID, how contacts come out of your agency CRM, write-back, how call summaries reach you, real-time opt-outs, compliance documentation and liability, and pilot design. We also cover the red flags that should end the conversation early. Run the checklist before you run the campaign.
Why a Strong Demo Is Not the Same as Due Diligence
In February 2024, the FCC ruled that AI-generated voices fall under the TCPA's restrictions on artificial or prerecorded voices, so calls still require the called party's consent. Confirm the wording in the declaratory ruling (FCC 24-17A1) and with counsel before quoting it. Penalties are assessed per call; legal commentary cites $500 to $1,500 per violating call with no statutory cap and illustrates roughly $15 million of exposure for 10,000 calls. Treat that as commentary arithmetic, not a regulator's figure.
Demos rarely show how consent is captured per contact, how suppression lists stay current, or where the call outcome lands afterward. Two Farmers agencies under the same brand can run very different books and consent records. These checks address your agency's workflow and state rules, not brand-wide policy. See our TCPA-compliant reactivation campaign guide and confirm agency-specific points with your counsel.
Check 1: TCPA Consent Setup for Insurance Calls
Before comparing voice quality, pin down consent.
Match consent tier to call type. Informational calls need prior express consent; marketing calls need prior express written consent. Verify against 47 CFR 64.1200 and counsel, not a sales page.
Track consent at contact level. Ask how consent is captured, timestamped, stored, and whether it travels with the record when your existing database syncs into the dialer. Consent staying in your CRM while the platform pulls a bare phone number is not real consent tracking.
Get revocation in writing. The FCC clarified revocation in 2025, and the Eleventh Circuit vacated the one-to-one consent rule in January 2025. Ask for the vendor's current process in writing, not a 2024-era deck.
Know your scrubbing cadence. National DNC, state DNC, internal opt-outs, litigator lists and reassigned numbers. Weekly refresh and monthly refresh are different risk profiles; know which you buy.
Layer in state rules. Colorado, California and Illinois add AI-specific obligations; Colorado's AI Act takes effect in 2026. Ask how the vendor tracks states where you write business.
Check 2: Disclosure, Recording Notices and Caller ID
Disclosure rules are still moving. The FCC's September 2024 proposed rule would require disclosure at the start of every AI-generated call. It remains a proposal, not final. Ask whether the vendor can toggle disclosure by state and campaign so your setup adapts if finalized.
Recording adds a layer in two-party consent states. Confirm how the platform announces recording, where transcripts are stored, and retention time.
Check caller ID. Is the number registered to your agency, and how does the vendor handle STIR/SHAKEN attestation? A blocked or mislabeled number burns through your best contacts and wastes the campaign. The FCC proposed a $6 million forfeiture against a political consultant for robocalls that combined an AI-cloned voice with caller ID spoofing; the same pairing that triggered that proposed penalty can mislabel your agency's number with a carrier.
Ask what happens when someone asks, "Am I talking to a real person?" There should be a scripted, honest answer and a defined path to a licensed agent for coverage and claims questions.
Keep your own record of each call's disclosure text, timestamp and script. If a complaint arrives, you want that file, not a vendor's assurance.
Check 3: How Contacts Come Out of Your Agency CRM
Once disclosures and caller ID are settled, ask where the numbers come from. Request a native Ricochet 360 connection, not a CSV you rebuild weekly. A real integration pulls contacts on your schedule, so the list stays fresh between campaigns. That is the workflow AI call agents for insurance agencies are built around: reactivate the database you own and sync outcomes back.
Confirm how the platform segments your book: lapsed policies, dormant leads untouched 12 or 24 months, upcoming X-dates and cross-sell households. Reactivation only works if the right slice gets called. Consent status and DNC flags must travel with each contact record; a dialer that sees a bare number without consent attached makes your compliance setup theoretical. Under 47 CFR § 64.1200, consent attaches to each call. Ask how duplicates, households and shared lines are handled. Policyholder, spouse and adult child on one number is normal and needs a written rule. Agree on attempt rules before launch: tries per contact, retry spacing and state calling windows. Uncontrolled volume breeds complaints. Next, confirm results land where producers work.
Check 4: Write-Back to the System You Already Use
Next, confirm where the outcomes land.
Aidan writes results back into Ricochet 360, so dispositions, activity notes, lead scores and callback tasks appear where producers already work. A spreadsheet export is a red flag: re-keying costs producer time and breaks the trail between the call and the record, the trail you need if a contact disputes a call.
Ask what "qualified" means here, and whether the agent can be built to those rules: current carrier, renewal date, coverage gaps, decision-maker and budget signals, all matched to your underwriting appetite rather than a generic script.
Get field mapping in writing: which CRM fields get written, what happens when the platform captures only partial data, and who cleans up incomplete records afterward. Then request the audit trail: timestamps, transcripts, recordings and retention periods. Your E&O carrier or franchise counsel may ask to see it, so design it in from the start.
Check 5: How Call Summaries Reach the Owner
If results land in Ricochet 360 but nobody reads them, the campaign still fails, so ask for a real summary email from a live insurance campaign, not a mockup. Aidan sends one after every successful call, so pin down what "successful" means, reached contact, qualified lead, appointment set, before you buy. A sample from an actual agency tells you more than a dashboard tour.
Owner reporting should answer three questions at a glance: how many contacts were reached, how many appointments or transfers resulted, and how many dormant policies reactivated. You should not have to review call recordings to get them. Set the bar with a framework for how to measure the ROI of an AI reactivation campaign. If you run multiple offices, confirm rollups by location so each producer and manager sees their own numbers without you forwarding anything.
Exceptions need a same-day path to a human: opt-outs, complaints, wrong-number flags and unresolved calls. Finally, decide who gets what. Owners want outcomes and risk, sales managers want appointment detail, compliance contacts want the audit trail.
Check 6: Opt-Outs and Revocation in Real Time
Ask how fast an opt-out takes effect in the dialer. Legal commentary circulates a vendor-side recommendation of automated opt-out within two seconds, but that is a recommendation, not a rule. Make the vendor document what they actually do. Revocation can arrive by voice, text, email, or in person to a producer. Map every path to the suppression list and test one end to end. Confirm suppression syncs back to Ricochet 360 so human follow-up, mailers, and other campaigns honor it. An opt-out that only stops the AI dialer is not an opt-out. Ask whether suppression is global or campaign-specific; someone who says stop on a reactivation campaign should not hear from a cross-sell next month. Finally, define the re-permission path. Documented consent is easier to defend than a verbal "sure, call me" a producer remembers. For consent sorting before calls start, see How Insurance Agencies Can Work Their Whole Database Without Breaking TCPA.
Check 7: Compliance Documentation and Who Carries the Liability
Opt-outs protect the contact. Documentation protects your agency. Do not assume your voice platform has handled compliance for you. Vendors disclaim responsibility in their terms; read the contract for indemnification and data ownership before signing.
Ask every vendor for a compliance pack: consent workflows, DNC and suppression process, disclosure scripts, opt-out handling, data retention, and how AI models and subprocessors are used. Your carrier, E&O insurer, or franchise counsel may ask for it, and having it ready shortens review.
Read the contract for indemnification, data ownership, deletion on exit, and subcontractor terms. "We handle compliance" is not a contract clause. Vendors that cannot produce this material often cannot explain the revenue risk of a mishandled call either.
Build your own file: consent records, campaign configurations, scripts, and disclosure logs. Confirm agency-specific obligations, including state insurance rules, with your own counsel and regulator.
Check 8: Pilot Design Before You Sign
With your compliance documentation in hand, make the pilot prove outcomes. A 30-day window on one defined segment is a workable starting point, such as dormant leads with no contact in 12 months. Keep human follow-up running so you have a comparison group.
Agree on metrics before the first call: contact rate, qualified lead rate, appointments set, reactivated policies, cost per appointment and opt-out rate. Undefined success is how pilots quietly become subscriptions.
Measure against your baseline. What does your team currently produce on that same segment in a month? The delta is the only number that matters when you decide.
Ask for proof from comparable agencies. Request figures from agencies with a similar book size, mix and state footprint, and ask for a reference call.
Write down exit criteria in advance. If the pilot misses them, you walk away, and knowing that up front keeps the vendor focused on outcomes rather than activity.
Red Flags That Should End the Conversation
A well-run pilot surfaces these problems early. Any one of them should end the conversation.
Consent and DNC blind spots. The vendor cannot show how consent status and DNC flags reach the dialer, or says compliance "is handled" without producing documentation.
No native Ricochet 360 write-back. A spreadsheet export breaks the audit trail. Aidan writes dispositions and notes straight back into Ricochet 360 for exactly this reason.
No per-contact audit trail. Ask to see what was said, what was disclosed and when someone opted out. A vendor who cannot produce that per contact leaves you defending calls you cannot reconstruct.
Blanket TCPA compliance claims. "Fully compliant" with nothing in writing, or a refusal to commit to specifics in the contract, is disqualifying. Legal commentary cites $500 to $1,500 per violating call with no statutory cap.
No human escalation path. Licensed-agent questions, complaints and requests to speak with a person need a defined route and a named owner, not a promise that someone will notice.
A polished demo does not outweigh any of these.
Run the Checklist Before You Run the Campaign
If those red flags are absent, you still have a decision to make. Three checks carry the most weight: consent and suppression handled inside the workflow, results written back to Ricochet 360, and call summaries that reach you without chasing anyone. Everything else is secondary.
Do not sign on voice quality alone. Ask for the compliance pack, a sample summary, and a write-back example from an insurance agency, not a generic demo. Confirm your state-specific and franchise obligations with counsel before you launch.
Then run a pilot on a dormant segment, as outlined in Check 8, and let the metrics make the decision.
Ask Aidan for a compliance-fit walkthrough using your own dormant contacts, so you see the integration and the reporting before you commit.
Conclusion
For Farmers and Allstate franchise owners, the right AI outbound calling software earns its place by reactivating your dormant database, qualifying leads, and syncing every outcome to Ricochet 360 without putting your agency's compliance posture at risk. Ask Aidan for a walkthrough built around your own contacts.