Introducing the new Trig.

Every customer should get the attention they need. But across hundreds or thousands of accounts, there is more work than any team can deliver. Knowing which customer is struggling still leaves someone to investigate the problem, prepare a response, and make sure the next step happens.

Over the summer, we rebuilt Trig to solve that capacity problem for account management and customer success. Today, we're introducing the first AI workspace where your team members manage agents, and agents do the account work.

Agents monitor customer activity, follow up on stalled onboarding, prepare renewal reports, and build expansion cases. Your team directs the work and reviews the results. Trig learns from how customers respond and uses that understanding to inform what happens next.

The ambition is to give a team member who could manage 50 accounts the capacity to manage 500. That requires the work behind those relationships to get done across the customer base, with the context to make it relevant to each account and a clear way for people to stay involved.

Trig brings those parts together: Trig Agents do the work, the Control Panel lets your team direct it, the Context Engine informs each task, and Integrations connect the work to your existing systems.

Tell Trig what you need to get done

The working model is simple: your team members manage agents, and agents do the account work. In practice, your team directs that work through assignments.

An assignment defines a task for agents to complete, such as preparing renewal reports for accounts renewing in the next two weeks. You describe what you need in plain language, then review the plan and permitted actions before activating it. Ready-made templates provide starting points for recurring tasks.

Each assignment specifies the accounts it covers, who the work is for, when it should run, and which tools and actions agents may use. Accounts can be selected by segment, owner, or customer need. Groups can update as customers meet the criteria, so the same assignment can serve new accounts over time.

Account work	What agents produce or do
Onboarding follow-up	Prepare a message based on the setup step a customer has missed and the context behind it.
Renewal preparation	Assemble contract details, usage, support history, and open commitments into a report before renewal.
Expansion preparation	Gather evidence that an account is ready to grow and draft the opening message.
Meeting preparation	Bring together recent changes, previous discussions, and points to cover before a customer call.
Post-call work	Draft the follow-up and write agreed notes, risks, and next steps to the CRM.

Assignments can run on a recurring schedule, before an account date, or when Trig detects a condition you have defined. A team might prepare meeting briefs every Monday, assemble reports two weeks before renewal, and start an onboarding follow-up when a milestone is missed.

Give agents the customer context behind each task

Those tasks depend on understanding the account. A useful renewal report needs to reflect what the customer wanted to achieve, what they have used, and which commitments remain open.

The Context Engine brings CRM, product, support, and billing data together with conversations and previous agent work. Its account memory retains customer priorities, purchase reasons, and past commitments, giving agents that context when they prepare the next task.

Your team can also define customer journeys: the stages and milestones that show whether customers are getting value. For onboarding, that might mean completing an integration and adopting a key workflow. For an established account, it might mean bringing a second team onto the product.

Trig compares customer activity with those milestones and relevant benchmarks to identify Signals, the risks and opportunities in your accounts. Slow onboarding, declining usage, and an account approaching its seat limit can each indicate a different need. Signals are ranked by potential revenue impact and can select accounts for an assignment or trigger work your team has configured.

You can also begin with a selected list of accounts and a straightforward task. Journeys and Signals give you more ways to target the work as your use of Trig develops.

Direct the work from one workspace

The Control Panel is where your team manages assignments and reviews what agents have done. Team members can see the work for their accounts alongside the customer context. Leaders can review coverage and completed work across team members, teams, and customer groups.

That makes it possible to manage high-touch customers and scaled customer programs in the same workspace. An enterprise account can have detailed renewal preparation, while a larger group of smaller accounts receives onboarding follow-ups tailored to their progress.

Each time an assignment runs, Trig records its status, the accounts involved, and what it produced. Your team can inspect that run history, trace a report or update back to its assignment, and change the instructions, accounts, recipients, or timing. Assignments can also be paused.

Needs you brings customer alerts and blocked work into a prioritized view. It explains which account is affected and what input is needed. A customer issue may require a conversation; a blocked CRM update may require a field mapping to be corrected. The person reviewing it has the context to decide what to do next.

Put agents to work across your existing tools

Trig uses connected tools to gather information and carry out the assignment. Account details and ownership can come from Salesforce or HubSpot, product activity from analytics tools, and previous discussions from your customer conversations.

