When does an AI agent use this pattern?

When the trigger described above matches the situation the agent is handling. The agent queries FusedFrames at runtime, this pattern is returned and the agent follows the recorded reasoning and steps to reach the recorded outcome.

How were the steps captured?

By the desktop app on the machine of someone who actually does this work. It records clicks, keystrokes, copy and paste, drag and drop, selected text and screen regions across HubSpot and Gainsight, then groups them into the meaningful steps shown above.

Where does the reasoning come from?

From the operator. When the desktop app sees a decision the action alone cannot explain, it asks why in the moment. The operator's answer is recorded and becomes the reasoning attached to the pattern, so the AI agent gets the thinking and not just the steps.

What if my team handles this differently?

Capture how your team actually does it. The desktop app records what your operator does on your tools and the web app distills that into a pattern shaped by your team. Each team's library reflects their own approach rather than the example shown here.

What if a case looks like this pattern but does not quite fit?

The pattern is linked to 1 alternative. The agent can follow the connections shown on this page to a related pattern that matches the case more closely.

How does my AI agent actually call this pattern?

Through the read-only REST API or the npm CLI. Create an API key in the dashboard, choose whether it accesses all libraries or specific ones and have your agent query at runtime. The response is structured JSON ready for tool use.

Is the data shown on this page from a live customer?

No. Example libraries on this site are illustrative. Patterns in your own account are built from your team's captured actions and stay private to your workspace.

How do I build a pattern like this for my team?

Install the desktop app on the machine of the person who already does this work, ask them to handle a real case end to end, then distill the captured action into a pattern in the web app. The pattern you end up with mirrors how your team actually operates.

Escalating to the exec sponsor

When the named champion has been silent for 14 days or more, the CSM logs an Exec Sponsor Touch on both HubSpot and Gainsight. Matching campaign tags on both records make sure the move shows up in every downstream report within a day.

Tags

exec-sponsorescalationhubspotgainsightsponsor-tracking

Lets your agent filter to the right pattern

Categories and tags scope the retrieval set, so your agent receives only the patterns relevant to the task instead of scanning the full library.

What and why

The observed behaviour and the reasoning behind it.

Behaviour

When the customer’s named champion has been silent for 14 or more days (no Gong call participation, no HubSpot email reply, no support ticket interaction), the customer success manager opens the customer’s contact record in HubSpot, creates a custom activity of type ‘Exec Sponsor Touch’ tagged with the campaign name, then switches to Gainsight, opens the C360 and adds a Sponsor Tracking timeline entry with the same campaign tag and the HubSpot activity URL.

Reasoning

When a champion has gone silent for two weeks, the formal Risk CTA path is often the wrong tool because the path forward is an exec-to-exec relationship motion, not a structured playbook. The team logs the touch on both records because each tool is the source of truth for a different report. HubSpot drives the executive coverage report finance reads for renewal forecasts. Gainsight drives the relationship-strength dashboard the CS Lead reads on Mondays. Logging on only one record means one of the two reports is wrong, and the team has been bitten by that before, when an exec ping that landed renewals appeared to never have happened in the QBR coverage review. The campaign tag on both records is what stitches them together when the leader runs the cross-tool audit at quarter end.

Gives your agent an operator's reasoning

Behaviour records the action; reasoning records the rationale. Your agent applies both to handle cases that diverge from the captured examples.

Cause and effect

What initiates this pattern and what it produces.

Trigger

The customer’s named champion has had no Gong call participation, no HubSpot email reply and no ticket interaction for 14 days or more, indicating relationship silence that needs an exec-led response.

Outcome

An Exec Sponsor Touch is logged on both the HubSpot contact record and the Gainsight C360 timeline with matching campaign tags, so both downstream reports reflect the move within a day.

Tells your agent when to act and what to verify

Your agent stays within the scope set by the trigger and outcome, so it doesn't extend beyond the work or finish before the outcome is met.

Standard operating procedure

Step-by-step instructions to reproduce this pattern.

HubSpot

Open the named champion’s contact record in HubSpot from the company record’s Contacts panel.

Always go via the company record so the contact-to-company association is visible. If the contact record is opened directly, you will not see whether the silence applies to the named champion or to a secondary stakeholder, and the difference matters.

Expected: The contact record is open with the activity timeline visible and the company association confirmed.

HubSpot

