Callback Watch · Practical guide
Is this a new job or a question about the last one?
Put the earlier garage-door visit in view before the office makes a new promise.
A note from the studio
A homeowner says the garage door is making a noise again. The office has a new call, but the earlier visit is under a different contact name. Someone needs to see both records before deciding what to do.
Featured podcast / The Deeper DiveThe customer calls againWatch the illustrated story or listen after the guide
A useful connection, with the reason visible
In this fictional example, a garage-door customer calls twelve days after a visit. Callback Watch shows a possible related job at the address and links to the earlier notes. There may be two doors, so the office checks the details before deciding whether the jobs are related.
A match does not establish the cause of the problem or whether a return visit is covered. It gives the person answering better context. Staff decide what can be promised.
A small first build
Compare one intake source with a defined set of recent jobs. Exact job references should do most of the matching. Gemini can help compare unclear notes; Supabase can store suggested links and staff decisions; Railway can host the review screen.
Test false matches as well as missed connections. Show the supporting facts, and let a person dismiss a suggestion. Nothing should create a free appointment or send a customer commitment on its own.
The pilot question
Count connections the office confirmed, false matches, and how long it took to find the earlier job. Those are observations your team can check without inventing a savings figure.
The same review pattern may help other home-service businesses, but each needs its own definition of a related request. Start with one source and a manageable set of records.
A practical first step
What we would put in place
- Choose one kind of repeat customer question.
- Identify the order reference and conversation your team needs.
- Test suggested matches and let staff confirm each one.
Starting tool cost
Scoped build; tools start near $5/monthRailway Hobby has a $5 monthly minimum with included usage. Supabase can start on its free tier; Pro starts at $25/month. Gemini matching is billed by tokens on a paid tier. The pilot quote depends most on access to your job history and how clean those records are.
Check Railway pricing USD, checked September 26, 2026. Tool fees are separate from design, development, and ongoing care. See how Mata.Works quotes the build and care.Featured podcast / The Deeper Dive
The customer calls again
A garage-door concern may be tied to an earlier visit. The office needs the previous record before making a new promise.
Read the episode transcript
AI voices perform a script reviewed by Mata.Works. Landon and Tam are the illustrated hosts. The business scenario is an example.
Landon: A homeowner says the garage door is making a noise again. Your team was at that address twelve days ago. Does that mean it is the same problem?
Tam: Not necessarily. There might be two doors. The customer might be describing something different. But the person answering should be able to see the earlier visit before making a new promise.
Landon: That sounds simple. Why does it get missed?
Tam: The first appointment may be under another household member's name, or the notes may be buried in a different screen. The customer repeats the story while the office hunts for it. Callback Watch would put a possible connection in front of the person taking the call.
Landon: What would that connection look like?
Tam: A small card: same address, a recent job reference, and the relevant notes. It says why the records might belong together. Staff can confirm the connection or dismiss it. A matching address alone is not a decision about what caused the problem.
Landon: Does the tool decide whether the next visit is free?
Tam: No. Your team decides what the earlier agreement covers and what to offer. The tool helps them find the record. It must not promise free work or book a return on its own.
Landon: What would you build this with?
Tam: Start with one intake source and a manageable list of recent jobs. Supabase can hold the links and review decisions. Gemini can help compare unclear notes after exact job references have been checked. Railway can run the review page.
Landon: What should the owner look for in the pilot?
Tam: How many suggestions were right, how many were wrong, and whether staff found the earlier job more quickly. Try it on fictional or approved examples first. If repeat calls regularly turn into a search party, show us that handoff and we can scope a small review tool around it.
Would this fix a real snag at your shop?
Review how repeat calls are handled