Settings and activity
3 results found
-
5 votes
An error occurred while saving the comment 
Pete
supported this idea
·
-
2 votes
An error occurred while saving the comment Pete
commented
I found a workaround for my Suzy/Susie problem. I don't know if it would help others, but I used Transfer on Context and put "Susie" in the context and directed it to Suzy's extension. IT WORKED!
An error occurred while saving the comment Pete
commented
This is a REALLY important to the functionality of the product. I completely agree with William's post is important and should be implemented urgently. I'd like to add another use case. We're a small company and have unique user names so people call and ask by first name. AIR appears to transcribe the voice making the request, and then search for user names that match. However, our user's name is "Suzy" and AIR translates that to "Susie" and is unable to find it. This is also an occasional issue with "Rachael" being spelled differently, apparently depending on the caller's pronunciation. Even "Peter" and "Pete" aren't handled well. While I'm not an AIR developer, my thought would be to add a nickname or alternate name table that would be searched first to reconcile the user name. This issue is critical to our continued use of AIR.
Pete
supported this idea
·
-
1 voteFuture Consideration · 0 comments · Developer Platform, APIs, & Integrations » Integrations: Other · Admin →Pete
shared this idea
·
I heartily endorse this request. I found another list of issues when trying to add from our external directory that I hope will also be considered:
1. The format for the phone numbers is too stringent. Adding +1 to a number is not as easy as it looks via Excel
2. The format for the phone number is too stringent. It should tolerate parens, dashes, dots, and spaces, 1 (262) 370-0597 should be accepted (I realize that foreign numbers could make this more difficult but there must be a way around this).
3. Special characters in Title and Company cause a failure…that should be allowed. Slashes aren’t allowed yet a title of Owner/President should be allowed.
4. It might be an option to allow duplicate phone numbers, especially where larger companies just use the company number as the business number, but with an extension, which has to be removed prior to attempted upload.
5. A person who owns multiple companies has a different company name but uses the same mobile number. These fail to load. You might consider allowing duplicate mobile numbers.
6. Company and mobile numbers that are the same aren’t allowed, but small companies do that.
7. Saving a file in CSV in Excel leaves a blank or end-of-file record that has to be removed by Notepad. But wait…Notepad has to save the file as .CSV instead of .TXT making it just harder to process. This takes a lot more IT knowledge than many administrators have.
I do understand the issue with duplicate numbers in recognizing an inbound call but dealing with it as an outbound call would seem to be easier to handle if searching for a name.
If you can solve the duplicate problem it should be optional to load duplicates.
Loading the bulk data should also allow loading with errors. In some cases, loading most of the people is worth something in the short term while trying to fix the errors later.