AI handoffs to staff: decide where inquiries wait for an owner
Before AI hands an inquiry to staff, decide where it waits until an owner is assigned and who picks it up.
Key points
- Log three states: unassigned to replied
- No one at night? Promise a later reply
- Name a morning picker for leftovers
Overview diagram in preparation
Contents
Record the handoff and the owner assignment separately
A&A perspective
An AI handoff declaration is the moment the AI decides to pass an inquiry to a person and replies to the customer, "I will hand this over to the person in charge." At that point, no one has yet taken the inquiry on. Record the moment an owner is assigned and the moment that owner replies as separate events.
From the sources
HubSpot, which makes customer-management and customer-support software, publishes the settings for how its AI support agent hands off to a person. By default, it hands off when it cannot answer, when the visitor asks to speak to a human, or when the agent is paused. You can also add an instruction to hand off when words such as cancellation or refund appear.
From the sources
HubSpot's documentation says the AI agent is available on its higher Professional and Enterprise plans and also requires HubSpot Credits.
From the sources
The same page describes the progress of a handoff through three statuses: the AI is handling the ticket (Pending), the AI has triggered a handoff but no human has been assigned yet (Awaiting Human Assignment), and a human has been assigned (Handed off). For the second status, the page says the ticket may need to be assigned manually.
A&A perspective
Automate & Augment (A&A), which writes this article, gives weight to the fact that HubSpot's documentation separates "passed to a person" from "owner assigned." The customer has been told "I will hand this over," yet inside the company there is a period in which the inquiry is still no one's job.
A&A perspective
Even if your support tool is not HubSpot, you can still draw these record boundaries. A&A's proposed design gives each inquiry passed to a person three states: unassigned, assigned and replied. Replied is not one of HubSpot's three statuses. A&A adds it to show whether a human reply has actually reached the customer.
Hypothetical example
As an example, consider a company that handles website maintenance on a monthly contract. It runs with four employees and a few contractors, and it leaves first replies to inquiries to AI. The AI is instructed to pass cancellation and refund questions to a person.
A&A perspective
How to decide the conditions for passing an inquiry to a person was covered in "Before AI handles inquiries: count wrong resolutions and handoffs."
Hypothetical example
Suppose that at 11 p.m. a customer writes, "I want to cancel next month." As instructed, the AI passes it to a person and replies, "I will hand this over to the person in charge." If the record has only one status, "handed off," the next morning's list cannot tell cases with an assigned owner from cases without one.
A&A perspective
A list that shows only unassigned cases makes clear which items someone should look at in the morning. Before counting how many inquiries the AI passed to people, set up this list first. A place where inquiries sit until an owner is assigned, like this list, is called a holding place in this article.
When no one is available at night, promise a later reply
A&A perspective
When an inquiry is passed to a person at a time when no one is available, the AI's reply should not say "I will connect you right away." It should say roughly when the customer will be contacted. If you promise an immediate handoff at a time you already know no owner is available, the customer waits expecting a person right away, while inside the company the inquiry is no one's job until morning.
From the sources
HubSpot's documentation lets you choose from three handoff methods: assign right away to the next available human agent, assign to a human agent who will follow up later, or do not hand off and let the AI keep answering. You can also write separate messages for when your team is available and when it is not.
From the sources
Assignment is based on whether a user is available at that moment. The page warns that if you specify only a team as the assignment target, availability is not taken into account, so the handoff happens even when no one is available. A separate page on working hours says that a user outside their working hours is set to Away and is not eligible for automatic assignment.
A&A perspective
A&A draws two points from this. One is to design on the assumption that owners are not assigned automatically at night. The other is to prepare the message shown to customers when no one is available separately from the one shown when someone is.
Hypothetical example
For the maintenance company above, the reply to a cancellation inquiry at night could be, for example, "We have received your cancellation inquiry. A staff member will contact you on the morning of the next business day." The deadline of the next business morning is set by the company, within what the person who picks up inquiries in the morning can keep.
A&A perspective
This reply does not shorten the customer's wait. It tells the customer in advance how long the wait will be, so the customer does not have to contact the company repeatedly during the night.
A&A perspective
Contacts that need action immediately, even at night, should not be pushed to the next day by this reply. For a maintenance company, a report that the site is not displaying is one such case. For these, decide separately on a night-duty person and a contact route.
Hypothetical example
Put the way to respond at each time of day into a handoff table. A handoff table lists, by time of day or type of inquiry, the holding place, the guidance given to the customer, and the person who picks the inquiry up and the deadline. For the maintenance company above, it could look like the following.
| Time and situation (hypothetical) | Holding place and message to the customer | Who picks up and deadline |
|---|---|---|
| Weekday daytime, an agent is free | Pass to an agent right away and tell the customer the AI is handing over to a person | If not assigned automatically, the employee on daytime intake duty, within the same day |
| Weekday daytime, everyone is at capacity | Place in a holding place that queues inquiries until an agent is free, and give a rough wait | Items past the maximum wait time in the holding place go to the employee on daytime intake duty, within the same day |
| Nights and holidays | Place in the unassigned list and say we will contact the customer on the morning of the next business day | That day's intake-rota employee, named in advance, within one hour of the start of the workday |
| Cancellation and refund inquiries | Place in the unassigned list regardless of time of day | The business owner takes these. Items that arrive at night are contacted on the morning of the next business day |
Name who picks up unassigned inquiries each morning
A&A perspective
Gather in the unassigned list the inquiries that dropped out of the waitlist, those that arrived through a channel excluded from the waitlist, and those that arrived at night. Then decide, down to the person's name, who picks them up at the start of the workday and by when an owner will be decided.
From the sources
HubSpot's waitlist page describes what happens when all eligible agents have reached their limit on the number of tickets they can handle. At that point, the inquiry is placed in the waitlist instead of the unassigned list. Inquiries handed off from the AI agent are also covered.
From the sources
In the waitlist, inquiries are ordered first by SLA (the response-time target) and then by wait time, and they are automatically assigned to the next agent with free capacity.
From the sources
To use this feature, an administrator must set a ticket limit for each agent. The page says the waitlist is a feature of the higher Service Hub Professional and Enterprise plans, and that an assigned seat is needed to set it up and view it.
From the sources
When all agents are at their limit, inquiries that arrive through a channel excluded from the waitlist, such as an event sign-up form, bypass the waitlist and stay unassigned. Inquiries that exceed the maximum wait time set for each channel, such as chat or phone, are also removed from the waitlist and stay unassigned.
A&A perspective
A&A reads the waitlist as a mechanism for times when agents are at capacity. The page assumes a situation in which agents have reached their limit, and it is not written as a place to catch inquiries at night when no one is working. The page also does not say that the waitlist keeps reply deadlines.
A&A perspective
Inquiries that remain without an owner appear mainly in three forms: those that exceeded the maximum wait time, those that arrived through an excluded channel while agents were at capacity, and those that arrived when no one was working.
A&A perspective
In A&A's proposed design, these are gathered in the unassigned list, and the handoff table from the previous section records who picks them up at the start of the workday and the deadline for deciding an owner.
Hypothetical example
In the maintenance company's example, the person who picks up is one employee on a rota by day of the week, and that person's name is written in the table. That person also decides the owner for items that go to contractors. Only cancellation and refund inquiries are handled by the business owner.
A&A perspective
The deadlines in the table are hypothetical values for this company. When you set your own, choose a length that the person picking up in the morning can actually keep, and align it with the deadline in the AI's night reply. If the reply says the morning of the next business day, place the deadline for deciding an owner earlier than that.
Summary
A&A perspective
The AI's "I will hand this over" is not a signal that an owner has been assigned. Record unassigned, assigned and replied separately.
A&A perspective
When no one is available at night, do not reply that you will connect the customer right away. Say that a staff member will respond later. In the reply, give the time of contact, such as the morning of the next business day.
A&A perspective
For inquiries that remain unassigned, such as those that dropped out of the waitlist or arrived at night, write in the handoff table who picks them up in the morning and the deadline.
The AI's "I will hand this over" is not a signal that an owner has been assigned. Record unassigned, assigned and replied separately. When no one is available at night, tell customers that a staff member will respond later. Write in the handoff table who picks up unassigned inquiries in the morning and by when.
FAQ
Can I use this approach without HubSpot?
Yes. Give your inquiry records unassigned, assigned and replied states, and build a list that shows only unassigned cases. First check whether the support tool you use lets you create a status field or a list.
Does the waitlist automatically assign owners to nighttime inquiries?
Not necessarily. HubSpot's waitlist is a mechanism for when agents have reached their ticket limit. Agents outside working hours are not eligible for automatic assignment, so decide who picks up nighttime inquiries in the morning.
Should the AI's reply name the person who will respond?
Telling the customer roughly when to expect contact makes it easier to keep the promise than naming someone. If owners are decided in the morning, no one is assigned yet at night. Reply under that person's name once an owner is decided.
Sources & editorial note
Primary pages read for this article. Publication dates below belong to the sources; access dates record our research.
- Set up and customize customer agent's handoff process
HubSpot · Updated 2026-10-26; original publication date not stated
Accessed 2026-11-03 - Use the waitlist in help desk
HubSpot · Updated 2026-10-01; original publication date not stated
Accessed 2026-11-03 - Manage user working hours and availability for scheduling pages, inbox, and help desk
HubSpot · Updated 2026-10-19; original publication date not stated
Accessed 2026-11-03