Create Accountor Login
Docs

Helpdesk Settings

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

MountDev Ops Helpdesk documentation | Updated November 21, 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.

Where to Find Them

Owners and admins find Helpdesk Settings on Helpdesk's Settings page, the last item of Helpdesk's menu (action helpdesk.settings.get). Departments is its own section on the same page, after Helpdesk Settings (Departments). The same page lists Helpdesk's modules and fields, with their icons, and Helpdesk's roles (Apps).

Support Addresses

Each address is an email address your clients write to, such as help@yourcompany.com. Email to it becomes tickets, and replies go out from it.

  • Many addresses: there is no limit on how many you add. The list shows the count, pages 25 at a time, and has a search, and up to 200 new addresses can be added a day to protect your account. Add Address is three steps and Add Several takes up to 50 lines at once. All of it is on Support Addresses (actions helpdesk.inboxes.list and helpdesk.settings.get).
  • Add Address or Change (action helpdesk.inboxes.save): the address, the sender name replies come from (such as your company name), Who sees its tickets (Everyone, or Owners and admins only, for addresses such as legal and HR), New Tickets Go To (Nobody, a person, or a group, below), and whether to send a receipt when a ticket starts.
  • New Tickets Go To: every new ticket from the address is assigned to this person or group the moment it arrives, so it shows in their notifications and in their My Tickets or My Groups (Assigning Tickets). Nobody is the start. An address for owners and admins only can send its tickets only to an owner or admin, or to a group (whose owners and admins hear about them). If the person's access is turned off, or the group is removed, new tickets arrive unassigned and the address says the choice no longer works. Spam is never assigned. Each address in the list shows where its new tickets go.
  • Receipt text for this address: an address can have its own receipt wording, in its Change form; left empty, it uses the receipt text in Change Settings, the same for every address. The address's line says Sends its own receipt when it has one.
  • Remove (action helpdesk.inboxes.remove): mail to that address is refused from then on. Its tickets and messages stay exactly as they are.
  • A Zoho Desk inbox (Zoho Desk in Helpdesk) from a connection saved earlier is listed here too, marked From Zoho Desk. Importing from other services is coming later, so it brings in no new tickets, and it goes with its connection: Connection opens it in Settings, Connections, instead of Remove.
  • Each address gets its own forwarding address (made as soon as the address is saved, and checked again once a day), so mail reaches your workspace without asking anyone to set it up (see Forwarding Your Mail, below). The address must also be verified for sending before replies can go out from it.
  • Bringing them over: (up to 500 addresses in one call, and any number of calls) addresses, ticket numbering, and Our Email Domains from another system come in with one step (action helpdesk.settings.import), which Import From File uses when the file carries them. It adds missing addresses, updates who sees each one's tickets and whether it sends receipts, keeps any sender name set here, sets the ticket number start only while none is set by hand, and sets Our Email Domains only while none are set here, and turns automatic follow-ups on once, only while they are off. Running it again changes nothing, and never turns follow-ups back on after someone here turned them off.
  • Private addresses: a person's own email address (such as jane@yourcompany.com, not a shared one like help@) can be a private address, shown in the list as Private to that person. Only that person sees its tickets and their messages, owners and admins included, and nobody else is told about them. It is set up the first time mail for that person reaches Helpdesk through a connected system that says whose address it is, sends no receipt, and assigns each new ticket to its owner, who hears about it in their notifications only (never by email, which would only echo it back to the same person). A private address cannot be changed, and its tickets cannot be moved to another address; they can be merged only with another ticket private to the same person, or by that person into a shared ticket after a confirm (Merging Tickets); Remove stops taking its mail, and its tickets stay private.
  • Mail from your own system to a person: a sign-in code or link is filed in the person's private address as automatic email: no receipt, and nothing is ever sent back. This holds even when it comes from one of your shared addresses, such as help@. The same email arriving twice (its Message-ID already here) is never a second ticket. Each one starts its own ticket, so a new code is never hidden in an old ticket. A notice from your own system (such as an email saying items are waiting in the app) is filed closed with a note, and nobody is told, so one notice never sets off another.
  • Mail for a person nobody here has: it goes to your first address for owners and admins only, never a shared one, and the ticket says which address it was sent to.
  • Email history of brought-in tickets: An import file can also bring each old ticket's email ids (action helpdesk.threads.import). A client's reply to any old email, including a receipt or a reply the team sent from the old system, then joins the ticket it belongs to instead of starting a new one, and replies sent from here thread under the old conversation in the client's email program. Rows whose ticket is not here yet are listed and skipped. Running it again changes nothing.

Forwarding Your Mail

Helpdesk Email Forwarding, in Helpdesk Settings (action core.inbound.forwards), shows a forwarding address for each of your support addresses, such as 3f9c0a7d12e4b6a8-52697665@in.example.com. Each one is unique to that address in your workspace and cannot be guessed.

  1. In your mail host (Google Workspace, Microsoft 365, or any other), set the support address to forward its mail to its forwarding address. Copy puts the forwarding address on your clipboard.
  2. Some mail hosts first send a confirmation code to the forwarding address. It arrives in Helpdesk as a ticket, so you can copy the code from there.
  3. Send a test email to your support address. The address shows Waiting for First Email until a forwarded message arrives, then Receiving, with when the first and last emails came in and how many have. Check Again looks again straight away.

