Mixpanel
HubSpot
- Stripe
Slack
Trig
Catch usage drops early.
Create an agent assignment that checks account usage, from spotting the first drop past the 20% threshold to your team’s next step.
Use this templateWhat the agent does when an account’s usage drops.
Each week, the agent tells you the first week an account’s usage falls more than 20% below its usual level, with the features that fell.
How this agent manages usage drops.
The data and records the agent needs access to in order to deliver the work, and where you want it delivered.
What the agent hands your team.
Every account you own, checked against its own usual level, with new drops first and ready to act on in just a few clicks.
- 1Usual level. Each account is measured against its own history.
- 2Every account. Accounts checked with no alert are listed too, with the reason.
Frequently asked questions.
What is a usage drop agent?
It is a Trig agent set up to catch drops in product usage early. Agents can be fully customized to work based on your own unique usage signals, conditions, and situations. In this configuration, the agent checks the accounts you own each morning and alerts you the first week an account’s weekly active users fall more than 20% below its usual level. The agent names the features that fell most and adds seats, the renewal date, and the contract value.
How does Trig know an account’s usage has dropped?
Agents can be configured to compare each account with its own history. In this template, the usual level is the account’s median weekly active users over its last 12 complete weeks, leaving out weeks the customer marked as seasonal, such as holidays or shutdowns. An account is flagged in the first week it falls more than 20% below that level. Accounts with too little history are listed separately with the reason.
What does the agent prepare for my team?
In this template, the agent is configured to alert you in the week an account first drops, for the accounts that meet your targeting conditions. In a week with no new drop, it sends nothing and records that the check ran. For each new drop, it shows last week’s usage against the usual level, the features that fell most, seats in use against seats licensed, and the renewal date and contract value, with a 12-week chart. Accounts that remain past the threshold, or cannot be assessed reliably, are listed with the reason.
Will the agent contact the customer or change their health score?
No. Trig never contacts customers directly without express approval, which is controlled at the code level. In this template, the agent reads usage, CRM, and billing records and changes no CRM field or health score. The alert goes only to the customer success manager who owns the account, and your team decides what happens next.
What does the agent need access to?
Weekly usage for each account from your product analytics, and the CRM account with its owner, renewal date, and contract value. Usage by feature, licensed and active seats from billing, and any seasonal weeks add useful additional context where available. In Trig, you choose which connected sources agents can read, and you approve whether each assignment may send messages or update records before it runs.
Can we change how the template works?
Yes. A template sets up the assignment: what to produce, which accounts it covers, when it runs, and which tools it can use. You review the plan before it runs, and you can edit its instructions, accounts, recipients, or timing at any time, or pause it.
How long does it take to set up this template?
A few clicks. Once the tools it reads from are connected to Trig, you can set up this template almost instantly, review its plan, and the agent starts work on your accounts’ weekly usage.
