Zepto Details AI Support System, Says Support Costs Fell 65%

The company’s newly disclosed system puts testing and live monitoring in one loop, but its operational and customer-service gains are Zepto-reported results rather than an independent evaluation.

By 3 min read
Zepto Details AI Support System, Says Support Costs Fell 65%
Zepto Details AI Support System, Says Support Costs Fell 65%

Listen to this story

The audio brief

About 1:29
0:001:29
Read transcript
Zepto says its AI support system now handles more than 100,000 tickets a day, with agents fully managing over 80 percent under human oversight. The notable part is not just the automation. It is the control system around it: testing before release, tracing what happens in production, and feeding failures back into development. Built with Databricks and MLflow, the system evaluates a multi-agent workflow that can classify a request, retrieve information, make a decision, and call transactional tools. It records prompts, model outputs, retrieved documents, tool calls, latency, and decision paths—not just the final answer a customer sees. Before an updated agent goes live, it is tested against a golden dataset of real and difficult examples. That dataset grew from 500 to 5,247 examples over six months. The release gate combines LLM judges for tasks requiring human-like judgment with code-based checks for things like tool-call counts and latency. A failed gate can block deployment, while failures from live traffic become new tests for the next version. Zepto reports a 65 percent reduction in support costs, four-times-faster resolution, 20 percent higher customer satisfaction, and three-times-faster development cycles, with payback in under a month. But these are figures from a Databricks customer case study, not an independent evaluation. Ticket mix and measurement methods were not disclosed. The key question is whether those results hold across support categories at this scale.

Story brief

3 key points

Zepto’s customer-support automation is being presented as an evaluation-and-observability system, not simply a chatbot deployment. Built with Databricks and MLflow, it uses traced prompts, retrieval, tool calls, latency, and decisions plus a 5,247-example golden dataset to gate releases and feed production failures back into development. For a workflow handling over 100,000 daily tickets, Zepto reports 65% lower...

  1. 01

    The evaluation dataset grew from 500 to 5,247 examples over six months as Zepto reduced its development-to-production accuracy gap.

  2. 02

    Agents fully manage more than 80% of tickets under human oversight, while the system traces tool calls, retrieval, latency, and decision paths.

  3. 03

    Zepto reports 20% higher customer satisfaction, 8% higher accuracy, fourfold faster resolution, and threefold faster development cycles.

Zepto says its AI customer-support system now handles more than 100,000 tickets a day, with agents fully managing more than 80% under human oversight. Its answer to the risk of automating service at that scale is not a single model upgrade: it is a quality gate that tests agent changes before release and sends live failures back into development.

The system, disclosed Tuesday in a Databricks case study, is a multi-agent setup built with Databricks and MLflow. Zepto and Databricks describe it as evaluation-first: teams define what acceptable performance looks like, evaluate agent versions against that standard, and monitor the same standards after deployment.

The operational problem is hidden failures

A support agent does more than write a response. It can classify a request, retrieve information, analyze inputs, make a decision and call transactional tools. Zepto’s framework traces those steps—including prompts, model completions, retrieved documents, tool calls, latency and decision paths—rather than judging only the final customer-facing answer.

Diagram of Zepto’s development and production loops connected by a quality gate.
Zepto describes a development loop, a production loop and a quality gate between them. Source: databricks.com.

A dataset becomes the release checklist

Before an agent version can move forward, Zepto evaluates it against a “golden dataset”: annotated examples covering ordinary requests, edge cases and failures. Its evaluation stack combines built-in and custom large-language-model judges, which score work requiring human-like judgment, with code-based scorers for deterministic checks such as tool latency or call counts.

The framework’s core feedback loop is deliberately circular. Production failures are captured and added to future development evaluation, while a quality gate decides whether a revised agent version is deployed or returned for more work. MLflow says its tooling can reuse judges and scorers from development in production monitoring; Zepto’s case study shows that pattern applied to a customer-support workflow.

Zepto’s reported deployment results
80%+Tickets fully managed by AI

Zepto reports that its agents fully manage more than 80% of support tickets with human oversight.

65%Support-cost reduction

Zepto reports a 65% reduction in support costs and payback in less than one month.

8 pointsDevelopment-to-production accuracy gap

Over six months, Zepto says it expanded its evaluation dataset from 500 to 5,247 examples while reducing this accuracy gap.

The results are promising, but company-reported

Zepto reports that the framework reduced support costs by 65%, improved customer satisfaction by 20%, raised accuracy by 8%, and shortened time to resolution fourfold. It also says development cycles became three times faster and that the investment paid back in under a month.

Those figures come from Zepto’s account in a Databricks customer story, not from an independent comparison or audit. The disclosure does not establish how the metrics were measured, which tickets remained under human handling, or how performance varied across different support categories. What it does show is a concrete operating choice: treat evaluation data, trace records and release thresholds as production infrastructure, alongside the agents themselves.

Sources

  1. docs.databricks.comdocs.databricks.com
  2. databricks.comEvaluation-First AI Agents: How Zepto Scales Customer Support on Databricks and MLflow

Loading discussion...