Hey, we just fixed that for you

A customer takes the time to tell you something is broken. Your team files it, fixes it and ships it, and the customer never hears a word. This watches your tracker for fixes a customer reported and, once each one is live, writes that customer a short note: what they told you, that it’s fixed, and how to see it.

What it does

• Finds the issues a customer reported that your team closed as done, on request or on a verified schedule.
• Waits until the fix is live, the way your team says it is: closed, labelled, or out in a release. Never on a guess.
• Knows who reported each one from User Chats to Issues and your customer list, including every customer who reported the same bug.
• Writes two or three warm sentences in the sender’s voice, in reply to the customer’s own email when there is one.
• One note per fix, per customer. Two fixes for one customer the same day go in one note.
• Leaves it in the sender’s Gmail Drafts until you turn on auto-send. Then it sends it itself.
• Marks the customer’s row on the team’s customer list.
• Keeps a short list of what customers wished for on calls, in email or in chat that never became an issue. When the team ships one, that customer hears “we just shipped it”, once, and only if it reaches their kind of account.

The reveal

On Tuesday a customer emails that the export stops at 10,000 rows. On Thursday the fix ships. By Thursday afternoon there’s a reply on their own thread: “You told us the CSV export stopped at 10,000 rows. That’s fixed now, so your next export will have every row. Does that match what you were running into?” They write back to say it does.

Configuration

• Your tracker: where fixes close, read with the account you connect.
• What shipped: your changelog, release notes or notes page, and merged work. Without it, the wish list stays off.
• Where wishes are said: the inboxes, call notes and chat channels User Chats to Issues and Call Recap Drafts already read.
• When a fix is live: when the issue closes, when it gets a label like deployed, or when a release ships after it closes.
• Who sends the note: one person on the team, from their own account.
• Auto-send: off until the sender turns it on in chat.
• How often: when you ask, or a few times on weekdays if an available scheduler can run the work and you approve it.

What it doesn’t do

• It doesn’t send until you turn on auto-send.
• It doesn’t write before the fix is live, or for issues closed as not planned or duplicates.
• It doesn’t touch your tracker. It only reads.
• It doesn’t write twice about the same fix or wish.
• It doesn’t say a feature is on when your team turns it on by hand. It offers to turn it on.
• It doesn’t mention issue numbers, pull requests or dates.

Triggers

Runs when you ask (“tell customers what we fixed”, “who should hear about this fix”). Regular checks need a verified scheduler and your approval; otherwise it runs a bounded check now and saves where it got to.