# \[DONE\] Phone number field/extension **URL:** \ **Category:** Ideas & Features\ **Tags:** flexible-domain\ **Created:** [December 2, 2019, 3:54am UTC](https://community.fibery.io/t/done-phone-number-field-extension/439 "2019-12-02T03:54:33Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\ **Post date:** [December 2, 2019, 3:54am UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/1 "2019-12-02T03:54:33Z")
I am building up a contact list app that I can then link to my meeting notes and action items. It would be great if we could have fields designed for phone numbers that could format and validate the content. It would be great if they could also trigger call behaviour on smartphones. The email field seems to provide validation but there doesn’t seem to be a way of triggering the default mail application to compose a new message. That would be a great addition as well. Apologies for inundating the community with (half-baked) requests! ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [December 2, 2019, 7:47am UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/2 "2019-12-02T07:47:39Z")
@cannibalflea This will be implemented in future, we are definitely going to add all possible fields into domain ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [July 18, 2020, 12:06am UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/3 "2020-07-18T00:06:41Z")
Any hope of this in Q3 this year? I think that it would be easier to move some of my enterprise clients to Fibery if I can build a robust CRM here. ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [July 18, 2020, 6:58am UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/4 "2020-07-18T06:58:09Z")
Hey @helloitse I really second the sentiment about using Fibery for a CRM. The capability is here, we have the API and Vizidrop as great supplements too - for import of data and analysis, respectively, that the other nocode stuff can’t duplicate. Definitely the phone # data type would be key though to make this work! ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [August 26, 2020, 10:23pm UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/5 "2020-08-26T22:23:54Z")
I regularly check the Changelog posts for any word of this feature. I’m worried though that Airtable will launch an official solution for syncing bases before it exists. This could be an easy win for the Fibery team. ---
**Author:** ![Nathalie\_Collins](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nathalie_collins/32/446_2.png) [@Nathalie\_Collins](https://community.fibery.io/u/Nathalie_Collins)\ **Post date:** [September 2, 2020, 11:34am UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/6 "2020-09-02T11:34:27Z")
> [@helloitse](#): > > Airtable will launch an official solution for syncing bases 🤣 I got a good chuckle out of this. ---
**Author:** ![Nathalie\_Collins](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nathalie_collins/32/446_2.png) [@Nathalie\_Collins](https://community.fibery.io/u/Nathalie_Collins)\ **Post date:** [September 2, 2020, 11:36am UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/7 "2020-09-02T11:36:21Z")
+1 upvote from me. ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [September 14, 2020, 7:27pm UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/8 "2020-09-14T19:27:58Z")
> [@Nathalie\_Collins](#): > > 🤣 I got a good chuckle out of this. Oddly enough, it’s here: See Synced tables > **[Airtable | Everyone's app platform](https://www.airtable.com/whatsnew)** > > Airtable is a low-code platform for building collaborative apps. Customize your workflow, collaborate, and achieve ambitious outcomes. Get started for free. ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [June 25, 2021, 10:28pm UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/9 "2021-06-25T22:28:49Z")
I am glad to see this: > [@CHANGELOG: June 24 / Group permissions (beta), Currency formatting, World app](https://community.fibery.io/t/changelog-june-24-group-permissions-beta-currency-formatting-world-app/1718/1): > > ## Money/Currency formatting for Number field > > Now you can format any Number field to display Money. For example, here we change an existing Number field to Money formatting. But I more readily need this request, so trying to bump again. @Team Fibery, any update? I am wondering how hard an implementation this would be? One huge benefit is my computer recognizes the phone # format so I can click to call contacts once this is implemented. Otherwise I have to use a text field and the computer doesn’t auto link that in the least. @helloitse good to see you here: > [@Hubspot Integration \[DONE\]](https://community.fibery.io/t/hubspot-integration/1292/8): > > I’m looking forward to a basic integration with Google Contacts and Calendar and eventually Gmail. The google contacts integration may be a fun one to dev myself if the open up the apps platform to third party developers. That said, is the ask to prioritize and Hubspot integration or native alternatives? I feel lost reading this thread lol Would be grateful if you could pop back over here and give this another bump, too! As well as possibly @JMaynier as you have shown an lot of interest in CRM use in Fibery! I believe you too @colman? Thanks! ---
**Author:** ![colman](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@colman](https://community.fibery.io/u/colman)\ **Post date:** [June 26, 2021, 10:58pm UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/10 "2021-06-26T22:58:43Z")
I have survived with just text fields so far, but I don’t have any exciting workflows based on phone numbers just yet - mostly email. I think it would be great and potentially not a huge lift (well, of course everything comes with an opportunity cost), although it’s not currently a huge pain point on my end ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 25, 2021, 12:05pm UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/11 "2021-10-25T12:05:08Z")
In development ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [November 10, 2021, 1:24pm UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/12 "2021-11-10T13:24:20Z")
Implemented Nov 10 2021 > [@CHANGELOG: Nov 10 / New Terms (App → Space, Type → Database), New Space Editor, Actions in Headers in Table View, Phone field](https://community.fibery.io/t/changelog-nov-10-new-terms-app-space-type-database-new-space-editor-table-view-actions-in-headers-delete-hide-edit-phone-field/2202): > > This releases transforms Fibery getting started experience and changes App (Space) creation process. sweat_smile New Terms (App → Space, Type → Database) After the [dense and deep discussion around new Fibery terms](https://community.fibery.io/t/in-dev-new-apps-creation-flow-new-getting-started-flow-new-terms/2148/), we decided to stick with this: App → Space Type → Database Space was a natural choice, but Type/Database/Table was not. We’ve decided to replace abstract Type term to a more concrete Database term. This decision still has some drawbacks, but we hope… ---
**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\ **Post date:** [November 11, 2021, 11:15pm UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/13 "2021-11-11T23:15:40Z")
@mdubakov and the team thank you for implementing this 😁 I had two questions: **1. Validation** > [@CHANGELOG: Nov 10 / New Terms (App → Space, Type → Database), New Space Editor, Actions in Headers in Table View, Phone field](https://community.fibery.io/t/changelog-nov-10-new-terms-app-space-type-database-new-space-editor-actions-in-headers-in-table-view-phone-field/2202/1): > > Note that this field has no validation, so you can put anything you want here Is validation going to be on the list of future improvements for this type or was this a deliberate choice? I saw in various places that validation is generally something that the team will be working on, but thought I should ask in regards to this specifically. I imagine validation is going to be quite helpful if/when we are also able to have external facing form-views (contacts, sales, CRM, etc.) **2. Field Conversion** Is there a process for converting existing text field to phone field? I’ve used a button to populate a new phone field with previous text data, but as new field types become available, it is really helpful to be able to just convert types. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [November 12, 2021, 8:02am UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/14 "2021-11-12T08:02:12Z")
We are not going to add validation, since phone numbers are diverse and it is quite hard to have all cases covered. Unfortunately field conversion is quite hard to implement and we are not going to do it in the next few months. So the best workaround so far is to create a new field and copy values from the old field in a table view or write an automatic rule that executes on schedule and it will just copy values from one field to another ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [December 19, 2021, 6:29am UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/15 "2021-12-19T06:29:34Z")
---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [December 19, 2021, 6:29am UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/16 "2021-12-19T06:29:37Z")