Agent Activity

Completed Inbound Call

v1 equivalent: none. v2 only.

Sent when an inbound call handled by an Augment agent ends — the carrier called in rather than being called. The payload is identical to COMPLETED_CALL apart from direction, which is always INBOUND.

post/COMPLETED_INBOUND_CALL

Request

Request body

idstring required

Unique event identifier (ULID)

workflow'TRACK_AND_TRACE' | 'CARRIER_SUPPORT' | 'POD_COLLECTION' | 'LOAD_BUILDING' | 'CARRIER_SELECTION' | 'SCHEDULING' | 'CUSTOMER_SUPPORT' | 'null' nullable required

The Augment workflow that produced this event, or null when no single workflow can be attributed. New values may be added over time, so treat this as an open set rather than a fixed list.

occurredAtstring date-time required

When the underlying activity occurred (ISO 8601)

loadNumberstring nullable required

Your load reference number

customerLoadInternalIdstring nullable required

Your internal load ID, if provided during load creation

eventType'COMPLETED_INBOUND_CALL' required

Event name for a completed inbound call.

Example request

{
  "data": {
    "callId": "01HZXK9P7QM3N8YV4TBWJC2RDF",
    "contact": {
      "name": "Jane Dispatcher",
      "externalId": "CONTACT-123",
      "email": "dispatch@carrier.com",
      "phone": "+15551234567",
      "phoneExtension": "204",
      "role": "DISPATCHER"
    },
    "summary": "Driver confirmed pickup and is en route to delivery.",
    "callStatus": "CONNECTED",
    "callType": "CHECK_IN",
    "outcome": "IN_TRANSIT",
    "actionItems": [
      "Follow up if driver has not arrived by 16:00."
    ],
    "analysisStatus": "COMPLETED",
    "timestamp": "2026-05-13T12:34:56Z",
    "loadDetails": [
      {
        "loadNumber": "LOAD-456",
        "loadStatus": "IN_TRANSIT",
        "driverLocationCity": "Dallas",
        "driverLocationState": "TX",
        "driverLocationCountry": "US",
        "driverLocationLatitude": 32.7767,
        "driverLocationLongitude": -96.797,
        "driverEta": "2026-05-13T16:00:00Z"
      }
    ]
  }
}

Response

Event acknowledged

Changes

No recorded changes to this operation across all 1 revision of this API.