HubSpot
Mixpanel
Gmail
- Zendesk
Slack
Trig
Diagnose every at-risk account.
Create an agent assignment that reviews every account that turns red, from finding the likely cause in its past year to the save play your team chooses.
Use this templateWhat the agent does when an account turns red.
When Trig flags an account at risk, the agent lays out its last 12 months, the likely cause, and two or three save plans.
How this agent manages at-risk accounts.
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.
The likely cause, the year behind it, and two or three save plays that fit, ready to read in under five minutes.
- 1Cause. The likely cause, how sure Trig is, and its evidence.
- 2Timeline. The account’s year, from the first sign to today.
- 3Usage. Active seats over 12 months against seats licensed.
- 4Plays. Save plays that fit the cause, with owners and dates.
Frequently asked questions.
What is an at-risk account review agent?
It is a Trig agent set up to find out why an account is at risk and how to save it. Agents can be fully customized to work based on your own unique risk signals, conditions, and situations. In this configuration, the agent reviews each account you own when its health turns red or it is marked at risk. The agent lays out the account’s last 12 months, names the likely cause, and sets out two or three save plays.
How does Trig find the likely cause?
Agents can be configured to read an account’s history in date order and match it against common causes, such as a sponsor or champion who left, stalled use, the customer never seeing the value they paid for, a service failure, a budget event, or a competitor being evaluated. The agent raises only causes the records show, says how sure it is, and lists missing data as a gap to fill.
What does the agent prepare for my team?
In this template, the agent is configured to deliver a review for each account that meets your targeting conditions. It opens with the contract value, days to the notice date, health now against 12 months ago, and whether to escalate. Then it gives the likely cause and how sure it is, a dated timeline, the customer’s own words, the people and teams the save plan can build on, and two or three save plays with steps, owners, dates, and signs they are working.
Will the agent contact the customer or offer a discount?
No. Trig never contacts customers directly without express approval, which is controlled at the code level. In this template, the agent reads your records and changes no CRM field or health score. A discount, credit, or term change appears only as a decision for whoever approves it under your rules, with the case laid out, and your team decides which save play to run.
What does the agent need access to?
The CRM account with its contacts, contract value, and renewal and notice dates, plus 12 months of health scores and product usage. Customer emails and calls, support tickets, the success plan, and your team’s own save plays 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 at-risk accounts.
