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 Outreach and Salesforce, 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.

Moving an unresponsive prospect to a break-up sequence

When an Outreach sequence reaches its final step with no reply, the SDR enrols the prospect in a two-step Break-up sequence. A manual seven-day Salesforce task acts as the safety net to disqualify the lead with reason 'Not Engaged' if no reply arrives.

Tags

outreachsalesforcebreak-upre-engagementno-reply

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 an Outreach sequence reaches its final standard step with no reply, the SDR removes the prospect from the active sequence and adds them to the team's two-step Break-up sequence. The Break-up sequence sends a short 'should I close your file?' email three working days after enrolment and a final goodbye email seven days after that. The SDR also sets a Salesforce task seven days out so they remember to disqualify the lead manually if no reply lands.

Reasoning

The team has measured break-up emails at three to four times the reply rate of any standard sequence step. People who ignore polite outreach respond to a clean 'closing your file' nudge because it forces a decision rather than asking for time. The two-step format with a goodbye seven days later catches prospects who almost replied but got distracted, the goodbye is a free shot that costs nothing. Setting the Salesforce task manually is belt-and-braces: the team has had Outreach automation fail to fire the disqualify webhook before and silent leads sat on the books for months.

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

A prospect has reached the last step of their original Outreach sequence with status 'Delivered' on every email and no Reply event captured. The team standard is six emails over fourteen working days before triggering break-up.

Outcome

The prospect is enrolled in the Break-up sequence and a manual seven-day disqualify safety-net task sits on the SDR's queue. Either the prospect replies and the SDR pivots to the demo-booking flow, or silence holds and the SDR closes the lead with reason 'Not Engaged' on the seventh-day task.

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.

Outreach

Open the SDR's Outreach Tasks tab and filter by 'Sequence Finished - No Reply'.

The filter shows only prospects whose original sequence reached its end with every step delivered and no Reply event captured. Do not run the break-up sequence on prospects whose sequence finished any other way, an open or a click without a reply is sometimes a thoughtful prospect mid-decision and a break-up email shuts them down.

Expected: A list of prospects ready for break-up is on screen.

Outreach

Tick the prospects to break up with and click Add to Sequence, then choose 'team-break-up-2-step'.

Use the team-shared Break-up sequence not a personal copy, the team-shared one has the legal opt-out language already baked in. Personal copies tend to drift and have failed deliverability checks before, the rev-ops lead enforces this on Friday review.

Expected: The break-up sequence dialog is open with the prospects loaded.

Outreach

Confirm sending mailbox, prospect time-zone and a Tuesday or Wednesday start, then click Add to Sequence.

Break-up emails on Mondays and Fridays underperform on reply rate. Tuesday and Wednesday landings are the team's measured peak. Always start the break-up no sooner than two working days after the original sequence finished, gaps shorter than that read as a coordinated nudge and reply rate halves.

Expected: The break-up sequence is enrolled with the right schedule and start day.

Salesforce

Open the prospect's Salesforce lead and create a manual task with subject 'Confirm break-up disqualify' and a Due Date seven calendar days out.

The manual task is the safety net. Outreach should fire a webhook on no-reply that flips the Salesforce Lead Status, but the team has watched it fail at least three times this year. Never trust the automation alone for the disqualify path.

Expected: A safety-net task is on the SDR's Salesforce queue for the seventh day.

Outreach

Set the prospect's Outreach Status to 'In Break-up' so the dashboard distinguishes break-up prospects from active ones.

Without the explicit status, break-up prospects show up in the active-pipeline dashboard which inflates reply-rate denominators and misleads leadership reporting. The status is a free-text field, the agreed value is exactly 'In Break-up' with the hyphen, anything else fails the dashboard pivot.

Expected: Outreach Status reads 'In Break-up' and the prospect is in the right reporting bucket.

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.

Often previous

Adding a prospect to a personalised cold email sequence

Often next

Disqualifying a lead with a documented reason Booking a demo from a positive email reply

Alternative to

Disqualifying a lead with a documented reason

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.

Moved 11 unresponsive prospects from 'rev-ops-mid-market' into the team break-up sequence

Set 7-day Salesforce safety-net task for prospect at Quayside Logistics

Pivoted to demo-book flow after positive reply landed on day 2 of break-up sequence

Closed prospect at Pyramid Foods with reason 'Not Engaged' on break-up day-7 task

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 396 times across 5 connections
Applications	Outreach, Salesforce
First seen	9 Feb 2026, 10:14
Last seen	5 May 2026, 12:48

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