Sometimes, a customer service rep (CSR) may service a person that is associated with multiple WhatIds (accounts, policies, opportunities, etc.) and when they create a task or log a call, they can only relate the task to one account, policy, opportunity, etc. There is no option to relate it to multiple things. Instead, they create the first log a call or task and relate it to the one account, policy, opportunity, etc. and then they clone the log a call/task and relate it to another account, policy, opportunity, etc. If there is another account, policy, opportunity, etc., they need to repeat the cloning step again.
What if, we can make this more efficient for the CSR?
What if, they can select the accounts, policies, opportunities, whatever they need to relate the task to on one screen and upon submit, it clones the tasks for each account, policy, opportunity, or whatever it is for them?
Let’s delight those CSRs and increase their overall productivity so they can move onto the next customer.
Learn this cool trick to bypass validation rules in your process or flow, just like you can with workflow rules.
This blog post was inspired by Yvonne Navas. Here are a few lessons learned from implementing this use case: Use an email alert with a Classic Email Template to send an email with a file attachment Use a record triggered after save/update flow to send the appropriate email Business Use Case: Addison Dogster is the system… Continue reading Send An Email with an Attachment When an Event is Created or Event Date Revised
Your company has a business model where multiple sales people representing different channels or product focuses, or an internal/external sales team, may interact with the same individual. There is a business need to track calls to the contact or events with the contact. These two use cases will be covered in a 2-part article series.… Continue reading Record the Last Event With A Contact
Customer Service Agents have to manage many cases and sometimes, even the best of them, may need a gentle reminder that a specific case may need a bit of love and attention. Enter automation… Here are a few lessons learned from implementing this use case: Create a formula to track case update threshold by business… Continue reading Send a Case Update Reminder Email When the Update Threshold Has Been Exceeded
Those flownatics who have used the OOTB file upload component know once the files are uploaded to the screen flow, that the files are not shown back to the user as a confirmation of the files uploaded. This can be achieved using OOTB flow by querying the documents, assigning the file title and extension to a text template adding it to a variable and then displaying that variable on a flow screen.
If you’ve created a time-dependent action on a workflow rule, a scheduled action in a process or a pause element in flow, now you can run part of your record-triggered after save/after update flow based on a dynamically schedule time using the new feature – scheduled paths – in Spring ’21! This new feature is… Continue reading Run a Segment of Your After Save/After Update Record Triggered Flow at a Dynamically Scheduled Time Using Scheduled Paths
One of the long awaited flow features is coming in Spring ’21 — the ability to use prior value in before or after update record triggered flows. This brings us closer to be migrating our processes into flows as Flow Builder is the end state declarative automation tool. In a record triggered flow, you can… Continue reading Reference Prior Value in a Before/After Update Record Triggered Flows
Update Opportunities for an Inactive Opp Owner Using Salesforce Flow – When an opportunity owner is deactivated, update the stage of the inactive user’s opportunities to “Pending Reassignment.” This was solutioned using Process Builder and Flow Builder.
This original blog post from 2018 was revised for a solution in Flow Builder.