MS CRM 2013 introduced the new type of Phone Number for single line text fields adding very usefull functionallity for formatting phone numbers and handling phonecall activities.
However the handlers for the Phone Number hyperlink are limited to Lync (lync://) and Skype (skype://) making it impossible to use CTI registered to the generic callto:// (or phone://) protocol handler.
Please add a system configuration option to use a generic CTI protcol handler besides Lync and Skype or provide a workaround other than misusing one of the two available protocol handlers; i.e. using a GPO to register the CTI implementation to handle lync:// or skype:// hyperlinks.
Comments
Thank you for this feedback! I've added this product suggestion to an upcoming investment in CRM communications. Thank you for providing feedback and helping to improve Dynamics CRM. Just a hint, for the time being by selecting Lync from the list of Communication Providers in the System Settings, CRM will actually use the tel: protocol which will simply use your system's default application for the tel: protocol. This will most likely change in a future release as we build out our communication integration capabilities, but for now you can use this workaround.
Category: Microsoft Office Integration
Thank you for this feedback! I've added this product suggestion to an upcoming investment in CRM communications. Thank you for providing feedback and helping to improve Dynamics CRM. Just a hint, for the time being by selecting Lync from the list of Communication Providers in the System Settings, CRM will actually use the tel: protocol which will simply use your system's default application for the tel: protocol. This will most likely change in a future release as we build out our communication integration capabilities, but for now you can use this workaround.
Category: Microsoft Office Integration
Administrator
Thank you for submitting your idea to our ideas portal. We appreciate your contribution and the time you took to share it with us. We have shipped many enhancements since this idea was posted and it is likely that it has been resolved. If not, kindly reopen. Thank you again for your continued support.