An HR FAQ chatbot launched without a source-of-truth owner or escalation path and gave employees wrong leave answers. What should the CHRO lead?
Select an answer to reveal the explanation.
Short Explanation
A chatbot with no owner is like a suggestion box that writes policy. Wrong leave answers are not a cute glitch—they send people home on the wrong day. Someone has to own the content, and there has to be a human off-ramp.
Full Explanation
Conversational HR technology still requires content governance and escalation. Redesigning an FAQ chatbot with knowledge ownership, a maintained source of truth, and a human escalation path prevents wrong leave answers that employees reasonably rely on when no owner maintains city policy in the bot. Disclaimers do not cure an ungoverned knowledge base.
Leaving the bot as-is with a disclaimer that answers may be wrong invites reliance on known error. Shutting HR phones so employees must use the bot exclusively removes the safety net the bad answers prove is needed. Letting the vendor's default knowledge base replace city leave policy imports generic content that will conflict with local rules and CBAs.
Exam caveat: escalation paths must reach qualified humans quickly; a ticket that sits three days is not a real safety net for leave deadlines. Operational check: assign a leave-policy content owner, sync the bot to the current policy repository, log low-confidence escalations, and mystery-shop leave questions until accuracy meets the standard. Document ownership so auditors can see who maintains the control. Re-test the control after the next tabletop or hiring cycle. Keep the civic workforce impact visible in the evaluation notes.