Review the Plain support queue
Connect Plain read-only and prepare a weekly review of recurring issues, response times, and at-risk customers.
The Plain support queue review template reads the threads opened or
updated in the review window, with their customers, labels, priorities, and
assignment, and groups them into recurring product issues, feature requests,
onboarding friction, and at-risk customers, reporting volume and time to first
response per group. It follows the customer-research marketing skill: short
anonymized excerpts as evidence, honest counts, and a closing list of
follow-ups worth human attention.
Enable and connect Plain
An operator must enable MANAGED_MCP_PLAIN_ENABLED. Plain's authorization
server at signin.auth.plain.com supports dynamic client registration, so no
static client is needed; connect the Plain card and sign in with your own
Plain account. Work on Repeat requests openid and offline_access only, and
access follows your Plain workspace role. Plain issues rotating refresh
tokens; Work on Repeat performs each rotation and stores the replacement
encrypted.
Set the variable
| Key | Example | Why it is a variable |
|---|---|---|
reviewWindowDays | 7 | The window should match the schedule; widen it for a monthly run without rewriting the instructions. |
Reference it in the instructions as {{reviewWindowDays}}.
Current beta boundary
Plain is connection-only until exact authenticated tool schemas are captured and reviewed, so the packaged routine ships as a preview. Support threads contain end-customer personal data, which is why even reads stay blocked until the review lands. Replying, assigning, snoozing, closing, and deleting threads are mutations and must remain blocked or approval-gated, and the routine's instructions already require anonymized excerpts.
Recovery
If authorization expires or is revoked, the connection moves to
reauthorization_required; reconnect the same card to update it in place.