![]() Slack automations can do so much more than ping a channel when something happens in Salesforce. What RevOps Needs from Slack Automation (and the Problem with Single-Purpose Slackbots □) Notify the sales team or sales manager when deals are pushed.Alert Customer Success and Account Execs of upcoming contract renewals.Share learnings from every Closed-Lost Opportunity with the whole team.Drive process adherence for desired sales methodologies (MEDDIC, BANT, etc.).Ring a digital gong for reps and celebrate won deals with the entire team.Notify sales leadership on the status of the biggest deals in the pipeline.Alert sales managers if opportunities have no activity within 14 days.Nudge reps to update the status of their opportunities with expired close dates.Alert your sales team when their opportunities have no activity for 10 days.Remind reps to update next steps for every opportunity.Instead, here are 10 Slack Automations RevOps teams love because Revenue teams actually use them: The result: Complexity is added to the tech stack with a tool whose only job is solving the wrong problem, while creating “alert fatigue” for reps. These Slack automations are often powered by expensive single-purpose Slackbots that add more noise than signal for reps, aren’t actionable, and don’t address the root of the problem: Reps simply don’t enjoy working directly in Salesforce or Slack. ![]() To solve this problem, RevOps teams have started using Slack-a collaboration tool that’s become a staple of the modern sales tech stack-to enforce workflows, share time-sensitive info, and corral scattered pieces of pipeline data back into Salesforce with automated Slack notifications. In reality, much of the work still happens outside Salesforce, across fragmented tools, spreadsheets, docs, and even notebooks as reps hack together their own workspace to work faster and easier than they can in Salesforce alone. Keep the only continue if in place, otherwise you’ll stop working whenever someone else stops a timer.In theory, Salesforce should be where the entire Revenue team works in lockstep to maintain the CRM as the source of truth. Same again really, set up all the same except trigger on the timer stopped event and leave the slack status empty, this unsets your status. Pop over to Basecamp (or whatever you use, etc, etc) Next up we need to make sure we’re setting our own status, rather than claiming credit for someone else’s work ![]() Leave the project section blank if you want it to work for everything! If you do figure out a way to do this free, please do blog about it and send me the link - I’ll give you some shoutouts here!Ĭhoose Everhour as the starting trigger, with a trigger event of a timer starting No I’ve not figured out a decent way to make it work without the multi-step zaps. Get your employer to pay for it or something. In this you’ll need a paid Zapier account. If you’re a smart cookie you’ll only need this screenshot to set it all up. You use whatever you’re using, the key point is that you need to be able to start and stop timers that includes the title of the task you’re working on. This one I’m not going to be so much help with. Time tracker integration (Everhour and Basecamp in my case) or Asana, or Jira, or something else that integrates with the time tracker you picked or Harvest, or Toggl, or some form of time tracking that integrates with The way I worked around this was to tie in my Slack status to display what I was doing. Not in the micro-manage screenshot every 5 minutes sense but a general gist. ![]() One of the first problems we discovered with this however was that it wasn’t really possible to see what I am working on. I recently went remote, work from home, the whole shebang. Actually that’s the only reason to do it. Why would you want to do that? Well for one thing it stops people asking what you’re up to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |