Settings and activity
15 results found
-
13 votes
Matthew supported this idea ·
-
18 votes
Matthew supported this idea ·
-
4 votes
Matthew supported this idea ·
-
7 votes
Matthew supported this idea ·
-
6 votes
Matthew supported this idea ·
-
22 votes
Matthew supported this idea ·
-
7 votes
An error occurred while saving the comment Matthew supported this idea ·
-
2 votes
Matthew supported this idea ·
-
3 votes
Matthew supported this idea ·
-
9 votes
An error occurred while saving the comment Matthew commented
This could solve the problem with our external contacts list being combined with the company directory.
Additionally, each division (folder) should be selectively visible at various levels - Global, Site/Company, Group.Matthew supported this idea ·
-
6 votes
An error occurred while saving the comment Matthew commented
So important. This saves 8 to 10 steps in accessing company directory.
Matthew supported this idea ·
-
2 votes
Matthew shared this idea ·
-
23 votes
An error occurred while saving the comment Matthew commented
Use the External contacts - External ID as a speed bin (dialing shortcut). As long as the bin numbering does not overlap with the tenant's site/extension numbering scheme. Then all we need is a 'Speed Dial' button in a line appearance position so execution can be [Speed]#### and Send.
Matthew supported this idea ·
-
7 votes
An error occurred while saving the comment Matthew commented
Presently the limited extension can place a call on global park from which the call can be retrieved by another phone, however requires a dialing code on the final destination phone to retrieve the call. The Park Group buttons are simply an automated shortcut for this feature. So, the limited extension is not in fact limiting the function of global park it is only limiting the convenience of having the feature available on a single button.
Matthew supported this idea ·
-
20 votes
An error occurred while saving the comment Matthew commented
Currently the External Shared contacts is blended with the corporate directory. This causes great confusion when we upload our vendor's speed dial list to the external directory feature. Even if we mis-label the contact name such as z_vendor [companyName] to push them all do the bottom of the list this is very sloppy. The external contacts either need a separate list if displayed on the web/desktop app or not displayed at all.
Also, the external contacts list spreadsheet has a column for External ID. This seems like should be the speed bin number (shortcut to dial into the phone to outpulse the full contact's phone number) however doesn't seem to work or I haven't figured out how this function works in RS yet.Matthew supported this idea ·
An arbitrary tenant wide speed dial is critical. Other phone systems and platforms provide this feature.
This does not necessarily need to be tied to a specific device model or device function.
We need the ability to set up an arbitrary short code / speed dial bin that effectively translates to a 10 digit phone number. The short-code to phone number relationship should be configured/managed in Admin Portal. Short codes can be any length allowable by the system - I suggest 4 digits to prevent confusion with site-code logic.
Dialing the short code (with or without a *code prefix) from any phone should cause that phone to connect the full 10 digit phone number assigned to the code dialed. Effectively saving the users time/button presses and allowing for end users to memorize short codes instead of having to memorize a list of 10 digit phone numbers for frequently dialed destinations.