AskHandle

Human Handoff

Move the conversation from AI to a human without losing context

Human Handoff lets an AskHandle agent transfer a conversation to a person when human support is needed.

AskHandle InboxExample: direct request for a person
Human HandoffAI pauses
Customer: I want to talk with someone about financing.

The customer sees:

AI Agent
I'm connecting you with a member of our team now.
The conversation appears in Inbox.

The handoff can go directly to AskHandle Inbox for live chat, to an existing customer-support system such as HubSpot or Intercom, or to another system through a webhook.

The user stays in the same conversation.

The AI pauses, the human agent takes over, and the conversation can later return to AI when the human is finished.

AI pauses while the human is active

When a conversation is handed off through AskHandle Inbox, AI pauses.

This is important because the user should not receive competing replies from both AI and a person at the same time.

The customer can continue messaging while the conversation waits for a human response.

Once a human agent claims the conversation, the agent can reply in real time.

When the human work is complete, the agent can choose Resume AI.

The AI then takes over again for future messages.

This creates a controlled transition in both directions:

AI → Human → AI

Claim and assign live conversations

Human handoff conversations can be managed by the team inside Inbox.

Agents can see live handoffs and work with assignment states such as:

  • all conversations
  • unassigned
  • mine

A team member can claim a conversation and take responsibility for it.

This is useful when several human agents are online and the team needs a clear way to manage who is handling each user.

The result is a simple support workflow:

AI handles the conversation

↓

Human Handoff triggers

↓

Conversation appears in Inbox

↓

Available agent claims it

↓

Agent replies live

Resume AI when the human is done

Human Handoff does not have to end the automated experience permanently.

A human agent may only need to handle one part of the conversation.

For example:

User: I need to change something on my account.

AI routes the request to a human.

The human agent handles the account-specific change.

Then the user asks:

What time do you close tomorrow?

The human can resume AI, allowing the agent to continue handling ordinary questions.

This reduces the amount of conversation a human needs to manage manually.

What the human agent sees

The Inbox is designed to give the human agent the context needed to continue the conversation.

The agent can review the conversation that already happened before the handoff instead of asking the user to repeat everything.

User information is also available in the conversation view.

If AskHandle already has history for that user, the human agent can see the relevant prior context as well.

This means the handoff is not a reset.

The human joins the conversation that is already in progress.

Keep the full conversation context

One of the most important parts of a good handoff is continuity.

The user should not have to explain everything again just because a human joined.

The handoff should preserve the conversation that already happened.

The human agent can review:

  • what the user asked
  • what the AI answered
  • information already provided
  • any relevant user context
  • prior conversation history when available

That allows the human to enter the conversation with context instead of starting from zero.

Tell the user what is happening

Human Handoff includes a Message to User.

This message is shown when the handoff is triggered.

Message to User

The default can be something like:

You are now being connected to a human agent. They will reply to you shortly.

Customers can change this wording to match their business and support process.

For example:
I'm connecting you with our support team now. You can keep messaging here while someone joins.

Or:

A member of our team will take over from here. Please stay in this conversation.

A confirmation is automatically appended after the configured message.

The user should understand that the AI is no longer handling the conversation alone and that a person will continue.

Ask one question before the handoff

Human Handoff can optionally pause and ask the user for one piece of information before transferring the conversation.

This works across flow types.

The question might ask for:
  • name
  • email
  • phone number
  • order number
  • account reference
  • preferred contact detail
  • a short description of the issue

For example:

Could you share your email so our support team can follow up if needed?

Or:

What is your order number?

The answer is passed to the human agent as contact information.

If no custom question is entered, the handoff can default to asking for email.

This is useful when the human agent needs one important identifier before taking over.

It should not be used to recreate a long intake form. If several structured fields are needed before handoff, AI Form is usually the better choice.

Ask for a rating after the human conversation

Human Handoff can optionally ask the customer to rate the conversation when the chat ends.

The customer provides feedback using a face-based rating.

This gives teams a lightweight way to collect feedback about the support experience after human involvement.

The rating option is optional and can be enabled when it is useful for the support operation.

Choose the destination based on how your team already works

There is no requirement to adopt a new helpdesk workflow.

Human Handoff → AskHandle Inbox

AskHandle Inbox is built in

Customers do not need an external helpdesk to use Human Handoff.

AskHandle includes its own Inbox for live conversations.

When Human Handoff sends a conversation to Inbox:

  1. AI pauses.
  2. The user can continue messaging.
  3. The conversation appears in the AskHandle Inbox.
  4. A human agent can claim the conversation.
  5. The agent replies directly from AskHandle.
  6. When the human is finished, they can resume AI.

This gives teams a complete AI-to-human workflow without requiring another support platform.

Use your existing helpdesk instead

Some businesses already manage support inside another system.

Human Handoff can route conversations into supported external workflows instead of AskHandle Inbox.

