Most of the work is the everyday, time-sensitive reality of food delivery: an order that arrives with items missing, a rider who can’t find an address while the food goes cold, a payment or refund that hasn’t come through, an account that’s suddenly locked. Each one needs a fast, accurate answer — and behind each is a customer, rider, or restaurant partner judging Uber Eats by how it’s handled.
The team works directly inside Uber’s own systems and resolves these issues end to end, across all three sides of the marketplace. Straightforward cases are closed on first contact; the tangled ones — where a single problem touches the customer, the rider, and the restaurant at once — get worked until they’re genuinely solved, not just closed.
What makes it work is that the team doesn’t operate at arm’s length. They run on Uber’s own playbook and answer in Uber’s own voice, so to the customer, rider, or restaurant on the other end, there’s no seam between an outsourced team and an in-house one. That seamlessness is deliberate: every interaction is held to the same quality bar and reviewed regularly, with feedback going straight back to the agents — so the standard holds steady over time, not just in the first weeks after launch.
It’s high-volume, fast-moving, and often emotional work: invisible when it’s done well, and costly when it isn’t.