---
title: "Delivery claims with an AI agent | StudioChat"
description: "Put in your own numbers and compare what answering one delivery claim across four screens costs today against the same claim handled by an agent."
url: https://studiochat.io/delivery-claims-with-an-agent
locale: en
translations: { es: https://studiochat.io/reclamos-con-un-agente.md, pt: https://studiochat.io/reclamacoes-com-um-agente.md }
site: https://studiochat.io
---

Tool

# One delivery claim, end to end

How many claims come in a month, how many minutes closing each one takes, what an hour of the person answering costs, what share ends in a wrong credit note and what that costs. Below, the same claim with an agent: where it goes, what it does at each step and what stays with a person.

One delivery claim, end to end

* the agent does it
* a person does it
* always a person

the steps of the claim

* the agent does itIdentify which order they mean Orders 
Resolves the order from the phone number, the name or the last purchase, without asking for a number the customer does not have.
* the agent does itQuery the carrier for the status Carrier 
Asks the carrier by tracking number and brings back the last event with its date, during the conversation.
* the agent does itTranslate it into a date Carrier 
Turns in transit into when it was due, what has happened since the last event, and whether to wait or whether this is already a problem.
* the agent does itSpot the delayed shipment Carrier 
Compares status against the window and flags the ones that slipped, instead of waiting for the customer to notice first.
* the agent does itWrite before they ask WhatsApp 
Messages the customer of a delayed shipment before they message, which is the only way the second message never exists.
* the agent does itOpen the claim with the carrier Carrier 
Assembles the claim with number, due date and last event, ready to send, which is the step postponed today for lack of time.
* the agent does itLog the case and what the carrier said CRM 
Records what was asked, what the carrier answered and what the customer was told, so the next message does not start from zero.
* always a personCommit to a new date CRM 
Promising a customer a day is a decision. A person makes it, with the claim already open and the carrier's answer in view.

Shipping enquiries per month: 300

Minutes answering one takes today: 14.0

Hourly cost of whoever answers: USD 12

Share answered badly or overpromised: 4%

What that second round with the customer costs: USD 40

Today that is 70 hours a month and 12 enquiries answered badly. Between the time and the second round, USD 1,320 a month.

With the agent holding 7 of the 7 steps, 3 hours and USD 60 are left.

The difference is USD 1,260 a month, USD 15,120 a year.

And 36% of that difference is not time: it is the answers that do not produce a second message the next day.

Of what a person still does, the heaviest step is: Commit to a new date.

You set all five numbers. How the minutes split across steps is ours, taken from how it gets done by hand. The modelling assumption: the badly given answer falls in the same proportion as checking the status and translating it stop depending on somebody having time.

This object is the interactive half of an article: [Answering where an order is takes four screens and one translation](/blog/reclamos-de-entrega)

## The playbook already exists. We multiply it.

[Talk to us now](https://cal.com/studiochat)

[Book a demo](https://cal.com/studiochat) [Or write to hey@studiochat.io](mailto:hey@studiochat.io)