Posted by AbleComm on October 7, 2009, 3:03 pm
One last thing which is not an issue to me but which I do find a bit interesting, and this is something for the PP billing dept, I am not quite sure how they were able to make it work in spite of this, but there is a complete mismatch with the currently listed billing address for my account and the billing address for the credit card on file. Moreover, the name in the billing address and the name on the credit card on file don’t even match. In this case, I am glad the billing dept was able to process it through in spite of these things. Although, it does concern me a bit that VISA did so. I’ll update them before anything else needs to be done in that regard.
At any rate, if you have any answers for solving the ringer problem that would be a nice first step. The CID thing is probably next on my list. The time display thing is merely an annoyance. Thanks!
P.S. One final thing of note which you might like to know, I am using Google Voice as a ‘front-end’ for ALL of my incoming calls. It doesn’t matter which line or which number the call comes in on. ALL of my phone numbers, with the exception of my PP #, point to a Google Voice number, which in turn then sends it to my real incoming number, which is my PP #. The ONLY people who know my PP # are PP & me. (Thank you for keeping it that way.)
The only numbers I give people are my GV #, a Toll-Free number which is being ported over to PP, and another number which I will soon be porting over to PP as a ‘virtual #’. (I have had both of those numbers for the past decade. Literally thousands of people have them, and I want them to have them.) Both the Toll-free # and the soon to be ‘virtual #’ point to the GV #, the GV # in turn points to my PP #. The same is true of my other VoIP #.
Just FYI, there are multiple reasons I am doing this, the first of which is that I have had the GV # for a few months now (since before I knew of PP), and I was not sure that the PP # would work in my geography – the only broadband option is fixed wireless (yeck!), the GV virtual # is free, and more importantly its call screening and call filtering capabilities are simply outstanding and unlimited. The ‘all-you-can-use’ free LD doesn’t hurt either. The ‘on-the-fly’ call recording capability is nice too. The fact that I can point several GV virtual numbers, from several ‘rate centers’, at the primary GV virtual # which will then perform all of the dirty work is really attractive as well.
I am also VERY KEEN to see just how well they can integrate it with their other functionalities, and if they can be the ones to finally reach the Holy Grail of true fully enabled, collaborative integration. IF they can turn the base functionality of the GV / GW platform into a quasi combination of ‘Office/Outlook’ (or better still ‘Notes’), ‘Share Point’ and ‘Salesforce.com’ all of which is then multi-channel communications enabled and integrated, they will then be well on their way to doing so. It will also not be as if they have a shortage of DB/storage capacity behind it. Forger Tablet PCs and iPhones, personally I want THIS. I’ll take smart data over a smartphone any day of the week.
In the near future, as in like later this week, I will also be setting up a second GV # which will route some incoming calls. This is simply to allow me to separate things into two different classes of incoming calls. Each class of which I can then track and store as separate data objects in separate stores.
Unfortunately, none of the Google interfaces yet has a robust enough functionality to manage a large volume of different data classes with multiple sub-classes without things becoming a bit of a mess. But I digress.
No, using GV as the front-end is NOT the source of the problems above, I have them regardless of whether or not I route the calls through the GV screen. Yes, I have tried things both ways. I just thought you might find this interesting and possibly useful, even if this message is now a novelette. J
Much appreciate anything you can offer in the way of assistance. Thanks!
Responses: