Build a Salesforce Lead Rescue Flow

Build a Salesforce Flow that creates follow-up Tasks for high-value Leads.

Introduction

30 Second Summary

A promising customer can disappear in plain sight when nobody owns the next call. When follow-up depends on memory, fast responses can become missed opportunities.

In this project, you will build a tested lead-response system in Salesforce for Northstar Equipment. You will package the automation's results into a local case study that a recruiter can review.

What You'll Build

Your demo will show a qualifying Lead with a high-priority Contact high-value lead Task already waiting on its activity timeline, supported by a self-contained evidence pack.

By the end of this project, you'll have:

A Lead rescue automation that places a high-priority Contact high-value lead Task on every newly qualifying Lead's activity timeline.
A three-case test story showing the original manual gap, Morgan's qualifying result, plus Dana's nonqualifying guardrail.
A recruiter-ready evidence pack containing the High-Value Leads by Source report. Its concise case study plus four screenshots can be shared without Playground access.
Secret Mission: Build a manager dashboard with a donut chart titled High-Value Leads by Source that compares the qualifying Lead Source groups. Capture it as a fifth evidence screenshot.

Are there any prerequisites?

You need a Windows device with internet access plus a personal email address that can receive a verification code. No Salesforce, coding, or CRM experience is required.

Before We Start

Before We Start...

Before the hands-on work begins, lock in the sales problem Northstar Equipment needs to solve. This gives every automation choice and recruiter artifact a clear purpose.

Create Your Salesforce Practice Environment

Northstar Equipment's lead rescue automation needs a safe Salesforce environment. A Trailhead Playground gives you room to test with fictional records without touching a real company's customer data.

Your recruiter evidence also needs a reliable home on your Windows device. Microsoft Edge gives you access to Salesforce Trailhead.

Notepad will hold your case study. Snipping Tool will capture proof that recruiters can review later.

In this step, get ready to:

Verify your Windows evidence tools and create the local evidence folder.
Create a free Trailblazer account and verify your email address.
Create the Lead Rescue Lab Playground and confirm that Leads are available.

Prepare your Windows evidence workspace

Your local folder keeps the case study and portfolio screenshots together. First, confirm that the tools for creating those artifacts are ready.

Select Start on Windows.
Type Notepad into the search field.
Select Notepad from the results.

You'll see a blank Notepad document. This is where you will build the written case study later.

Return to Start.
Type Snipping Tool into the search field.
Select Snipping Tool from the results.

You'll see the Snipping Tool window. The keyboard shortcut gives you a faster way to capture evidence while Salesforce is open.

Verify the capture shortcut by pressing Windows logo key + Shift + S.

You'll see the screen dim beneath the Snipping Tool overlay. That confirms the capture shortcut is working.

Cancel the capture to return to your desktop.
Open File Explorer by pressing Windows logo key + E.
Select Desktop in the left navigation pane.
Select New.
Select Folder.
Type Salesforce Lead Rescue Case Study as the folder name.
Press Enter.

Your capture kit is ready. The new folder gives every case-study artifact one predictable home.

Can't see the capture overlay?

Return to Snipping Tool from the Windows search results.
Press all three shortcut keys at the same time.
Try the shortcut again after the Snipping Tool window opens.
Help me verify Snipping Tool on Windows.

Create and verify your Trailblazer account

A Trailblazer account connects your learning progress to your practice environment. Salesforce provides this personal account for free.

Select Start on Windows.
Type Microsoft Edge into the search field.
Select Microsoft Edge from the results.

You'll see Microsoft Edge open. Use this browser for the Trailhead account and Playground so both stay in one session.

Type https://trailhead.salesforce.com/ into the address bar.
Press Enter.
Select Get Started for Free.
Complete the sign-up form using your personal email address.
Follow the account prompts until the email verification page opens.

Email verification is the only credential check in this setup. The single-use code confirms that the email address belongs to you.

