HUMAN HANDOFF CHECKLIST
By Aditya Kandari · adkandari.com

Complete with the people responsible for operating the workflow.
This is an operational scoping aid; adapt it to your business requirements.

[ ] Define the assistant's allowed tasks and approved sources.
[ ] List questions it must not answer or decisions it must not make.
[ ] Write the exact wording for uncertainty and missing information.
[ ] Define how a visitor can ask for a person.
[ ] Name the person or team who owns each handoff.
[ ] Specify business hours and what happens outside them.
[ ] Confirm the real handoff channel: queue, phone, email, or another agreed system.
[ ] State whether a handoff creates a notification, transfers a call, or only records a request.
[ ] Never promise a callback or response time unless the business can deliver it.
[ ] Define what context is passed and collect only what is needed.
[ ] Test a failed notification and an unavailable staff member.
[ ] Give staff a way to pause the assistant.
[ ] Set a review cadence for handoff failures and unanswered questions.

For a demo, label simulated handoffs clearly. For live use, test the entire path with the responsible team before launch.

Owner: __________
Last tested: __________
Next review: __________

Want this built for your business? Start with a free AI check.
https://adkandari.com/start