How the call moves
One recognition path for a code-mixed conversation.
The speech layer centers everyday language switching. The sequence below follows caller speech into a configured reception flow.
How the call moves
Signal Path
- 01
Caller speaks
Hindi + EnglishCode-mixed speechThe caller can move between Hindi and English as the question changes.
- 02
ASR listens
Code-mixed ASR focusHinglish-first recognitionRecognition is organized around code-mixed speech rather than a single-language assumption.
- 03
Reception responds
Voice receptionistConfigured after recognitionThe recognized request moves into a reviewed reception flow.
Requests stay in this browser session and are matched against the selected call register.
Interactive call-flow demo
Test a Hinglish request against a sample call register.
Choose a service context, edit the caller request, then see which topic and next question the browser-side rules select.
Call register output
ReadyChoose a context, edit the sample if you want, then run the test.
Requests stay in this browser session and are matched against the selected call register.
Production readiness
A real rollout starts with the front desk.
ASR fine-tuning is one layer of a production receptionist. The operating brief defines what happens before, during, and after each call.
- Map the recurring questions
- Document the questions callers actually ask and the Hinglish phrasing the team already hears.
- Set response and handoff boundaries
- Decide what the receptionist may answer, what it must confirm, and when a person should take over.
- Verify the production destinations
- Connect and test only approved telephony, scheduling, or business systems before presenting them as live.
Questions before deployment
Deployment Questions
The browser demo labels it for review instead of inventing an answer. A production deployment needs an approved clarification or human-handoff path for the same situation.
How does the browser demo work?
Choose a service context, enter a short caller request, and run the test. Browser-side rules match the request to a configured reception topic and next question.
What happens when a request does not match a configured topic?
The browser demo labels it for review instead of inventing an answer. A production deployment needs an approved clarification or human-handoff path for the same situation.
Are calls recorded or transcripts stored?
This public site does not define production call recording, transcription, storage, retention, or model-training use. Those choices need a deployment-specific data notice and approval before calls go live.
Which telephony, scheduling, or business systems are connected?
None are claimed by this public site. Only approved destinations that have been configured and tested for a specific deployment should be presented as connected.
Can this handle emergencies or provide clinical advice?
No such capability is claimed. Clinic examples are limited to administrative reception and are not an emergency service or a source of clinical advice.
What must be confirmed before a production rollout?
Call flows, handoff rules, destinations, data handling, consent requirements, and business integrations must be approved and tested for the specific deployment.