Vor Kurzem aufgerufene Suchen


Keine vor kurzem aufgerufene Suchen

Feature request: Add array of email errors to ticket schema or as a query parameter on email end point



Gepostet 12. März 2025

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 array of objects to the effect of:

"notification errors":[
	{"recipient": [user ID],
	"identity": [user email],
	"notifications": [a1b2c3,d4e5f6,g7h8i9]
	}
]

 

What problem do you see this solving? (1-2 sentences)

 

In order to collect delivery errors from the email endpoint, you need to loop through each recipient on each notification. In the case of tickets with multiple followers and CCs, and numerous notifications, this can become an intensive process.

 

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)

 

I'm currently trying to pull email errors from thousands of proactive tickets with multiple recipients each. This is a regular proactive tickets campaign and this would streamline each outreach going forward.

 

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

 

Looping each ticket, each notification, each recipient to identify bad email addresses.

 

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

 

Either include a “notification errors” array on the ticket object, as a query parameter on the email end point, or some other common end point.

 

 


0

0

0 Kommentare

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Sie finden nicht, wonach Sie suchen?

Neuer Post