Which overdue repairs should our team follow up today?

A worked jewelry example: how Claude turns “what is overdue?” into a clean list your team can act on, and where the human takes over.

Worked exampleApplies to The Edge · Claude

Short answer

Ask “which repairs are past their promised date?” and Claude reads the repair records it is permitted to see, as of the last export, and hands back a short list: the customer, the item, the promised date, and how many days over. It does not call anyone. It gives your team a current, source-backed list so the follow-up stays human.

Who this is for

A jewelry store team that wants to start the day with the overdue-repair list in front of them, without pulling a report or clicking through the point of sale.

What you need first

• The Edge, or your point of sale, connected through the scheduled export.
• The repair fields in scope: customer, item, promised date, status.
• A person who will make the calls. Claude surfaces the list; your team owns the conversation.

How it works

1. The question. Someone asks, in plain words, “which repairs are past their promised date?”
2. The permitted fields. Claude reads only the repair fields its role is allowed to see: customer, item, promised date, current status.
3. As of the last export. The answer is current as of the last export. A repair finished after that is not reflected until the next run, and Claude is clear about the date it is working from.
4. A source-backed answer. It lists each overdue repair with the days over, drawn from the records, not guessed. An illustrative list (fictional, for shape only): a watch battery promised Tuesday, now three days over, and a ring sizing promised yesterday, one day over.
5. The human handoff. Your team reads the list, calls the customers, and updates the repair in the point of sale. Claude does not write anything back.

What it can and cannot do

It can

• Surface the overdue list, source-backed, as of the last export.
• Keep the answer to the fields and customers a person's role is allowed to see.
• Save the daily report pull, so the team spends the time on the calls.

It cannot (as we run it today)

• Know about a repair completed after the last export. That shows up next run.
• Make the follow-up call or change the repair record. The handoff is deliberately human.
• Show a customer or a field the person's permissions exclude.

How current is the list?

As of the last export, not the live counter. A repair marked done an hour ago may still show as open until the next export runs, so treat the list as this morning’s picture and confirm anything time-sensitive in the point of sale before you call.

How we know

EvidenceSupported capability under gate

The connection this example runs on is in production on The Edge, which we last verified running on August 27, 2026. Past-due repairs is a lookup that connection supports, answered as of the last export. The list above is a constructed example to show the shape of the answer. We do not publish a real store’s repair data.

Where to go next

• Talk to us about your jewelry storeTell us what you run and what you would ask.
• How do I connect The Edge jewelry POS to Claude?The connection behind this example.
• Is yesterday's export fresh enough for this question?Match the question to the data.