Selected past performance · Updated August 2, 2026
A human-reviewed bilingual AI concierge workflow
Designed and implemented a bilingual English/Spanish AI concierge for a Georgia healthcare-adjacent practice. The system uses practice-approved content, human-review boundaries, PHI-avoidance guardrails, provider escalation, pre-care and aftercare resources, booking guidance, and accessibility considerations.
Situation
A public-facing practice was receiving more inquiries than the front desk could answer consistently. Response time varied by shift and by language. Staff were handling routine questions and sensitive questions through the same channel with no defined boundary between them.
Risk and friction
- Sensitive health-adjacent details arriving in an unstructured channel.
- Inconsistent answers across staff and shifts.
- Language access depending on who was working.
- No record of which questions were escalated or why.
Intervention
- Classified inquiry types by consequence, then defined what the concierge could answer.
- Routed anything clinical, billing-sensitive, or identifying to a named human.
- Wrote the bilingual English/Spanish response set with accessibility considerations.
- Set the human review point before any non-routine response was sent.
- Trained staff on the escalation path and the refusal language.
- Recorded escalations so the routing rules could be revised.
Measured result
Across the broader 18-month operational engagement, the client achieved documented 39.7% year-over-year revenue growth and reached profitability for the first time. This result reflects the broader engagement, not the AI concierge alone, and is not a guarantee of future performance.
Evidence limitation
This result reflects the broader engagement, not the AI concierge alone, and is not a guarantee of future performance. Resilience Ventures does not provide compliance certification for any regulation or standard.
Buyer-safe takeaway
The gain came from deciding what would never be automated, then automating the remainder with a named reviewer. The same sequence applies to a service desk, a branch, or a call queue.
Next step
Discuss a similar operating challenge.
If a queue, desk, or service channel is producing inconsistent answers, that is a workflow and boundary question before it is a tool question.
Contact question: what audience and outcome does your initiative need to support?