Trigger next action in campaign to fire upon task completion
C
Carson Aune
We have lots of messages we want to send out to people automatically after missed calls in a nurture sequence. Right now, they just send out on a strict timeline (whether or not the call was completed). Can cause a lot of confusion when a lead gets a message about a missed call they never received in the first place!
HIGHLVL-I-1651
Log In
S
Sales & Marketing
Merged in a post:
Remove Manual Actions via Trigger
J
Jay Nisbett TEST
There is a huge compliance issue currently...When we are adding manual calls via a campaign or otherwise - it's adding them as of a certain date and assigning the user as of a certain date.What that means for all of is that your leads can be put into a manual call list, then opt out and be put on DND, but remain in that manual call list.You are power dialing leads that have opted out...It should either be automatic: if on DND, remove manual actions.ORThere should be a trigger to allow us to do this.
HIGHLVL-I-2556
B
Brian Del Terzo
This is an important request, and it connects to a larger issue with how Manual Actions behave inside the Power Dialer. Right now, if a contact opts out or is marked as DND, the call won’t go through, but the Manual Action still sits in the queue. The agent ends up seeing the task, attempting the call, getting an error, and then having to manually check the contact record to figure out why the task exists at all. That creates unnecessary work and introduces a real compliance risk.
Having the ability to automatically remove Manual Actions through a trigger would solve that problem immediately. It would ensure that anyone who opts out or is put on DND is fully cleared from the queue without relying on users to clean up tasks one by one.
This would also help resolve another pain point many of us are facing with sorting and filtering pending Manual Actions. Duplicate tasks can appear when contacts flow through multiple workflows or status changes, and the call queue becomes cluttered with tasks that shouldn’t be there. Being able to remove Manual Actions programmatically would keep the queue clean, make sorting more accurate, prevent duplication, and ensure the dialer only presents valid, actionable calls. https://ideas.gohighlevel.com/conversations/p/enable-re-ordering-of-manual-actions
Both issues point to the same need: stronger automated control over Manual Actions so the Power Dialer remains clean, compliant, and efficient.
D
David Hall
This is HUGE! This is one thing that separates some of the other software from HighLevel. The ability to have an automation built that will trigger another event after a task is marked as completed is crucial for many operations. From the sales cycle to customer service, this is a big thing that saves loads of time for agencies and clients.
Let me give some use case examples:
- Prospecting - Prospect in the pipeline goes through email sequences and does not schedule an appointment, task is created for user to call the prospect to follow up. When task is completed, the system would then immediately send an email or sms saying "Hey NAME, I just called about ____ a few minutes ago. Give me a call back when you get a chance." - TIME SAVER
- Prospecting - Prospect fills out a form requesting information. Because the information needs to be tailored to the prospect, a task is created to email information. Task completed...SMS gets sent out letting the prospect know to check their email. - TIME SAVER
- Customer Service - Client schedules appointment for annual account review. Task is created telling user that appointment has been set and directs user to prepare any paperwork/reports necessary for the meeting. When task is completed, email goes out to the client letting them know that everything has been completed/prepared and offers a form for the client to be able to offer additional discussion topics. - Keeps things from falling through the cracks, but also does not set client expectation until user has completed their part.
- Customer Service/Workflow Management - This is something we use ALL THE TIME in another software... When we onboard a new client, we assign workflows to the client. For example, content development.
It works similar to: Client is tagged with content development tag which adds them to automation. Email is sent to client requesting specific information. Task is created for user that is a "make sure you get the requested info" task. Once they have the info, they mark the task as complete. A new task is generated directing them to start keyword research on the content. Once that is completed, an email update is automatically sent to the client letting them know what has been done. Then a content research task populates for the user. Once that is complete, the client is emailed. Writing task. Client emailed. Conditional logic: If the user is supposed to upload the content, then a task is created to do so. Client notified. If the client is loading their own content, Send to client task. Must be completed manually. Then process repeats based on the schedule assigned to the user.
This has allowed us to build out complete project management automations with client interactions automated all throughout that saves time for everyone.
M
Mariah Guyton
THIS WOULD BE SO HELPFUL!! We get this request on a daily basis