Good talking today; quick recap

Every customer call ends with promises on both sides, and the recap email is the thing that makes them real. It is also the email most likely to slip. This reads the notes and the transcript after each customer call, pulls out what the customer said they would do and what you said you would do, picks the check-in day, and leaves the email in your Drafts. You read it and send it.

What it does

• Finds the customer calls of the last two days from your meeting-notes tool, on request or on a verified hourly schedule. Skips internal calls, standups, vendors, investors and recruiters.
• Works out who the customer is from the attendees, your calendar and the transcript. When it is not certain, it writes nothing and tells you why.
• Reads the transcript, not just the summary. Every line in the recap traces to something said on the call.
• Writes a short email in your voice: what you’ll do, what they’ll do, the day you’ll check in, one personal line if there was one.
• Adds one line of advice on using your product, when the team has connected a place that shows how the customer uses it.
• Leaves it in your Gmail Drafts, on the thread you already have with them if there is one. It never sends.
• Puts the check-in day on the team’s customer list, so the person comes back as a follow-up when it arrives.

The reveal

The call ends at 2:30. At 3:00 there is a draft in your inbox: “Good talking today; quick recap,” four bullets of theirs, two of yours, “I’ll check in Wednesday,” your sign-off. You change one word and send it. Wednesday morning, their name is on your follow-up list.

Configuration

• Where your calls are: the meeting-notes tool to read, and the calendar that says who was on each call.
• Who sends recaps: the people on the team who take customer calls, each from their own account.
• Your voice: greeting, sign-off and the few habits that make an email yours, learned from your real sent mail.
• Where you see usage: optional. A place that shows how a customer uses your product, for the one line of advice.
• How often: when you ask, or every hour on weekdays if an available scheduler can run the work and you approve it.

What it doesn’t do

• It doesn’t send. Every recap waits in Drafts.
• It doesn’t add promises. No dates, prices, refunds or features that were not said on the call.
• It doesn’t guess who the customer is. Unsure means no draft and a note to you.
• It doesn’t file bugs the customer raised. That is what User Chats to Issues is for.

Triggers

Runs when you ask (“draft a recap for my call with Dana”, “follow up on that call”). Hourly checks need a verified scheduler and your approval; otherwise it runs a bounded check now and saves where it got to.