In short
Consig runs pre-visit intake as an outbound voice conversation. Patients answer long-form questionnaires by phone, in their own words, at a time that suits them. The completed form returns as structured data, together with a full transcript and recording. In the Xela OS partnership, a pre-surgical questionnaire of more than sixty questions was converted into a conversational voice form.
Why does patient intake cost clinics so much time?
Specialty clinics carry a data collection burden that nobody bills for. A new patient arrives without records. The clinic mails a ten-page questionnaire that most patients never complete. Staff then spend thirty to forty-five minutes on the phone filling in the gaps, and the clinician reviews the same ground again in the room.
That adds up to roughly an hour and a half of uncompensated work per new patient, repeated for every referral. The information itself is not the hard part. Reaching the patient, holding a long and sometimes sensitive conversation, and getting clean structured data out the other end is.
How does a voice intake call work?
Consig calls the patient, verifies identity, and walks through the questionnaire as a conversation rather than a form. Questions that must be asked exactly run as scripted stages; open-ended answers ("tell me about your symptoms") are handled conversationally and mapped back to the fields the clinic needs.
For the first deployments with Xela OS, Consig converted a specialty pre-surgical questionnaire running to more than sixty questions into a conversational voice form. The result lands in Xela as discrete, source-linked fields ready for the chart, not as a transcript somebody has to read.
Can a call safely capture insurance, consent and health history?
Voice intake covers long-form questionnaires, insurance and consent capture, and pre-visit preparation. The Journey.ai foundation that powers authentication also lets a call capture consent, collect health data, or take in a form or record without those inputs passing through the AI.
Every call is placed under HIPAA and TCPA controls and the state-by-state rules governing automated patient outreach, enforced by Consig. Identity is confirmed with passkeys, device biometrics or one-time passcodes before the conversation reaches anything sensitive.
Where does intake lead next?
Once the voice channel is in place, the same calls extend to scheduling, medication refills, recall and post-visit follow-up as each clinic is ready. Intake is often the first workflow because the time saved is so easy to see.
How a Consig call works
- Receive the referral. The platform that owns the record, such as Xela, triggers the intake call with the questionnaire the clinic uses.
- Reach the patient. Consig places a branded, reputation-managed call and checks whether it is a good time, scheduling a callback if not.
- Verify identity. Passkeys, device biometrics or one-time passcodes confirm the patient before any health history is collected.
- Run the conversational form. The questionnaire is asked as a conversation, with scripted stages for required items and conversational handling for free-form answers.
- Return structured results. The completed form comes back as structured data with a full transcript and recording, ready for the chart before the visit.
Frequently asked questions
How long a questionnaire can a voice intake call handle?
Long ones. For the first deployments of the Consig and Xela OS partnership, Consig converted a specialty pre-surgical questionnaire of more than sixty questions into a conversational voice form. Patients answer in their own words, and the completed form returns as structured data with a transcript and recording.
Does the clinic need a new integration to turn on voice intake?
Not when the clinic runs on a platform that already embeds Consig. For Xela clinics, Xela handles the EMR connection it already owns, so the clinic turns on voice without a second technical project. Platforms that want to offer voice intake to their own customers integrate Consig once through its API.
Is the patient's data exposed to the AI during intake?
Consig is designed to limit what the AI sees. Identity verification runs through Journey.ai's Zero Knowledge Network, so credentials and biometrics stay out of the conversation layer, transcripts and any third-party LLM. The same foundation lets a call capture consent or take in a form without those inputs passing through the AI.
What does the clinic get back after the call?
Structured data mapped to the questionnaire's fields, a full transcript and the recording. In the Xela partnership, results return through Xela's intelligence layer as discrete, source-linked fields, so the chart is ready before the patient arrives and staff are not reading transcripts to find answers.