Sourya Silwal

Attention Salesforce Consulting Partners 👇 Salesforce partner structure has changed. Instead of Base, Ridge, Crest or Summit ladder, now we have: ✅ Summit – top strategic partners ✅ Select – proven delivery partners What this means: • You got to have real pipeline and projects to become a partner. • Certification and Trailblazer Score still matters, but it is more about output than your prep. • More focus on AI-first, and you got to show up your dominance in Agentforce, Einstein, and Data Cloud enablement. How this impacts your status: read along this blog to discover all updates in details: https://lnkd.in/dR5Ej26C #SalesforceFY27 #Consultingpartner #Trailblazerscore #MarTech #Agentforce #salesforceupdates #salesforcepartnerprogram #BuildWithMIDCAI MIDCAI

4

Salesforce Ben just published a new deep dive video on building real-time Salesforce integrations. It’s a companion piece to their earlier Salesforce Ben article on the same topic and expands on: • Why true real time requires event-driven architecture • Why bidirectional sync is critical • Where common integration approaches break down at scale In the video, Salesforce Ben references Declarative Webhooks by Omnitoria as an example of a Salesforce-native solution designed for: ✔ Event-driven updates (no polling) ✔ Bidirectional data flow ✔ Strong security and data sovereignty We appreciate Salesforce Ben continuing to invest in thoughtful, practical integration content — and for including our approach as part of the broader conversation. 🎥 Watch the full video: https://lnkd.in/gchiurCc Try Declarative Webhooks free on the Salesforce AppExchange: https://lnkd.in/g8fENURT #SalesforceBen #SalesforceIntegrations #Omnitoria #Architecture

5

Stop repeating the same instructions in every AI prompt. Use Agent Skills to help transform how you build on Salesforce. I put together a 12-page visual guide breaking down everything you need to know 👇 📖 What's inside: ⚠️ The problem — why your prompts are bloated (6,300+ tokens wasted per session) ⚡ The fix — Skills load knowledge on demand, not on every call 🔄 The execution flow — query → skill manager → tools → output ☁️ 19 Salesforce-specific skills — Apex (150-pt scoring), LWC, Flow, SOQL with live query plans, Agentforce, deployment, and more 🤖 7 specialised AI agents — a full team that delegates, builds, tests, and deploys 🧩 Skills vs MCP — how they complement each other 🔗 All the resources to get started today Note - Most of these skills come from Jag Valaiyapathy's sf-skills repo . Thanks Jag for this outstanding skill resource 🙏

35

Salesforce Director of Strategic Technology Partner Sales, Mark Zoroya, discusses our latest announcement, Five9 Fusion for Salesforce. This offering combines Five9’s real-time system of action with Salesforce’s #1 AI CRM to help businesses deliver better customer experience, hyper-personalized self-service, and achieve smarter results with a future-ready foundation. #PartnerPowered #CustomerExperience #CRM #AI

1

1 Comment

Salesforce Agentforce is powerful. But without MuleSoft to orchestrate the data and actions across your stack, you’re giving your agents the same fragmented view your support teams had before. Swivel chair isn’t solved just because you added an AI agent. If your systems aren’t connected, you’re just swivel chairing between agents instead of screens. Agentic AI only works when it's grounded on the right data and when it can act. That means APIs. That means integration. That means MuleSoft. Thanks to Jeff Mains for having me on his podcast!

18

4 Comments

Most Salesforce implementations don’t fail because of bugs. They fail because no one understands how the system actually behaves. If your Salesforce org feels slow, fragile, or impossible to change, this is the framework I use to fix it. My 4-step approach to make Salesforce work at scale: 1️⃣ Validate transactions Before fixing anything, I map what really happens when a user works with an Account or Opportunity (or any other object). One action → many queries → integrations → hidden side effects. 2️⃣ Redesign repetitive queries (globally, not locally) Don’t patch single errors. Redesign transaction logic so related data is queried once, not dozens of times across automations. 3️⃣ Define order of execution Decide what must run synchronously and what can safely run asynchronously. Performance improves immediately when this is done right. 4️⃣ Rewrite after redesign Code or Flow — it doesn’t matter. What matters is: single-query patterns proper error handling logging data-driven decisions I don’t fix symptoms. I fix the system. If your Salesforce org feels harder to change every month, that’s a warning sign. 💬 Happy to share how this applies to real-world orgs. Salesforce Application Architect | FixYourOrg.com

17

1 Comment

