Now live · Talk to Ellie — DIAL3D's voice agent. No demo call required.
Solution

Multi-facility admit-line ops, managed centrally without losing local fit.

Multi-state, multi-program behavioral health operators have a unique problem: every facility has its own intake script, payor floor, and clinical fit criteria — but the parent organization needs central oversight, consistent quality, and unified reporting. DIAL3D handles both layers natively.

Multi-facility operators lose 22% of cross-facility referral opportunities.

Patient calls Facility A; A is full or out-of-network; ideally the patient gets routed to Facility B in the same parent org instead of to a competitor. Most operators handle this manually with mixed results. AI routing handles it natively.

Source · DIAL3D operator benchmark · 142 admissions lines · 2025

Operational capabilities mapped to this use case.

Per-facility scripting

Each facility has its own intake script, voice, and clinical floor — all administered from one console.

Cross-facility referral routing

Caller at Facility A who fits better at Facility B routes natively within your organization.

Centralized reporting

Cross-facility dashboards: which programs are above/below benchmark, where to invest, where to optimize.

Facility-level + parent-level RBAC

Local admissions directors see their facility. Parent leadership sees everything. Audit trail on access.

Single contract, central billing

One MSA, one BAA, one invoice across all facilities. Pricing scales with usage, not seat count.

State-specific compliance

Per-state licensing, payor mix, and 42 CFR Part 2 specifics handled by facility config.

Questions, answered straight.

If we don't have an answer, we'll tell you who does.

Email our admit-line team
How do you handle different state licensing requirements?
Each facility config encodes state-specific licensing, payor floor, and regulatory notes. Caller geography routes to the right facility config automatically.
What about EHR consistency across facilities?
If you run Kipu across all facilities, the same connector serves all. If facilities run different EHRs, we configure per-facility connectors during onboarding.
Can we A/B test scripts across facilities?
Yes — split-testing scripts is built in. Use it to find the highest-converting variant before rolling to all facilities.
How is pricing structured for multi-facility?
Enterprise plans are structured around aggregate usage, not per-facility. Unit economics improve with scale.
Who manages day-to-day operations?
Local admissions directors run their facility config. Parent-org admins have read-everything plus override capability.
Does Cross-facility referral routing actually work?
Yes — when caller A's eligibility fits better at facility B, the agent offers the referral and warm-transfers in your org rather than to a competitor.
How long does multi-facility onboarding take?
Typical 3-6 weeks depending on facility count and EHR diversity. We've onboarded 30-facility operators.
Can we phase the rollout?
Yes — most multi-facility customers start with 2-3 pilot facilities, validate, then roll the rest in 4-6 week tranches.

Multi-facility ops, demoed against your actual portfolio.

Thirty minutes. We screen-share the multi-facility console, run a cross-facility referral scenario, and walk you through the central dashboards.

Chat with Ellie