MountDev Ops Helpdesk
How MountDev Ops Helpdesk works, page by page. Updated November 20, 2026
MountDev Ops Helpdesk documentation | Updated November 20, 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.
Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.
Tested Every Release
All 781 of Helpdesk's own automated checks run on every update.
What they cover: Tickets | Email | Files and attachments | Spam and abuse protection
What Helpdesk Is
Helpdesk keeps every ticket and every message on it. Client email to your support addresses becomes tickets, and your team replies from each ticket by email. It starts with the modules below, and every one of them can be changed, given its own icon, turned off, or deleted on Helpdesk's Settings page, the last item of its menu, the same as any module (Modules and Fields). Adding Helpdesk adds CRM too, because tickets link to companies and contacts.
In These Docs
- The Inbox: where Helpdesk opens. Your tickets by tab (Open, Waiting on Customer, Waiting on Us, Closed, Spam, and All) with their counts, filtered by who they are assigned to, mailbox, or a search.
- Tickets and Replies: how email becomes tickets, the conversation and its files, replying to everyone on the conversation by your business hours with time to undo, forwarded client email, emails as they really look, Add to Reply (upload links, sharing staging access, sharing files, and daily follow-ups), internal notes, assigning, moving a message to a new ticket, status, and the close rule.
- Departments: your teams as Helpdesk departments, each address's tickets landing in one, who sees which tickets, and moving a ticket between departments.
- Assignment Rules: round robin and fewest open tickets for a team's new tickets, who counts, what happens when nobody is available, and Pass It On.
- Assigning Tickets: tickets for a person or a group, where each support address sends its new tickets, a group's ticket becoming the replier's, and your notifications.
- Merging Tickets: bringing tickets that are one conversation together, with suggestions, and undoing a merge.
- Automatic Follow-Ups: reminders when a client has not answered, then a closing notice, and daily follow-ups until a vendor or outside support team answers.
- Suggested Replies: your assistant reads the ticket and everything around it and suggests a reply in your team's voice, checked for review risk, that a person sends, changes, or asks again; what it learns, its monthly limit, and Learn From Past Replies.
- No Automatic Replies: people who never get a receipt or automatic follow-up, set on a ticket, a CRM contact, or in Helpdesk Settings, with loop protection.
- The Spam List: mail from senders you never want in your Inbox goes to the Spam tab instead, and Not Spam moves a ticket back.
- Automated Senders: email from backup services, security plugins, and WordPress's own update emails is kept but filed Closed, out of your ticket queue, and a problem one reports is one notice to owners and admins.
- What Your Clients See of Their Requests: your clients' Requests page in their own workspace, with each request's conversation, its files, and replies that join the ticket as an emailed reply does; who sees which requests; and what never shows.
- Zoho Desk in Helpdesk (Off for Now): importing from other services is coming later; a saved connection stays listed and replies on tickets already here still go out.
- Import From Zoho Desk (Off for Now): the import card is gone from Settings; use Import From File.
- Kinds and Levels: the kinds of records and areas Helpdesk declares, and the levels each one has.
- Support Addresses: as many addresses as you like, a list that pages and searches, Add Address in three steps, Add Several, and the daily limit that protects your account.
- Helpdesk Settings: your support addresses, who sees their tickets, receipts, ticket numbers, your signature, who hears about new tickets, where each address's new tickets go, upload links, and shared file links.
- Permissions for Connections: every permission an app or an AI assistant can be given in this app, with its level.
Starting Modules
- Tickets: listed on the Inbox page rather than in the menu. Subject, status (Open, Waiting on Customer, Waiting on Us, or Closed), company, contact, requester and their email, number, inbox, website, who it is assigned to, when it was last replied to, admins only, spam, project (the old typed code), Linked Project and Linked Task (with Projects too, Linking a Project), Not Applicable reason, Merged into (the ticket a merged ticket went into), and Also on this ticket (the requesters of tickets merged into it).
- Messages: shown on each ticket rather than in the menu, since a message only makes sense inside its ticket. Subject, ticket, direction (Incoming, Outgoing, or Note), who it is from and their email, to, cc, the message, and when it was sent.
