A Salesforce Workflow for Event Prospecting

A Salesforce workflow for event prospecting should start before anyone scans a badge. The goal is to turn event research into a controlled revenue process: target accounts become Campaign Members, fit and intent determine priority, owners get clear tasks, and every meeting stays attributable to the show. RevOps should be able to answer who is working each account, what happened, and what enters pipeline without rebuilding the story from spreadsheets.

laptop computer on glass-top table

That structure matches Salesforce's 2026 RevOps guidance: align teams on shared goals and KPIs, standardize the process, and consolidate data in one system. For event prospecting, the practical unit of that system is a Salesforce Campaign with consistent members, statuses, ownership, and reporting.

Build the Campaign before importing prospects

Create a parent Campaign for the quarterly or annual event programme, then a child Campaign for each show. Salesforce Support's 2025 Campaign management walkthrough shows why this model matters: Campaign hierarchies connect related activity, Campaign Members tie Leads and Contacts to each initiative, and member statuses provide the detail needed for engagement and influence reporting.

Use one naming convention, such as FY26 | Event | Web Summit Lisbon, and require these fields:

Event start and end date, city, region, and owner
Budgeted and actual cost
Target segment, territory, and ICP definition
Prospecting start date and follow-up SLA
Scryon event ID or another stable external key

Keep Campaign Member Status values operational: Targeted, Contacted, Meeting Requested, Meeting Booked, Attended, Follow-up Due, Qualified, and Disqualified. Do not use a generic Responded status for every meaningful action. A booked meeting and a booth scan should never look identical in a report.

For a broad technology event such as Web Summit Lisbon 2026 on November 9–12, the audience spans founders, investors, corporate leaders, sales, and marketing. Segment the Campaign before outreach so reps can distinguish target enterprise accounts from the wider 70,000-plus audience instead of treating the whole floor as one list.

Map event intelligence to the right Salesforce records

Do not create a new Lead for every attendee row. Stage the event data, match it to existing records, then upsert only what sales will use.

Event data	Salesforce destination	Purpose
Company name, domain, industry, size	Account	Match and score account fit
Name, title, work email, role	Contact or Lead	Identify the buying role
Event, outreach state, meeting state	Campaign Member	Track execution and engagement
ICP score, intent, reason codes	Campaign Member custom fields	Explain priority to the rep
Conversation notes and next step	Task or activity	Preserve context and accountability

Use the company domain as the primary account match, work email for the person, and a stable event key for Campaign membership. Queue uncertain matches for review. The sequence should remain match → enrich → upsert, following the same controls in the post-event CRM hygiene playbook.

This is also where Scryon fits: verified attendee and company context enters Salesforce through the integration layer, while Salesforce remains the system of record for ownership, activity, and pipeline.

Trigger Flow from priority, not from record creation

A record-triggered Flow that fires whenever any Campaign Member appears will create noise. Set entry conditions that reflect both fit and intent:

Campaign type is Event
Account and contact matching is complete
ICP score clears the agreed threshold
The member is new to outreach or has a meaningful status change
No open event-prospecting task already exists for that account and show

Then let Flow assign the owner by territory or named-account rule, create a dated task, set the next status, and alert the right queue. High-fit accounts with a booked or requested meeting should route immediately. High fit with no intent can enter a pre-event sequence. Low fit should not consume an AE task merely because the record exists.

Pair those gates with your event lead scoring model so the Flow exposes a reason such as Named account + VP Sales + meeting requested, not only a number. Lane Four's review of Salesforce and RevOps priorities for 2026 makes the dependency clear: automation and AI compound weak processes when records are fragmented, while structured workflows and clean data make them useful.

Give reps one event work queue

Create a list view or Lightning page filtered to the active Event Campaigns owned by the logged-in rep. Show account, contact, title, ICP score, meeting state, last activity, next task, and event date. Reps should not need to join Campaign exports in a spreadsheet to decide whom to contact.

Use SLA bands that match the event lifecycle:

Before the show: Tier 1 outreach task due within one business day
Meeting requested: Owner follows up until booked or closed
On site: Notes and next step logged the same day
Qualified after the show: Opportunity or sales-accepted stage within 24 hours
No fit or no interest: Disqualify with a reason instead of leaving an open task

Report the workflow as revenue operations

Build dashboards from the same Campaign structure: target accounts by tier, outreach completion, meetings booked, attendance, qualified accounts, opportunities created, pipeline, and closed-won revenue. Add conversion by ICP band and owner so RevOps can see whether the routing rule works, not just whether reps completed tasks.

Before activating the Flow, test a sample Campaign in a sandbox. Confirm creates versus updates, duplicate handling, task ownership, status transitions, and Campaign influence. Then publish a one-page runbook with field definitions and rollback steps. That turns event prospecting into repeatable Salesforce infrastructure rather than another one-off import.

When the workflow is ready, browse the event directory for the next Campaign, bring the target account list into Salesforce, and let ownership and status drive the work.