Voice agents that schedule, verify, and recall — connected to NexHealth.
WFW connects directly to NexHealth's API. Patients self-schedule by phone, get eligibility answers during the call, and receive automated recall outreach — all driven by live NexHealth data.
No after-hours voicemail black hole. No manual recall lists. Every action writes back to NexHealth automatically. HIPAA BAA included.
Live Data Flow — Inbound Scheduling Call
HIPAA Business Associate Agreement included
PHI never stored in WFW. All patient data handled exclusively via the secure NexHealth API.
Capabilities
What this integration enables.
Three concrete patient engagement capabilities unlocked by connecting WFW to NexHealth.
Live Data
Phone-Based Appointment Self-Scheduling
When a patient calls to book an appointment, the agent queries NexHealth for available slots by provider and service type. The patient selects a time, and WFW creates the appointment in NexHealth via the API — no front-desk staff required.
Live Data
Eligibility Verification Before Booking
Before creating an appointment, the agent triggers an eligibility check through NexHealth's insurance verification flow. Patients are informed of their coverage status during the call — reducing no-shows from insurance surprises.
Live Data
Recall Outreach for Overdue Patients
WFW queries NexHealth for patients who are past their recall threshold and initiates outbound calls automatically. Each call surfaces the patient's last visit date and next recommended service — pulled from NexHealth in real time.
Data Flow
How it works.
What moves between WFW and NexHealth on every patient call.
Patient identified on inbound call
Caller ID or spoken name and DOB is matched to a NexHealth patient record. The agent now has access to the patient's appointment history, provider preferences, and insurance status within the call context.
Eligibility check runs before scheduling
WFW calls NexHealth's eligibility verification endpoint with the patient's insurance on file. The result — active, inactive, or needs verification — is spoken to the patient before the appointment is offered.
Appointment created in NexHealth
When the patient confirms a slot, WFW writes the appointment to NexHealth via POST /appointments. The patient receives NexHealth's standard confirmation message through their preferred channel.
Extraction data available for review
GET /v2/calls/{id}/extractions returns the confirmed appointment details, patient intent, and any extracted PHI-adjacent fields from the call — ready for staff review or downstream workflow triggers.
Use Cases
Before and after.
Real patient engagement workflows transformed by the NexHealth + WFW integration.
Before
Front-desk staff fielding scheduling calls between 8am–5pm. Patients who call after hours leave voicemails that are returned the next business day.
After
WFW answers 24/7, checks NexHealth availability in real time, and books the appointment before the patient hangs up. After-hours calls convert instead of bouncing.
Before
Staff manually verifying insurance for the next day's schedule — a 20-30 minute daily task that still produces day-of surprises for patients.
After
Patients hear their eligibility status during the scheduling call itself. Insurance issues surface before the appointment is created, not at check-in.
Before
Recall lists worked manually by staff who rotate through patients between other tasks — inconsistent timing, variable follow-through.
After
WFW monitors recall-due dates in NexHealth and calls automatically. Patients with overdue cleanings or follow-ups are reached at the right time, every time.
Technical Details
Integration specifications.
Connection method, auth, data fields, and HIPAA handling for your compliance and IT teams.
| Connection method | NexHealth API — REST over HTTPS |
| Auth method | NexHealth API key + institution ID, stored encrypted in WFW vault |
| Data pulled from NexHealth | Patient name, DOB, appointment history, insurance status, recall-due date, provider preferences |
| Data written to NexHealth | New appointment records, appointment status updates, recall completion flags |
| Avg API round-trip | 150–250ms — within real-time voice conversation tolerances |
| PHI handling | Never stored in WFW. Held in memory for call duration only. HIPAA BAA required. |
API Endpoints
The WFW endpoints this integration enables.
These /v2/ endpoints become available once NexHealth is connected. Trigger recall calls, pull confirmed booking data, and monitor patient engagement campaigns via the WFW REST API.
Full API Reference →Available Endpoints
/v2/calls/initiateTrigger an outbound recall call for a NexHealth patient
/v2/calls/{id}/extractionsRetrieve extracted patient intent and confirmed appointment data
/v2/agents/{id}Check agent health and NexHealth connection status
Setup
Connect NexHealth in three steps.
No middleware required. Credentials entered once, HIPAA BAA signed, integration live.
Add NexHealth credentials
Enter your NexHealth API key and institution ID in WFW admin under Integrations → NexHealth. Credentials are encrypted and stored in the WFW vault.
Sign the HIPAA BAA
WFW generates a Business Associate Agreement covering PHI handling for this integration. E-sign in the admin portal in under 2 minutes.
Enable on your agent
Toggle NexHealth active on your agent's integration settings. All inbound calls will resolve patient data from NexHealth in real time from that point forward.
Get Started
Connect NexHealth to your voice agents.
24/7 scheduling, eligibility verification, and recall outreach — all powered by live NexHealth data. HIPAA BAA included. No middleware to maintain.
Connect NexHealthQuestions? Talk to our team →