Salesforce Data Management for Marketing Follow-Up

Please, stop calling me MQL and asking your sales team to call me after a webinar. I feel we can easily improve the event follow-up playbook... The broken event follow-up playbook: - Mark event sign ups as MQLs in Hubspot/Salesforce - Starting 5-emails nurturing sequence pushing attendee to book a demo - Assigning MQLs to sales and asking to call Webinar sign-ups ≠ buying intent. Here is how to refine event follow-up playbook to align it with the level of demand of the sign ups and their buyer journey stage. 1/ MARKETING: - Upload a recording and slides to a relevant content hub - Download and qualify sign ups by ICP criteria - Segment all qualified contacts by tiers - Match tier 1 and tier 2 accounts with the pipeline status and buyer journey stage - Add all accounts to the demand gen retargeting group aligned with the buyer journey 2/ SALES - Connect & engage with net new tier 1 and tier 2 accounts who consumed content in the content hub - When connected, ask for feedback and do progressive profiling to understand better where they are in the buying journey and what their needs - Suggest "bridge" activities (e.g. strategy sessions) to create logical bridge between current buyer needs and your product 3/ MARKETING AND SALES - Discuss collected insights and move accounts to a relevant ABM playbook matched with the accounts' journey stage. --- Nobody is signing up for the webinar to listen to the blatant product promotion or high-level stuff that ChatGPT can provide. B2B buyers come for practical learnings, connections and entertainment. Educate -> engage -> create demand -> research and understand the buyer journey stage and current needs of your prospects -> create "bridge" activities / buyer enablement - this is how you influence the buying process with webinars and generate pipeline.

A Company has 50 sales reps. Each spent ~9 hours/week fighting their CRM. 450 hours wasted. Every week. --- The problems: ❌ Duplicate accounts (same company, 8 different spellings) ❌ Invalid phone numbers (some 7 digits, some 13) ❌ Customers receiving cold outreach ❌ Deals stalling with no follow-up ❌ Data eroding at 30%/year Their solution attempts: → Weekly training sessions → Slack reminders → Manager reviews → "Please be more careful" emails Result? Nothing changed. --- We stopped trying to change behavior. We changed the SYSTEM. --- Here are the 5 guardrails we built: 1️⃣ LOOKUP FIELDS BEFORE NEW RECORDS Before creating a new account: → System forces search of existing records → Shows fuzzy matches ("Target Integration" matches "TargetIntegration") → Must explicitly choose "Create New" after seeing matches Result: 90% reduction in duplicate accounts --- 2️⃣ PHONE NUMBER VALIDATION Validation rule: → Must be exactly 10 digits → Auto-strips spaces, dashes, parentheses → Won't save record if invalid No more 8-digit numbers. No more international formats mixed with domestic. Clean data, every time. --- 3️⃣ AUTOMATED CUSTOMER STATUS UPDATES When deal closes: → Webhook fires to automation platform → Lead status → Customer status (automatic) → Record locked from outbound sequences → Customer success team notified Result: Zero customers receiving cold outreach --- 4️⃣ DEAL STALL ALERTS Escalation metric: → Any deal untouched for 15+ days → Auto-notification to manager in Slack → Includes deal context + last activity → Manager can reassign or follow up Result: 95% reduction in stalled deals --- 5️⃣ AUTO-ENRICHMENT VIA CLAY Every 30 days: → Clay syncs with CRM → Pulls latest LinkedIn data → Updates job titles, company info → Flags records with outdated data Result: Data erosion from 30% → 3% --- The outcome: ✅ 450 hours/week saved across team ✅ Duplicate records down 90% ✅ Invalid data down 95% ✅ Customer satisfaction up (no more awkward outreach) ✅ RevOps team freed from cleanup duty Cost to implement: ~$500/month in tools Value created: $67,500/week (450 hrs × $150/hr) ROI: 13,400% --- The lesson? You CANNOT train your way to clean CRM data. Humans fail. Get busy. Forget. Take shortcuts. But systems with guardrails? They enforce quality automatically. --- 🎯 Make bad data input IMPOSSIBLE, not discouraged. That's the difference between: → RevOps as data janitors → RevOps as strategic operators --- Which guardrail would save your team the most time? Comment below what resonates for you.

