Five skills, one customer list
A small team’s customers write in, get on calls, report bugs and, some weeks, cancel. Somebody on the team owes each of them something: a reply, a recap, a fix, a question. Customer Comms is five skills that keep that list and do the writing, so the person on the team only reads and hits send.
They share one customer list: one row per customer, who on the team owns them, whether they pay, what the team owes them, and one line of advice on using your product, when there is a place to see how they use it. Each skill adds to that list or reads from it.
Every email they write waits in Gmail Drafts. None of them sends. A GitHub issue is the one thing filed on its own, and only after you say where issues go.
Each skill is a page of plain instructions in your workspace. Read it, change it in chat (“make the recaps shorter”, “never write to our investors”), and it says what it changed.