MountDev Ops 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.
What It Does
Everything here is built and described in the MountDev Ops Helpdesk docs. Anything marked Planned is described in the docs but not built yet.
✓The InboxWhere Helpdesk opens.What the Inbox Is | New Ticket | Parts in the Menu | The Unread Counter | Views | Filters and Search | Each Row | Closed Accounts | Buttons on a Row | Selecting Tickets | Paging | Opening a Ticket | For AI AgentsRead about The Inbox ✓Tickets and RepliesHow 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...How Email Becomes a Ticket | Forwarding a Client's Email | Tickets From Your Website Forms | Opening a Ticket Yourself | The Ticket Screen | Attachments on a Ticket | Emails as They Really Look | Replying | Who Gets a Reply | Add to Reply | Upload Links | Sharing Staging Access | Sharing Files | Linking a Project | Checklists and Approvals | Internal Notes | Assigning | Moving a Message to a New Ticket | Moving a Ticket to Another Address | The Close Rule | The Account Beside a TicketRead about Tickets and Replies ✓DepartmentsYour teams as Helpdesk departments, each address's tickets landing in one, who sees which tickets, and moving a ticket between departments.What a Department Is | Departments in Helpdesk Settings | Addresses | Who Sees Which Tickets | Moving a Ticket | Workflows and AI AssistantsRead about Departments ✓Assignment RulesRound robin and fewest open tickets for a team's new tickets, who counts, what happens when nobody is available, and Pass It On.What a Rule Does | Who Counts | When Nobody Is Available | Where a Rule Applies | Set Rule | What the Person Sees | Moving a Ticket Into a Department | Reassign | Pass It On | Workflows and AI AssistantsRead about Assignment Rules ✓Assigning TicketsTickets 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.Who Has a Ticket | A Group's Ticket Becomes the Replier's | Your Notifications | A Notification Bell in the Workspace (Planned) | For AI AgentsRead about Assigning Tickets ✓Merging TicketsBringing tickets that are one conversation together, with suggestions, and undoing a merge.Merging From a Ticket | Merging From the Inbox | What Happens | One Scroll for a Merged Ticket | Undoing a Merge | Private Tickets | Suggested Merges | Who Can MergeRead about Merging Tickets ✓Automatic Follow-UpsReminders when a client has not answered, then a closing notice, and daily follow-ups until a vendor or outside support team answers.What They Do | Which Tickets Get Them | Seeing Them | When They Stop | Setting Them Up | Daily Follow-Ups Until They AnswerRead about Automatic Follow-Ups ✓Suggested RepliesYour 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...What It Reads First | The Suggestion | How It Writes | The Review-Risk Check | How It Learns Your Voice | Learn From Past Replies | Settings | From Your Other Systems | CostRead about Suggested Replies ✓No Automatic RepliesPeople who never get a receipt or automatic follow-up, set on a ticket, a CRM contact, or in Helpdesk Settings, with loop protection.What It Does | On a Ticket | On a CRM Contact | In Helpdesk Settings | If It Was Turned Off After an Email Was Waiting | Loop Protection | Bringing In a List | Nothing Is LostRead about No Automatic Replies ✓The Spam ListMail from senders you never want in your Inbox goes to the Spam tab instead, and Not Spam moves a ticket back.Every Email Lands in Helpdesk | Marking a Ticket as Spam | Not Spam | The List | Bringing In a Spam List | Spam Deletes ItselfRead about The Spam List ✓Automated SendersEmail 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.Why It Exists | What Happens to Their Email | When It Reports a Problem | The List | Bringing In a ListRead about Automated Senders ✓What Your Clients See of Their RequestsYour 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.Requests in Your Client's Workspace | What Your Clients Never See | Who Sees Which Requests | Replies From the Requests Page | Downloads Are in Your Activity Log | Requests for a Client With No Hub AccountRead about What Your Clients See of Their Requests ✓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.What It Does | What StaysRead about Zoho Desk in Helpdesk (Off for Now) ✓Kinds and LevelsThe kinds of records and areas Helpdesk declares, and the levels each one has.What Helpdesk Declares | How the Levels MapRead about Kinds and Levels ✓Support AddressesAs 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.As Many Addresses as You Like | The Daily Limit | Add Address | Add Several | Forwarding AddressesRead about Support Addresses ✓Helpdesk SettingsYour 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.Where to Find Them | Support Addresses | Forwarding Your Mail | Ticket Numbers, Receipt, and Signature | Link Old Project CodesRead about Helpdesk Settings ✓Helpdesk Permissions for ConnectionsEvery permission an app or an AI assistant can be given in this app, with its level.See the assignment rule of each department, in plain words | See the Automated Senders list (senders whose email is filed Closed, out of the ticket queue) | Tell Suggested Replies what another system knows about a client: automated emails sent, services, incidents, recent work, or billing notes | Stop daily follow-ups on a ticket | Make a new department: an empty team at the top level that Helpdesk uses | See the departments you can see, with their people, tickets, and addresses | Rename a department | Leave owners and admins a note about a change a department needs | See the Helpdesk addresses a page at a time, with a search | Find projects and tasks to link a ticket to | Unlink a project from a ticket (or every project) | Link a ticket to a project or one of its tasks (beside any projects it links to) | Merge tickets into one | Find tickets that look like the same conversation, to merge | Undo merging a ticket | Add an internal note to a ticket | See your Helpdesk notifications: new tickets, client replies, and tickets assigned to you or your groups | Mark your Helpdesk notifications read, for one ticket or all | Count the open tickets linked to projects | Create a project from a ticket and link the ticket to it | See what a new project made from a ticket starts with | Find tickets to link to a project | See the tickets linked to a project | See whether a CRM contact gets automatic replies from Helpdesk | See the email addresses with automatic replies off (No Automatic Replies) | Undo a reply before it goes out | See Helpdesk Settings and addresses | Turn off a shared file's link | Move a client message to a new ticket | Change a ticket's status (Waiting on Us opens again on its own two business days later) | Give a ticket to whoever its department's rule picks | Move a ticket to a department | See a ticket and its conversation | Move tickets to another support address | See the Inbox: tickets by tab, newest activity first, with each tab's count | Turn off an upload linkRead about Helpdesk Permissions for Connections What It Starts With
Helpdesk comes ready to use with these modules, and every one of them can be changed, turned off, or deleted in its Settings.
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.
All 781 of Helpdesk's own automated checks run on every update.
What they cover: Tickets | Email | Files and attachments | Spam and abuse protection
Your business data is kept apart from every other company and out of our reach.
- Every company gets its own separate database and its own encryption key.
- No one at Cascadia Web Services can open your data. None of our staff tools, logs, or admin screens can reach it.
- If you ever want our help inside your account, you grant a named person temporary access for a set time, you can end it at any time, and you see everything they do.
- Updates never remove or change your data. Before any update is released, it is tested to prove every record comes through unchanged.
- Every release is tested to confirm no one outside your company can reach your data.
How your data is protected
Read the Helpdesk DocsSee All FeaturesChangelogUpdatesBack to MountDev Ops