Nathan Cassella
-
Activité totale53
-
Dernière activité
-
Membre depuis
-
Abonné à0 utilisateur
-
Abonnés0 utilisateur
-
Votes15
-
Abonnements18
Commentaires
Activité récente par Nathan Cassella-
We've been experiencing the same issue that many users have brought up over the last month. All last year when I was my team was working on cleaning up our Guide; we didn't see a captcha once, now ...
-
Is there any movement on increasing attachment size? Our customers in specific segments need process documentation specific to them, and like Miguel those documents can get rather large. It wou...
-
I'm a little confused by this. It seems you are tailoring this routing for specific tags related to specific customers, which isn't practical for many other customers. What I need to understand is ...
-
Barry Neary chat traffic and having messaging enabled are two different things. Our chosen bot (ADA) requires code to be embedded into our guide header; to avoid conflicts, all other bots need to b...
-
So this is a joke right? If I decide not to use your messaging platform and work with one of your preferred partner such as Ada using their chatbot I can't benefit from the omnichannel routing? S...
-
This is basic functionality. There's no reason this should be pushed back.
-
CJ Johnson I agree with you; my main concern is that any dataset that reflects Tickets Created or Solved needs to use the same calculation, which is not the case. So if I am being told to use the D...
-
Eugene Orman I appreciate you clearing this up. I have a few suggestions going forward: 1. Use the same logic across all datasets when defining Tickets Created and Tickets Solved: Those numbers are...
-
Does no one see this as a flaw with the software that says near real-time reporting?
-
Lou, The role solution doesn't meet the requirements. In roles, you can limit options but can't wholly limit ticket interaction. The OEM Partner isn't supporting the products with the customer; the...