Notification if No Email Address Associated with Requester

I can't believe this doesn't already exist. If you aren't using SMS, there is no other way to send a message via text - so if a public message is sent and there is no email, the system should provide some type of notification that the requestor does not have an email address on their contact card. 

When this mistake is made, it's very difficult to go back and find to correct. You only find out after it's too late in most cases because the agent sent the pertinent info, but the requestor never got it. 

Yes we need this too, a warning message exist if the ticket requester has a sample/test domain,

We need this same warning to show if the user does not have an email. As our staff will assume the user got an email when in fact nothing was sent..

Please prioritize. 

We need this feature as well. Seems like it would be pretty simple. We get tickets that are voicemails sometimes. If a return call doesn't pick up, we will often email reply to the ticket. If the email isn't in the ticket, and we forget to manually add the email, then there is an email reply being sent into the void. Would love a little pop up or help text letting my agents know that there is no email in ticket or CC, so may not be reaching anyone

+1 Piling on to the need here.

At present, I'm occasionally reminding our agents to "Be sure to glance over to the right at the Zendesk User Data app widget to ensure the requester has an email address when you save a Public Reply", but this is a pretty inefficient approach.

I understand that one is not required to send notifications to requesters for Public replies, so ZD may not want to implement a universal data validation restriction.  However, email notifications to requesters for Public replies is default Zendesk behavior, so at the very least a soft / dismissible / ignorable pop-up or warning would be appropriate.

Going one step further, I would even settle for a trigger condition for "requester has no email address", which I could use to send the agent an email afterwards.  For example, "FYI: You just sent an email to nowhere on #12345."  To be clear, an in situ warning would be preferable.

+1

There's also no easy workaround, since you can't create triggers to watch for this; there are no conditions that search for the requester's email.

+ 1. This is an absolutely crucial gap to be closed. Agents easily overlook the missing email address. There's has to be an error/warning message, or the ability to create a trigger condition. 

+1 

Like the others in this thread I would like to see a solution to this issue. It seems like a rather trivial issue since a trigger notifying the agent that there is no email attatched would go a long way.  

A much-needed feature for sure. Trigger condition would work the best

We just came across this issue too. Wow! There's got to be a solution for this. Zendesk - are you listening?

We need a solution here. Thanks!

Hey all, thanks for engaging on this thread and providing feedback on this product area. We have logged this feedback for our backlog but do not currently have plans to implement this into our roadmap as we are focused on features to surface outbound email bounce information and the ability for customers to connect their email servers directly to their Support Instance. We will continue to leave this thread open for community comments for more use cases and if anything changes in the future on our end we will update as soon as possible. We understand this may be frustrating for folks but hope transparency is helpful in your understanding. Thank you again for providing your feedback to us!

Benjamin Kirsch, Thanks for updating this request.

The outbound email bounce would not be relevant in this use-case, as there would be no email attached to the customer in the first place.

Hopefully, this request can get a higher priority soon.

Hi @benjamin24

I agree with Kristian, above; I'm not convinced that outbound email bounce reporting would have any impact or relevance here.  This issue is for requesters with no email address.  An agent saves a Public Reply >> the agent assumes the Public Reply notification is sent to the requester.  However, no email is sent because the requester does not have an email address.

Technically, this functionality makes sense.  No email address = no email sent.  The issue is that Zendesk lets my notification trigger fire & fail without any indication it failed.  I described this pretty thoroughly in my original post (https://support.zendesk.com/hc/en-us/community/posts/4408868307866-Notification-if-No-Email-Address-Associated-with-Requester/comments/4643424118170).

I hope you will revisit this topic before excluding it from future planning.  I think either we are misunderstanding your update, or you are misunderstanding the stated issue.  Thanks for your help.

+1 on this. We need visibility if there is no email to send the notification for the request. In a similar way we receive an internal note if an SMS has not been sent, I'd love to see this logged in the ticket. 

@benjamin24 You just announced the update about email delivery failure notices for agents. From the documentation it seems like this topic here is still not fixed with the update. Is this correct?

Hey @metzdorf,, that feature already exists within the To and CCs section of the Composer .  See “Step 5” under the To CC a user from the ticket interface section.  

If you have any feedback on that feature I can pass it along to the PM and team that implemented that!

hello @benjamin24 

Indeed we see a little /!\ but ONLY if agent clicks on “CC” button which is very rarely..

Product should think about a better way to notify when no email addres.. thank you

Major +1 - This is an urgent and business-critical issue for us. We're seeing hundreds of customer replies go undelivered every week because there's no way to track when a ticket lacks a Requester email, since Requester emails are continuously going missing from tickets due to a different issue that can’t be fixed on our end for the foreseeable. This is seriously impacting our ability to support customers effectively.

If a direct notification isn’t currently possible, we urgently need a workaround — such as a trigger condition that detects when the Requester’s email is missing from a ticket. That would at least give us a way to flag and address these cases before they result in missed communication.

This gap is creating real risk for customer experience and needs immediate attention.