Forwarded mail is taken in exactly like mail sent to the support address itself: it joins its ticket or starts a new one, with receipts as you set them. Replies still go out from your own support address. Removing an address stops its forwarding address too.

Moving one mailbox at a time. Nothing changes for a support address until you point it at its forwarding address, so you can move your mailboxes one by one and check each with a test email. Until you do, that address keeps working the way it does now. Your workspace is the only place that holds the mail you receive here: it is never kept anywhere else on the way in.

  • If your workspace cannot take a message right now, the sending mail server is told to try again later and delivers it again on its own. Nothing is lost and nothing needs your attention.
  • If an address does not accept mail (a forwarding address that was removed, one with a wrong code in it, or one for a support address you deleted), the sender gets a short reply saying so, and nothing is filed in your workspace.
  • Each workspace sees only its own mail. A forwarding address works only for the workspace it was made in.

Ticket Numbers, Receipt, and Signature

Delete Spam After is its own button on the Settings page, next to Change Settings. It opens a small pop up with one choice (7, 14, 30, 60, or 90 days, or Never) and Save, and the Settings page says the current number of days (The Spam List). It saves only that setting (action helpdesk.settings.save), and it is not part of Change Settings, so the setting has one place.

Change Settings (action helpdesk.settings.save) holds:

  • Ticket numbers start with: a letter, then up to 11 letters or digits, ending with a dash, such as HELP-. Leave it empty to follow your Company Code on Settings, Numbering (ACMET- with the code ACME), or T- while you have no code (Numbering). The box shows that start, faded, while it is empty. New tickets continue after the highest number already used with that start, including imported tickets, and a number is never given out twice. A start another kind of record already uses is refused. Helpdesk Settings shows the next ticket number. When you change it, Existing Records offers Also update existing tickets, with how many and an example (T-1042 becomes ACMET-1042); each ticket keeps its old number, and replies quoting the old number still join it (Updating Existing Records).
  • Receipt: the text of the receipt. It goes out in your company's email template, under the headline "We Have Your Request", starts with "Hi" and the client's first name, and ends with the address's sender name, the client's subject, the ticket's Reference line, and a line saying why it was sent (the client sent a request to that address). Every new ticket gets one, however many the same person sends.
  • Signature: one short extra line for the sign-off of the person replying, such as pronouns or a tagline (The Sign-Off). The sign-off already has their photo, name, and job title, and the template has your company name, phone, email, and website, so anything here that repeats those is left out. Under the box, a preview shows how your replies look, signed by you, and changes as you type.
  • Our Email Domains: your company's own email domains, separated by commas (empty at first). A reply never copies an address on these, team members included, so old or other company addresses stay off client emails. Addresses on the domains of your Helpdesk addresses and your team are left off too, except team members themselves.
  • Who hears about unassigned tickets: Owners and admins (the start), Everyone, or Nobody. They get an email about each new ticket, reply, and ticket opened again, with a link to it. An assigned ticket goes to its assignee alone, or to everyone in its group, and admin-only tickets only ever go to owners and admins.
  • Days an upload link works: from 1 to 60 (14 at first).
  • Days a shared file link works: from 1 to 365 (30 at first). Each file shared in a reply goes as a secure download link that works this long (Sharing Files).
  • Close tickets only with a project or a Not Applicable reason: the close rule (Tickets and Replies), off at first. A linked project or task counts, and so does an old Project code.
  • Show each address under its department in the Inbox: lists each department's busiest addresses (up to 8) under it in the Inbox's list of views, so a company with many addresses is never shown them all. The rest are found with Go to a View (The Inbox). Off at first.
  • Suggest merging matching tickets: when a new ticket arrives from a requester with an open ticket of the same subject, the new ticket offers to merge (Merging Tickets). On at first.
  • Load images in emails automatically: the pictures in a client's email show as soon as a ticket opens, with no click. Turn it off to hold them back until a person selects Show Images on that message (Tickets). Tracking pixels (pictures 0 or 1 pixel wide and high, or hidden) never load, with this on or off. On at first.

Your time zone and business hours are set once for every app, on Settings, Business Hours. Helpdesk sends replies and automatic follow-ups during those hours and writes dates in emails in that time zone. A time zone a company set here before Business Hours existed is still used until Business Hours are saved.

Follow-Ups sets the automatic follow-ups (Automatic Follow-Ups), Daily Follow-Ups sets the wording, time of day, and weekends of daily follow-ups until they answer (Daily Follow-Ups Until They Answer), Spam List shows the spam list (The Spam List), and Automated Senders lists the senders whose email is filed Closed, out of your ticket queue (Automated Senders).

Ask Us Anything

We’d love to hear from you!