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

Disqualifying a lead with a documented reason

When a prospect is decided to be unqualified, the SDR sets a structured Disqualify Reason on the Salesforce lead with a free-text note in the prospect's own words. They finish the Outreach sequence with a matching status, recycling Bad-Timing leads in 90 days and closing every other reason without recycle.

Tags

salesforceoutreachdisqualifyclosed-lostrecycle

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

Once a prospect is decided unqualified, the SDR opens the Salesforce lead, sets Lead Status to 'Closed - Disqualified', picks a structured Disqualify Reason from the picklist and adds a free-text supporting note in the prospect's own words. They then open Outreach and finish the active sequence with status 'Finished - Disqualified', not 'Out of Office', so it does not auto-resume the next month. Bad-Timing disqualifications get a follow-up task ninety days out, every other reason closes the lead without recycle.

Reasoning

A disqualify is not a deletion, it is a record. The Disqualify Reason field feeds the marketing channel-quality dashboard and a free-text quote explains the picklist when leadership review the report. Finishing the Outreach sequence with the right reason matters because Out-of-Office sequences re-enrol after thirty days and the prospect receives the same opener again, which they remember and dislike. The Bad-Timing recycle exists because budget windows shift, the team has closed deals against ninety-day-old recycle tasks more than once and it pays for itself.

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 discovery call concluded the prospect is not a fit, an inbound lead failed the score check at triage time, or an unresponsive prospect has finished the break-up sequence with no reply.

Outcome

The Salesforce lead has Lead Status 'Closed - Disqualified', a structured reason picklist value, a supporting note and either a recycle task or a finished-without-recycle state. The Outreach sequence is finished with the matching reason and will not auto-resume.

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.

Salesforce

Open the prospect's Salesforce lead from the SDR's queue and click Edit on the Lead Status field.

Open the lead from the SDR's queue not from a global search. Going through the queue makes sure the lead is actually owned by the SDR, disqualifying a lead owned by an AE is a hard error that requires a manual reassignment to undo.

Expected: The Lead Status field is editable.

Salesforce

Set Lead Status to 'Closed - Disqualified' and Disqualify Reason to one of the picklist values.

The picklist values are 'Not A Fit', 'Bad Timing', 'No Budget', 'Has Competitor', 'Wrong Contact' and 'Job Change'. Never default to 'Not A Fit' if any other value applies, the marketing dashboard groups by reason and 'Not A Fit' becoming the catch-all hides real signal about which channels send the wrong leads.

Expected: Lead Status reads 'Closed - Disqualified' and Disqualify Reason has a specific picklist value.

Salesforce

In the Disqualify Notes field, paste a single-sentence quote from the prospect explaining the disqualification.

Always quote the prospect rather than paraphrase. A quote like 'we have a three-year contract with Competitor' tells the AE far more than 'has a competitor in place'. The Notes field is what the AE reads if the lead recycles in ninety days.

Expected: Disqualify Notes contains a verbatim or near-verbatim quote from the prospect.

Salesforce

If Disqualify Reason is 'Bad Timing', click Save and Add Task and set a follow-up task ninety days out, otherwise just Save.

Bad Timing is the only reason that gets an automatic recycle. Job Change recycles only if the prospect has gone to another ICP company and that gets handled by a separate workflow. The ninety-day window matches the average budget cycle in the team's ICP and produces the highest recycle conversion rate.

Expected: Either a recycle task is on the queue ninety days out, or the lead is closed without follow-up.

Outreach

Open Outreach, find the prospect's active sequence and click Finish.

Click Finish, never Pause. Pause leaves the prospect in a paused state which a colleague might unpause by accident. Finished is terminal and cannot be undone without recreating the prospect record.

Expected: The sequence is in Finished state.

Outreach

When the Finish dialog asks for a status, choose 'Finished - Disqualified' and the matching reason from the secondary picklist.

Never choose 'Out of Office' here, that status auto-resumes after thirty days and the prospect receives the same first email again. The team has been called out by prospects for that exact mistake and the rule is hard.

Expected: The Outreach sequence is closed permanently with a status that matches the Salesforce reason.

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

Triaging a newly assigned inbound lead Logging a discovery call outcome Moving an unresponsive prospect to a break-up sequence

Alternative to

Moving an unresponsive prospect to a break-up sequence

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.

Disqualified lead at Stonebridge Foods with reason 'Has Competitor', quoted three-year contract

Closed Bad-Timing disqualification on Lumen Cloud with 90-day recycle task

Finished Outreach sequence as 'Finished - Disqualified' for prospect at Marlowe Capital

Disqualified inbound MQL with reason 'Wrong Contact', flagged for re-routing in rev-ops channel

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 142 times across 5 connections
Applications	Salesforce, Outreach
First seen	2 Feb 2026, 15:42
Last seen	6 May 2026, 14:25

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