Live Call Events

Get notified the moment a call is accepted and the moment it connects, instead of waiting for the standard end of call report. Live Call Events work with every Connect distribution strategy — only the dialling step changes, the events fire the same way.

Opt-in feature. Live Call Events are enabled per account on request. Ask your Logimeter contact to activate them, then give us the webhook URL(s) that should receive the events.

The Two Live Events

1. First Agent Answered

Fires the moment an agent accepts the call by pressing 1, before the customer is connected. Ideal for showing an "agent found" status as early as possible and fixing lead ownership in your system.

2. Agent Connected

Fires once the agent is actually connected to the customer. Ideal for the moment you want to push customer details to the agent's mobile app so they can capture data during the call.

Workflow per Distribution Type

The dialling step differs per strategy, but the live events fire identically: an agent accepts (First Agent Answered), then the agent is bridged to the customer (Agent Connected).

Dialling (varies by strategy) First Agent Answered event Agent Connected event

SEQUENTIALone agent at a time

DialAgents dialled one at a time, 30s window each

AcceptAn agent presses 1, sequence stops

Live eventFirst Agent Answered fires

BridgeAgent connected to customer

Live eventAgent Connected fires

CALL_ALLall agents at once

DialAll agents in the group rung simultaneously

AcceptFirst to press 1 wins, rest cancelled

Live eventFirst Agent Answered fires

BridgeAgent connected to customer

Live eventAgent Connected fires

HEAD_STARTone agent first, others delayed

DialRandom agent first, others follow after a delay

AcceptFirst to press 1 wins, rest cancelled

Live eventFirst Agent Answered fires

BridgeAgent connected to customer

Live eventAgent Connected fires

FIRSTfirst available agent

DialFirst available agent is dialled

AcceptAgent presses 1 to confirm

Live eventFirst Agent Answered fires

BridgeAgent connected to customer

Live eventAgent Connected fires

SINGLEone assigned agent

DialThe one assigned agent is dialled

AcceptAgent presses 1 to confirm

Live eventFirst Agent Answered fires

BridgeAgent connected to customer

Live eventAgent Connected fires

Event Payload

Example JSON delivered to your webhook when an agent accepts the call:

Event payload — first_agent_answered

{
  "event_type": "first_agent_answered",
  "request_uuid": "3df69d0e-4fc9-4de6-9b92-cb1b0e730d18",
  "reference": "partner-reference-code",
  "accepted_stamp": "2026-05-25T14:39:08",
  "state": "A_ACCEPTED",
  "connect_type": "LEAD_CONNECT",
  "call_distribution": "SEQUENTIAL",
  "partner": { "id": 1, "name": "Partner Name", "uuid": "..." },
  "company": { "name": "Dealership", "reference": "DEAL001" },
  "leg_a": {
    "name": "John Smith",
    "number": "27716184724",
    "reference": "SE001",
    "uuid": "178f9e25-...",
    "confirmed": false,
    "bridged": false,
    "bridge_stamp": null
  }
}

call_distribution in the payload reflects whichever strategy was used for that request. leg_a carries the accepting sales executive's details, ready to populate your app the moment the call connects.

Field	Description
`event_type`	`first_agent_answered` or `agent_connected_to_customer`
`state`	`A_ACCEPTED` on acceptance, `ANSWERED` once connected
`accepted_stamp`	UTC timestamp when the agent pressed 1
`leg_a.bridge_stamp`	UTC timestamp the agent was connected to the customer, empty until then
`leg_a.reference`	Your reference for the sales executive, for matching in your LMS

Webhook Delivery

Events are delivered asynchronously to your webhook URL(s), resolved the same way as your existing end of call callbacks — configurable at the request, partner, or dealership level.
Every delivery attempt is logged for audit and troubleshooting.
To test, point the webhook at a capture tool (e.g. Beeceptor), place a Connect call with any distribution strategy, and confirm the JSON event lands on acceptance and, if enabled, on connection.

Live Call Events pair naturally with Sequential Distribution, but they are independent — enable either or both.