You will find below how the missed call reasons are defined in SmartFlows tool and the differences compared to the current one.
Event |
Current Behavior |
SmartFlow Behavior |
Is it new Behavior? |
---|---|---|---|
short_abandoned |
|
|
NO |
out_of_opening_hours |
|
|
YES |
no_available_agent |
You can easily add more users or teams to your call distribution to help. |
|
NO |
agents_did_not_answer |
|
|
NO |
abandoned_in_ivr |
|
|
YES |
abandoned_in_classic |
|
|
YES |
The hierarchy to set the missed reason is:
If the call pass through a ring to widget (or more) and the caller hang up or the call ends (arrive to flow ends) the behavior will be:
-
If it was ringed an agent (in at least one of the rings to) the missed call reason will be
agents_did_not_answer
-
If it was not ringed at least one agent (In any of the rings to) the missed call reason will be
no_available_agent
If the call do not pass through a ring to widget (or more) and the caller hang up or the call ends (arrive to flow ends) it will follow the next hierarchy:
-
If the call ends or the caller hangs up during the first 10 seconds the missed call reason will be
short_abandoned
-
If the caller hang up during the IVR message widget or during the IVR gather the miss reason will be
abandoned_in_ivr
-
If the caller hangs up or the call ends in the “At any other time” branch of a Time rule widget and the call duration is more than 10 seconds then the missed call reason will be
out_of_opening_hours
. If the call duration is less than 10 seconds, then the missed call reason will beshort_abandoned
-
For any other case the missed reason will be
abandoned_in_classic