# Telephone number recognition: smart phones

**URL:** <https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043>\
**Category:** Factual Questions\
**Created:** [April 29, 2013, 8:11pm UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043 "2013-04-29T20:11:00Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ellen\_Cherry](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ellen_cherry/32/3600_2.png) [@Ellen\_Cherry](https://boards.straightdope.com/u/Ellen_Cherry)\
**Post date:** [April 29, 2013, 8:11pm UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/1 "2013-04-29T20:11:00Z")

</div>

I have an iPhone and no experience with other smart phones. I need to know for an email newsletter and various other online communications for work if all smart phones are able to tell this is a phone number and call it if it appears in text:

(123) 321-4321

This works with my phone. Do any phones require a different format, such as 123-321-4321? Are they all smart enough to know a phone number when they encounter it, and permit you to dial right from where it appears?

Are there any industry standards for this and if so can someone point me to where I can read them?

Thanks!

---

<div class="post-metadata">

**Author:** ![DataX](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@DataX](https://boards.straightdope.com/u/DataX)\
**Post date:** [April 29, 2013, 8:28pm UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/2 "2013-04-29T20:28:42Z")

</div>

I’m not sure if they are all smart enough - here is one standard:

> **[RFC 3966: The tel URI for Telephone Numbers](https://datatracker.ietf.org/doc/html/rfc3966)**
>
> This document specifies the URI (Uniform Resource Identifier) scheme "tel". The "tel" URI describes resources identified by telephone numbers. This document obsoletes RFC 2806. \[STANDARDS-TRACK\]

Also - if you can use HTML - there is the “tel” anchor link - which probably will work in more cases.  
[http://www.simonbingham.me.uk/index.cfm/main/post/uuid/making-a-telephone-number-clickable-on-android-14](http://www.simonbingham.me.uk/index.cfm/main/post/uuid/making-a-telephone-number-clickable-on-android-14)

However - if you think about it from a programming standpoint - (NPA)NXX-XXXX will almost always be a telephone number - while I could see cases where NPA-NXX-XXXX might be a part number or something. So if you were going to err on the side of caution - I’d pick the first - but it probably doesn’t matter.

---

<div class="post-metadata">

**Author:** ![filmore](https://avatars.discourse-cdn.com/v4/letter/f/7993a0/32.png) [@filmore](https://boards.straightdope.com/u/filmore)\
**Post date:** [April 29, 2013, 8:49pm UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/3 "2013-04-29T20:49:59Z")

</div>

I would doubt if the phones are looking for an exact match to a standard. The phone numbers on pages are typed in by humans, and as such will show lots of variation. It’s not like the humans are required to follow any sort of written phone number standard. I may write it as 123.456.7890 but you write it as (123) 456-7890. It’s not like either of us are following a standard. As long as neither of us get too crazy with the format, we can recognize it.

As a computer programmer, I would think it’s much more likely that they are looking for the common pattern of groups numbers separated by certain delimiters. They may recognize these as phone numbers:

111.222.3333  
111-222-3333

but not this:

111a222b3333

I doubt they’re following any standard. Rather, the programmers know what most of the common phone number patterns look like and search for that.

As an related story, years ago I wrote a program to parse addresses from the on-line classifieds for garage sales. There is an actual standard for addresses used by the post office (geocoding), but that’s not necessarily how humans write their address. I would look for common patterns like “numbers blahblah [ave/rd/road/st/street]” and then convert it into the standard format. Then I would look up those addresses in the tax records to find the most expensive houses having garage sales. I got a lot of great stuff for next to nothing that way. Since these phones are parsing addresses written by humans, I would guess they look for common phone number patterns and then internally convert it to the standard format rather than only look for the standard format.

---

<div class="post-metadata">

**Author:** ![beowulff](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/beowulff/32/542_2.png) [@beowulff](https://boards.straightdope.com/u/beowulff)\
**Post date:** [April 29, 2013, 9:54pm UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/4 "2013-04-29T21:54:25Z")

</div>

I just tried a little test on my iPhone 4s.  
I sent an email with the following strings.  
The ones in bold were automatically turned into hyperlinked phone numbers, the other were not:  
\*\*(123) 456-7890  
123 456 7890  
123-456-7890  
\*\*123(456)7890  
123456(7890)  
\*\*1234567890  
\*\*123.4567890

---

<div class="post-metadata">

**Author:** ![filmore](https://avatars.discourse-cdn.com/v4/letter/f/7993a0/32.png) [@filmore](https://boards.straightdope.com/u/filmore)\
**Post date:** [April 29, 2013, 10:06pm UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/5 "2013-04-29T22:06:10Z")

</div>

There is no requirement that smartphones must recognize phone numbers. A phone may or may not recognize phone numbers in emails, texts and web pages. It’s completely up to the manufacturer. The nicer phones will do it, but the more basic ones may not have that feature.

---

<div class="post-metadata">

**Author:** ![Digital\_is\_the\_new\_Analog](https://avatars.discourse-cdn.com/v4/letter/d/a88e4f/32.png) [@Digital\_is\_the\_new\_Analog](https://boards.straightdope.com/u/Digital_is_the_new_Analog)\
**Post date:** [April 29, 2013, 11:03pm UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/6 "2013-04-29T23:03:05Z")

</div>

> [@beowulff](#):
>
> I just tried a little test on my iPhone 4s.  
> I sent an email with the following strings.  
> The ones in bold were automatically turned into hyperlinked phone numbers, the other were not:  
> \*\*(123) 456-7890  
> 123 456 7890  
> 123-456-7890  
> \*\*123(456)7890  
> 123456(7890)  
> \*\*1234567890  
> \*\*123.4567890

I would expect those four bolded ones to be properly parsed by most modern smartphones.

---

<div class="post-metadata">

**Author:** ![jasg](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jasg](https://boards.straightdope.com/u/jasg)\
**Post date:** [April 29, 2013, 11:17pm UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/7 "2013-04-29T23:17:47Z")

</div>

This can vary not just by smartphone type, but by the email or browser App in use when viewing a potential number.

I just tried the test Beowulff gave above on my iPhone and iPad. The built in mail App behaved as he notes, but the GMail App does not recognize any of the strings as phone numbers. Likewise, the Web interface in the default Safari browser did not recognize them.

---

<div class="post-metadata">

**Author:** ![SeaDragonTattoo](https://avatars.discourse-cdn.com/v4/letter/s/df705f/32.png) [@SeaDragonTattoo](https://boards.straightdope.com/u/SeaDragonTattoo)\
**Post date:** [April 30, 2013, 1:21am UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/8 "2013-04-30T01:21:57Z")

</div>

Oops, too big a correction, see my next post

---

<div class="post-metadata">

**Author:** ![SeaDragonTattoo](https://avatars.discourse-cdn.com/v4/letter/s/df705f/32.png) [@SeaDragonTattoo](https://boards.straightdope.com/u/SeaDragonTattoo)\
**Post date:** [April 30, 2013, 1:31am UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/9 "2013-04-30T01:31:32Z")

</div>

> [@beowulff](#):
>
> I just tried a little test on my iPhone 4s.  
> I sent an email with the following strings.  
> The ones in bold were automatically turned into hyperlinked phone numbers, the other were not:  
> \*\*(123) 456-7890  
> 123 456 7890  
> 123-456-7890  
> \*\*123(456)7890  
> 123456(7890)  
> \*\*1234567890  
> \*\*123.4567890

That’s really interesting! (Samsung Galaxy S2) My Gmail and Yahoo both linked the following in bold. Yahoo gave obvious blue hyperlinks, while Gmail did not, but if I tap on the numbers Gmail gave the call or text options for the same ones Yahoo did:

(123) **456-7890**  
123 456 7890  
**123-456-7890**  
123(456)7890  
123456(7890)  
**1234567890  
123.4567890**

I would think the ###-###-#### format would be a universal one to use. If a phone is going to do it, it will be with that one across the board.

---

<div class="post-metadata">

**Author:** ![Digital\_is\_the\_new\_Analog](https://avatars.discourse-cdn.com/v4/letter/d/a88e4f/32.png) [@Digital\_is\_the\_new\_Analog](https://boards.straightdope.com/u/Digital_is_the_new_Analog)\
**Post date:** [April 30, 2013, 2:05am UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/10 "2013-04-30T02:05:32Z")

</div>

…and my expectations, once again, have been dashed. I guess this is why I do low level code, and not UI work.

---

<div class="post-metadata">

**Author:** ![Heracles](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/heracles/32/487_2.png) [@Heracles](https://boards.straightdope.com/u/Heracles)\
**Post date:** [April 30, 2013, 3:02am UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/11 "2013-04-30T03:02:19Z")

</div>

Apple [won a lawsuit](http://articles.businessinsider.com/2011-12-19/tech/30533308_1_import-ban-patent-ruling-patent-claims) against HTC, a few years back, because this very feature was in Android. So some smartphones don’t have the feature because of this, methinks.

---

<div class="post-metadata">

**Author:** ![Absolute](https://avatars.discourse-cdn.com/v4/letter/a/b2d939/32.png) [@Absolute](https://boards.straightdope.com/u/Absolute)\
**Post date:** [April 30, 2013, 3:22am UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/12 "2013-04-30T03:22:19Z")

</div>

> [@jasg](#):
>
> This can vary not just by smartphone type, but by the email or browser App in use when viewing a potential number.
> 
> I just tried the test Beowulff gave above on my iPhone and iPad. The built in mail App behaved as he notes, but the GMail App does not recognize any of the strings as phone numbers. Likewise, the Web interface in the default Safari browser did not recognize them.

I am viewing this thread on safari on my iphone 5 / ios 6.1 and it recognizes the bolded entries as phone numbers.

---

<div class="post-metadata">

**Author:** ![Harmonix](https://avatars.discourse-cdn.com/v4/letter/h/3ec8ea/32.png) [@Harmonix](https://boards.straightdope.com/u/Harmonix)\
**Post date:** [April 30, 2013, 3:42am UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/13 "2013-04-30T03:42:06Z")

</div>

Android has an emulator for a PC.

> **[Lancer l'émulateur à partir de la ligne de commande  | ...](https://developer.android.com/studio/run/emulator-commandline?hl=fr)**
>
> Découvrez les fonctionnalités de ligne de commande que vous pouvez utiliser avec Android Emulator.

I’ve never installed it myself so I can’t help you there.

Why not ask your work to buy a phone for the purpose of seeing how they appear on mobiles? Android phones can be had for 99$ if you look hard enough.

---

<div class="post-metadata">

**Author:** ![Ellen\_Cherry](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ellen_cherry/32/3600_2.png) [@Ellen\_Cherry](https://boards.straightdope.com/u/Ellen_Cherry)\
**Post date:** [April 30, 2013, 1:35pm UTC](https://boards.straightdope.com/t/telephone-number-recognition-smart-phones/657043/14 "2013-04-30T13:35:26Z")

</div>

Thank you, everyone!

I wonder if this:

> [@](#):
>
> Also - if you can use HTML - there is the “tel” anchor link - which probably will work in more cases.  
> [http://www.simonbingham.me.uk/index](http://www.simonbingham.me.uk/index)…-on-android-14

as DataX suggests would solve all my problems. Although I am really sure they should get me a another phone!