Click ‘Log activity’ and choose the custom activity type ‘Exec Sponsor Touch’.

The custom activity type was added by the CS Lead specifically so executive touches do not get lost in the regular Email/Call/Meeting timeline. Standard activity types do not appear in the executive coverage report.

Expected: The Log Activity dialog opens with type set to Exec Sponsor Touch.

HubSpot

Tag the activity with the active campaign name (e.g. ‘Q4 Renewal Push’, ‘Champion Re-engagement’, ‘Loss of Champion Recovery’).

Campaign tags are how the activities get rolled up in the cross-tool audit. The tag has to match exactly between HubSpot and Gainsight, including capitalisation. The team keeps the canonical list pinned at the top of the CS leader’s Notion page.

Expected: The activity carries the right campaign tag and will roll up alongside the matching Gainsight entry.

HubSpot

Write the body with three lines: who is reaching out (your VP), the deal value, the renewal date.

Format: ‘Reach-out: [VP name] · Deal value: $[ARR] · Renewal: [date]’. The body is what the leader reads in the executive coverage report. The three pieces of information are the only ones the leader needs to decide whether to step in personally.

Expected: The activity body contains the three structured fields the leader’s report depends on.

HubSpot

Save the activity, then copy its permalink URL from the activity card.

The permalink is the URL with the activity ID, not the contact URL. Click the timestamp on the saved activity card and the URL bar updates to the permalink. That is the link to copy.

Expected: The HubSpot activity is saved and its permalink URL is on the clipboard, ready to paste into Gainsight.

Gainsight

Open the same customer’s C360, click ‘Add Timeline Entry’ and set Type=Exec Touchpoint.

Type=Exec Touchpoint feeds the relationship-strength dashboard. Other types (Meeting, Call, Email) do not. The dashboard is what the CS Lead reads on Monday mornings to decide which accounts the leader should call this week.

Expected: The Timeline Entry dialog opens with type set to Exec Touchpoint.

Gainsight

Tag the entry with the same campaign name and paste the HubSpot permalink URL into the body, then save.

The campaign tag must match the HubSpot tag exactly. The HubSpot URL stitches the two activities together when the leader runs the cross-tool audit at quarter end and asks ‘which exec touches actually moved a renewal’.

Expected: The Gainsight Timeline entry is saved with the matching campaign tag and the HubSpot permalink, so both reports reflect the touch within a day.

Hands your agent your team's exact steps

Your agent executes the documented procedure in order, against the applications named at each step, producing consistent output across human and agent runs.

Book a demo

Related patterns

How this pattern connects to other patterns in the library.

Alternative to

Creating a Risk CTA after a health drop

Often previous

Creating a Risk CTA after a health drop Mining Gong sentiment for at-risk signals

Often next

Moving a renewal to Commit in HubSpot

Lets your agent confirm the match and its scope

Alternative patterns let your agent compare candidates and select the closest match. Previous and next patterns define position in the workflow, so the agent operates within the scope of this one.

Supporting actions

Actions that provide evidence for this pattern.

Logged Exec Sponsor Touch on Helios Energy contact (Q1 Renewal Push tag)

Added Exec Touchpoint timeline entry on Juniper Retail C360 with HubSpot URL

Tagged ‘Champion Re-engagement’ on Apex Marine after 17 days of champion silence

Renewal Manager @sara.bjornson cc’d on Beacon Hospitality exec touch (renewal in 41 days)

Shows your agent the evidence behind the pattern

Each pattern is derived from captured action sequences. Your agent can reference the source actions to verify any field, so nothing it acts on is authored by hand or hallucinated.

Metadata

Timestamps and identifiers.

Evidence	Observed 12 times across 3 connections
Applications	HubSpot, Gainsight
First seen	9 Feb 2026, 10:54
Last seen	4 May 2026, 13:28

Helps your agent rank patterns by confidence

Action count and last-seen timestamp weight each pattern by frequency and recency, so your agent selects the highest-scoring match rather than the first returned.

Questions

Frequently asked questions

Book a demo View all examples

Speak to the founder

Get a demo. Watch a live capture, then an AI agent query the result.

Ask anything. Pricing, security or integrating with your stack.

No purchase obligation

Book a call

Start capturing

Record in minutes. Install once and work as normal.

Plug AI agents in. One API call from any AI agent stack.

Refund on unused credits if you cancel