A support team that sends replies with receipts

Halden Freight is a made-up company, and this is an illustrative story. We wrote it to show how a team in a familiar situation might use Lanternfish, and the numbers below are examples, not measurements. Any resemblance to a real company is accidental.

The situation

Halden Freight moves parts between warehouses, and its support team of nine answers customers about delays, customs paperwork and contract terms. The answers exist, but they live in four places: a shared drive of contract PDFs, the ticket history, a wiki of internal rules and a busy chat channel where the senior people on the team trade tips.

Before Lanternfish, a hard question went to whoever "knew where it was." That person was usually in a meeting. Customers waited, and new hires learned quickly that the fastest way to answer was to ask a colleague instead of searching.

What changed and what they noticed

The team connected the drive, the ticket system and the chat workspace in one afternoon. Nothing had to be moved or tagged. Each person kept exactly the access they already had, which mattered because the contract folder is limited to account managers and the leads.

The first habit that changed was small. Instead of pinging a colleague, people typed the customer's question into Lanternfish and read the answer. Every sentence carried a receipt, so a reply could quote the clause or the earlier ticket directly. The support leads asked everyone to paste the receipt link into any reply that quoted a policy.

In this story, first replies went out in about half the time. The more interesting change was what happened afterwards. Fewer customers wrote back with "where does it say that?", because the answer already showed where.

Three other effects showed up within a few weeks:

• New hires reached a normal pace sooner, since they could check an answer themselves instead of waiting for a senior colleague.

• The wiki got better. When a receipt pointed to an outdated page, someone fixed the page that same day.

• Disagreements got shorter. When two people remembered a rule differently, they opened the receipt and settled it.

What did not change, and how to try it yourself

A person still decides what to send. Lanternfish drafts nothing on its own and marks any sentence it could not source as an inference, so the team treats those as prompts to check, not as facts. When an answer comes back thin, they treat that as useful information: it usually means a rule was never written down, and the team writes it down.

The senior team members also kept their chat channel. They simply stopped using it as the only memory of how things work.

If you want to repeat the exercise, pick ten questions your team answered last month and ask them again. Open the receipts, and note which ones point to the right passage and which ones point to something outdated. That list is the fastest way to learn where your documents need attention, whether or not you adopt anything else.