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 happens when a case looks like this pattern but does not quite fit?

The connections shown on this page link to related patterns that may match the case better. The agent can follow those edges to find a closer fit.

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.

Converting a qualified lead and handing off to the AE

Once the demo is booked and the prospect is qualified, the SDR converts the lead to a Salesforce Opportunity at Discovery owned by the assigned AE. They add themselves to the Sales Team for credit attribution, finish the Outreach sequence and post a structured handoff in the Account Chatter.

Tags

salesforceoutreachlead-convertopportunityae-handoffcredit

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 the demo is on the calendar and the prospect is scored as a sales-qualified lead, the SDR clicks Convert on the Salesforce lead, ticks Create Opportunity, sets the Opportunity Stage to 'Discovery' and confirms the Account Owner is the same AE attached to the demo invite. They then add themselves to the Sales Team list with role 'SDR' for credit attribution, finish the active Outreach sequence with status 'Finished - Converted to Opp' and post a structured handoff message in the Account Chatter feed tagging the AE.

Reasoning

Lead conversion is the single moment that determines whether the SDR gets credit for a closed-won deal three months later. Forgetting the Sales Team membership is the team's most common credit-loss error and it is silent, the SDR only finds out when commissions are paid. Setting Opportunity Stage to 'Discovery' rather than 'Qualification' matters because Salesforce automation triggers a different welcome email to the AE for each stage. Posting in Chatter with the @-mention notifies the AE so they walk into the demo with the prospect's pain quote, demo time and open questions in front of them, cold-handoff demos convert forty percent worse on the team's measure.

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 accepted a demo time, the Salesforce lead has Status 'Working - Demo Scheduled' and the SDR has marked them as a sales-qualified lead during their discovery-call notes.

Outcome

An Opportunity exists in Salesforce at Discovery stage owned by the assigned AE. The SDR is on the Sales Team for credit attribution. The Outreach sequence is finished with the matching reason and a Chatter handoff post sits on the AE's feed with the discovery brief, the demo time and the prospect's pain quote.

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 qualified lead in Salesforce and click the Convert button at the top right of the record.

Convert is greyed out unless the lead has Status 'Working - Qualified' or 'Working - Demo Scheduled'. If grey, fix the status first via the disco-call notes pattern, never edit the status field manually to bypass the gate, downstream automation reads the status change reason and the wrong path fires.

Expected: The Convert dialog is open.

Salesforce

On the Convert dialog, tick 'Create Opportunity', set Stage to 'Discovery' and Close Date to thirty days out as a placeholder.

Always tick Create Opportunity. Without it the Account is created but the deal does not exist in pipeline reports. Stage 'Discovery' fires the right onboarding email to the AE; 'Qualification' fires a different email and the AE has called this out twice already as confusing. Close Date thirty days is a placeholder, the AE will adjust after the demo, never leave it blank or Salesforce defaults to today which kills the ageing report.

Expected: Create Opportunity is ticked, Stage is Discovery and Close Date is thirty days out.

Salesforce

Set Account Owner to the right AE based on the territory mapping confirmed when the demo was booked.

Always reuse the same AE who was attached to the demo booking. Reassigning between booking and convert confuses the prospect when two different names show up on calendar invites. If the AE has changed for any reason, message the previous AE in the rev-ops channel before saving, courtesy heads off territory disputes that surface at quarter end.

Expected: The right AE is set as Account Owner on the new Account.

Salesforce

Click Convert. On the new Opportunity record, open the Sales Team panel and add yourself with role 'SDR'.

This step is non-negotiable. Salesforce does not add the converting SDR to the Sales Team automatically and SDR commission attribution is read off Sales Team membership at deal close. Forgetting this step is the single most common cause of disputed commission three months later. Always set role 'SDR' specifically, not 'Sales Development', the picklist value that drives commission rules is exactly 'SDR'.

Expected: The SDR is on the Opportunity Sales Team with role 'SDR'.

Outreach

Open Outreach, find the prospect, click Finish on the active sequence and choose status 'Finished - Converted to Opp'.

Never leave the sequence active after lead convert. The next sequence email lands after the prospect has met the AE which makes the SDR look out of touch. The 'Finished - Converted to Opp' status is read by the rev-ops report that measures SDR-to-AE handoff time against the team SLA.

Expected: Outreach sequence is finished with the right status and the audit trail is intact.

Salesforce

Open the Account Chatter feed and post a handoff message tagging the AE with @, pasting the discovery brief, the demo time, the prospect's pain quote and any open questions.

Tag the AE with @-mention so the message lands in their notifications, plain mention without the @ does not notify. Use the team's handoff template heading 'AE handoff - {prospect name}' so the AE can search their feed for handoffs later. Skipping the Chatter post means the AE walks into the demo cold, the team's measured outcome on cold-handoffs is a forty percent worse demo conversion.

Expected: A tagged handoff message is on the Account Chatter feed and the AE has been notified.

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

Logging a discovery call outcome Booking a demo from a positive email reply

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.

Converted lead at Heliograph Labs, opened Opportunity at Discovery stage with AE Maya Chen

Added self to Sales Team with role 'SDR' on new Opportunity for credit attribution

Finished Outreach sequence as 'Finished - Converted to Opp' for prospect at Brava Health

Posted Chatter handoff with discovery brief, pain quote and demo time to AE

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 36 times across 5 connections
Applications	Salesforce, Outreach
First seen	13 Feb 2026, 16:18
Last seen	5 May 2026, 13:42

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