We've long had a problem with A2Billing where a customer will make an outbound phone call, and the remote end is busy. A2Billing's behaviour is to just drop the call, without any explanation for the customer.
Maybe this was an oversight from the fact that nearly everyone has call waiting or voicemail these days, but the fact of the matter is that it needs to inform the customer that the party they are calling is busy, rather than just dropping the call. Every time this happens, the customer complains that our long distance is broken, when it's not.
|