# Handoff

> A handoff is when an AI agent passes the customer to a person or another channel instead of finishing the job. Vendors differ on which handoffs void a resolution.

Published 2026-11-12 · Reviewed 2026-11-12. Canonical: https://attify.app/glossary/handoff

A handoff is when an AI agent passes the customer to a person or to another channel instead of completing the job itself: a transfer to a live agent, a "DM us", a phone number, or a person on the customer's team stepping in. Vendors disagree about which handoffs stop an outcome from counting, which is one reason their rates differ.

## Vendor rules, from their own documentation

- **Intercom**: a customer asking for a human is not billed as a resolution, but a teammate joining after Fin answered can still leave it resolved ([Intercom](https://www.intercom.com/help/en/articles/8205718-fin-ai-agent-outcomes)).
- **HubSpot**: only handoffs the visitor starts count (asking for a human, a configured phrase); a manual assignment does not ([HubSpot](https://knowledge.hubspot.com/customer-agent/analyze-your-customer-agents-performance)).

## In Attify's standards

| Job type | A handoff that fails the claim |
|---|---|
| [Support](https://attify.app/standards/support-resolution) | The final reply redirects instead of answering (keyword screen or judge), or a person replied after the AI, or the platform recorded a transfer to a person |
| [Sales meetings](https://attify.app/standards/sales-meetings) | A person on the customer's team wrote to or called the prospect before the booking, or rebooked it after a cancellation |
| [Bookings](https://attify.app/standards/bookings) | The conversation was handed to a person before the booking, or staff changed the appointment within 48 hours |

For support, a reconstructed claim (when the data holds no vendor flag) leaves handoffs out of the claim to begin with, so the claim is as generous as a careful vendor's.

## For developers

In the [Ingest API](https://attify.app/docs/ingest), a `handoff` event carries `to`: `human`, `agent` or `external`. Only `human` and `external` are handoffs in the sense above.

## Questions

### Does a human replying after the AI void the AI's resolution?

Under Attify's standard, yes: the AI did not finish the job. Vendor rules differ. Intercom's help article says a teammate joining after Fin answered can still leave the conversation resolved, and HubSpot counts only handoffs the visitor started.

### Is 'DM us' or 'call this number' a handoff?

Yes. A final reply that sends the customer elsewhere instead of answering is a handoff, found by a published keyword screen and by the judge.

### How do I send handoffs to Attify from my own agent?

Send a handoff event with to set to human, agent or external through the Ingest API, or set the proven.handoff attribute in OpenTelemetry. A handoff to another AI agent is not a handoff to a person.

## Sources

- Attify: [Attify Audited Resolution Standard v0.11: check (b)](https://attify.app/standards/support-resolution#audited-resolution), read 2026-11-09
- Intercom: [Fin AI Agent outcomes](https://www.intercom.com/help/en/articles/8205718-fin-ai-agent-outcomes), read 2026-11-08
- HubSpot: [Analyze your customer agent's performance](https://knowledge.hubspot.com/customer-agent/analyze-your-customer-agents-performance), read 2026-11-08
