Using Agentforce and Marketo to Triage Stalled Nurture Leads

The useful agent is the boring one

Salesforce’s loudest 2025 Agentforce marketing story was campaign creation. On June 11, 2025, Salesforce announced Marketing Cloud Next and said Agentforce Campaign Creation was generally available, with agents drafting briefs, audiences, email, SMS, and Flow-based journeys. Fine. I get the appeal. But the ops win I would actually ship first is smaller and closer to revenue: use an Agentforce campaign agent to triage stalled nurture leads before they hit sales.

That sounds less cinematic than autonomous campaign work. It also fixes a problem I see every quarter in founder-led B2B teams running paid search, LinkedIn ads, webinars, and SEO content from the same Marketo Engage instance. Marketing has 4,000 people sitting in nurture. Sales sees 300 recycled MQLs. Half of them clicked one email in May, ignored the pricing page, and still have a closed-lost opportunity from 2024. Nobody needs another task that says ‘follow up.’ They need the next action, or they need silence.

Marketo already has the clues

Marketo Engage program-member data is underrated because operators treat it as campaign plumbing. Adobe’s Program Members API can return fields like leadId, programId, statusName, membershipDate, reachedSuccess, and custom program-member fields. The same Adobe docs note that program-member records can have up to 20 custom fields, and the endpoint can query by searchable fields such as leadId, statusName, and reachedSuccess. That is exactly the grain you want for nurture triage.

A lead score tells you someone added up points. Program-member history tells you the shape of the interest. Did the person register for the March 2026 webinar and no-show? Did they reach success in the ‘ROI calculator’ program on July 9? Did they move from ‘Invited’ to ‘Attended On Demand’ after a retargeting click? Those details matter when a sales rep has 11 minutes between calls and one shot at writing a useful note.

I would not ask an agent to invent intent from a generic engagement score of 74. I would ask it to read the last 90 days of program memberships across three or four channels and decide whether there is a real reason to interrupt a rep. In a SaaS motion with a $12,000 annual contract value, my first rule would be blunt: no sales task unless the lead has reached success in at least one bottom-funnel program or has two separate high-intent actions within 21 days.

The Salesforce side keeps it honest

The CRM stage matters because nurture is full of ghosts. Adobe’s Salesforce sync docs say Marketo syncs with Salesforce all day, pauses for 5 minutes between syncs, and syncs leads, contacts, accounts, opportunities, campaigns, custom objects, activities, and users depending on permissions. Adobe also says Marketo uses 25 Salesforce API calls per sync session to check for updates, with leads, contacts, accounts, opportunities, campaigns, and activities synced in batches of 200 per API call. That cadence is good enough for triage. It is not real-time intent, but it is close enough for a same-day SDR queue.

This is where Agentforce can do useful judgment work. Salesforce’s own Marketing Cloud Next help says Agentforce can draft and refine multichannel campaigns, generate briefs, summarize campaign performance, and use Flow-backed agent actions such as Create a Campaign from a Brief, Draft a Campaign Brief, Save Campaign Brief, and Save Campaign. Salesforce’s Adobe Marketo Engage connector also lists actions like Get Lead, Activate Smart Campaign, Sync Leads, and Sync Program Member Status, with MuleSoft for Flow requirements for many connector use cases. Put those pieces together and the practical pattern is clear: Flow does the governed work, Agentforce reads context and proposes the next step.

For a 15-person company, I would keep the first version almost painfully narrow. Pull Marketo program-member history for the last 90 days. Pull Salesforce lead or contact status, lifecycle stage, owner, open opportunity count, last activity date, and last closed-lost reason. Add SLA rules from a small Salesforce custom metadata table. Then ask the agent for one of four outcomes: create sales task, keep in nurture, suppress for 30 days, or send to marketing review.

What the agent should see

The agent needs fewer fields than most teams think. Start with Marketo leadId, email, acquisition program, program IDs, status names, success flags, membership dates, and maybe two custom fields such as contentTopic and offerStage. From Salesforce, add Lead.Status, Contact.Lifecycle_Stage__c, OwnerId, LastActivityDate, ConvertedDate, Account.Tier__c, and open opportunity stage. If you use person accounts, include that branch from day one because Salesforce’s Summer ’25 notes called out Agentforce Sales Development support for Contacts and Person Accounts, not only Leads.

The SLA table should be boring. For example, ‘Pricing page plus product demo webinar success within 14 days creates a same-day SDR task.’ ‘Closed-lost competitor reason suppresses for 60 days unless the lead reaches success in a migration guide program.’ ‘Student, consultant, and vendor email domains stay in nurture unless account tier is named.’ ‘Existing open opportunity routes to the opportunity owner, not the SDR pool.’ You can store those as custom metadata in Salesforce or as a small Data Cloud object if that is already where your team keeps activation rules.

