Friday, November 13, 2009; 1:10 AM
Here's how this works: Let's say you signed up for Google Voice sometime in the past. The main benefit of Google Voice is that it forwards calls to your other phones ¿ the whole "one number for life" thing. So you probably told Google Voice a few of your other phone numbers ¿ home, work, mobile, etc. And then perhaps you stopped using the service after testing it.
Now if you call my Google Voice number from any of those real phone numbers that you told Google about, the caller ID and archived information on Google Voice (missed and received calls, voicemails) says your Google Voice number, not the number you are calling from.
That creates confusion. If I have your mobile number stored in my phone, it doesn't recognize the Google Voice caller ID and I tend to ignore the call. Then I read the transcribed voicemail and realize it's someone I know. I check my address book and the number isn't right, though. I add the new number and maybe delete the old one, thinking you've changed phones. It's a mess.
Inbound text messages have the same problem. And if I return the text message and you don't have the feature turned on to your real mobile phone, you won't get them.
I get why Google is doing this. They want people who have Google Voice to use that number, and this is a helpful way of pushing the issue. It's free marketing, and there is a logic behind the "feature," too.
But just because someone gives me one of their phone numbers doesn't mean they want to give me their Google Voice number. Maybe they abandoned the service. Or maybe they just don't want me to have that number.
What if you sent me an email from your work account to my Gmail account, and Google automatically changed the from address to your Gmail account? This is a direct analogy to what's happening with Google Voice.
None of these exceptions apply here. Google needs to add an opt in for this feature, and do a better job of syncing these calls in my address book, or abandon the practice.