Angela C.

What if your Salesforce Screen Flows could collect payments? With KULTURRA, they can. In this video, see how to embed a payment component directly into a flow with no custom code needed. ✔ Collect payments via credit card or ACH ✔ Link payments to Opportunities, Quotes, or custom objects ✔ Trigger follow-ups automatically—all inside Salesforce Turn screen flows into "money flows". 👉 Learn more about Kulturra: https://kulturra.com/ 👉 Try it on AppExchange: https://lnkd.in/gpdTcj6 

9

So what's the deal with Insurance solutions when looking at ServiceNow vs. Salesforce? Salesforce = front-office CRM + industry core for insurance (policy/product/claims modules via Salesforce Industries, aka Vlocity). It can be the system of record for key policy/claims functions if you buy the Industries SKUs. ServiceNow FSO Insurance = workflow backbone that unifies claims, servicing, and underwriting work across your existing cores—with ACORD-informed data model, Now Assist (GenAI) for claims summaries, and prebuilt insurance workflows. It explicitly positions itself to connect legacy/cores rather than replace them. But what are the real differentiators? For me the “one platform/one data model” for cross-team work; which does not require core replacement sets ServiceNow apart, even in the early stages of the product. -forgive my typos :)

46

4 Comments

Proud to have contributed to this Agentforce-powered Photo Booth demo, showcasing how AI can transform a traditional identity and badging experience into a more conversational, intelligent, and engaging journey. My contribution focused on helping shape an experience where generative AI becomes the center of engagement, orchestration, case creation and automation on the Salesforce platform—guiding users naturally, adapting to inputs in real time, and moving beyond rigid form-based workflows. It was exciting to be part of something that not only demonstrates platform innovation, but also creates a memorable experience for participants. Salesforce Salesforce Architects #Salesforce #CapgeminiGovernmentSolutions

7

Salesforce drives innovation. But beneath the surface, misconfigurations, over-permissioned users, and ungoverned integrations silently accumulate risk. Governance isn’t just policy—it’s visibility, control, and real-time enforcement. Our ebook, “What You Can’t See Can Hurt You: The Guide to Governance in Salesforce,” breaks down the hidden vulnerabilities in Salesforce environments and what security-minded teams can do about them. Download it today: https://bit.ly/40Svei2

8

Flow errors aren’t just technical—they’re design mistakes waiting to happen. This article breaks down the most common Flow pitfalls that even experienced builders run into, from ignoring Order of Execution to skipping fault paths. It’s a practical guide that helps Salesforce professionals build smarter, more stable, and more scalable automations that actually support the business. If you’re looking to strengthen your Flow skills and avoid the traps many admins and consultants face, this is a must-read. 👉 Read the full article here: https://lnkd.in/gdyEUQcP 𝗝𝗼𝗶𝗻 𝗦𝗮𝗹𝗲𝘀𝗳𝗼𝗿𝗰𝗲 𝗧𝗿𝗮𝗶𝗹 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆: 👉WhatsApp Group: https://lnkd.in/eQFEqcjk 👉Telegram Group: https://lnkd.in/gCj_V5Zh #Salesforce #SalesforceAdmin #SalesforceFlow #Automation #SalesforceTips #ProcessAutomation #SalesforceTrail

18

We’ve seen too many Salesforce projects start in the wrong place. Too many discovery sessions focus on “what features do we need?” instead of “what journey do we want to support?” When you start with features, you end up with a system that mirrors your internal departments. It works fine… until a customer moves from one team to another and the experience falls apart. When we start with the customer journey, something different happens: 1. The process design naturally cuts across silos 2. The data model supports end-to-end visibility 3. Metrics reflect outcomes, not just activity counts The truth is, Salesforce already has the flexibility to follow your customer’s path. It just needs to be set up with that path as the blueprint. That’s why we tell every client: if you can’t clearly describe your customer journey from first contact to long-term loyalty, you’re not ready to implement #Salesforce. #crm #customerjourney #customerexperience

13

1 Comment

Salesforce Tip of the Day – Lightning Out Use Lightning Out to embed your Lightning Components in external web applications — perfect when you want Salesforce functionality outside the platform. ✅ Allows you to render Lightning components on non-Salesforce pages. ✅ Great for customer or partner portals that aren’t on Experience Cloud. ✅ Uses your Salesforce org as the component host and authentication source. Example setup: 1. Add the Lightning Out dependency in your Visualforce or external page: HTML <​script src="/proxy/aHR0cHM6Ly9sbmtkLmluL2RjRDVKUDVh"><​/script> 2 Bootstrap your Lightning app HTML <​script> $Lightning.use("c:MyApp", function() { $Lightning.createComponent("c:MyComponent", {}, "lightningContainer"); }); <​/script> Tip: Make sure CORS and Lightning Out dependencies are properly configured in Setup → CORS and Lightning Out Dependencies.

1

https://lnkd.in/eRswnGHq If you are a salesforce architect involved in a multiple-country project worried about compliance laws to meet in each country, here is a good blog that will provide guidance on org strategy for each country and also provide solutions for reporting.

1