Customer success integrations and automations

What this work has in common

The systems that know a customer is in trouble are rarely the ones the account team works in. Product usage sits in the warehouse. Tickets sit in the help desk. Survey responses sit in a third tool. Call notes sit in a conversation intelligence product. The CSM works in the CRM and sees none of it until the renewal conversation.

The work in this category is choosing a small number of signals somebody can act on and putting them where that person already works, with the reason attached. A drop in weekly active users on its own is noise. A drop in weekly active users on an account with two open priority tickets and a renewal in sixty days is a reason to call.

The guides cover the handoff from sales to onboarding, routing support tickets on skill and account, product usage and survey data into the CRM, and health signals built so they can be checked against what actually happened.

The usual stack is Salesforce, Zendesk, a warehouse such as Snowflake, a product analytics tool such as Amplitude, Gong and Slack. The prompts name those systems as a worked example, and the design carries across to the equivalents.