---
title: "Match Handoff Hours to Team Coverage"
description: "Set work hours so visitors transfer only when someone can answer."
category: "Pro Tips"
canonical: "https://www.proxyai.app/help/pro-tips/match-handoff-hours-to-team-coverage"
---

> For the complete documentation index, see [llms.txt](https://www.proxyai.app/llms.txt). Request public content pages with `Accept: text/markdown`.

# Match Handoff Hours to Team Coverage

In **Add-ons → Hand-off → Settings**, choose the team's timezone, start and end times, and staffed days. Outside that schedule, the bot keeps answering instead of placing visitors into the waiting queue. The [Human Handoff Guide](/help/add-ons/human-handoff-guide) explains the queue and the agent view.

Check **Add-ons → Hand-off → Inbox** regularly during active hours. Select a waiting conversation to read its transcript and AI briefing, reply as an agent, or choose **Return to bot** when human ownership is no longer needed.

### Test the handover at the schedule boundary

Choose hours that reflect actual staffing rather than the hours you wish support could cover. Confirm the timezone with the people who will answer, especially when the team works across locations. An apparently correct start time in the wrong timezone can leave customers waiting when nobody is available.

After saving, test a customer request during staffed hours and inspect the conversation in the handoff inbox. Read the transcript and briefing before replying, then return the conversation to the bot when the human portion is finished. Treat this as a handover process rather than only a scheduling setting.

Use the selected chatbot's configuration and channel for the test. Another bot or another account may have a different schedule. If a visitor does not reach the expected flow, record the time, timezone, bot and channel before changing more settings.

The [Human Handoff guide](/help/add-ons/human-handoff-guide) describes the queue and agent view. The [multi-channel support article](/blog/multi-channel-ai-chatbot-one-bot-every-channel) provides context for running the same assistant across several customer entry points.
