Create Accountor Login
Docs

The Inbox

Part of the MountDev Ops Helpdesk documentation. Updated November 19, 2026

MountDev Ops Helpdesk documentation | Updated November 19, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

!The Helpdesk Inbox listing open tickets.

!The Helpdesk Inbox listing open tickets, on a phone in dark mode.

Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.

What the Inbox Is

The Inbox is where Helpdesk opens, first in its menu, with its parts under it. It lists your team's tickets like an email client, with the ticket that has the newest activity at the top, so the tickets that need you are always in view and closed tickets never crowd them (action helpdesk.tickets.inbox). Tickets are listed here rather than in the menu. They are still found by search, can be imported and exported, and their module is changed on Helpdesk's Settings page like any other (Modules and Fields).

New Ticket

Select New Ticket at the top of the Inbox to open a ticket yourself and send the client its first email: pick a contact or type an email address, then add a subject and your message, and share files with it if you like (Opening a Ticket Yourself). It shows for anyone who can reply to tickets.

Parts in the Menu

The Inbox's parts are in the left menu, under Inbox, and the page's title is the part you chose. There are no tabs above the list.

  • Open (where the Inbox starts): every ticket still to do. That is a ticket with the status Open, no status, or any status your company added other than Waiting on Customer, Waiting on Us, and Closed.
  • Waiting on Customer: tickets waiting for the client to answer.
  • Waiting on Us: tickets your team is working on behind the scenes. Each opens again on its own two business days after it was set and moves back to Open (Waiting on Us).
  • Closed: tickets that are done, including calendar notifications and read receipts, which are closed as they arrive (Tickets and Replies).
  • All: every ticket except spam, so Open, Waiting on Customer, Waiting on Us, and Closed add up to All.
  • Spam: tickets marked as spam, and every email from a sender on the spam list, with no receipt and no notice to your team (The Spam List). Open one and select Not Spam to move it to the Inbox. Only owners and admins see this part, because only they see spam.

The Unread Counter

Open shows a counter, the same badge as Alerts in the left menu: how many open tickets have a notification on you that you have not read yet. The same number shows on Helpdesk in the Service list and on Service in the left column. Opening a ticket reads its notification, and all three go down together, live. Only Open has a counter. It counts only your own notifications, for tickets you may see (action core.nav.counts, asked by the menu itself; AI agents and API keys have no menu and no counters).

The counter and the rows show only tickets you may see. Tickets from an admin-only address, and spam, are counted and listed only for owners and admins, and a role that shows someone only their own records counts and lists only theirs (Roles and Access).

Views

On a computer the Inbox has a list of views down its left side, like a mail app's folders. One click flips the list.

  • My Tickets: tickets assigned to you. Unassigned: tickets assigned to nobody. All Inboxes: every department you may see, and tickets in no department, in one list.
  • Departments: each department you may see, with the departments inside it indented under it and a small arrow to collapse it. A department's view holds the departments inside it. A department that would only repeat All Inboxes (you see one department and no ticket is outside it) is not listed.
  • No Department: tickets that are in no department, listed where departments exist and some ticket has none.
  • Addresses: with Show each address under its department in the Inbox on in Helpdesk Settings, each department lists the addresses that have tickets, the busiest first, up to 8.
  • Saved Filters: your own named filters, each with a Remove button.
  • Spam: the last view, with its count, for owners and admins only (The Spam List).

Each view shows a count: how many of its open tickets have a notification on you that you have not read, the same number the left menu uses. The view you chose, the departments you collapsed, and your saved filters are your own settings, kept with your account, so they follow you to another device and nobody else sees them (action helpdesk.inbox.prefs).

Go to a View is a box at the top of the list. Type a department or an address and the list narrows to matches, and Enter opens the first one. Esc clears it. There is no keyboard shortcut to jump between views, only this box, reached with Tab.

On a phone, or any narrow window, the list is one button at the top, such as View: All Inboxes with its count. Select it to open the same list, and the box when there are more than five views.

Each Row

