Skip to content

Will-Call Flow

verify_member
--> get_active_trips
--> [find trip with is_will_call=true]
--> activate_will_call(trip_id)
sequenceDiagram participant Agent participant MCP Agent->>MCP: verify_member(member_id, dob) MCP-->>Agent: session_id Agent->>MCP: get_active_trips(session_id) MCP-->>Agent: trips[] (find is_will_call=true) Agent->>MCP: activate_will_call(session_id, trip_id) MCP-->>Agent: driver dispatched

When a roundtrip is booked with return_type = "will_call", the return leg is created as OnDemand (no scheduled pickup time). The member calls when they are ready to be picked up, and the AI agent activates the return leg.

  • activate_will_call uses the Organization action (not Broker) – consistent with the member-backend
  • AddedByEntityID is set to the real member UUID (falls back to "mcp-service" if unavailable)
  • No pre-fetch trip lookup – the trip service validates ownership and status internally
  • Estimated pickup is calculated as current time + 15 minutes and included in the response message

Establish a session. Alternatively, activate_will_call supports lightweight re-verification without a full session.

List active trips and find the one with is_will_call: true.

Activate the will-call return leg.

  • Input (with session): session_id, trip_id
  • Input (re-verification): trip_id, member_id, first_name, dob
  • Output: trip_id, status: "activated", confirmation message

activate_will_call supports two verification methods:

  1. Existing session – Pass session_id from a prior verify_member call
  2. Lightweight re-verification – Pass member_id + first_name + dob directly (no session needed)

The lightweight path is useful for quick will-call activations where the member just needs to confirm identity without a full booking session.

Error Recovery
No will-call trips found Inform the member they have no pending will-call trips
Trip already activated Inform the member their pickup is already in progress
Verification failed Re-confirm member identity