UNICEF guidance extends chatbot review to relational design and incident response

Ask district safeguarding, IT, procurement and student-support leaders whether an instructional assistant can drift into personal advice. Who owns complaints and what support exists outside class hours? A bounded review of one configured product could identify decisions needed before access. The value hypothesis is a more informed approval, not a safety guarantee. Do not present international recommendations as U.S. legal compliance or assume a district needs a companion product.

Use synthetic scenarios to test whether a selected assistant stays within its instructional purpose, identifies itself clearly and provides an accessible support route. Prerequisites are configuration access, a documented data flow and approved escalation rules. Test feature changes and account boundaries as well as individual outputs. Proposed acceptance requires all defined high-priority test failures resolved before release; passing a finite suite cannot prove absence of harm.

The student-support director should own response procedures, with IT managing feature suspension and privacy staff handling records. Rehearse complaints and escalation before launch, train teachers on referral boundaries and schedule review after changes. Proposed acceptance requires each rehearsal to reach its named owner within the locally agreed response window. Monitor unresolved cases and staff capacity. Risks include unsupported after-hours expectations, excessive incident-data retention and users being unable to reach a person.