- Asana
Mixpanel
HubSpot
- Zendesk
Slack
Trig
Catch stalled onboarding early.
Create an agent assignment that watches every open rollout on your accounts, from spotting where it stalled to the restart your team chooses.
Use this templateWhat the agent does when a rollout stalls.
When Trig sees onboarding or a rollout stall, the agent shows where it stopped, the likely cause, and two or three ways to restart.
How this agent manages stalled rollouts.
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.
Where the rollout stopped, the likely cause, and the ways to restart it, ready to read in under a minute.
- 1Cause. Where it stopped and the likely cause, with sources.
- 2Milestones. Each step of the plan, done or missed, by date.
- 3Usage. Active users in the rollout against the target.
- 4Restart. Ways to restart it that fit the cause.
Frequently asked questions.
What is a stalled onboarding agent?
It is a Trig agent set up to catch onboarding and rollouts that stop moving. In this configuration, the agent watches each open rollout on the accounts you own and alerts you when a rollout stops moving, measured by milestones, usage, and checkpoint targets. The agent shows where the rollout stopped, the likely cause, and two or three ways to restart it.
How does Trig detect stalled customer onboarding?
Agents can be configured to check your customer onboarding milestones and weekly usage against the rollout plan. In this template, a rollout has stalled when no milestone has moved for 14 days, active users have been flat or falling for 21 days, active users were under half the target at day 30, 60, or 90, or a setup step has been blocked for more than 10 working days.
What happens after Trig detects stalled onboarding?
In this template, the agent is configured to deliver an alert for each stalled rollout that meets your targeting conditions. It gives the stall tests that are true, with their figures, where the rollout stopped, and the likely cause from the records, quoting the customer where it can. Then it sets out two or three ways to restart it that fit the cause, with who is involved and what working looks like within 14 days, and the account’s renewal date and value. Your team chooses how to restart the rollout. Trig can then draft an email for you to edit and approve before Trig sends the email.
Will the agent contact the customer about the rollout without my approval?
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 milestone. When you choose a way to restart the rollout, Trig can draft the email for you to edit and approve before Trig sends it.
What does the agent need access to?
The rollout plan with its milestones and owners, weekly product usage for the people in the rollout, and the CRM account with its renewal date and value. Setup tickets, customer emails and calls, training records, and the sales handoff 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 onboarding and rollouts.