Available options include:

  • HubSpot
  • Intercom
  • Webhook

This allows AskHandle to handle the automated part of the conversation while the existing support operation remains the place where human agents work.

A smaller team may prefer:

AskHandle Inbox

because it is included and requires no extra setup.

A team already running support in HubSpot may choose:

HubSpot

A team using Intercom may choose:

Intercom

A business with its own support infrastructure may choose:

Webhook

Works across AskHandle communication channels

AskHandle Inbox can receive handoffs from the customer communication channels connected to the agent.

The Inbox interface supports handoff activity from:

  • WhatsApp
  • Web Messenger
  • Chat Portal

A customer can therefore use the same human-support workflow even when users are coming from different channels.

The conversation remains attached to the channel where the user started it.

Human Handoff is the bridge between the AI conversation and whichever human workflow the business wants to use.

Human Handoff usually starts with intent

Human Handoff is often connected to a Router.

For example:

Router

Product questions
→ Document Search

Inventory search
→ Data Search

Book appointment
→ AI Answer

Speak with someone
→ Human Handoff

When the Router recognizes that the user wants a person, the conversation moves into the Human Handoff node.

The same node can also be reached from other parts of the flow when a human should take over.

The handoff does not need to happen only because the user explicitly says:

I want to speak with someone.

The agent can also be designed so certain requests always go to a person.

A customer says:

I need help with an existing order.

The Router sends the conversation to Human Handoff.

Before transferring, the node asks:

What is your order number?

The customer replies:

483921

The answer is included for the human agent.

The conversation is then handed off.

This gives the human a useful reference before they join.

Human Handoff vs. AI Answer

AI Answer is designed to keep the conversation automated.

Human Handoff is designed to move responsibility to a person.

Use AI Answer when the request can be handled through:

  • general AI responses
  • configured knowledge
  • live web browsing
  • scheduling
  • email
  • calculations
  • product cards
  • other AI skills

Use Human Handoff when:

  • the user asks for a person
  • the business requires human review
  • the request needs human judgment
  • an account-specific action must be performed by staff
  • the automated workflow has reached its escalation point

The two often work together inside the same agent.

Human Handoff vs. Router

Router and Human Handoff solve different problems.

Router

decides where the conversation should go.

Human Handoff

transfers the conversation to a person or human-support system.

A common pattern is:

Router

General question
→ AI Answer

Policy question
→ Document Search

Inventory search
→ Data Search

Human support
→ Human Handoff

Router identifies the intent.

Human Handoff performs the transfer.

Human Handoff vs. AI Form

Human Handoff includes an optional pre-handoff question for one important detail.

AI Form is better when several fields need to be collected or verified before the human takes over.

Use the pre-handoff question for something simple such as:

  • email
  • name
  • order number
  • phone number

Use AI Form for a structured intake such as:

  • qualification
  • service request
  • quote requirements
  • technical support details
  • account information
  • project brief

Then place Human Handoff after the AI Form.

Design the handoff around the human team

A good human handoff should answer a few operational questions clearly:

When to use Human Handoff

Human Handoff is useful when:

  • users should always have a path to a person
  • some requests require human judgment
  • account-specific actions cannot be completed by AI
  • sales conversations should move to a representative at the right time
  • a support workflow needs escalation
  • staff already work in HubSpot or Intercom
  • a custom system should receive handoff events
  • a business wants AI to handle routine conversations while humans handle exceptions

The node is especially valuable because it lets AI automation and human support operate as one continuous experience instead of separate channels.

What Human Handoff does

Not every request should stay with AI.

A customer may ask to speak with a person.

A workflow may identify a request that requires human judgment.

A support case may need an account-specific action that should be handled by a team member.

A sales inquiry may reach the point where a person should continue the conversation.

Human Handoff is the node that connects those conversations to a human support workflow.

It can:

  • transfer a conversation to AskHandle Inbox
  • let a human agent claim and reply to the conversation
  • pause AI while the human is responding
  • resume AI when the human is finished
  • collect information before the handoff
  • show a configurable message to the user
  • send conversations to HubSpot
  • send conversations to Intercom
  • send conversations to another system through a webhook
  • optionally ask the user for a rating after the conversation ends
  • What kinds of requests should reach a person?
  • Should the user provide one piece of information first?
  • Where should the conversation go?
  • Who is responsible for claiming it?
  • What context should the human see?
  • When should AI resume?
  • Should the customer be asked for feedback afterward?

The goal is not simply to add a "talk to a human" button.

The goal is to make the transition from automated support to human support predictable for the customer and manageable for the team.

One conversation, two kinds of support

Human Handoff lets businesses use AI without isolating customers from their team.

AI can handle the questions and tasks that are suitable for automation.

When a person is needed, the conversation moves into AskHandle Inbox, HubSpot, Intercom, or the customer's own system.

The user keeps the same conversation.

The human keeps the context.

And when the human is done, AskHandle can resume the AI experience.