Skip to main content

Set up inbox to handle email tickets without any code

No code email ticketing

When a customer sends an email to the support team in a typical business scenario, it usually lands in the inbox of the respective email app, such as Gmail or Outlook. This process is often disorganized and difficult to streamline.

No code email ticketing offers a solution to manage customer support requests or tickets through email without the need for programming. This system automatically directs incoming emails to the appropriate customer support agent or group, and utilizes an inbox ticket section to monitor and control the status of each ticket.

You can enable no code email ticketing here.

Features offered by the tickets section:

  • The primary objective of no code email ticketing is to simplify the management of customer support requests and enhance the efficiency and effectiveness of customer service teams.
  • All customer queries raised via email are compiled and listed in a unified user interface (omni-channel customer support suite).
  • Admins can view all tickets sent to or received by the support email address.
  • As an Agent, you will be assigned with the tickets (based on the group or auto-assign settings). You can select an email that needs attention and reply to it on time.

Once the email tickets have been set up according to the instructions provided in configuration page, the inbox will receive emails. From there, you can view the email support requests as tickets on the email tickets page, which can be seen in either List view or Detailed view.

note

Email tickets are assigned only to an Inbox agent (although Inbox admin will have the permission to see and contribute to the operations in Inbox).

  • For an inbox admin, all the chats/tickets will be accessible.
  • For an inbox agent, only the chats/tickets assigned to them will be accessible.

ticket-created event (custom event) gets triggered when a email ticket is created and assigned to an agent.


1. Email tickets list view

  1. Log in to yellow.ai platform and open Inbox > Tickets.

  2. The landing page will have a ticket list and count, Sort and filter options, manual ticket creation, SLA messages, email details (agent ID, ticket ID, subject line, ticket creation time), priority, ticket status, and assigned group/agent.

FeatureDescriptionRelated links
Tickets- My tickets: List of tickets assigned to a particular agent.
- Collaborating tickets: List of tickets where multiple agents have been assigned/working on a ticket.
- Unassigned tickets: This list displays the tickets which are not yet assigned to any agent.
- Resolved tickets: Tickets that have been resolved.
Email details- Each ticket is auto-assigned with a number when created, which will be its respective ticket ID.
- Each ticket contains the subject of the email under which you can find the requestor's name and the created date.
- You can also see the priority, status, agent name, and the group to which the agent belongs.
- You can perform bulk actions on these tickets.
Ticket status, Bulk actions
Sort and filterLast modified date is considered as the date & time when the ticket was recently modified/updated. By default, tickets are arranged based on the last modified date with their corresponding ticket ID. You can sort by Last modified date.Search and apply filters
Manual ticket creationYou can choose to create an email ticket manually.Create new tickets

2. Email tickets detailed view

  1. Log in to yellow.ai platform and open Inbox > Tickets.

  2. Click on any of the ticket grids, and the detailed view of that respective ticket opens.

2.1 Ticket screen elements

FeatureDescriptionPreview
Ticket ID & SubjectTicket ID# and Subject are displayed on the top of the ticket thread
SLA logHover over SLA log to see the SLA policy applied for this ticket. Learn more here.
Ticket statusBy selecting Resolve ticket, the ticket gets resolved. You can also change the ticket statuses.
Download & share threadYou can copy the link to the transcript or download the transcript of the email conversation in this ticket- Be mindful of the user information provided in the email thread
Email threadTo and from messages along with the sent/received time

2.2 Email response screen

FeatureDescriptionPreview
Add templateYou can add(change/preview/delete) a pre built template. Learn more here.
ReplySelect Reply from the dropdown to reply to the previous mail. To address cannot be changed.
ForwardSelect Forward from the dropdown to reply to the forward the above email thread to a new email ID.
Internal notesSelect Internal notes from the dropdown to add internal notes that only the Inbox admin and agent to whom this ticket is transferred can see.
Add CC and BCCClick Cc/Bcc and add the mail IDs
Quick actionsYou can send prebuilt email templates or configured canned response or ..
If there are multiple canned responses, you can search for the required canned response using keyword or text. Click here for details.
Formatting optionsYou can add quick responses, attach up to 5 files (each less than 10 MB), Bold/italicize/underline text, and add numbered/ordered list to the reply body.
Select/change email IDAll the emails configured for inbox are displayed here, you can select the email ID from which you wish to send this email.
If you have received a mail on different mail ID and you send a reply using a different mail ID- the user will receive the old conversation thread in the current mail.
Email bodyYou can only send a reply when the body contains some information. To send a reply without any content, use blank spaces.
note

Auto-save draft message

The draft message saving option allows the agents to save their composed messages (or private notes) automatically, ensuring that their work is preserved when switching between chats or windows, or even when accidentally closing the tab. The ticket interface will display an indication to show that a draft has been created and these drafts will be visible only to the agent who authored it.

Limitations:

  • Session-based retention: Drafts are retained only until the user session concludes. Upon session end, drafts may be cleared to maintain privacy and optimize system resources.
  • Browser compatibility: Cross-browser compatibility is not functional in this situation. For example, when Chrome and Firefox browsers are simultaneously opened, and a cloud app is accessed on both, any draft created in one browser (e.g., Chrome) cannot be observed within the corresponding chat in the other browser (e.g., Firefox).
  • Incognito mode: Drafts are not compatible with incognito mode. Agents should refrain from using incognito browsing when relying on the draft feature to ensure a seamless experience.

2.3 Customer contact details

FeatureDescriptionPreview
Contact detailsCustomers name, number and email are displayed. You can view activities that are happening with this email contact by clicking the Recent conversation. Click View all to see all the details on the Contacts tab.

2.4 Email ticket details

FeatureDescriptionPreview
Email ticket detailsPriority: You can change the priority to low, medium, or high
Assignee: You can assign the email conversation to a Group (which gets auto-assign to an agent) or you can assign this thread to an agent. Configure Email group and agent.
Tags: You can tag this conversation to any of the configured tags.

2.5 Other details

FeatureDescriptionPreview
Ticket fieldsThese are custom fields, you can configure and arrange them in settings.
CollaboratorsMore than one agent can help to resolve a ticket (similar to a group chat). Add collaborator names by selecting the names from the dropdown menu.
Activity logThe activity log consists summary of all the changes/updates that have taken place on this ticket (ticket ID). For example, Change of status/priority, Transfer of ticket from one agent to another, Reopening of the ticket, Breach of SLA, etc.