Feb 08 2017 11:09 AM
I am sure this is on the roadmap, but we're testing call queues and the callerID that an agent receives in a long GUID string rather than the original callerID.
Oct 06 2017 10:20 AM
Ahem,
Soon has been and gone Mohamad.
We really need some feedback - getting +1 cross at skype every phone call I pickup. (+2 when its someone I don't want to speak to).
It's been a YEAR of +1/2's with no feedback.
Add the amount of team wastage picking up a call, talking through with customer and handing back to the appropriate person. This is costing us.
We deserve better and frankly its only that I'm such a nice guy I haven't come a knocking with pitch forks - I'm sure I can get a group togethor at this stage.
Can you please spend time Monday finding out some up to date information for us, be honest about whats happening, what technical roadblocks are in the way, etc.
Not knowing is the killer. Makes me feel a little unloved and definetely regretting the decision to move on to your platform.
Rant over ... I'm off to put my chill music playlist on via groove.
Oct 25 2017 01:24 AM
Mohamad, seriously - are still working on skype for business online especially on the call queues features, or should we just change to another active service like pstn calling from telekom?
You told us 8 months ago this feature is fixed.
We cannot work without any feature which allows us to let ring multiple phones for the service number and without seeing the caller id (even no caller id would be better than this stupid hashs / guids). Team calling, which is setup from the SFB client, is also no solution for this.
Please provide us at least some new infos about that. thank you.
Oct 25 2017 06:31 AM - edited Oct 25 2017 06:32 AM
A private message from Carlos Farrica:
"Right now the only information avalilable is that it was anticipate until the end of civil year but dont have any precision on time.
Now i am trying to have it on RoadMap."
We'll see what comes of it.
Oct 31 2017 03:43 PM
Dare I say this has just been fixed!? We have been pushing this hard with MS the last couple of days and just tested it successfully!
Oct 31 2017 09:21 PM
Earlier today, we started seeing the Caller ID on all incoming queue calls. Unfortunately, the name of the queue no longer displays. The long GUID number is still displaying. For our company, employees are assigned to multiple call queues, and we need to see which queue the call is being routed from. The ideal solution would be to show the Caller ID as it does as of this morning, and to replace the GUID number with the name of the queue.
Nov 01 2017 08:48 AM
WOW - I'm getting the caller id correctly too. (with long queue name but we cannot have everything!).
Happy Wednesday 1st November 2017 everyone.
Nov 01 2017 08:50 AM
Long queue guid was also solved if you follow the procedure here:
Nov 01 2017 09:05 AM
Nov 01 2017 09:05 AM
Breathes sigh of relief Now I can let my superiors know that that it's worth keeping this.
Nov 01 2017 09:07 AM
Nov 01 2017 09:15 AM
Nov 01 2017 09:18 AM
Nov 02 2017 06:33 AM
Nov 02 2017 06:38 AM
We don't seem to be able to get the queue name to appear.
ITs good that we now get the caller number but under it we still have the GUID.
In the SfB Adim centre the queue names have an active directory error against them.
I have edited them and saved them but the AD error is still there!!
Any ideas??
Regards
James Lupton
Nov 02 2017 06:51 AM
WE do not have an on-premises system just the online version!!
Nov 02 2017 06:52 AM
WE do not have an on-premises system just the online version. So not sure where we should powershell from or too!!
Nov 02 2017 06:54 AM - edited Nov 02 2017 06:54 AM
Call support or try recreating it from scratch.
Nov 02 2017 06:54 AM