HubSpot
Mixpanel
- Zendesk
Slack
Trig
Prepare your weekly at-risk meeting.
Create an agent assignment that reviews at-risk renewals before your weekly meeting, from checking each save plan to the renewals you choose to step into.
Use this templateHow the agent reviews at-risk renewal plans.
The agent checks each save plan has an owner and is progressing, and names the renewals that need you.
How this agent manages at-risk meeting prep.
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 at-risk renewal on your team checked four ways, with the ones that need you first, ready to read in under three minutes.
- 1Needs you. The renewals to step into this week, with a suggested way to help.
- 2Four checks. Each save plan checked for an owner, progress, contacts, and the customer taking part.
Frequently asked questions.
What is an at-risk meeting prep agent?
It is a Trig agent set up to prepare the head of customer success for the weekly at-risk meeting. Agents can be fully customized to work based on your own unique risk signals, conditions, and situations. In this configuration, the agent runs before each weekly at-risk meeting, and again when a red renewal comes within 30 days of its notice date. The agent checks the save plan on every at-risk account your team owns and ranks up to three renewals that need you.
How does Trig know a save plan has stalled?
Agents can be configured to check each save plan against your team’s records. In this template, each plan gets four checks: it has an owner and a next step with a date, it is making progress, more than one person at the customer is engaged, and the customer is attending meetings and replying. The agent then rates each plan on track, stalled, or failing. Without customer activity data, it says progress could not be checked.
What does the agent prepare for my team?
In this template, the agent is configured to deliver a one-page prep for the at-risk accounts that meet your targeting conditions. It opens with the value at risk and the plans stalled or failing. It then warns of red renewals within 30 days of notice and accounts with no customer contact for 21 days, lists accounts with no plan, and shows the four checks for every plan. Each renewal that needs you comes with a suggested way to help.
Will the agent contact customers or change the at-risk register?
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 nothing in the at-risk register or the CRM. It never blames a customer success manager or estimates the probability of churn. Your team decides where to step in, and each plan’s owner makes any updates.
What does the agent need access to?
The at-risk accounts and their save plans from your CRM or customer success platform, and the CRM accounts with value, notice dates, meetings, emails, and contacts. Without a register, the agent rebuilds the list from red and amber accounts and asks your team to confirm it. Product usage and support tickets 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 weekly at-risk meetings.