The output should be short enough to paste into a task without embarrassment. I like this format: recommended action, evidence, reason, and expiration date. A good task says, ‘Call today. Maya attended the August 12 security webinar, clicked the SOC 2 checklist email on August 14, and belongs to a Series B fintech account with no open opportunity. Ask whether the Q4 vendor review includes access governance.’ That is a rep-usable next action. ‘Highly engaged nurture lead’ is landfill.

Where Campaign Agent fits

Campaign Agent is still relevant here because the triage loop starts inside campaign operations, not sales automation. Salesforce’s Campaign Agent help article from October 31, 2024 describes it as part of Agentforce and says it can generate campaign briefs, segment target audiences, draft content, and construct customer journeys in Flow. The May 29, 2025 Salesforce campaign-creation article says recent enhancements helped marketers create multi-series campaigns, integrated email and SMS flows, and journey visualizations. That is the flashy layer. The same Flow foundation can support a quieter workflow after a nurture program has been running for 30 days.

I would build this as a weekly ‘stalled nurture review’ campaign process. Every Monday at 7:30 a.m. account-local time, Flow selects leads that have been in a nurture program for at least 45 days, have no sales activity in 21 days, and reached success in at least one Marketo program in the last 90 days. The agent reviews the Marketo history and Salesforce record, applies the SLA rules, and writes a recommendation to a custom object called Nurture_Triage__c. Sales only gets a task when the confidence threshold clears 80 and the action is specific.

That confidence number should not pretend to be science. I would calculate it from visible factors: 30 points for bottom-funnel success, 20 for two-program engagement in 21 days, 15 for ICP account fit, 15 for recent web or form activity, minus 25 for closed-lost inside 60 days, minus 20 for no valid phone or business email. The agent can explain the score, but the score itself should be deterministic enough that RevOps can debug it on a Tuesday afternoon.

The guardrails make or break it

Do not let the agent create opportunities. Do not let it change lifecycle stage on its own in version 1. Let it create a draft task, a triage record, or a Marketo status update such as ‘Sales Review Suggested.’ Adobe’s Program Members API supports updating program member status in batches of up to 300 lead IDs per call, and Salesforce’s Marketo connector includes Sync Program Member Status. That is plenty of write access for the first pass.

The riskiest failure is not a strange sentence from the model. The riskiest failure is routing stale leads with official-looking confidence. Put three checks in place before a task reaches sales. First, require a current Salesforce owner or queue. Second, require the evidence to include at least one dated Marketo event. Third, expire the recommendation after 7 days. A lead who clicked a webinar replay on August 3 is different on August 21.

I would also sample the rejects. Every Friday, pull 50 leads the agent kept in nurture and review 10 by hand. In one B2B database I audited in 2025, the false negatives were hiding in partner webinars because their program statuses ended at ‘Attended’ instead of ‘Reached Success.’ That one channel taxonomy mistake made 18 percent of webinar-influenced leads look weaker than they were. Agents do not fix messy channel definitions. They expose them.

The operator playbook

Start with one nurture stream and one sales team. If paid search is your highest-intent channel, pick the nurture program that catches non-demo conversions from Google Ads, such as calculator downloads or comparison guides. If organic is doing the heavy lifting, pick the SEO nurture tied to three or four money pages. Do not start with every program in Marketo. You will spend two weeks arguing about edge cases before a single rep sees a better task.

Run the pilot for 30 days. Track five numbers: leads reviewed, sales tasks created, tasks accepted by reps, meetings booked, and leads suppressed. I would expect a healthy first pass to create tasks for 5 to 12 percent of reviewed nurture leads. If it creates tasks for 40 percent, your rules are mushy. If it creates tasks for 1 percent, you picked a dead stream or your Marketo success statuses are too strict.

The best part is the feedback loop. When reps reject a task, force a reason: bad fit, bad timing, no clear action, already contacted, wrong owner, or duplicate. Feed that back into the SLA rules every two weeks. After two cycles, the agent becomes less like a campaign novelty and more like a patient ops analyst who reads the stuff nobody has time to read.

Agentforce’s 2025 marketing-agent updates made the big promise visible. Marketo program-member data makes it useful. The move is not to hand your campaign calendar to an autonomous agent and hope the machine finds pipeline. The move is to let the agent sit between nurture and sales, read the receipts, and pass along only the leads with a next action worth a human’s time.