Managing your tickets via email with the Mail API Follow

Our Mail API has long been a great tool for email-only help desks and agents looking to quickly triage tickets from their inboxes. Since we originally launched the Mail API, we've received lots of great community feedback, and we recently announced a new version of the Mail API that offers you more flexibility in managing your tickets via email.

Note: Only agents can use the mail API. These commands will be ignored, if they are used by end-users or light agents.

If you're already an avid user of the Mail API, the single biggest change you'll notice with the new Mail API is a switch from putting commands in the subject to putting them at the beginning of the email body.

For example, if you want to tag a ticket with a particular product that the customer is emailing about, you put #tags product6000 at the beginning of the email body as shown below:


You might also notice that we've added shortcuts for some of the longer commands. For example, you can now use #solved instead of #status solved .

If you're not already using the Mail API, but find yourself in your inbox more than in Zendesk Support, then it might be time to give it a try.

How can I use the Mail API to improve my workflow?

One of the simplest ways you can take advantage of the Mail API is by using it to assign tickets to yourself when you reply to customers. If you begin your email with #assignee then the ticket is automatically assigned to you when your reply is added to the ticket.

If you're like a lot of our customers, you probably have multiple groups in your Zendesk Support. In that case, you can also add #group name or #group ID to assign a ticket to a particular group.


Sometimes, you might want to mark a ticket as solved when you reply. That's easy to do using #solved . Just make sure you also set an assignee. Otherwise, the ticket won't be marked as solved.

The Mail API isn't just for updating a ticket when you reply to a customer, though. You can also use it to add private comments to a ticket. If you begin your email with #note then the comment will only be visible to your agents, not the customer. This can be helpful if you're assigning the ticket to someone else in your group for further review, as you can then combine the #assignee and #group commands to quickly delegate the task to them.

There are a few other commands supported by the Mail API, so be sure to check out our Mail API documentation for more information.

As always, we welcome your input. If there are feature's you'd love to see in the Mail API, we encourage you to go to our Feature Request forum and let us know. Otherwise, we hope you'll find the updated Mail API helpful!

Have more questions? Submit a request


  • 0

    we have requesters that have multiple organizations is there a command like:

    #organization ABC COMPANY

    to change the org as well?



  • 0

    Hi Harry!

    The Mail API can only be used to add or modify system ticket properties. The customer's Org is not a ticket property, so it can't be modified by API.

    Please let me know if you have any other questions!

  • 0

    I have an issue when using this that I get an internal note that simply states [no content]

    I use the following:

    #assignee <my email address>

    What am I doing wrong?

  • 0

    Hey Brett!

    What is the content of the email that you're trying to send into Zendesk?

  • 0


    I' a light agent for my company. At the top of this article you mentioned "These commands will be ignored, if they are used by end-users or light agents."

    I have just replied to a ticket and inserted #public false. The e-mail stayed internal. Does this mean that your API works well for light agents?


  • 0

    Hi Pieter!

    Because you're a light agent, your comment would have been added as an internal note whether you inserted #public false or not. The mail API does not work for end-users or light agents, only full agents and admins.

Please sign in to leave a comment.

Powered by Zendesk