Lead Routing Nightmares: The Event Marketer’s Version of a Horror Story 🔥 You just wrapped a killer event. The booth was buzzing, your sessions were standing-room only, and your reps are already talking about deals in motion. Then the questions roll in… “Hey… where did my leads go?” “Why is my best prospect marked as ‘Cold’?” “Wait - why did Sales never follow up?” Cue: The Black Hole of Event Leads™️ If you’ve ever lost sleep over MQLs vanishing into thin air, you’re not alone. But it doesn’t have to be this way. Here’s how field marketers and ops teams can team up to close the loop and stop wasting pipeline: 🧠 1. Align on Lead Nomenclature - Before the Event Set up your event in Salesforce/Marketo with clear, agreed-upon campaign tags. Here's a few suggested ideas: Campaign Type = [SPON-EVT] / [HOST-EVT] Source = “Field Event - [Name]” Lead Status = “Qualified - Needs Review” Custom field = “Event Name” for easy attribution Avoid freeform chaos by using picklists. Bonus points if you templatize campaign setup and share it with reps beforehand. 📊 2. Define Lead Scoring Criteria Based on Event Type Not all event leads are created equal. Scoring helps route leads intelligently based on real engagement: 👉 Sponsored Events Hot = Scanned + had meeting or high intent = Route to AE Warm = Scanned, no meeting = Route to SDR Cold = Badge swipe or booth fly-by = Nurture 👉 Hosted Events Attended = High priority Registered, No-Show = Lower score Feed these signals into Marketo or HubSpot scoring models to influence routing logic in Salesforce. 🔁 3. Build Real-Time Routing Rules That Don’t Suck Marketo or HubSpot should automatically route hot leads (e.g. attended, scheduled meeting, high intent) directly to assigned reps or territories. → For example: “If [Lead Scanned at X Event] AND [Title includes VP/Director] → Assign to AE within Account Owner’s region in Salesforce” Not sure how to build this? Partner with MOPs before your event and test the flow with dummy records. 📬 4. Make the First Follow-Up Effortless No rep should have to dig through Salesforce reports post-event. Give them a filtered lead view in Salesforce or a dedicated HubSpot List. Preload a follow-up sequence into Outreach/Salesloft with messaging tailored to the event theme. Bonus: Add a “Last Event Touched” field so Sales can reference context without playing detective. ✅ 5. Pressure-Test the Whole Flow Create a test lead pre-event and walk it through your campaign flow: → Marketo/HubSpot Form → MQL Score → Salesforce Assignment → Rep Notification No skipped steps. No surprises. TL;DR: Field events should drive revenue, not reporting nightmares. Talk to your MOPs teammates early, test everything twice, and don’t let good leads die in a broken workflow. 🧡 Have your own horror story or workaround? Let’s trade notes👇 #FieldMarketing #B2BMarketing #EventMarketing

Spring '26 New Release info -  🚀 Marketing Cloud Next: Run Event-Triggered Flows When CRM Records Change Spring ’26 introduces a powerful new capability in Marketing Cloud Next Growth & Advanced Edition: You can now trigger Event-Triggered Flows directly from CRM record changes. This means marketing actions can happen instantly, at the exact moment a business event occurs — not minutes or hours later. 💡 What you can do ✅ Case closed → Send a personalized email immediately ✅ Opportunity stage updated → Notify the owner automatically ✅ Field value changed → Create tasks or send messages ✅ Any CRM event → Trigger real-time automation This time I tested: 👉 “Case closed → instantly send a personalized email to the Contact” Flow setup: 1️⃣ Event-Triggered Flow 2️⃣ Trigger: Prospect/Lead/Contact or Related Record Change 3️⃣ Object: Case 4️⃣ Condition: Status = Closed 5️⃣ Use Apex Class Data Provider for email personalization 6️⃣ Send Transactional Email with case details The email includes: • Case Number • Subject • Customer name • Closed date (Slash formats) • Fully personalized content Just real-time CRM → Marketing automation ⚡ 🎯 Why this is big Until now, triggers were mainly: • Email engagement • Journey events • Data Graph events Now we can use CRM changes themselves as triggers!! Conceptually, it feels like the “Salesforce Entry Source” in Journey Builder, but natively built into Marketing Cloud Next. This is a perfect fit for a CRM-centric marketing architecture. If you’re using Marketing Cloud Next, definitely try this for: ✔ transactional emails ✔ service follow-ups ✔ operational notifications ✔ real-time customer engagement Game changer for automation 👏 Blog: https://lnkd.in/gMQcbmkV — Nobuyuki Watanabe Stay tuned for more Salesforce Marketing Cloud tips 😎 #Salesforce #Agentforce #MarketingCloudNext #MomentMarketer #MarketingChampion #MarketingChampions

