Drafted from what happened on the call, sent from wherever the conversation started, and logged against the request that triggered it.
“The scheduled exports you asked for in March went live last week…”
“Following up on the SSO rollout — your admin hasn't been invited yet…”
“You mentioned publishing weekly. It's been three weeks since the last…”
“Congrats on the launch — noticed the new team spun up 14 seats…”
Every send is recorded, so the follow-up history survives the person who sent it.
Gmail, Outlook, the original Slack channel, or a direct message resolved from the contact email.
Drafts reference the specific ask, commitment, or shipped feature behind them — not a generic check-in template.
Marking done, sending an email, and posting to Slack all record the destination, the message, and the requests they close.
Review each draft individually, or send a personalized batch across a whole segment at once.
The customer success jobs this feature does. Entries marked partially shipped have known gaps.
After every customer call, a CSM spends twenty minutes writing notes, updating fields, extracting action items, and drafting a follow-up.
BuildBetter records the call, extracts the commitments and tasks, updates the account record, and drafts a follow-up that reflects what was said.
A transcript becomes updated fields, a task list, and a ready-to-send follow-up draft.
A customer asks for something, engineering ships it eight months later, and nobody ever tells the customer who asked.
Shipped work is matched back to the customers who requested it, and the follow-up drafts itself — sendable by email, to the original Slack channel, or as a direct message.
A release matches its requesters and produces per-customer follow-ups ready to send.
Tasks
The queue every follow-up lands in, across BuildBetter, Attio, and HubSpot
Close the Loop
The follow-up writes itself once you have shipped what they asked for
