Calls place on hold report?

Status
Not open for further replies.

houston

Customer
Joined
Jul 21, 2009
Messages
66
Reaction score
2
I am demoing 3cx for a customer. The goal is fewer dropped calls, resulting in fewer lost sales, by using a call queue for customers calling in pickup orders.

While someone is in the queue, they're being told "you are number X". Cashiers are encouraged to alternate between face to face customers and calls by the ringing phones. Call queue statistics are accurate.

The cashiers are where they're running into a problem. They've realized that they can stop the annoying queue ringing by answering calls and immediately putting customers on hold.

Calls on hold prioritizes face to face customers over phone orders, screws up the queue statistics, breaks the "you are number X" messaging, and stops ringing the phones. Which means calls on hold get forgotten. Cashiers have been known to finish with the face to face customers and then walk off to do some other task, so quite literally forgotten.

They need a report that shows when calls are put on hold with the caller ID of the call, the extension, whether the caller hung up while on hold, and the start and end timestamps. Filtering by all fields should be possible. That'd let them check camera video to determine which cashier needs retraining or reassignment.

Soooo, how can I create such a report?

So far I like 3cx, but this is a pretty significant pain point across my customers industry. If there's no way (or very soon to be way) to get this info, I'm not sure 3cx will be a good fit for them.

Also, I don't think disabling the hold button or somehow having a phone ringing if someone is on hold solves the problem, the cashiers. They'd just lay the phone on the counter instead.
 
Hello @houston

Unfortunately there is no way to see when the call was placed on hold as calls that are put on hold count towards the talking time. Technically the call was answered and it is still active. Putting a call on hold does not show up in any report.
 
Each change of the call state requires a unique SIP command. I am very much not a programmer and only have passing acquaintance with SIP commands, but I am assuming 3cx keeps a log of the commands for troubleshooting and makes it visible to the admin. (I'm not going to be happy when I go to check later if it doesn't.)

I guess someone decided it's not worthwhile to parse the log for useful information, add it to the database the reports are pulled from, and allow for much greater report detail? Again, not a programmer, but I'm not seeing a technical obstacle here. If there's a concern about system load or some such, just make it an opt-in feature and provide a minimum system requirement for it's use. Can you share any of the reasoning behind the decision to not provide detailed logging?

I'm demoing the system for a customer that's a franchisee. The franchise has around 1,500 locations. All with nearly identical work flow and reporting needs. Hold "abuse" is a significant pain point to sell to.
 
Also, it would be useful to see calls on hold tagged with a different color. Blue perhaps.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,930
Messages
589,802
Members
164,803
Latest member
fcentral