Industry study · Ride sharing & Food delivery
Develop ride and delivery support agents that reason from participant evidence and applicable remedy policies. Teammately makes the conditions behind expert resolutions testable across disputes and recovery scenarios.
For marketplace AI product owners, participant support leaders, and trust and safety teams
What changes the decision
A marketplace assistant may hear conflicting accounts from riders and drivers, or customers, couriers, and merchants. It must establish what the evidence supports, understand the effect of a remedy on each participant, and distinguish an ordinary service dispute from a situation requiring an urgent handoff.
Applied industry study · These are development and assessment methods, not reported customer results.
The context
A rider’s report, a driver’s account, and available trip events may disagree about what happened.
Judgment to capture
Which observations support each interpretation? What remains unverified? How should the assistant explain the next step without assigning unsupported blame?
The context
A missing or damaged-order report may involve customer, merchant, and courier context, with incomplete evidence about where the problem occurred.
Judgment to capture
Which remedy is authorized by the established policy? What must be checked before attributing responsibility or applying a consequential action?
The context
A routine complaint may include information that changes the required routing and the scope of ordinary support.
Judgment to capture
Which supplied criteria require urgent handoff? What information should be preserved, and which ordinary recovery actions should wait?
The people behind the standard
Agents prepare contrasting accounts and remedy comparisons, then adapt questions about evidence sufficiency. Experts explain when participant differences change the judgment. Findings become proposed rubrics and coverage with explicit attribution, remedy, and handoff conditions.
Evidence gathering, explanations, remedies, and participant-specific service needs.
Trip and order context, downstream effects, and local operating constraints.
Urgent routing criteria, evidence handling, and the limits of ordinary support.
Remedy authority, comparable-case treatment, and review of consequential actions.
Coverage and improvement
Make the basis of a remedy visible before optimizing support behavior. Experts establish which evidence justifies an explanation or action, while coverage preserves the differences between participants and workflows.
Teammately’s contribution
Rubrics separate an authorized remedy from a supported attribution of responsibility. Policy context identifies the participant, workflow, and urgency conditions under which an explanation or action is appropriate.
What this makes possible
Rubrics express what can be offered, what can be concluded, and what remains disputed for the participants involved.
Teammately’s contribution
Lemon Weave synthesizes participant reports, event histories, policy context, and resolution variants from separate ride and delivery coverage designs. Keep unverified accounts distinct from established events.
What this makes possible
The candidate must interpret the evidence available instead of relying on a synthetic case that already assumes who is responsible.
Teammately’s contribution
Trialground evaluates explanations, proposed remedies, and recorded handoffs. Use failures to investigate how the harness interprets evidence and applies the policy for the participant and workflow.
What this makes possible
Inspect whether a gain for one participant group introduces unsupported blame, inconsistent remedies, or missed escalation elsewhere.
Harness experiments can improve evidence gathering and remedy selection. Lemon Weave can also target training examples at conditions where the model assigns blame or proposes a remedy without adequate support.
Assessing progress
Assess ride and delivery cases separately before comparing shared support behavior. Their participants, evidence, and operating dependencies are different.
Examine results by participant role and evidence condition. Speed or customer satisfaction alone cannot establish a justified resolution; track unsupported remedies, unnecessary referrals, and protected escalation behavior.
Adjacent workflows
Ground operational guidance in participant role, local context, and current order state.
Evaluate recommendations against explicitly defined service tradeoffs and operating constraints.
Define a separately scoped review process for evidence handling and expert escalation.
Start with the applicable policy, appropriately scoped trip or order evidence, and the teams accountable for remedies and handoffs. Define what a justified resolution requires.