A lot of people screw up data enrichment. And not in small ways...in big ways. I've walked into instances where: 😱 Recent sales-entered data was being overwritten by stale enrichment data 😱 Instead of setting up an integration, a massive file was imported all at once, into standard fields, without a data back-up....leaving no audit trail and losing historical data 😱 Enrichment was set up to trigger every time a record was created or updated in Salesforce, creating a situation where only 1,000 records or less could be updated at one time without hitting the Salesforce API limits 😱 Enrichment data wasn't standardized, so each vendor was entering in different formats for fields like employee size So, how do you set it up correctly? Here's what it should look like... Typical steps included: 1. Input Stage: Define the entry points for raw data (e.g., web forms, imports, email captures). 2. Cleaning Stage: Build workflows to: 🔺 Standardize formats (e.g., phone numbers, dates, addresses). 🔺 Correct invalid or missing data (e.g., normalize country names to ISO codes). 🔺 Remove duplicates based on unique identifiers (e.g., email or account ID). 3. Enrichment Stage: 🔺 Match records with external datasets to fill gaps. 🔺 Append metadata (e.g., confidence scores, enrichment source). 4. Output Stage: Push cleaned and enriched data back into your CRM or database. Example washing machine flow: 1. Input: New leads enter from web forms or imports. 2. Cleaning: 🔺 Deduplicate by email or company domain. 🔺 Standardize phone numbers to E.164 format. 🔺 Normalize country names to ISO codes. 3. Enrichment: 🔺 Call Clearbit API to append industry, company size, and LinkedIn URL. 🔺 Validate emails with an email verification tool. 4. Output: Push cleaned and enriched data back to CRM, tagging it with the enrichment source and date. Things to consider: 🔻 Typically, you want to enter enrichment data into separate custom fields. This is duplicative, but if you don't have really strong audit trails and strong enrichment rules, you shouldn't write into a default field because you could cause confusion and frustration with sales, if you overwrite their recently entered data. 🔻 You need to understand all of the fields you're enriching very intimately...what is their purpose, at which stage do they need to be enriched? Don't be lazy and enrich every field at every record edit, it'll harm your systems and speed-to-lead. 🔻 Make sure any enrichment automation takes race conditions into consideration -- what other automations could be triggered, and how would that impact the API limits/system performance? 🔻 How will you monitor results? Set up reports and audit trails, whether through Snowflake or field history in Salesforce. 🔻 Don't forget about consent management fields! Running out of room....what else? Did you find this helpful? #marketing #sales #marketingoperations #revenueoperations

Now that your tradeshow is over, what do you do next? After a breather and some time to recuperate from Dreamforce/Inbound, you now need to follow up with the interest you created. Follow-up is obviously critically important, but dropping them all into your marketing automation or sales engagement tool isn't going to cut it. Here's what I've always done with my teams to set and convert more meetings with the right reps after events. Your routing should be based on a few critical criteria:  – Status (eg, target account, open op, customer, etc) – Lead or account score  – Territory (geo, industry, or however it's set up) – Segment (SMB, MM, ENT) Now, here's what the operation side of things should look like: – First, Lead-to-Account matching (L2A) is essential before uploading all of your lists. Few things are worse than SDRs reaching out to customers asking to book an intro meeting. – For all of your routing rules, your lead assignment and distribution tool should assign and update ownership to the proper team and update Lead Status field in Salesforce as Assigned. – Create a Task in Salesforce for the reps to follow up within your SLA (ideally 24 hours). – Notify reps via Slack and email that they have new leads to follow up with. If the lead status hasn't changed in 5 working hours (ie, is still without ownership), ping the assigned reps again. – Add the leads to the right Events Campaigns and update their status accordingly (eg, for a VIP dinner, mark Attended or No Show). – Set up a Lead Conversion Flow to automatically create an Opportunity in Salesforce if the lead is marked as Sales Qualified. Now, hopefully your reps have sequences/cadences that require personalization set up in your sales engagement platforms. The sooner you follow up with buyers, the better. I don't ascribe to the belief that "everyone is following up right after the show, so let's wait a few days until the noise calms down." First, you're giving others too much credit for having their 💩 figured out. Second, if everyone thinks that way, everyone will also be waiting. Third, the longer you wait, the more likely buyers will forget you. What did I miss?