Open the verification message in your email inbox.
Select Verify my email in the message.
Read the single-use code from the message.
Return to the Trailhead verification page.
Enter the single-use code.
Select Submit code.

Your free Trailblazer account is now verified. You can use it to create the isolated Salesforce environment for Northstar Equipment.

Didn't receive the verification message?

Check the spam folder for the verification message.
Confirm that the email address on the Trailhead page matches your personal email address.
Request a fresh verification message from the Trailhead page if the original code has expired.
Help me complete Trailhead email verification.

Create and launch your Playground

A Trailhead Playground is a private practice environment tied to your Trailblazer account. It keeps Northstar Equipment's fictional records separate from live customer data.

Why use a Trailhead Playground?

A production Salesforce environment serves real users and stores live business records. A Trailhead Playground lets you test customizations safely while learning the same administration workflow.

Return to the Trailhead tab in Microsoft Edge.
Open Salesforce's Create a Trailhead Playground unit.
Select the org name in the Playground selector.
Select Create Playground.
Enter Lead Rescue Lab as the Playground name.
Select Create.

This is the slowest part of the setup. It typically takes 3–4 minutes to create a new Trailhead Playground.

Keep the Trailhead page open while provisioning completes.
Select Lead Rescue Lab in the Playground selector after provisioning.
Select Launch.

You'll see the Playground open in a new Microsoft Edge tab or window. Your Trailblazer session launches it without a separate Playground sign-in.

Before you open the Salesforce Sales app, do you expect this fresh Playground to include a workspace for Lead records?

Select App Launcher in the Playground.
Select Sales.
Select the Leads tab.

You'll see the Leads workspace inside the Sales app. This confirms that Lead Rescue Lab has the record area needed for Northstar Equipment's automation.

Can't reach the Leads workspace?

Return to Trailhead to confirm that Lead Rescue Lab is selected in the Playground selector.
Launch the selected Playground again.
Use the App Launcher to return to Sales.
Help me find Leads in my Trailhead Playground.

Frame the Salesforce content so personal account details remain outside the image.
Press Windows logo key + Shift + S.
Drag around the Sales app with the Leads tab visible.

Your evidence workspace and Salesforce Playground are ready. Next, you'll capture a valuable Lead and expose the missing follow-up that your automation needs to solve.

Capture the Manual Follow-Up Gap

Your Salesforce Sales app is ready for practice. Now Northstar Equipment needs to test a business risk: a valuable prospect may be stored without a clear next action.

You'll create a high-value Lead for Avery Stone. Then you'll check whether storing that prospect creates clear follow-up work for its owner.

In this step, get ready to:

Create Avery Stone as a high-value Lead for Summit Manufacturing.
Confirm Salesforce stored Avery's qualification data.
Check Avery's Activity timeline for assigned follow-up work.

Create Avery's high-value Lead

A Lead is a CRM record for a prospective customer. Northstar Equipment uses 1000000 as its project-defined qualification threshold.

Avery's revenue of 1500000 places the record above that threshold. Its source shows how the prospect reached the sales team.

Switch back to the Salesforce Sales app in Microsoft Edge.
Select the Leads tab.
Click New.
Enter Avery in First Name.
Enter Stone in Last Name.
Enter Summit Manufacturing in Company.

The form now identifies Avery Stone as a prospective customer from Summit Manufacturing.

Enter 1500000 in Annual Revenue.
Select Partner Referral in Lead Source.
Select Open - Not Contacted in Lead Status.
Click Save.

You've got the baseline in place: Avery Stone is now a concrete high-value record for testing the follow-up process.

Can't see a Lead field?

Scroll through the full Lead form if Annual Revenue or Lead Source sits outside the visible area.
Return to the Leads tab from earlier if you opened a different type of record.
Help me find the required Lead fields.

Confirm Avery's stored details

The Details tab is the data proof for this test. This check confirms Avery's qualification data was saved correctly.

