Will-Call Flow
Sequence
Section titled “Sequence”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
How Will-Call Works
Section titled “How Will-Call Works”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.
Activation Details
Section titled “Activation Details”activate_will_calluses the Organization action (not Broker) – consistent with the member-backendAddedByEntityIDis 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
Step-by-Step
Section titled “Step-by-Step”Step 1: verify_member
Section titled “Step 1: verify_member”Establish a session. Alternatively, activate_will_call supports lightweight re-verification without a full session.
Step 2: get_active_trips
Section titled “Step 2: get_active_trips”List active trips and find the one with is_will_call: true.
Step 3: activate_will_call
Section titled “Step 3: activate_will_call”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
Verification Paths
Section titled “Verification Paths”activate_will_call supports two verification methods:
- Existing session – Pass
session_idfrom a priorverify_membercall - Lightweight re-verification – Pass
member_id+first_name+dobdirectly (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 Scenarios
Section titled “Error Scenarios”| 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 |