FAQ
How does ClaimVox handle TCPA consent?
We capture explicit consent at the start of each conversation, store the language you approved, and timestamp the event. If a contact opts out, we suppress future outreach and record it in the audit log. For inbound leads sourced from ads, we can reference your ad platform’s consent records and mirror that language in follow-ups.
What languages are supported?
English is included in all plans. Spanish is included in Pro and higher. We support additional languages as add-on lines. Your scripts, disclosures, and follow-ups are localized by professional translators so intent—not just words—is preserved.
Where does VoxVault™ run?
VoxVault™ lives in secure, private cloud storage dedicated to your firm. Your documents, prompts, and transcripts stay under your control and never train public AI. Access is role-based, changes are logged, and you can export or purge data on request.
How do you secure transcripts and e-docs?
Files are encrypted in transit and at rest. We apply retention windows that you choose, maintain searchable audit trails, and restrict access by user role. If you require it, we can mirror storage to your existing document system so records live where your team already works.
How quickly can we go live?
Most firms launch intake in 7–14 days. Week 1 covers call flows, approvals, and integrations; Week 2 is rehearsals with your team, then go-live. VoxVault™ can be enabled in parallel once we receive your source documents (templates, checklists, memos).
Will this replace our staff?
ClaimVox removes hold time and repetitive questions so your people focus on higher-value conversations. Most firms redeploy staff to follow-ups, medical records, and client care—while signing more qualified cases overall.
What ROI should we expect?
Firms typically see faster response times, higher signed-case rates, and lower cost-per-signed case. We baseline your current funnel, then track lift weekly so you can attribute results to specific campaigns and channels.
How do we control messaging?
You approve every script, disclosure, and playbook before go-live. Changes require an admin to publish and are versioned with rollback. That means consistent messaging across phone, SMS, and chat—without surprises.