Question 1

What does Verigence cost?

Accepted Answer

The 30-day evaluation is a no-cost trial of one administrative workflow. A paid-pilot quote follows only after we measure the scoped workload, outcomes, delivery cost, and staff-review requirements.

Question 2

Is Verigence HIPAA-compliant?

Accepted Answer

Verigence is built for HIPAA-eligible deployments with tenant isolation, PHI minimization, audit events, evidence trails, and synthetic data by default in demos. Production PHI requires the right BAAs, eligible services, and customer-specific legal/compliance signoff. We do not market a deployment as HIPAA-compliant without that coverage.

Question 3

What's the difference between Verigence and voice AI tools or EHR patient-engagement modules?

Accepted Answer

Developer voice tools give you the call runtime; EHR modules usually live inside one incumbent workflow. Verigence is built around the front-office workload independent practices feel every day: missed calls, eligibility questions, referrals, follow-up, review items, and audit evidence, with human review before risky actions.

Question 4

What languages does Verigence support?

Accepted Answer

English and Spanish are shown in synthetic healthcare demos. Production language support, disclosure, translation quality, and human escalation are validated per workflow before release. Other languages remain on the roadmap.

Question 5

Can I keep my existing phone numbers?

Accepted Answer

Yes. Verigence can be configured for overflow, after-hours, or dedicated workflow numbers through telephony providers such as Twilio when the required BAA/product gates are satisfied. The product is designed to route demand into the access workflow without forcing a rip-and-replace of your phone system.

Question 6

What integrations does Verigence have?

Accepted Answer

The public demo uses a demo-safe voice path plus typed contracts for work items and evidence records. Eligibility, scheduling, SMS, and EHR/PM paths are synthetic, sandbox, or gated by tenant approval, provider eligibility, BAAs where required, and human review. ConversationRelay is an intended gated transport, not a live production-PHI path today.

Question 7

How does the agent handle interruptions?

Accepted Answer

Synthetic voice scenarios demonstrate interruption handling and review routing when identity, language, coverage, or clinical-safety confidence is uncertain. Production behavior is validated per configured workflow before release.

Question 8

What if I need a custom prompt or workflow?

Accepted Answer

The healthcare-first roadmap starts with after-hours access, eligibility and prior-auth status, referral conversion, no-show recovery, and follow-up. If your workflow needs more than configuration, we scope it as a design-partner workstream and keep the same contracts: staff review, evidence, and compliance gates.

Frequently asked questions