Recherches récentes
Pas de recherche récente

Preveena Balasubramanian
Adhésion le 25 mars 2022
·
Dernière activité le 17 août 2023
Suivis
0
Abonnés
0
Activité totale
6
Votes
2
Abonnements
2
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Preveena Balasubramanian
Preveena Balasubramanian a ajouté un commentaire,
You can find this option in Messaging -> Authentication section
Afficher le commentaire · Publication le 17 août 2023 · Preveena Balasubramanian
0
Abonnés
1
vote
0
Commentaire
Preveena Balasubramanian a ajouté un commentaire,
Hello,
What works well today with the SLA feature?
SLA allows to have comprehensive conditions with different targets.
What limitations do you hit while using it?
The main limitation comes to one touch tickets where the status is changed from New to Solved, there is no SLA target activated. While in Ticket events we could see the SLA with no targets applied, the explore reports this as No SLA triggered.
What do you wish it would do differently for you? Why?
Enforce a ticket background update so that SLA target gets activated before the ticket is marked solved. When the agent submits the ticket as solved with SLA trigger conditions, ticket should have an auto update identifying the SLA and then mark as solved.
What is the impact on your business?
We have a majority of tickets falling under one touch resolution and has huge impact to our SLA metrics. Manual intervention is required to update the SLA status in our report.
Afficher le commentaire · Publication le 25 mars 2022 · Preveena Balasubramanian
0
Abonnés
0
Votes
0
Commentaire