Excellent example for improving performance when using WhatsApp, especially for those with many agents using this tool. Enable subtitles in your language and 1080p quality:
https://www.youtube.com/watch?v=kHTemjVWEG0&list=PLYStC_2TZBSU
Opportunity β Quotes Scenario: When a Quote is approved, automatically mark it as the Primary Quote and uncheck all other Quotes. Questions: β’ How do you update multiple child records? β’ How do you avoid recursive updates?
@* Sales Cloud - Best Practices * @* Sales Cloud - Getting Started *
Hi @Rohit .
I would use a Record-Triggered Flow with a Scheduled Path on the Contract.
Flow:
Contract β Scheduled Path (30 Days Before End Date) β Duplicate Check β Create Renewal Opportunity β Notify Owner
This is cleaner than calculating the 30-day window manually. Salesforce supports Scheduled Paths based on a date field with a positive or negative offset.
Hope This Helps!!
π Big shoutout to our incredible Forum Ambassador, @Smitha Thomas for an awesome deep dive on "Make a Feild Avalible as a Dashboard Filter!π Check out the article here >> https://help.salesforce.com/s/articleView?id=005408536&type=1
π Found it helpful? Have thoughts to share?
Let us know by clicking the "Yes" or "No" button at the bottom of the articleβyour feedback helps us improve!> π Found it helpful?" style="display: block;" /> #Reports & Dashboards
π Salesforce Winter β27: TOP New Features for Developers & LWC!
Salesforce Winter β27 is bringing some exciting updates for Salesforce Developers and Lightning Web Components (LWC). π₯
In my latest video, I cover the TOP Winter β27 features that developers should know, including:
π» New developer capabilities
β‘ Lightning Web Components (LWC) improvements
π API & platform enhancements
π Performance and scalability updates
π Security & governance improvements
π οΈ Features that can make development faster and more productive
If you're a Salesforce Developer, LWC Developer, or working with the Salesforce Platform, these updates are definitely worth checking out!
π₯ Watch the video:
https://www.youtube.com/watch?v=8j97AenYLpM
πΊ Subscribe to Salesforce Hunt:
https://www.youtube.com/@SalesforceHunt
@Agentblazer Community Group @* Sales Cloud - Getting Started *@* Release Readiness Trailblazers *@* Sales Cloud - Best Practices *@* Salesforce Administrators *@* Service Cloud *
π Salesforce Winter β27: Exciting New Features for Flow Builders! β‘
Salesforce Winter β27 is bringing some great improvements to Flow β making automation easier to build, debug, maintain, and scale.
Here are some of the Flow features every Salesforce Admin & Developer should know π
πΉ 1. Improved Flow Builder Experience
Build and manage your flows more efficiently with enhancements to the Flow Builder experience.
πΉ 2. Better Flow Debugging & Troubleshooting
π
New improvements make it easier to understand whatβs happening during flow execution and identify issues faster.
πΉ 3. Enhanced Flow Performance
β‘
Salesforce continues to improve Flow capabilities so you can build more scalable automation while keeping performance in mind.
πΉ 4. More Powerful Flow Logic
π§
New enhancements provide additional flexibility when designing complex automation and business logic.
πΉ 5. Improved Flow Management
Managing multiple versions and maintaining automation becomes easier with continued improvements across the Flow lifecycle.
π‘ Why does this matter?
Flow is becoming more than just a point-and-click automation tool. With every release, Salesforce is making Flow a stronger platform for building enterprise-grade automation with less custom code.
π If you're working with Salesforce Flow, Winter β27 is definitely a release worth exploring.
Which Winter β27 Flow feature are you most excited about? π
π₯
Want to see these features in action?Iβve covered the Salesforce Winter β27 Flow features in this video:
π https://www.youtube.com/watch?v=8j97AenYLpM&t=348s
@Agentblazer Community Group @* Sales Cloud - Getting Started *@* Release Readiness Trailblazers *@* Sales Cloud - Best Practices *@* Salesforce Administrators *@* Service Cloud *
Hi, We're working on sending offline conversions from Sales Cloud to Google Ads. I've been tasked with researching best practice so I'm hoping someone out there has done this in a way that works well. Specifically, I'm wondering how you have gone about populating the GCLID in Salesforce and assigning it to Opportunities. 1. If someone clicks multiple ads do you retain multiple GCLIDs or overwrite the existing GCLID? 2. If a user clicks an ad and there is no immediate conversion, but a conversion occurs 6 weeks later from a non-Google campaign, do you assign the GCLID to the Opportunity or do you only assign to opportunities that result directly from a click? 3. Do you associate GCLIDs with specific campaign members or with contacts generally? I have my own thoughts on this but have been asked to research best practice, so any feedback as to how other businesses handle this would be much appreciated. FYI we intend to use opportunity created, opportunity stage changes to 'Sale Recorded' and opportunity stage changes to 'Sale Complete' as conversions. We use Sales Cloud (we don't have Account Engagement or Marketing Cloud). Thanks!
@* Sales Cloud - Best Practices * @* Sales Cloud - Getting Started *
Iβd keep the GCLID history tied to the lead/contact and carry the relevant one to the Opportunity. For multiple clicks, keeping the history can make attribution much easier later.
π Big shoutout to our incredible Forum Ambassador, @Manoj Nambirajan for an awesome deep dive on "Send Opportunity Notification for Specific Stage Movements"!π Check out the article here >> https://help.salesforce.com/s/articleView?id=005393369&type=1
π Found it helpful? Have thoughts to share?
Let us know by clicking the "Yes" or "No" button at the bottom of the articleβyour feedback helps us improve!> π Found it helpful?" style="display: block;" /> #Flow
Hi,
We are trying to figure out an option that would enable our sales users to send emails to their lists with a pre-built HTML email. Is it possible through sales engagement? How can we execute this?
Hey, you can do this with List Emails in Sales Engagement. Just select your list, choose the HTML template youβve already built, and send it out from there. Works pretty well for bulk sends to contacts or leads. Let me know if you run into any issues setting it up.
Hello,
Does anyone know if Salesforce offers a standard Meeting Minutes solution ?
thank you.
Jan
Short answer: there is no dedicated 'Meeting Minutes' object or feature in Salesforce, but you have a few native options depending on how formal you need it:
- Quick/manual: log the meeting as an Activity (Event) and put the minutes in the description, or attach an Enhanced Note to the related Account/Opportunity/Contact. That is the closest out-of-the-box way to keep minutes on the record.
- AI-generated (the modern route): Einstein Conversation Insights records and transcribes calls from Zoom, Teams or Google Meet and now produces generative call summaries - an editable Summary tab on the call record with key points, next steps and customer feedback. That is effectively auto-drafted minutes tied to the record.
- Formal template (attendees, agenda, decisions, action items as structured fields): not native - either a small custom Meeting object or an AppExchange app.
So nothing branded 'Meeting Minutes,' but Activities/Notes for manual and Einstein Conversation Insights for automatic cover most needs.
If this helps, please mark it as the Best Answer so it helps the next person - thanks π
I have inlucded the activity tab on the Case object. But the email action is visible even after adding the email action on the page layout. I have attached the screenshot for reference.
I don't face this issue on the Account object.
Help me to fix this issue.
@* Sales Cloud - Best Practices * @* Service Cloud * @* Sales Cloud - Best Practices *
#Service Cloud
Hey @Guru Prasad T not sure if you resolved this yet but the reason you're seeing this behavior is that the Case object is designed around Chatter feeds. Activities, updates, and related actions are handled through the feed architecture rather than through a separate composer tab. Looks like you need to use Chatter components to achieve the functionality you're looking for