Nope, not the correct place. It is in Colorado.I asked Google now to call Aero Works in Arizona and it brought up a place in Queen Creek , AZ near Phoenix and was loading it up to call til i stopped it. Is that the correct place? I dont know what town your in so i just said Arizona.
But that illustrates half the problem I have with only having Google Now for even local searches: it will often revert to that kind of search. All I really want to do is call a contact in my address book. Google Now rarely gets that right for me if I use voice. It often does a google search instead.
Worse, it is inconsistant between voice and text search. If I say just "aero" it will only do a google search for aero. The contact "Aero-Works" is not listed to call--unless it happens to be in the list of search results from the web.
However, if I call up Google Now from scratch and instead type "aero" then Google Now will bring up Aero-Works in the list of contacts it displays. But, even more confusing, if I type "aero" after first using voice to search, it also simply does a google search and will not display my contact Aero-Works. wtf? Google DID start as a search company, right? If so why the heck is this so screwy?
I should note that Siri would also not dial for me when I said "Aero-works" because the hyphen was not recognized (duh). However, I am able to correct what Siri heard, add the hyphen, and have it try again. Call is made. If I correct Google now so that it says "call Aero-Works" it only does another google search. Ugh.
This would not be a big deal but for the phone app. For the love of God it will not find Aero-Works no matter what I type. Why the heck is that? What exactly is so "special" about that contact, and many many others, that causes it to be skipped--most of the time--when I search for it in the phone app? The iOS phone app will even search through the Notes field for a contact when searching.
It's becoming a song-and-dance just to make a phone call.
Michael