Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

mfg
Beigetreten 16. Okt. 2021
·
Letzte Aktivität 18. Feb. 2025
Folge ich
0
Follower
1
Gesamtaktivitäten
731
Stimmen
241
Abonnements
223
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von mfg
mfg hat einen Kommentar hinterlassen
Adding a multiple template feature would be helpful and significantly reduce the complexity of accomplishing this. Alternatively, the complexity of this may be less than it seems. Is it possible to get a recipe for accomplishing this?
Kommentar anzeigen · Gepostet 18. Feb. 2025 · mfg
0
Follower
0
Stimmen
0
Kommentare
mfg hat einen Post erstellt
Experimenting with the new email error feature via API and curious how far the data goes back. I'm using the api/v2/email_notifications.json?filter[ticket_id]=623 end point.
Since this is a new feature, how far back to email error history go? I assume it goes all the way back for each ticket but would like to verify any constraints on reporting.
Bearbeitet 13. Feb. 2025 · mfg
0
Follower
0
Stimmen
0
Kommentare
mfg hat einen Post erstellt
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)
Add updating skills as a condition for triggers
What problem do you see this solving? (1-2 sentences)
We need to generate end user use case specific notifications when a ticket's skills are updated.
When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)
We currently make minimal use of skills-based routing due to this issue.
Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)
Adding skills via a separate trigger based on a different condition.
What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)
Better support for implementing skills-based routing including but not limited to exposing skills as conditions for triggers
Gepostet 11. Feb. 2025 · mfg
2
Follower
2
Stimmen
1
Kommentar
mfg hat einen Post erstellt
I have encountered this across multiple machines, multiple formats, after wiping cache, etc - this message won't go away and has been in place for months.

Whenever I try to click it too slowly the whole menu closes. If I succeed in ninja clicking it fast enough, it goes away but returns on the next pop out. Killing me.
Gepostet 11. Feb. 2025 · mfg
0
Follower
1
Stimme
2
Kommentare
mfg hat einen Post erstellt
I am writing an automation to accommodate for rate limit errors - specifically 429s. In order to do so, my error handling needs to pull the [ratelimit-reset
] property from the error message, then add a delay. However, without hammering the end point and causing whatever errors across the production API, I'm not able to test for real world results.
Is there a way to test where you can manually trigger a 429 message without actually causing one?
Gepostet 11. Feb. 2025 · mfg
0
Follower
0
Stimmen
0
Kommentare
mfg hat einen Kommentar hinterlassen
Are there any plans to provide a method to monitor and report on these issues, or to query for end users with undeliverable email identities? Will this data be included in a data set in Explore?
Kommentar anzeigen · Gepostet 11. Feb. 2025 · mfg
0
Follower
1
Stimme
0
Kommentare
mfg hat einen Kommentar hinterlassen
Richard J - I did not, the search API doesn't really think about things that way from what I have pieced together
Kommentar anzeigen · Gepostet 03. Feb. 2025 · mfg
0
Follower
1
Stimme
0
Kommentare
mfg hat einen Post erstellt
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)
As an admin, I would like to be able to review the message pushed to a webhook in the same way you can view emails/notifications sent to various users in the history.
What problem do you see this solving? (1-2 sentences)
I am troubleshooting a difference in the payload received via API - I'm expecting one set of keys, but only getting headers.
When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)
On-going - core feature that doesn't exist. This is an issue whenever I am building or testing.
Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)
No.
What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)
Add an element to the ticket history that shows the JSON body of what was pushed to the webhook URL, preferably with values instead of placeholders.

Gepostet 31. Jan. 2025 · mfg
0
Follower
2
Stimmen
1
Kommentar
mfg hat einen Post erstellt
Can I create a custom Help Center page template and insert a form dropdown for a different brand?
Gepostet 30. Jan. 2025 · mfg
0
Follower
0
Stimmen
0
Kommentare
mfg hat einen Post erstellt
It would be helpful to have an option to simplify testing triggers if you could know that an email won't be generated regardless the triggers an event may interact with.
Currently you would need to either design to your best knowledge triggers that wouldn't activate email triggers or modify/deactivate triggers to cover the use case. In the event of a misfire, you may unintentionally send an email to an external end user with test data or real looking data.
Having a simple kill switch would allow for testing without the risk of confusing customers and would also allow an admin to see other triggers that may misfire in the event history of a test ticket.
Gepostet 29. Jan. 2025 · mfg
0
Follower
1
Stimme
1
Kommentar