Salesforce introduced Agentforce Vibes yesterday at Dreamforce, and in typical fashion I immediately switched screens and launched it to try it out. I think this might be the biggest shift yet in how we build on the platform. While “vibe coding” isn’t new, we’ve all been doing it in our own way, I used to rely on ChatGPT or Gemini. I’d feed them my org’s structure, fields, objects, and step-by-step directions for what I wanted the LWC or Apex code to do. Then I’d copy and paste the output into the Dev Console or VS Code, test it, fix the issues, and repeat the loop. With Agentforce Vibes, that entire workflow changes. I launched it directly in the browser from the setup icon, and it connected to my instance with full context. It knew my fields, metadata, and objects. It even gave me options for how to build what I needed. My favorite part? It can build Flows directly from metadata with natural language. Making automating workflows even easier and faster. This isn’t just AI-assisted coding, it’s org-aware, secure, and native to Salesforce. Excited to see the kind of components and automations people start creating now that non-developers have easier access to developer tools. https://lnkd.in/g_f6_Pyy

24

$CRM #Salesforce Q3 FY26 (October quarter): • Current RPO +11% Y/Y to $29.4B • Revenue +9% Y/Y to $10.3B (in-line) • Operating margin 21% (+1pp Y/Y) • Non-GAAP EPS $3.25 ($0.39 beat) FY26 guide: • Revenue +10% to $41.5B ($0.3B raise) • Adj. op. margin unchanged 34.1% Source: @economyapp

5

Salesforce recently added 6,000 Agentforce enterprise customers. At the heart of this momentum is a fundamental truth: agentic AI must be trusted to be impactful. #Agentforce 360 is built on the Trust Layer — a framework within the Salesforce ecosystem designed to uphold security, privacy, guardrails and ethics while driving AI effectiveness across the platform. This foundation is what enables companies like Williams-Sonoma, Inc. and Engine to deploy enterprise-ready agents at scale today. 🚀 Williams-Sonoma’s Sameer Hassan said it best: "You don't need Agentforce to go build a chatbot. What Agentforce helped us do more quickly and with more confidence is build something that's more enterprise-ready." We are proud to help organizations of all sizes and across all industries transform into Trusted Agentic Enterprises. We aren't just building agents; we are building a foundation for the next century of business. Read more in VentureBeat: https://lnkd.in/ev29kP5r

50

2 Comments

🤖🛠️✨ Week One Wrap-Up: AI Force Training Agentforce Boot Camp! Wrapping up Section 1 of the Agentforce Boot Camp and wow, this was one of those foundational weeks where you really feel the shift in how you think about building with AI in Salesforce. ✅ This week it was about learning to think in systems, mapping data, defining inputs and outputs, and structuring prompts that work like real integrations. ✅ I especially appreciated the emphasis on bi-directional design, where Flows don’t just use AI to spit out answers but send Salesforce data to AI and get tailored responses back. 🛠️ The final exercise was about creating a flexible Prompt Template and integrating it into a Screen Flow. Not just generating an email draft, but giving users a customized experience. As a Salesforce consultant, I’m already thinking about what kind of agents I could design for my clients with this. It’s one thing to understand AI features. It’s another to design for them. This section forced me to think about: 🔹How to standardize quality in outputs 🔹How to reduce user effort without losing control 🔹How to prepare data and variables so AI doesn’t hallucinate or go off-brand Week 2 is going to focus on using these foundations to build better, faster, and more modular prompts. I can’t wait to keep leveling up.

13

1 Comment

Salesforce rarely fails at the platform level. It fails at the data layer. Duplicate leads, stale contacts, and unreliable reporting quietly erode trust in the system. I put together a deep dive on Salesforce Auto Merge & Auto Delete, including: • Record identification logic • Merge behavior most teams misunderstand • The underlying system objects involved • Safe automation patterns for ongoing cleanup If you’re serious about governed, scalable CRM data, take a look 👇 #Salesforce #SalesforceAdmin #CRM #DataQuality #SalesOps #Automation

15

1 Comment

Obliterate bugs in your Salesforce implementation. Create test Automation in plain english. Visit us at Booth #10 at #TDX to find out how Salesforce #QA #TestAutomation

26

2 Comments

