← Back to the Agent Playbook
Interactive walkthrough · Play C-06

Watch the Escalation Context Pack get built inside HubSpot

Click through how a custom HubSpot agent compiles ticket history, open commitments, key contacts and account value the moment a ticket is escalated, then adds it to the ticket as a note and notifies the owner in Slack.

6 steps~3 minutesUse ← → keys

Click the numbered orange boxes in the guide to jump to each part of the screen. Illustrative mockup with fictional data.

How the Escalation Context Pack play works

Escalation Context Pack is a custom HubSpot agent (Agent Builder) that a ticket workflow runs on escalation with the Run agent action (beta). It compiles ticket history, open commitments, key contacts and account value into a note on the ticket, and the workflow sends the owner a Slack notification.

The problem

Escalated tickets lose time while teams search for history and commitments, and promises made in email get missed.

How the play runs

  1. A ticket workflow runs the agent on escalation (Run agent, beta)
  2. The agent compiles ticket history, open commitments, key contacts and account value
  3. It adds the pack to the ticket as a note; the workflow notifies the owner in Slack

What JayOh builds

The custom agent in Agent Builder (JayOh build), the escalation workflow with a Slack notification, and a context pack template.

What we measure

  • Time to resolution on escalations
  • Minutes spent gathering context
  • Repeat escalations

Guardrail

Scope the agent's data access in its instructions and keep sensitive account data out.
HubSpot agentCustom agent (Agent Builder)
TeamCustomer Success, Support
Timeline2-week quick win
TriggerTicket workflow → Run agent (beta)
HubSpot Credits1 per agent action unit

Escalation Context Pack FAQ

What is an escalation context pack?

A short note added to an escalated ticket with its history, open commitments, key contacts, account value and renewal date.

How does the agent find open commitments?

It reads emails and notes logged in HubSpot for promises like dates or fixes, and lists any that aren't marked done.

Does the pack expose data people shouldn't see?

It shouldn't. JayOh scopes what the agent reads in its instructions (the ticket and its associated records), excludes payment details and contract terms, and tests the scope before launch.

How fast is the pack ready?

Within a minute or two of the escalation, usually before the owner opens the ticket.

Related plays

Want escalations to start with the full story?

We build the trigger and pack template in two weeks and measure time to resolution before and after.