Each row shows the requester with their initials and their company, when someone last wrote, the ticket number and subject, and the first words of the latest message (with who on your team wrote it, when it was your team). Below that are its markers, who it is assigned to ("Assigned to you" when it is yours, or the group's name), and the mailbox it came in on when you have more than one. Markers show what needs attention:

  • New: the client wrote and nobody on your team has replied yet. The row is in bold with a dot on the initials.
  • Needs Reply: the client wrote back after your team's last reply. The row is in bold with a dot on the initials.
  • Waiting on Customer: your team replied and is waiting for the client.
  • Waiting on Us: your team is working on it, with when it reopens beside the marker, such as "Reopens Tuesday, October 20, 3:00 PM" in your company's time zone.

Spam and admin-only tickets carry a Spam or Admins only label. Helpdesk does not track which tickets each person has read, so New and Needs Reply are about the conversation, not about who opened it.

Character codes that some older messages were kept with (such as a code in place of an apostrophe) show as the characters they stand for.

Closed Accounts

Email from a client whose account is closed comes in like any other: a new ticket in the Inbox, marked Closed account on its row and on the ticket, with a note saying so. It is never closed, filed as spam, or refused because the account is closed, and the team is told as usual. No automatic receipt goes out, since a receipt would promise work, so answer it yourself when an answer is needed. A ticket is marked when the sender's company in CRM has the status Former, or when the account they sign in with says it is closed. See Closed Accounts.

Buttons on a Row

Each row has buttons on the right: Merge, Mark as Spam (owners and admins only), Close, and Move (when you may move tickets and there is another address to move to). On a computer they fade in at the right edge of the row when the pointer is over it or a control in the row has keyboard focus, taking the place of the date. The subject and preview shorten with "..." to make room for them, so no text sits under a button, and the row's text runs across the full width until then. In a list narrower than about 820 pixels (a laptop with the Views column open, for example), the five buttons become one Actions button, which opens a short menu with the same choices. They are always in the page, so Tab reaches them, and they are always shown on a touch screen. On a phone each row has one Actions button that opens a short menu with the same choices, and the menu opens upward when it would run off the bottom of the screen. Esc or a tap elsewhere closes it.

  • Merge: opens the same pop up as Merge on a ticket, with this ticket kept (Merging Tickets).
  • Mark as Spam: asks once. The sender goes on your spam list and the ticket goes to Spam, where it is deleted after the number of days in Helpdesk Settings, Delete Spam After, unless the sender is a known contact (The Spam List). Action helpdesk.spam.mark.
  • Close: sets the status to Closed (action helpdesk.status). The ticket leaves Open and shows a Closed label in All. Closed has its own Status filter.
  • Move: moves the ticket to another address (Moving a Ticket to Another Address).
  • Not Spam: on a row in the Spam view, moves the ticket back to the Inbox and takes its sender off the spam list. Nothing is sent to the sender.

A row button or menu never moves the page. Each one does its work in place and keeps the list where it was. A row that leaves the view, such as a ticket you mark as spam while the Open view shows, fades out, the rows below slide up, the counts update, and keyboard focus moves to the next row.

Progress on a Row

The moment you press an action, its row frosts over with a small spinner and the action's word: Closing, Marking as Spam, Merging, Reassigning, or Moving. The row's buttons, its checkbox, and its link are turned off while it works, so pressing twice sends the change once. For Merge, Reassign, Move, and Mark as Spam the pop up or question comes first, and the frost starts when you confirm and the pop up closes.

  • When it works and the ticket leaves the view, the frost stays until the change is confirmed, then the row fades out where it is, and then it closes up so the rows below slide up. The row never jumps to another place in the list while it goes. With reduced motion on in your device, the row still fades, and the rows below close up at once.
  • When it works and the ticket stays, as with Reassign, the frost fades off and the row updates where it is.
  • When it cannot be done, the frost fades off, the row comes back exactly as it was, and a short line inside the row says why, in full and always readable, with Dismiss. Nothing is lost. The line goes away when you try again, dismiss it, or the list is redrawn.

You do not have to wait. Press actions on several rows one after another, and each row works on its own, shows its own frost, and finishes on its own. A change someone else makes to a ticket never replaces a row while it is working. Rows are separated by a line and have no outline of their own; only the list keeps its rounded corners.

Selecting Tickets

Check the box at the start of a row to select it. A bar appears with how many are selected, Merge (for two or more, Merging Tickets), Mark as Spam (owners and admins), Close, Move, and Clear. Merged tickets never show in the Inbox or its counts.

Each bulk button runs the same action once for each ticket, frosts every checked row at once, and finishes each row on its own (up to four at a time, the rest wait with the same frost). A ticket that fails shows its reason on its own row while the others go through. A note under the filters says plainly what happened overall, such as "Closed 5 of 6. T-1041 could not be closed: it was changed a moment ago." The tickets that worked stay done, and the others are left exactly as they were.

Move moves the checked tickets, up to 100 at a time, to another support address (action helpdesk.ticket.move), exactly as Move to Another Address does on one ticket (Moving a Ticket to Another Address). Choose the address, and check Assign by the new address's rule to give every ticket to whoever that address sends its new tickets to. Each ticket moves whole or not at all: when some cannot move (one already at that address, or one your role does not let you change), the others still move, and a note says how many moved and why each of the rest did not. When none can move, the dialog stays open and says why. Move shows for anyone who can reply to tickets when there is more than one address to choose from.

Paging

The Inbox shows 25 tickets at a time, with how many there are in all. Select Show More for the next 25. It never loads every ticket at once, however many you have.

Opening a Ticket

Select a row to open the ticket in place (Tickets and Replies). Inbox in the menu goes back to the same part, filters, and place in the list. The list updates on its own when tickets change.

For AI Agents

An AI agent you connect can read the Inbox as the person who connected it, with the same views and filters (department, assigned to, and status), search, paging, and the same limits on what it may see (action helpdesk.tickets.inbox). It only reads; it changes nothing.

Ask Us Anything

We’d love to hear from you!