Research & tools
Human handoff receipt builder
Quick answer
Offering a transfer, accepting it and replying to a shopper are different events. This receipt records them separately, so an assigned or accepted conversation is not silently counted as a first human response.
Record three events separately
Use the supplied worked inputs, then replace them with your own declared record.
Worked result
Accepted, response not recorded
The named person accepted the transfer. That is not yet a recorded reply to the shopper.
-
Transfer offered
2026-11-01T12:00:00Z
-
Human acceptance
2026-11-01T12:05:00Z
-
First human response
Not recorded
- Accepting owner
- Example support owner
- Offer-to-acceptance, minutes
- 5
- Offer-to-first-response, minutes
- Unknown
Inputs stay in this page. The tool makes no account, store or provider requests and does not save your entries.
Method & limits
The receipt distinguishes the offer of a transfer, a named human’s acceptance and the first human response. Its two elapsed clocks begin at the supplied offer time. A missing response remains unknown, not zero.
This offer-to-response clock is not Zendesk First Reply Time, which begins at ticket creation and ends at the first public agent response. This authored receipt neither sets an SLA nor verifies that a helpdesk logs a human acceptance event.
Use the helpdesk’s actual response-time report for provider-defined metrics.
Sources & scope
-
Zendesk, ticket reply time
Source checked 2026-11-07. Zendesk first public reply metric begins at ticket creation. This tool defines a separate offer-to-response receipt clock.
The tool’s declared-input record and review steps are authored by Offload. Provider documentation supplies the specific source facts, rather than evidence of a live account check.
Discuss this with Offload
Ask about your use case and the work it would involve.
Enquire