Select the Details tab on Avery's Lead record.
Confirm Company shows Summit Manufacturing.
Confirm Annual Revenue reflects 1500000.
Confirm Lead Source shows Partner Referral.
Confirm Lead Status shows Open - Not Contacted.

Avery's record now shows every value needed for the test. The qualification rule has a reliable input.

Reveal the manual follow-up gap

The Activity timeline is where Salesforce displays related Tasks. A scheduled follow-up should appear there with its subject.

Before you check, do you think saving a high-value Lead also scheduled the follow-up work its owner needs?

Select the Activity tab on Avery's Lead record.
Inspect the timeline for a Task with the subject Contact high-value lead.

You'll see no Task with the subject Contact high-value lead. That shortfall is intentional for this test.

The valuable Lead exists. Its owner still has no assigned next action.

Why the Empty Timeline Matters

A CRM record can preserve qualification data without creating a sales action. Avery's empty Activity timeline makes that handoff failure visible.

This gives you a before state for testing the automation later. The same record values make the comparison credible.

You have captured the exact failure Northstar Equipment needs to solve. Next, you'll turn its revenue rule into assigned follow-up work.

Automate High-Value Follow-Up

Avery Stone's record proved the sales gap: a valuable Lead can sit untouched without any follow-up work. Northstar Equipment now needs that gap closed automatically.

Salesforce Flow Builder can watch a Lead as it is saved. In this step, you'll turn the 1000000 revenue rule into a high-priority Task for the Lead owner.

In this step, get ready to:

Define the entry criteria for high-value Leads.
Map a follow-up Task to the triggering Lead owner.
Prove the active flow with a qualifying Lead.

Why a Record-Triggered Flow?

A record-triggered flow starts when Salesforce saves a Lead that meets its criteria. It runs in the background without depending on a sales representative to launch it.

Manual task creation repeats the gap you saw on Avery's record. This flow converts the qualification rule into assigned work.

Configure the Lead trigger

The trigger chooses which Lead changes start the automation. Northstar's project-defined threshold treats Annual Revenue of 1000000 or more as high value.

Switch back to the Lead Rescue Lab tab in Microsoft Edge.
Click App Launcher.

The app menu opens over your existing Playground.

Select Automation.
Click New in the Flows panel.

You'll see the available flow types.

Select Record-Triggered Flow.

Flow Builder opens with the trigger configuration ready for your Lead rule.

Select Lead as the object.
Set Trigger the Flow When to A record is created or updated.

The flow can now respond to new Leads or existing Leads whose data changes.

Set the condition requirements to All Conditions Are Met (AND).
Choose Annual Revenue as the condition field.

The trigger now evaluates the Lead's revenue whenever the record is saved.

Set the comparison operator to Greater Than or Equal.
Enter 1000000 as the comparison value.

The condition now includes Leads whose Annual Revenue reaches the threshold exactly.

Set the update behavior to Only when a record is updated to meet the condition requirements.
Select Actions and Related Records.

The update behavior prevents unrelated later edits from creating repeated follow-up Tasks.

Click Done.

The trigger card now summarizes the Lead object and the Annual Revenue entry rule.

Create the follow-up Task

The Task needs an owner who receives the work. It also needs a Lead association so the work appears on the correct activity timeline.

Click the plus icon beneath the trigger card.
Select Create Records.

The Create Records configuration panel opens beside the flow canvas.

Enter Create High-Value Follow-Up as the element label.
Choose the option to create one record.

This element creates one follow-up record each time an eligible Lead enters the flow.

Set How to set record field values to Manually.
Set Object to Task.

The element now exposes the Task fields that control assignment and activity details.

The resource picker is a little fiddly because the owner field sits inside the triggering Lead resource.

Select Assigned To ID as the first Task field.
Choose the triggering Lead resource as its value.

The resource picker now shows the fields available on the Lead that started the flow.

