When you receive an email notification about a ticket, you can reply to it in your email client, rather than in the agent interface.
Remember, when you reply to a ticket notification, you are replying to the helpdesk, not directly to the user or agent who triggered the notification.
Depending on how your helpdesk is set up, replying by email will either be treated as a reply to the user or as an *Agent Note (see Replying to a ticket).
Every notification says what will happen if you reply, near the top of the email body.
This is what it will look like if your helpdesk is set to make a note:
In this case, the content of your email will be added as a note on the ticket in the agent interface. The user will not receive an email. Agents will be notified about your response according to their notification settings.
This is what it will look like if your helpdesk default is set to send a reply to the user:
In this case, the content of your email will be sent to the user, and any users who are cc’d. Agents will be notified about your response according to their notification settings.
When replying, make sure to enter your message above the
=== REPLY ABOVE === line.
When replying to a ticket notification by email, you can override the default setting of your helpdesk using a special Action Code (see Replying to tickets by email).
Enter the code
#note at the very top of your response, before any other content, to ensure your reply is treated as an agent note.
Enter the code
#reply at the very top of your response, before any other content, to send a reply to the user.
If you CC an agent in on your email reply, the agent will be added to the ticket as a follower (provided you have the correct permissions to do that).
If you CC a user in on your email reply, the user will be added to the ticket CC Field (see Replying to a ticket) if the helpdesk settings allow. For example, your helpdesk is set to require new users to register and you CC in an unregistered address, that person will not be CCed.
If a user CCs in another user, they will be added to the CC field (again, depending on helpdesk settings).
If a user CCs an agent, by default, they will not be added as a follower to the ticket, although your admins can enable that.
When a user or agent sends a ticket message by email, attached files will be stored and displayed on the message within the agent interface.
Your admins may set limits on the type and size of files you are allowed to attach. Remember that most email systems will reject large files (the limit varies, but is typically 5MB-50MB), or files that look like they might be harmful, like
.exe files. It is usually more reliable to share files using the Downloads area of the portal.
The action codes to set urgency, follow and unfollow are newly added as of January 2015. If they do not work on your helpdesk they will be available soon; if you have an On-Premise helpdesk, ask your admins to update to the latest version.
When replying to a ticket email notification, you can carry out most of the actions you could from the agent interface by adding special email action codes to your message.
Action codes must be placed at the top of the email message. They all begin with a # symbol, and some can be followed by an option:
For example, if you reply to a user by email and put
#status resolved at the top, the relevant ticket will be set as resolved.
Deskpro strips out the codes from any resulting messages, so they are not visible to users.
You can use multiple action codes in one email. Put each code on a separate line, above all the other message content, e.g.
#awaiting-agent #note #priority urgent
|#status option||Sets ticket status. Available options:agent__user__resolved__pending||
|#awaiting-agent||Shortcut for#status agent||
|#awaiting-user||Shortcut for#status user||
|#resolved||Shortcut for#status resolved||
|#hold||Shortcut for#status pending||
|#unhold||Removes pending status and sets status to awaiting agent.||
|#note or#is-note||Sets message to be an agent note rather than a reply to the user||
|#reply or#is-reply||Sends messageas a reply to user|
|#assign option or#agent option||Assigns the ticket to the agent specified. Option can be:Agent email address. Full agent name (e.g., “john doe”).||
|#follow option or#unfollow option||Adds specified agent as a follower. Options as #assign||
|#team option or#assign-team option||Assigns ticket to the team specified||
|#user option||Used only if an agent is sending new ticket to the helpdesk, this sets the ticket user by email address.||
|#label option or#labels option||Adds labels to the ticket. Provide labels as a comma-separated list.||
|#dep option or#department option||Sets the department.||
|#urgency number(1 to 10)||Set urgency||
|#cat option or#category option||Sets the ticketcategory.||
|#prod option or#product option||Sets the product.||
|#pri option or#priority option||Sets the priority.||
|#field value||Sets any customfield.#field is name of the custom field with spaces removed or turned into dashes, value is the value to set.||
|#noreply||Prevents message from being added to the ticket. Lets you use action codes without sending an actual reply to the ticket.||
When Deskpro is searching for values based on a string title or name (for example, a category name or an agent name), all comparisons are case-insensitive and ignore white space and punctuation. Here are a few examples:
Your option values are treated the same way. So
#assign Booker dean dewitt or
#assign booker dean de-WITT would both match the name “Booker Dean-DeWitt”.
When setting the value of a custom toggle field (where the value is either on or off, set by a single checkbox), use
no. For example, if you have a toggle field called Discount, you could set the value to yes with: