Is it by design that Post-Call Webhooks are not triggered when using 'Transfer to agent' in convers

[civic lantern]

AI-generated Answer for ikki01

Yes. Post‑call webhooks are only emitted after a call has finished and analysis is complete; they are not triggered at intermediate events like agent‑to‑agent transfers. You’ll get a single post_call_transcription (and optional post_call_audio) webhook once the overall conversation ends. (elevenlabs.io)

If you need to react at the moment of transfer, use the real‑time WebSocket events: the agent_tool_response event indicates when a system tool (such as transfer_to_agent) has executed. (elevenlabs.io)

References:

• Post‑call webhooks (trigger timing and payloads). (elevenlabs.io)
• Webhooks overview (event type post_call_transcription). (elevenlabs.io)
• Agent transfer (transfer_to_agent system tool). (elevenlabs.io)
• Client events (agent_tool_response). (elevenlabs.io)

Sources:
Webhooks | ElevenLabs Documentation
Client events | ElevenLabs Documentation
Post-call webhooks | ElevenLabs Documentation
Webhooks | ElevenLabs Documentation
Agent transfer | ElevenLabs Documentation
Client events | ElevenLabs Documentation

[brazen token]

When there is Agent A connected via 'Transfer to agent' and Agent B called from A, will the Post-Call Webhook be triggered when B ends? And if so, will it be the Post-Call Webhook configured for A or B that gets called?

[civic lantern]

AI-generated Answer for ikki01

Short answer: the official docs do not state how Post-Call Webhooks behave when a conversation uses Transfer to agent (A -> B). They don’t specify whether the webhook fires when B ends, nor whether A’s or B’s webhook configuration is used in that scenario.

What is documented:

• Post-Call Webhooks fire when “a conversational AI call has finished and analysis is complete.” The payload includes agent_id and conversation_id. (elevenlabs.io)
• Webhooks are dispatched only once per event, and Post-Call settings can be configured at workspace level and (per the changelog) overridden at the agent level. The docs do not describe precedence during inter-agent transfers. (elevenlabs.io)
• The Post-Call payload structure (including agent_id) is documented; you can also query the conversation after the fact to confirm which agent is associated to the final conversation record. (elevenlabs.io)

Given the lack of explicit guidance in the docs about transfers, I can’t confirm which agent’s webhook configuration will be applied. I recommend a quick validation in your environment and checking the agent_id in the resulting webhook (or via GET Conversation) to see which agent the platform attributes the finished call to. (elevenlabs.io)

Sources:
Webhooks | ElevenLabs Documentation
Webhooks | ElevenLabs Documentation
Post-call webhooks | ElevenLabs Documentation
Post-call webhooks | ElevenLabs Documentation

[brazen token]

I'm asking this question because I actually experimented and the Post-Call Webhook is not being called. Is it possible that it might not be called at all?