Select the Lead's Owner ID field.

This mapping routes the follow-up work to the same person who owns the qualifying Lead.

Set Priority to High.
Set Status to Not Started.

The Task now enters the owner's workload as urgent unfinished work.

Set Subject to Contact high-value lead.
Select Name ID as the next Task field.

The subject tells the owner exactly what action to take. Name ID controls which Lead displays the Task.

Choose the triggering Lead resource for Name ID.
Select the Lead's record ID field.

The Task is now associated with the same Lead record that crossed the revenue threshold.

Leave Related To ID blank.
Click Done.

The flow canvas now shows the Create High-Value Follow-Up element beneath the trigger.

Why Leave Related To ID Blank?

Name ID links the Task to a person record such as a Lead. This link places the Task on that Lead's activity timeline.

Related To ID links a Task to a non-human record. A Lead-associated Task should leave that mapping empty.

Activate and test the flow

A saved flow remains a draft until activation. Activation makes the automation available when the next qualifying Lead is saved.

Click Save in Flow Builder.

The save panel opens so you can identify the automation and document its purpose.

Enter Create High-Value Lead Follow-Up as the flow name.
Enter Creates a follow-up Task for the Lead owner when Annual Revenue reaches 1000000. This supports timely sales response for high-value prospects. as the description.

The name identifies the automation. The description records the business rule behind it.

Click Save.

You'll see the flow name at the top of the saved canvas.

Click Activate.

The flow now shows as active and can respond to qualifying Lead records.

Click App Launcher.
Select Sales.

The Lead workspace opens inside the same Playground.

Select the Leads tab.
Click New.

You'll see a blank Lead form for the qualifying test record.

Enter Morgan in First Name.
Enter Reyes in Last Name.

The form now identifies the test Lead as Morgan Reyes.

Enter Apex Logistics in Company.
Enter 2000000 in Annual Revenue.
Select Web in Lead Source.

Morgan's Annual Revenue is above Northstar's high-value threshold.

Click Save.

Morgan's Lead record opens after Salesforce saves it.

Before you inspect the timeline, ask yourself what Task details the flow should create.

Select the Activity tab.

You'll see a Contact high-value lead Task on Morgan's activity timeline.

Expand the generated Task on the activity timeline.

Its details show High priority. Its status shows Not Started.

Compare the Task assignee with Morgan's Lead owner.
Confirm Morgan Reyes appears as the Task name.
Check that the Task's Related To field is empty.

The Task belongs to Morgan's Lead owner and appears on Morgan's activity timeline.

That's the missed handoff fixed: Morgan's qualifying Lead now carries assigned follow-up work without manual scheduling.

Task Missing From Morgan's Timeline?

Confirm Create High-Value Lead Follow-Up shows as active in Flow Builder.
Check that Morgan's Annual Revenue is 2000000.
Check that the trigger operator is Greater Than or Equal.
Help me find why Morgan's automated Task is missing.

Your flow now turns Northstar's high-value rule into owned follow-up work. Next, you'll test the low-value guardrail and package the results as recruiter evidence.

Test, Report, and Capture Evidence

Morgan Reyes now has a high-priority follow-up Task created by your Salesforce flow. You have proved that the qualifying path works.

One successful record leaves two important questions. Does the guardrail leave low-value Leads alone? Can a recruiter understand the result without entering your private Playground?

You will answer those questions with a negative test. You will also build a grouped report before packaging the results into a local evidence pack.

In this step, get ready to:

Test a low-value Lead to prove the automation guardrail works.
Build a report that groups high-value Leads by acquisition source.
Package the test results into a case study with four privacy-framed screenshots.

Test the nonqualifying path

A negative-path test checks that automation rejects records outside its rule. Dana Cole gives you that proof because her company revenue falls below Northstar Equipment's qualification threshold.

