Hi Joe:
Thanks for your explanations. As the a2b architect, I am sure you know exactly how it can be implemented. You mentioned using the speed dial screen as-is but it may not be intuitive because the customer needs to know which local access number (DID) to point to the destination number.
If using the speed dial screen is the fastest way to implement then one additional field on that screen would be needed to hold the local access number just like the speed dial numbers (0-9). And from there user will know the local access numbers to dial and the can change it anytime they want.
Then the call processing would be as you explained as follows: 1. The customer calls in, 2. and in the dialplan you look up the callerID from the appropriate table, 3. then you look up the number (this is the dest.# pointed to the local access # user dialed) to dial from the speed dial table, then you send the call into A2Billing (no prompt). 4. (by me). If no matching local access number is in the speed dial table then prompt user to enter destination # as usual.
As I am writing this, I am thinking this will be great for users, as they will have both features for their convenience. (customers love this). In addition, it will help us compete with a lot of other services out there with this feature.
What do you think?
Thank you!
|