✨ ✨ ✨ New Series: SFMC Real-World Scenarios✨ ✨ ✨ 🚀 SFMC Reality Check – Day 1 Nobody tells you this when you start working in Salesforce Marketing Cloud: Most SFMC problems are not “advanced”. They’re basic things missed under pressure. Here’s one of the most common real-world mistakes 👇 𝗦𝗖𝗘𝗡𝗔𝗥𝗜𝗢 ◾ Campaign ready ◾ Audience looks correct ◾ Email preview looks perfect ◾ Send goes out… ◾ Engagement is terrible And everyone starts blaming subject lines, content, or timing. 𝗧𝗛𝗘 𝗔𝗖𝗧𝗨𝗔𝗟 𝗜𝗦𝗦𝗨𝗘 ◾ You sent to the wrong audience version ◾ Or an old snapshot DE ◾ Or a DE that wasn’t refreshed before send So technically, the send worked. But it worked on the wrong data. 𝗪𝗛𝗘𝗥𝗘 𝗧𝗛𝗜𝗦 𝗛𝗔𝗣𝗣𝗘𝗡𝗦 ◾ SQL query not scheduled before send ◾ Automation failed silently ◾ Someone copied a DE “just for testing”… and used it in production ◾ Last refresh date never checked 𝗦𝗜𝗠𝗣𝗟𝗘 𝗥𝗘𝗔𝗟-𝗪𝗢𝗥𝗟𝗗 𝗙𝗜𝗫 Before every production send, ask 3 questions: ◾ When was this DE last updated? ◾ What automation or query feeds this DE? ◾ Is this the same DE used in preview and send? This one habit alone prevents a huge percentage of “mystery” SFMC issues. 𝗤𝗨𝗜𝗖𝗞 𝗠𝗜𝗡𝗗𝗦𝗘𝗧 𝗦𝗛𝗜𝗙𝗧 SFMC doesn’t fail loudly. It fails quietly when data assumptions are wrong. If you’re working in SFMC today: Keep shipping. Keep validating your data. Keep learning through real projects. That’s how confidence is built. #SFMC #SalesforceMarketingCloud #MarTech #MarketingAutomation #EmailMarketing #Trailhead

41

1 Comment

Here is a Salesforce Decision Guide Format you can use to evaluate technologies, architectures, or platforms (like choosing between LWC and Aura, or deciding when to implement Agentforce). https://lnkd.in/gzFKuG6B

2

As a Product Manager in Salesforce Insurance vertical, I see data every day on how insurance brokerages drive their growth. But, one recurring pattern that keeps us up: The Silent Renewal Stall. [LOOK AT THE TWO CHARTS ATTACHED BELOW] 👇 👈 On the left: A "Healthy" Renewal Pipeline. Everything looks great because the Close Dates are in the future. 👉 On the right: The Reality. When you filter by Activity Signals, you see that nearly half of that pipeline is stalled. In most insurance brokerages, renewals make up the vast majority of revenue, a high-70% range. Yet, most brokerages are optimised for "New Business," leaving renewal signals incomplete. The Math of the Leak: ✅  Acquiring a new client costs 5–9 times more than retaining an existing one. ✅  Preventable leakage, including missed or poorly managed renewals, often runs in the low single-digit percentage of revenue. ✅  For a $10M commission brokerage, that is hundreds of thousands of dollars in avoidable loss. This isn’t a producer discipline problem; it’s a signal design problem. If a renewal hasn't had activity in 30 days, it’s a "Silent Stall". By the time it shows up on a standard report, the client has often already shopped their policy elsewhere. I’ve created a technical playbook to fix this. It uses 5 custom formula fields to turn Salesforce into a Revenue Assurance Engine that flags these stalls in real-time. I’m sharing the full configuration logic and the management scripts I've built for our community. Comment "STALL" below and I’ll DM you the playbook directly. #Insurance #Salesforce #RevOps #Brokerage

49

9 Comments

Salesforce UI will lie to you. The API won’t. When you’re building a real integration, the only reliable way to understand what a customer org actually supports is through Salesforce CLI. Edition gaps, metadata drift, Connected App collisions, ghost objects, API-only users - none of this shows up in the UI. This breakdown covers the real failure modes surfaced through CLI, Tooling API, and scratch-org testing. If you’re integrating with Salesforce at any serious level, this is the layer you should be working at. #Salesforce #SalesforceDevelopers #SalesforceCLI #APIDevelopment #MetadataAPI #ToolingAPI #DevOps #SaaS #WordPressDevelopers #Engineering #SoftwareArchitecture #CRMIntegration #Debugging #APITesting

6

I love me some high quality FREE of cost, INVALUABLE gain content. What other FREE resources are you using to skill up on Salesforce?

6

Stop starving your GPUs! ⚡ Salesforce AI Research hit peak utilization and slashed costs by using Google Cloud Managed Lustre. Learn how we did it at our #GoogleNext session. 📅 April 24 | 1:45 PM 📍 Breakers A (BRK2-188) #AI #SalesforceAIResearch #GoogleCloud #AIFoundry #SFResearch

5

Ever struggled to figure out when to use typed or untyped deserialization in Salesforce? Let’s break it down in a quick and super digestible way 💡👇

15