IVR Advanced Settings – Call Outcome Handling
T
Tayla Cameron
For IVRs, it would be extremely helpful if the Advanced Settings allowed us to define what happens when a call is unanswered, declined, busy, or fails, directly within the Connect Call action.
Right now, we have to use an IF condition after every Connect Call step to handle these outcomes, which makes workflows unnecessarily long and complicated—especially in more complex call flows.
Example issue:
Without the IF step, if a user declines a call, the call ends, but then immediately rings the user back. This creates a poor user experience and unnecessary confusion.
If we could configure the call outcomes (e.g., “If unanswered, send to voicemail” or “If declined, move to X step/branch”) directly within the Connect Call settings, it would greatly simplify IVR workflows.
Log In
E
Eddy CEO WhatSnap.ai - Connect YOUR phone to GHL
The callback loop issue is the worst part. Client gets confused when they decline and it immediately rings again. We've built some pretty ugly workflows just to prevent that behavior.
E
Eddy CEO WhatSnap.ai - Connect YOUR phone to GHL
The IF condition spam after every Connect Call is ridiculous. Our workflows look like spaghetti just to handle basic call outcomes that should be built into the action itself.
C
Cynthia Giles*
As a daily user of this and not just a SAAS reseller, it is exceptionally annoying. Please fix.