Brief account health from Pylon
Connect Pylon read-only and prepare a weekly brief of accounts whose support signals point to churn risk.
The Pylon account health brief template reads the accounts in one segment
with their open issues, recent conversations, and health signals, flags
accounts with rising issue volume, unanswered conversations, or overdue
commitments, and proposes one human follow-up per at-risk account with the
account and issue cited. It follows the churn-prevention marketing skill:
surface risk early, separate observed evidence from interpretation, and hand
the save motion to a person.
Enable and connect Pylon
An operator must enable MANAGED_MCP_PYLON_ENABLED. Pylon's authorization
server at o.auth.usepylon.com supports dynamic client registration, so no
static client is needed; connect the Pylon card and sign in with your own
Pylon account. Pylon publishes no granular OAuth scopes, so the token can reach
only what you can already see in Pylon.
Set the variable
| Key | Example | Why it is a variable |
|---|---|---|
accountSegment | Enterprise | The segment or tier under watch changes; the brief's shape does not. |
Reference it in the instructions as {{accountSegment}}.
Current beta boundary
Pylon is connection-only until exact authenticated tool schemas are captured and reviewed, so the packaged routine ships as a preview. After review, the first manifest should stay read-only: account, issue, and conversation reads. Replies, reassignment, closing, and account edits are mutations and must remain blocked or approval-gated.
Recovery
If authorization expires or is revoked, the connection moves to
reauthorization_required; reconnect the same card to update it in place.