Completed work goes to the destination your team chooses. Briefs and reports can be viewed in Trig or delivered to a connected messaging or document tool. Outreach uses your connected communication tools, and CRM updates are written back to the account record.

Your team authorizes the sources agents can read and the actions an assignment may take. A follow-up can remain a draft for a person to send, or be sent through a permitted connection once the wording has been approved. Reviewing an assignment establishes what it is allowed to do on subsequent runs.

That keeps the workspace connected to the places where customer conversations happen and account records are maintained. The work your team reviews in Trig can become a message, document, or record update in the system where it is needed.

How the parts work together on stalled onboarding

Consider a team monitoring 500 customer accounts. It wants to help new customers who have missed an integration milestone in onboarding. This is an example of how the team could configure the work.

1. Define the work and its limits. The team creates an assignment for the onboarding segment. It asks agents to review the missed milestone and prepare a relevant follow-up, choosing the sources they may use, the recipient, and whether the message should remain a draft or be sent after wording approval.
2. Identify the accounts that need help. When monitoring detects the configured condition, the assignment uses the affected account's product activity and conversation history. A recent discussion may explain that the customer is waiting for an administrator to finish setup. That context informs the message.
3. Prepare and deliver the response. The agent prepares a follow-up about completing that integration, using the account's context. It drafts or sends the message within the approved instructions. If the assignment also includes a CRM update or a notification to the owner, those actions use the authorized connections.
4. Review the work and customer progress. The team can see what the assignment produced and resolve anything that needs human input. Subsequent account data shows whether the integration was completed, giving the team evidence to review alongside the outreach.

The same assignment can cover every account that meets its criteria. Your team sets the task and checks the work, while agents gather the relevant history and prepare the response for each customer.

Learn from what happens after the work

Trig follows both the work completed and the customer's subsequent progress. In the onboarding example, sending a message completes an action; seeing the customer finish the integration shows progress toward the assignment's objective.

The Context Engine compares subsequent activity with the intended progress and connects the account's history with eventual renewal, expansion, contraction, or churn. Successful and unsuccessful responses inform how agents approach similar customer needs in future tasks.

For your team, this creates a way to review the assignment over time. You can see what agents did, what customers did afterward, and where the instructions need adjusting. Customer progress is evidence for that review, with the wider account history providing context for the result.

That makes learning part of the ongoing account work. Each new task can use what is already known about the customer, including previous agent work and what followed it.

What the $1 account price and AI credits cover

Trig prices account monitoring separately from AI work. Monitoring keeps account information current on the selected cadence and covers account checks and analysis. AI credits cover work such as creating assignments, processing information, preparing plans and briefs, and drafting outreach.

Standard starts at $250 per month for up to 500 accounts monitored weekly, with unlimited users and 10,000 AI credits worth $100 included once when you start. Those credits are shared across the organization.

Item	How it is priced
Standard	$250 per month, including up to 500 accounts monitored weekly.
Additional accounts	$1 per account per month beyond the included 500, monitored weekly.
Daily monitoring	An additional $9 per selected account per month.
AI work	Uses credits, with more available to purchase as needed after the initial allocation.

For example, 1,000 accounts monitored weekly cost $750 per month for the plan and monitoring: $250 for the included 500, plus $500 for the additional 500. Additional AI credit purchases are separate. Standard's first three months are paid upfront, which is $750 for the base plan, followed by monthly billing.

Weekly and daily monitoring determine how often account data is pulled from connected sources. Agents can do the same types of work at either frequency, with assignment schedules and triggers configured separately. The pricing page explains the options and credit purchases in detail.

Start with one task, then expand account coverage

Trig's team helps connect the data and set up your first assignment. You bring a recurring task, choose the accounts, authorize access to the relevant systems, and identify who will review the work.

After the first runs, review what agents produced, how much time your team spent checking and correcting it, and whether customers made the progress you intended. Those measures help you decide what to change and which work to add next.

The capacity gained depends on the tasks agents take on and the attention your customers need from people. As more recurring work is handled through assignments, your team members can spend more of their time on customer conversations and decisions while extending coverage to accounts they previously could not actively manage.

An agent for every account is a way to put that capacity to work across your whole customer base: agents keep up with customers and do the account work, while your team directs how they help each customer succeed.