Skip to content

Tickets

Overview

Tickets is the live support workspace for reviewing, updating, and responding to organization support requests. From the ticket queue you can open a ticket, read the full conversation thread, update routing and ownership, add private internal notes, and send a customer-facing reply — all without switching tools.

Each ticket shows requester and organization, status, priority, queue, tags, assignee, conversation history, attachments, unread count, and recent activity. If your organization tracks support effort, the ticket detail view shows time totals and supports timer automation.

Tickets update in real time: new messages, routing changes, assignment updates, and viewer activity appear while you work.

When to use Tickets

Use Tickets to process incoming support requests, triage work, hand off cases, or follow up on in-progress items.

If you need help from Eos support, use Submit Eos Ticket instead. This is also the route to use when someone asks how to raise, open, create, or submit a ticket in Eos.

You can also email support@eoshq.com. These are the two supported ways to contact Eos support; Help does not list a support phone number.

Raise a ticket with Eos support

  1. Select your profile picture in the top-right banner.
  2. Select Submit Eos Ticket.
  3. Select New Ticket.
  4. Enter a short Subject and describe the problem in the details box. Add an attachment if it will help explain the issue.
  5. Select Submit.

The submitted ticket appears on the same Submit Eos Ticket page. Return there to see its status, read responses, or add more information.

  • Triage new requests and handle ongoing tickets from a shared queue
  • Find tickets by subject, requester, organization, or a phrase from a recent message
  • Filter by Status and reorder with Sort to focus the queue
  • Re-route work by changing Queue, Priority, Tags, or Assign To
  • Add processor-only context in Internal notes and mention teammates there
  • Reply to the requester from the ticket thread and attach files
  • Review time totals and use timer automation when configured

How it works

Work from the Ticket Queue

The queue lists tickets for your organization with summary information on each card: status, organization, requester, updated time, unread count, and a preview. Use Search to locate a known ticket and the queue controls to filter by Status or change Sort order.

Select a ticket card to open the ticket detail panel and begin working from the current live state.

Read the full thread before acting

Open the ticket detail to review the subject, full conversation history, timestamps, and any attachments. Read the thread before changing routing or sending a reply to avoid acting on the preview alone.

Update routing and ownership

In the detail view you can change metadata that directs how the ticket should be handled: Status, Queue, Priority, Tags, and Assign To. After making changes, click Update to apply them.

If Assign To is not available, assignment may be restricted by your role or permissions.

Internal notes for processor-only collaboration

Use Internal notes for private processor-to-processor communication and handoffs. Mentions in internal notes surface other processors for follow-up while keeping the content out of customer-facing replies.

Replying to the requester

Use the reply composer in the ticket thread to send customer-facing messages. Attach files when needed; sent replies become part of the ticket history so anyone who opens the ticket later can see what was communicated.

Time tracking and timer automation

If your organization enables time tracking, the ticket detail displays time totals for that ticket. Organizations can configure timer settings so work timers may:

  • Start automatically when you begin working on a ticket
  • Start automatically after a short delay
  • Be canceled or started immediately during the pending delay

Admins manage these settings in Configuration > Ticket Processing, rather than Settings > Your Org. Check the timer settings to understand whether timers auto-start and what delay, if any, applies.

Ticket Processing remains an additional option for Weekly time entry when the user has the required license and ticket access. Changing the configured Time Tracking levels does not remove ticket-only time entry or require a Project or Task for it.

Viewer awareness

Viewer activity shows who else is viewing the same ticket. Viewer indicators update live for the currently opened ticket so you can see when colleagues are looking at the same case.

Typical workflow

  1. Open Tickets and scan the queue for unread activity or recently updated work.
  2. Narrow the queue with Search, the Status filter, or Sort.
  3. Click a ticket to read the full thread and check attachments.
  4. Update Status, move the ticket to the correct Queue, set Priority, add Tags, or use Assign To, then click Update.
  5. Add Internal notes for handoffs or escalations; mention colleagues if you need follow-up.
  6. Send a reply from the reply composer and attach files as needed.
  7. Review the ticket’s time totals if your organization tracks effort.

Controls and what they do

Control Purpose
Search Find tickets by subject, requester, organization, or message preview text
Status filter Show only tickets in a specific handling state
Sort Reorder the queue by activity, subject, organization, or priority
Ticket card Open the selected ticket; shows status, requester, organization, updated time, unread count, and preview
Status selector Change the ticket’s handling state
Queue selector Route the ticket to the appropriate operational queue
Priority selector Mark the ticket’s urgency
Tags input Add labels to categorize and report on tickets
Assign To Change ticket ownership when assignment is available
Update Apply metadata changes made in the detail view
Internal notes Add processor-only notes and mentions
Reply composer Send customer-facing replies within the ticket thread
Attachments Include files in messages or replies
Time totals Display tracked time for the ticket when enabled

Things to watch for

  • Internal notes are private to processors. Use the reply composer for messages the requester should receive.
  • Read the full conversation and any attachments before updating routing or replying.
  • Assignment may be restricted by role; if you can’t use Assign To, contact an administrator.
  • Tickets update live; another processor may change status, assignment, or notes while you’re viewing a ticket.
  • Viewer indicators reflect who is looking at the currently opened ticket.
  • Timer behavior depends on organization settings: automatic start, delayed start with cancel/start-now options, or no auto-start.
  • Profile — user settings
  • Settings — organization-level configuration (including timer settings and assignment rules)
  • Help topics and articles for detailed workflow guidance
  • Submit Eos Ticket — open this from your profile menu to raise a support ticket and follow its responses