Return to the Sales app from earlier.
Select the Leads tab.
Click New.
Enter Dana in First Name.
Enter Cole in Last Name.
Enter Northwind Fitness in Company.
Enter 250000 in Annual Revenue.
Select Web in Lead Source.

The form now represents a valid Lead that sits below the project-defined revenue threshold.

Click Save to create Dana's Lead record.

Before you inspect the activity timeline, do you expect Dana to receive the same Task as Morgan?

Select the Activity tab on Dana Cole's Lead record.
Inspect the timeline for a Task with the subject Contact high-value lead.

You should see no Task with that subject. That is the intended result because Dana's Annual Revenue does not meet the 1000000 threshold.

Good work. Your automation now has evidence for both the qualifying path and the nonqualifying guardrail.

A test matrix turns those individual checks into a repeatable record. You will start the matrix in a Notepad document before adding the rest of the case study.

Press the Windows key to open Windows search.
Type Notepad into the search field.
Press Enter to open Notepad.

The finished document needs a clear structure so a recruiter can connect the business problem to the evidence.

Add Business Problem as the first section heading.
Add Solution as the second section heading.
Add Design Choice as the third section heading.
Add Test Matrix as the fourth section heading.
Add Result as the fifth section heading.
Add Skills Demonstrated as the sixth section heading.
Add 60-Second Demo Script as the final section heading.

Your document now has a place for every part of the case study. The test matrix is the first section you can complete with observed evidence.

Document Avery Stone's expected before state plus the observed missing Task in the first matrix row.
Document Morgan Reyes's expected qualifying outcome plus the observed high-priority Task in the second matrix row.
Document Dana Cole's expected nonqualifying outcome plus the observed missing Task in the third matrix row.
Select File in Notepad.
Select Save As.
Choose the Salesforce Lead Rescue Case Study folder from earlier.
Enter Salesforce Lead Rescue Case Study.txt in the File name field.
Select OK to save the document.

Build the high-value Leads report

The test matrix proves individual outcomes. Lightning Report Builder turns the same Lead data into an operational view that a manager can use to compare acquisition sources.

Return to the Sales app.
Select the Reports tab.
Click New Report.
Select Leads as the report type.
Click Start Report.

You should now see a Leads report in the report builder. The initial preview can include records outside Northstar Equipment's high-value rule.

Set Show Me to All Leads.
Set Date Field to Create Date.
Set Range to All Time.
Add Annual Revenue as a report filter.
Select greater or equal as the filter operator.
Enter 1000000 as the filter value.
Apply the Annual Revenue filter to the report.

The preview should retain Avery Stone plus Morgan Reyes. Dana Cole should be excluded because her Annual Revenue is below the filter value.

Group the report rows by Lead Source.
Add Lead Owner as a report column.
Add First Name as a report column.
Add Last Name as a report column.
Add Company/Account as a report column.
Add Annual Revenue as a report column.
Add Lead Source as a report column.

Click Save.
Enter High-Value Leads by Source in Report Name.
Click inside Report Unique Name to generate the unique name.
Click Save.

Before you run the saved report, which Leads do you expect to remain after the revenue filter is applied?

Run the saved High-Value Leads by Source report.

You should see Avery Stone under Partner Referral and Morgan Reyes under Web. Dana Cole should remain absent from the report.

You now have a manager-ready view of high-value Leads. The grouping connects sales qualification to acquisition-source reporting.

Report Includes Dana Cole?

Confirm the Annual Revenue filter uses greater or equal.
Confirm the filter value is 1000000.
Confirm Dana Cole's Annual Revenue is 250000.
Ask for help with the report filters.

Capture the recruiter evidence pack

Your Trailhead Playground is private. A local evidence pack lets a recruiter review the business problem plus your tested solution without receiving Playground access.

Frame Recruiter-Safe Evidence

Each screenshot should focus on the Salesforce result that supports your case study. Keep the relevant record name plus the evidence visible.

