Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Jeremy Mifsud
Beigetreten 16. Okt. 2021
·
Letzte Aktivität 27. Sept. 2024
Folge ich
0
Follower
0
Gesamtaktivitäten
62
Stimmen
20
Abonnements
20
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Jeremy Mifsud
Jeremy Mifsud hat einen Kommentar hinterlassen
After contacting support, it looks like tickets that are deleted or marked as spam are also being counted as automated resolutions?
The support team is unable to clearly tell us where our usage is being used. The web-widget bot stores no contextual data and no report/metrics for the amount used by 'deleted tickets', which in my opinion, should not be charged in the first place.
As others may have pointed out, automated resolution after 72 hours is too-harsh, e.g. we don't operate on weekends. That forces us to give a response in 1 business day, and that is assuming there aren't bank holidays before/after weekend.
Kommentar anzeigen · Gepostet 27. Sept. 2024 · Jeremy Mifsud
0
Follower
0
Stimmen
0
Kommentare
Jeremy Mifsud hat einen Kommentar hinterlassen
Currently, I'm using the Classic Web Widget. There's no information to see where my automated resolutions are coming from to even see if this is worth. In effect, you are charging us $2 for our users to search something through our Help Centre through the web widget.
Kommentar anzeigen · Gepostet 27. Mai 2024 · Jeremy Mifsud
0
Follower
2
Stimmen
0
Kommentare
Jeremy Mifsud hat einen Kommentar hinterlassen
Thanks Scott for the update! Will be looking forward to these enhancements!
Kommentar anzeigen · Gepostet 22. Dez. 2023 · Jeremy Mifsud
0
Follower
1
Stimme
0
Kommentare
Jeremy Mifsud hat einen Kommentar hinterlassen
Hi Chandra, Oh that's interesting?
So to confirm, if a ticket goes to -5 minutes (for example), and an internal note update is done to remove SLA, then a public reply, will no longer constitute as a breach?
Kommentar anzeigen · Gepostet 18. Dez. 2023 · Jeremy Mifsud
0
Follower
0
Stimmen
0
Kommentare
Jeremy Mifsud hat einen Kommentar hinterlassen
2023 is almost over, and this functionality "planned for H1 2023" has received no further updates.
It's really as simple as adding a Next Reply Time SLA that does not trigger when the ticket is either "pending" or "on-hold". Would love an update on this
Kommentar anzeigen · Gepostet 17. Dez. 2023 · Jeremy Mifsud
0
Follower
1
Stimme
0
Kommentare
Jeremy Mifsud hat einen Kommentar hinterlassen
I have tried this however this still creates on difficulty:
If we set something to on-hold and "pause", if an end-user follows-up, the Next Reply is due in 0 minutes and that is not feasible. The SLA still breaches.
Kommentar anzeigen · Gepostet 17. Dez. 2023 · Jeremy Mifsud
0
Follower
0
Stimmen
0
Kommentare
Jeremy Mifsud hat einen Kommentar hinterlassen
I understand that the ability to create users is intentionally restricted, however this seems like a poor design.
My agents can, from their email e.g. agent@company.com send an email to a new client and cc support@company.com, and the user will be automatically created.
Agents can also access and create tickets to users created outside their groups (and in other brands).
If Zendesk can explain a practical reason why these are limited, I would appreciate it. It feels like a ploy for Zendesk to get more teams to upgrade to Enterprise, which is not feasible for an essential feature that should be included in all plans.
Kommentar anzeigen · Gepostet 19. Aug. 2023 · Jeremy Mifsud
0
Follower
0
Stimmen
0
Kommentare
Jeremy Mifsud hat einen Kommentar hinterlassen
Thanks Paolo.
I will have to use a single bot then; will need to figure out how to use conditional statements so that some intents function differently based on the user's country (product).
Kommentar anzeigen · Gepostet 16. Aug. 2023 · Jeremy Mifsud
0
Follower
0
Stimmen
0
Kommentare
Jeremy Mifsud hat einen Post erstellt
I want to switch from live chat to messaging and use conversational bots, but struggling with some information on how to set things up (even after spending hours reading articles).
I see that I can set up multiple conversational bots, however can find 0 information about how to trigger which bot and where.
For example, would I be able to set so that one bot is used on our website, and a different bot to be used in our Help Centre? Or two different bots whether someone is logged in (in-app) or not logged in (e.g. on pricing page)?
Any information is appreciated!
Gepostet 14. Aug. 2023 · Jeremy Mifsud
0
Follower
2
Stimmen
2
Kommentare
Jeremy Mifsud hat einen Kommentar hinterlassen
If I understand correctly, re-assignment of messages it not available for Growth plans?
E.g. if an Agent has 2 messages and disconnects, the message will not be re-assigned? Or can they still be re-assigned manually / through custom triggers?
Kommentar anzeigen · Gepostet 14. Aug. 2023 · Jeremy Mifsud
0
Follower
0
Stimmen
0
Kommentare