Sam Naegle
Has anybody had problems with conference numbers not showing up as interactive links? Some of my users are able to see the numbers as links while others have to copy paste the numbers into the dial-er. Is this an issue with the users mobile device or xMatters form?
0
Comments
Please sign in to leave a comment.
The rendering of a link on a mobile phone is done by the phone itself. iPhones seems to do a nice job of it, but Androids struggle with providing a "pause" character for the dial string. The actual format of the message can be adjusted easily using the design tools if there is a known better format out there.
Do any of your users have a recommendation for what will work on their phone?
Conference number and three commas between the pass code works for most of my users. 1888XXXXXXX,,,XXXXXX This even works great on my droid but for some reason it just dose not translate to some users.
FWIW: I just tried sending that example via SMS to a Samsung Galaxy S5 and it only converted the 1888XXXXXXX into a clickable dial string. The commas and bridge number are left out. However it worked great for email.
If that is the format you want, you can very easily change your message template to support it. You can even create multiple dial strings to support each device. All you have to do is go into the Developer tab, select the Communication Plan, select the form, and then go to the Messages view to edit the message templates. Select the appropriate one for email, or SMS, make the changes you want, save the changes, and you are all set.
If you need help, our Support desk or your CSM will be happy to walk you through it.
One more follow up... I just noticed that the S5 does work with 1-866-123-1234x1234567 where the bridge has up to 7 numbers, but as soon as you go over 7 characters, the S5 stops linking it.
From memory we got around this on Samsung devices by prefixing the number with "tel:" - eg tel:1800007241,,<conf code>