Exclude browser chrome from every frame. Exclude email addresses plus personal account details.

The first screenshot establishes the original manual follow-up gap.

Return to Avery Stone's Lead record in the Leads tab.
Select Avery's Activity tab.
Press Windows logo key + Shift + S to open the Snipping Tool overlay.
Drag the capture frame around Avery's manual follow-up gap.
Select Save as in Snipping Tool.
Choose the Salesforce Lead Rescue Case Study folder.
Enter 01-manual-gap as the file name.
Confirm the save.

The first image now proves that a valuable Lead existed before automated follow-up work was available.

The second screenshot captures the rule that closes the manual gap.

Return to Automation from earlier.
Open the Create High-Value Lead Follow-Up flow.
Display the active flow entry rule with its Annual Revenue condition visible.
Press Windows logo key + Shift + S.
Drag the capture frame around the active entry rule.
Select Save as.
Save the capture as 02-flow-rule in the case-study folder.

The second image now records the threshold plus the trigger behavior behind the automation.

The third screenshot proves that the qualifying path creates assigned follow-up work.

Return to Morgan Reyes's Lead record in the Sales app.
Select Morgan's Activity tab.
Expand the Contact high-value lead Task so its high priority is visible.
Press Windows logo key + Shift + S.
Drag the capture frame around Morgan's automated Task.
Select Save as.
Save the capture as 03-automated-task in the case-study folder.

The third image now proves that a qualifying Lead receives the intended high-priority Task.

The fourth screenshot shows the operational report that a manager can reuse.

Return to the Reports tab.
Open High-Value Leads by Source.
Confirm the Lead Source groups plus report columns are visible.
Press Windows logo key + Shift + S.
Drag the capture frame around the finished report.
Select Save as.
Save the capture as 04-high-value-report in the case-study folder.

Your four screenshots now follow a clear story from manual failure to operational visibility.

The images show what happened. The case-study text explains why the solution matters.

Switch back to the Notepad document from earlier.
Explain the missed high-value Lead follow-up risk under Business Problem.
Describe the assigned high-priority Task automation under Solution.
Explain why a record-triggered flow fits this Lead data change under Design Choice.
Summarize the contrasting Avery Stone plus Morgan Reyes plus Dana Cole outcomes under Result.
List your configuration plus testing plus reporting plus business communication capabilities under Skills Demonstrated.
Write a one-minute walkthrough that follows the order of your four screenshots under 60-Second Demo Script.
Save Salesforce Lead Rescue Case Study.txt.

Before you inspect the folder, do you expect to see one case-study document plus four evidence screenshots?

Press the Windows key to open Windows search.
Type Salesforce Lead Rescue Case Study into the search field.
Select the local case-study folder from the search results.

You should see Salesforce Lead Rescue Case Study.txt plus files named 01-manual-gap, 02-flow-rule, 03-automated-task, and 04-high-value-report.

That is a strong finish. Your folder now proves the business problem plus the automation rule plus both test paths plus the reporting result.

Secret mission

Add a Manager Dashboard to Your Case Study

Your report compares qualifying Leads across acquisition sources. In this mission, you will turn those groups into a manager dashboard and capture a fifth evidence screenshot.

Clean Up Your Resources

These learning resources cost $0, so leaving Lead Rescue Lab available does not create a usage charge. Decide whether to keep the work available, pause by closing the browser, or clean the practice data from Salesforce.

Resources you used:

Three fictional Lead records for Avery Stone, Morgan Reyes, and Dana Cole.
An active record-triggered flow named Create High-Value Lead Follow-Up.
An automation-generated Task named Contact high-value lead on Morgan Reyes's activity timeline.
A saved report named High-Value Leads by Source.
An optional dashboard named High-Value Lead Dashboard from the Secret Mission.
A local Salesforce Lead Rescue Case Study folder containing Salesforce Lead Rescue Case Study.txt plus four evidence screenshots. The folder also contains 05-manager-dashboard if you completed the Secret Mission.

Keep everything running

No action is needed. Choose this if you want to keep demonstrating the automation or reviewing your evidence.

Keep Lead Rescue Lab connected to Trailhead.
Leave Create High-Value Lead Follow-Up active so new qualifying Leads continue receiving follow-up Tasks.
Retain the fictional Lead records so your positive and negative tests remain visible.
Keep the High-Value Leads by Source report.
Keep High-Value Lead Dashboard if you completed the Secret Mission.
Retain the Salesforce Lead Rescue Case Study folder with its document and evidence screenshots.
Continue using fictional records only in this learning environment.

Pause - I'll come back to this later

Close the Playground when you finish reviewing your saved work. The learning environment has no usage charge while you are away.

Close the Lead Rescue Lab tab in Microsoft Edge.
Leave the flow, Lead records, report, and optional dashboard saved in the Playground.
Keep the Salesforce Lead Rescue Case Study folder on your Windows device.
Return through Trailhead when you are ready to continue.

Delete - I don't want to use this again

Deleting practice data is permanent inside the Playground. Your local evidence folder remains separate until you remove it in the final cleanup group.

Open Automation in the Playground.
Select the Flows tab.
Open Create High-Value Lead Follow-Up.
Select the Related tab.
Open the action menu for the active flow version.
Select Deactivate.
Confirm the flow version no longer shows as active.

The automation can no longer create Tasks. Remove its inactive version next so the flow itself is cleared from the Playground.

Return to the Flows list.
Open the actions menu at the far right of Create High-Value Lead Follow-Up.
Select View Details and Versions.
Select Del next to the inactive version.
Select OK to confirm.
Confirm the flow no longer appears in the Flows list.

Remove the optional dashboard before its source report. This order prevents the dashboard from depending on a report you have already deleted.

Open the Dashboards tab if you completed the Secret Mission.
Open the actions menu for High-Value Lead Dashboard.
Select Delete.
Confirm the deletion when Salesforce prompts you.
Confirm the dashboard no longer appears in the Dashboards list.

The dashboard dependency is now clear. Delete the saved report next.

Open the Reports tab.
Open the actions menu for High-Value Leads by Source.
Select Delete.
Confirm the deletion when Salesforce prompts you.
Confirm the report no longer appears in the Reports list.

The remaining Salesforce resources are the fictional records and Morgan's generated Task. Remove the Task before deleting its Lead.

Open Morgan Reyes's Activity tab.
Delete Contact high-value lead from its Task action menu.
Confirm the Task no longer appears on Morgan's activity timeline.
Open the Leads list in Sales.
Delete Avery Stone from the record action menu.
Delete Morgan Reyes from the record action menu.
Delete Dana Cole from the record action menu.
Confirm all three names are absent from the Leads list.

Permanently deleting the local folder also removes its document and screenshots. Check that you no longer need those files before using this shortcut.

Press Windows logo key + E to open File Explorer.
Open your Desktop folder.
Select the Salesforce Lead Rescue Case Study folder.
Press Shift+Delete to bypass the Recycle Bin.
Confirm the permanent deletion when Windows prompts you.
Confirm the folder no longer appears on your Desktop.

Nice Work!

You pulled it off! Your tested lead rescue automation now turns qualifying prospects into assigned follow-up work.

What you learned:

Use Salesforce Flow to turn a revenue qualification rule into a high-priority Task for the Lead owner.
Validate the automation with a three-case test matrix covering the manual gap plus the qualifying path plus the nonqualifying guardrail.
Present a recruiter-ready evidence pack built around the High-Value Leads by Source report. The concise case study plus four privacy-framed screenshots make the work viewable without access to your private Trailhead Playground.
Secret Mission: Create a manager dashboard that compares the Partner Referral and Web source groups. Save the donut chart as a fifth evidence screenshot.

Ready to quiz yourself?