Create Accountor Login
Docs

Tickets and Replies

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.

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

How Email Becomes a Ticket

When a client emails one of your support addresses (Helpdesk Settings), Helpdesk files it on its own:

  • A reply joins its ticket. Helpdesk first matches the email to the conversation it answers. Then it looks for the ticket number, written as [T-12] in the subject or as the Reference line at the end of every reply you send, when the email comes from that ticket's requester. Last, it joins a ticket from the same sender with the same subject in the last 30 days.
  • Anything else starts a ticket. The new ticket gets the next number, the status Open, the sender as requester, and the address it came in on. If the sender's email matches a contact in CRM, the ticket links to that contact and their company.
  • A closed or waiting ticket opens again when the client writes.
  • Receipts: a new ticket gets a receipt from addresses set to send one, at once, at any hour, even while you are closed (Email and Business Hours). Every new ticket gets one, however many the same person sends. A reply to a ticket never gets one, even when it opens a closed ticket again: it is a conversation already going. When no receipt goes out, the ticket says why in a short line in its conversation: the sender did not pass the sender checks, it looks like an automatic email, receipts are off for that address, automatic replies are off for that person (No Automatic Replies), or the email was forwarded in by your team.
  • Sender not verified: when the sender's address fails the checks that prove it is really theirs, the ticket is still made and marked "Sender not verified". It never joins another ticket by number or subject, is never linked to a CRM contact, and gets no receipt.
  • Automatic mail (out-of-office replies, mail robots, bulk mail) joins the sender's latest ticket from the last week, never opens a ticket again, and never gets a receipt. So does a burst of three new tickets from one sender within an hour. This keeps two automatic responders from emailing each other forever.
  • A person replying through a support system: some support systems (such as the helpdesks vendors use) mark every email they send as automatic, their people's answers too. A reply like that still opens the ticket again and tells your team when it answers a ticket your team wrote on (by its email headers, the ticket number, or its subject) and its words are not a receipt or an out-of-office reply. A note in the conversation says so. It never gets a receipt or anything else automatic. Out-of-office replies, receipts, mail robots, and bursts stay automatic.
  • Files the client attaches are kept with their message, up to 20 files, 20 MB each, and 25 MB together. Anything past that is listed by name as too large to keep. Small images that are part of an email signature are kept but not shown.
  • Admin-only addresses: mail to an address set for owners and admins only makes a ticket that only owners and admins see, anywhere in the workspace.
  • The spam list: mail from a sender on it becomes a ticket in the Spam tab, with no receipt and no notice to the team (The Spam List).
  • Calendar notifications and read receipts (a meeting accepted, declined, tentatively accepted, updated, or canceled; an email with calendar content, such as an .ics file; or a notice that an email was read, such as a subject starting "Read:") are filed so nothing is lost, but closed at once, with no receipt and no notice to the team. A new one becomes a ticket that is already Closed (in the Closed tab), with a Not Applicable reason and a line saying why. One that answers a ticket (by its email headers or the ticket number) joins that ticket without opening it again, with a line saying so. Helpdesk reads the email itself (its subject, the kind of content, and its attachments), so it works however the email arrived.
  • Your team hears about it: the ticket's assignee (or everyone in its group), or whoever Helpdesk Settings names for unassigned tickets, gets an email about a new ticket, a reply, or a ticket opened again. The assignee, or everyone in the group, also gets a notification (Assigning Tickets). Automatic mail tells nobody.
  • Who it goes to: a new ticket is assigned to whoever its support address's New Tickets Go To names, a person or a group (Helpdesk Settings).
  • Mail from one of your own support addresses is never filed, and the same email is never filed twice.
  • Replies from the Requests page: a client who answers a request from the Requests page of their own workspace is filed exactly as if they had replied to your email, with the same rules for opening it again, receipts, files, and telling your team (What Your Clients See of Their Requests).

If Tickets or Messages are turned off, or a field your company made required cannot be filled from an email, the email is refused and the sender is told it could not be delivered. Nothing is changed.

Each record's history shows changes made by email as coming from email.

Forwarding a Client's Email

When someone on your team forwards a client's email to one of your support addresses, the ticket is the client's, not theirs:

  • The client is the requester: Helpdesk reads the original sender from the forwarded message, as Gmail, Outlook, and Apple Mail write it ("Forwarded message", "Begin forwarded message", or the From, Sent, and Subject lines), or from an email attached whole (Forward as Attachment). The ticket's subject is the original subject.
  • Linked in CRM: when the client's email matches a contact in CRM, the ticket links to that contact and their company.
  • The forwarded words show: the message is the client's, with their words, and the whole email shows as it looks.
  • A note says who forwarded it, with anything they wrote above the forwarded message.
  • No receipt goes to the client, since they did not write to your support address themselves. Later replies from the client join the same ticket as usual.

It counts as a forward only when it comes from the address of a person in your workspace and passes the sender checks, so a client cannot pass off an email as someone else's. A forward from anyone else is filed as their own email, with the forwarded words kept in its text.

Tickets from Your Website Forms

When your company also has Forms, a form can open a Helpdesk ticket for each submission (Building Forms). The ticket is from the person who sent the form, linked to their CRM contact and company, with their message, their other answers, and the page they sent it from, and your team hears about it as for any new ticket. It needs a support address set up here; until then the submission is kept in Forms and says why it is not a ticket. The receipt goes out only when the form sends no auto-reply of its own.

Opening a Ticket Yourself

To write to a client first, select New Ticket at the top of the Inbox (action helpdesk.tickets.new). Anyone who can reply to tickets can open one.

  • To: type a name to find a contact in CRM and select them, or type any email address. When you pick a contact, the ticket links to them and their company. When you type an address that belongs to a contact in CRM, it links to that contact the same way. A contact without an email address stays linked while you type one. Select Unlink to leave the contact off.
  • Cc (optional): anyone else to copy, separated by commas, up to 20. Never one of your own support addresses.
  • Subject and Message: the subject becomes the ticket's subject, and the message is the ticket's first email to the client.
  • Share Files: check it to send files with the first email, exactly as in a reply (Sharing Files): each file goes as a secure download link. Pick files from your Files app (action helpdesk.tickets.new.files finds them), or select Upload Files to add files from your computer, several at once, or drop them on Share Files. Each upload shows a bar until it is stored and is picked for the email. Send waits until every upload is done.
  • Status After Sending: Waiting on Customer at first, for when you need the client's answer. Choose Waiting on Us when your team still has work to do (the ticket opens again on its own after two business days; Waiting on Us), or Open to keep it open. The status is set the moment you select Send, even when the email waits for business hours, and Undo puts it back to Open. Waiting on Us is offered only when your Status field has that choice.

Select Send, and the new ticket opens. It starts like any new ticket: the next number, your first support address, and whoever that address's New Tickets Go To names (Helpdesk Settings), and your team hears about it as for any new ticket (never you). A line in its conversation says who opened it.

Files you upload in New Ticket wait for you, seen by nobody else, until you select Send. Then the ones you kept checked move onto the new ticket and stay there, on its Files card, like files uploaded in a reply (Files Added Before a Record Exists). Close New Ticket without sending, and the files you uploaded there are removed. Uploading needs the Files app and the right to open tickets.

The message goes out exactly like a reply (Replying): a minute to undo, your business hours (with Send Now), your company's email template, your sign-off, and the ticket's Reference line. Its subject is the ticket's own, without "Re:", since it is the first email. If the ticket was going to a group, it becomes yours, as when you reply. No receipt is sent, since the client gets your message itself. When the client answers, their email joins the same ticket, and every later reply works as on any ticket.

The Ticket Screen

Open a ticket from the Inbox to see its conversation as a mail thread: the newest message at the top and the oldest at the bottom (action helpdesk.ticket.get). The page opens at the top and never scrolls on its own, not when you open the ticket and not after you send a reply: a new message simply appears at the top. The thread is one centered column with a line down its left and a dot for each message: client messages, replies your team sent (an accent dot), internal notes in yellow, and events (such as a ticket closed automatically) as a short line between them. Each shows who wrote it and when, and a new day starts with a divider. Replies and emails still waiting to go out come first, with when they go.

  • Long threads. The newest five messages show, and all the older ones wait behind one row at the bottom, Show 12 Older Messages (the number is how many). Select it and they appear below, with the page staying where you were.
  • The header reads top to bottom: the back link (Inbox) on its own row, the ticket's subject, then one row with the status and flags (such as Admins only, Spam, Closed account, or Merged) followed by the ticket number, then the requester, email, and company on their own muted line, separated by |, then labeled pairs on one line: Assigned to, Project, Follow-ups (On, Done, Held, Off, or Stopped), and Attachments, the count of the ticket's attachments (select it to open the first), which wrap onto more lines on a phone. After a clear gap come Status (action helpdesk.status; Waiting on Us starts its two business days here), Assigned to (owners and admins), Close Ticket (or Reopen), and More. A long subject wraps to at most three lines, and the full subject shows when you hover it and is read in full by a screen reader. The ticket's Details are beside the thread on a wide screen and above it on a narrow one, below. Every record page's header follows the same order (The Record Header).
  • More opens a menu in place under its button, and closes with Esc or a tap anywhere else. It holds Merge (Merging Tickets), Move to Another Address (Moving a Ticket to Another Address), Move to Department (when your company has departments), Pass It On (when the ticket is assigned to a person), Edit Details (change any of the ticket's fields), and, last and in red, Mark as Spam (owners and admins). On a ticket in Spam, Not Spam takes its place, and a note at the top says the ticket is in Spam.
  • Details are always in view on a wide screen: a panel 340 wide on the right of the thread (when the page area is at least 880 wide, which is about 1100 of window with the menu closed) that stays in place as you scroll the thread and scrolls on its own when it is taller than the window. On a narrower screen, or a phone, the same facts are one Details row above the thread, closed to start, that you press to open in place and press again to close. There is no Details button and no slide-over, so the facts are never shown twice. It starts with the requester and their email, the company (select it to open it in CRM), who it is assigned to, the project, and Automatic Replies (On or Off for each address). With Projects too, each linked project is a link that opens it, with Link a Project (or Link Another Project) and Unlink (Linking a Project). More Details holds anyone also on the ticket, the contact, the number, mailbox, department, website, and when it was opened and last active. Below are Company (the company's people, websites, services, and open work; with no company on the ticket, one line that says so and Link a Company, which opens the Ticket Details form where you pick one), Files, and Team Chat. Each shows its title, then one line that says what it is, then its button on the left. Upload and shared links are at the end. Pairing codes are not on a ticket; they belong to records such as websites (Pairing Codes).
  • The reply bar is docked at the bottom of the window and floats over the conversation as you scroll. It starts as one bar that says Reply and who it goes to. Select it and the reply area opens in place. On a phone the bar is the full width of the page, sits above the bottom edge of the screen (and the home bar on a phone that has one), and the chat button moves up above it so nothing covers it. The reply area opens as a sheet from the bottom, with the tabs at the top and the send row at the bottom, and only the middle scrolls; the box for your words is tall enough to write in. Collapse it with the arrow at its top right or Esc: what you wrote stays until you send it. Inside are the Reply and Internal Note tabs, who the reply goes to (Who Gets a Reply) and the address it comes from, the box, Add to Reply, the business-hours note, and the send row.
  • Your replies show who they went to (To and Cc) under the name of the person who sent them.
  • Plain text messages are shown with their paragraphs, quoted lines set apart, and web addresses as links. Earlier messages quoted at the end fold away under Show Earlier Messages. Character codes some older messages were kept with (such as a code in place of an apostrophe or quotation mark) show as the characters they stand for.
  • An email follows your theme. A client's email is drawn in your light or dark theme, with no white block, and keeps its formatting (bold, lists, links, tables, quotes). Colors the sender chose that would be hard to read are changed to fit. An email that sets its own dark look is shown exactly as the sender made it, in both light and dark, so it is never turned over twice. A company logo in an email keeps its own color tile in both themes, and its sign-off, footer, and badges read in dark. View Original shows the email with the sender's own colors on a paper-colored panel, for a designed email such as a newsletter, and Follow Theme goes back. Show as Text shows only the words.

Attachments on a Ticket

Each file that came with a message shows on that message: a picture as a small thumbnail with its name, type, and size, and any other file as a chip with an icon, its name, type, and size. Select one to open it in a pop up on the same page, never in a new window. The pop up is one size for every file, with its title and "2 of 3" at the top, the file in the middle, and Previous, Next, Close, and Download at the bottom.

  • Pictures (PNG, JPEG, GIF, and WebP) and PDFs are shown in the pop up. Any other kind says "No preview for this type" and offers Download.
  • Previous and Next walk through all of the ticket's files in the order of the messages, and each is turned off at the ends of the list.
  • Download shows Preparing with a spinner until the file is ready, then saves it. The pop up stays open.
  • Esc closes the pop up. Opening or downloading a file is written in your Activity Log, as before.
  • The same files are listed under Files in Details, newest first, and open the same pop up.

The screen works with the Tab key, and Esc closes any pop up.

Emails as They Really Look

A client's email shows as they designed it, with its formatting, colors, tables, and the pictures placed in it, in a frame that grows to fit. The replies your team sends show the same way, as the client saw them (without the quoted history, which is already above). Messages brought over from the hub that were kept as HTML show the same way; ones kept as plain text show as formatted text.

  • Safe to open: nothing in an email can run or act on its own. No script ever runs in the frame, scripts, forms, and anything that could reach your workspace are taken out, and nothing from the internet loads unless you ask.
  • Pictures from the internet load by themselves when a ticket opens, so the sender can tell when the email was opened. If your company turns off Load Images in Emails Automatically in Helpdesk Settings, they are held back until you select Show Images on that message. Tracking pixels (pictures 0 or 1 pixel wide and high, or hidden) never load. Pictures sent inside the email always show.
  • Show as Text switches to the plain words of the email, and Show as Designed switches back. The plain words are what search, notices to your team, and AI agents use.
  • Links open in a new tab.
  • When you reply, the client's last message is quoted as plain words.

Replying

Write in the reply area and choose what happens to the ticket afterward in After Sending: Wait on Customer, Wait on Us, Close Ticket, or Keep Open. Then select Send (action helpdesk.reply). Enter starts a new line, as in any email; the reply goes only when you select Send. Your last choice is remembered on this device and starts as Wait on Customer; Wait on Us and Close Ticket are offered only when your Status field has those choices. An internal note has no After Sending and never emails.

  • Kept safely until it goes: the reply is kept by your workspace, not your browser, so you can leave the ticket, work on others, or close the page. It goes out on its own.
  • A minute to undo: the reply waits one minute, shown as "Sending in" with a countdown.
  • Business hours: when your company is closed (Business Hours), the reply waits until you open, shown as "Sends at" with the time, such as "Sends at 10:00 AM Thu". The reply box says so before you send.
  • Send now: when you are closed, check Send now (outside business hours) in the reply area to send it after the undo minute anyway. A reply already waiting for business hours shows Send Now (action helpdesk.reply.send_now); it then goes after its undo minute. The person who wrote it, or an owner or admin, can.
  • Undo (action helpdesk.reply.undo): until the reply goes out, even hours later, the person who wrote it can select Undo on the ticket, which puts the text back in the reply box.
  • It goes out from the address the ticket came in on (or your first address), to everyone on the conversation (Who Gets a Reply), with the subject "Re:" and the ticket's subject, so it lands in the client's existing conversation. It is in your company's email template, the same look as a receipt, ends with your sign-off (a small profile photo or your initials, your name, and your job title from Profile), quotes the client's last message, and says under it why it was sent, with the ticket's Reference line. Every web link in it carries campaign tags.
  • The ticket's status becomes Waiting on Customer (Wait on Customer), Waiting on Us (Wait on Us), Closed (Close Ticket), or Open (Keep Open) the moment you send, even when the email waits for business hours. Undo puts the status back. When it goes out, it appears in the conversation.
  • If the email service refuses it, it shows as Not sent with the reason. Nothing is tried again on its own; select Copy to Reply to put it back in the reply box.
  • A ticket needs a requester email to reply to, and your company needs at least one address in Helpdesk Settings.
  • If the reply does not go out, the person who wrote it gets an email saying so, with their reply.
  • Wait on Customer starts the automatic follow-ups when they are on (Automatic Follow-Ups); Keep Open, Wait on Us, and Close Ticket end them.

Send and Close

Send and Close (choose Close Ticket in After Sending, then select Send) sends your reply and closes the ticket in one step, for when your reply finishes the request. It shows for replies only, never for internal notes, and only when your Status field has a Closed choice.

  • The reply goes exactly as with Send: the undo minute, your business hours (it still waits for your opening, and Send Now still works), your company's email template, your sign-off, and the same people.
  • The ticket closes the moment you send, even when the email waits for business hours. The waiting reply shows Closes Ticket.
  • Closing checks come first. Send and Close makes every check Close Ticket makes before anything is kept or sent: you may change the ticket, your Status field has a Closed choice, and, with the close rule on, the ticket has a project or a Not Applicable reason. When one says no, nothing is sent, the ticket stays as it was, your reply stays in the reply box, and you see why. Fix it (for example, add a Not Applicable reason in Details) and select Send and Close again, or select Send to reply without closing.
  • The client gets only your reply. Closing a ticket never emails the client, so nothing about the close can reach them before or after your reply.
  • Undo puts the reply back in the reply box and the ticket back to the status it had, unless someone changed the status since. If the email service refuses the reply, the ticket opens again the same way, and you get an email saying the reply was not sent.
  • If the client writes before your reply goes out, the ticket opens again as usual, and stays open when your reply goes.
  • Automatic follow-ups and daily follow-ups stop, since a closed ticket waits on nobody, even when Follow Up Daily Until They Answer is checked.
  • The Activity Log says "Queued a reply on ticket 12 and closed it", and the ticket's history shows the status change as yours, the same as selecting Close Ticket.

Waiting on Us

Waiting on Us is the status for a ticket your team is working on behind the scenes, such as while you order a part, wait on a colleague, or finish a fix. It keeps the ticket out of Open without losing it: after two business days it opens again on its own, so nothing is forgotten.

  • Set it from the ticket's Status menu, choose Wait on Us in After Sending and select Send to send your reply and set it in one step, or choose it as Status After Sending in New Ticket. Send and Wait on Us shows for replies only, never for internal notes, and only when your Status field has a Waiting on Us choice. You cannot combine it with Send and Wait on Customer or Send and Close.
  • When it reopens: two business days after it was set, at the same time of day, by your company's Business Hours and their time zone. Days you are closed, such as weekends and holidays, do not count, the same way automatic follow-ups count. Set on Friday at 3:00 PM, it opens again on Tuesday at 3:00 PM. Set after you close, it opens again at your next opening after that time. With a schedule that is always open, every day counts.
  • The ticket shows when, under its header, in your company's time zone, such as "Reopens Tuesday, October 20, 3:00 PM", with who set it. The Inbox's Waiting on Us tab shows it on each row too.
  • When the time comes, the ticket's status becomes Open, a note in its conversation says "Opened again automatically: it was Waiting on Us for two business days.", and whoever it is assigned to hears about it in their notifications ("Opened again"), the same way they hear about a reply. A group's ticket tells every member; an unassigned ticket tells whoever hears about unassigned tickets (Assigning Tickets). The client is never emailed.
  • Changing the status first stops it: choose any other status (or Close Ticket, or reply with another After Sending choice) and the ticket never opens again on its own. Choose Waiting on Us again, or select Send and Wait on Us again, and the two business days start over from then.
  • When the client writes back, the ticket becomes Open at once and the timer stops, since they are waiting on you now. A client's reply never makes a ticket Waiting on Customer by itself. An automatic email, such as an out-of-office reply, leaves it as it is.
  • Undo on a Send and Wait on Us reply, or on a New Ticket's first email, puts the status back, and stops the timer, unless someone changed the status since.
  • Status changed another way, such as in Details, by an automation, an AI agent, or the API, is caught up in moments by Helpdesk's background work: Waiting on Us starts its two business days, and any other status stops them.
  • Your clients see a ticket that is Waiting on Us as Open on their Requests page, never as waiting on them (What Your Clients See).
  • Every company has the Waiting on Us choice, including companies that had Helpdesk before it came. It is added once, after Waiting on Customer, and your Activity Log says so. Rename or remove it on Helpdesk's Settings page like any choice, and it stays the way you left it. Without it, Send and Wait on Us does not show.

Who Gets a Reply

A reply goes to everyone on the conversation, like Reply All in an email program. The line above the reply box shows them: To the person who wrote last, and Cc everyone else.

  • Everyone on the conversation is the requester, the requesters of tickets merged into this one, everyone who wrote on the ticket, everyone their emails were sent to or copied, and anyone your team added to an earlier reply. When Brian writes in and Derek answers, your reply goes To Derek with Brian copied.
  • Never included: your own Helpdesk addresses and their forwarding addresses, automatic senders (such as noreply and mailer-daemon addresses, unless that is the requester), and anyone on your spam list. An automatic email, such as an out-of-office reply, does not make its sender the To.
  • Take someone off: select the x beside their address. Taking off the To moves the first Cc up.
  • Add someone: select + Add, type the address (the people on the conversation are suggested), and select Add or press Enter. Esc closes it. You can copy up to 20 people.
  • Your changes stay until you send. Undo puts the reply back with the people you chose, and a waiting reply shows who it goes to.
  • Tickets from before Helpdesk 0.9.0 still reach everyone who wrote on them; who was copied on those older emails was not kept.
  • Receipts go only to the person who started a new ticket. Automatic follow-ups go to the people the waiting reply went to.

Add to Reply

Add to Reply, beside the send buttons in the reply box, opens a short list of extras to send with the reply. Check any of them; the button shows how many are on, and each one shows by name under the reply box. Select the button again, press Esc, or click anywhere else to close the list. They are cleared once the reply is sent, and Undo puts them back with the text.

  • Collect Files: a link where the client can send you files (Upload Links).
  • Share Staging Access: the link and login of a staging site, so the client can review your changes (Sharing Staging Access).
  • Share Files: a secure download link for each file you pick (Sharing Files).
  • Follow Up Daily Until They Answer: when you are waiting on a vendor or an outside support team, a short follow-up each day until they actually answer (Daily Follow-Ups Until They Answer). It starts checked while daily follow-ups are on, or paused because they answered, so your next reply keeps them going or starts them again. Uncheck it to stop them with this reply.

Sharing Staging Access

When you have made changes on a staging site (a private copy of the client's website), check Share Staging Access in Add to Reply to give the client its link and login in the reply, so they can look over the changes before they go live.

  • Where the login comes from: a Login field, such as Staging Access on a task in Projects (Login Fields). Owners and admins add one in Projects' Settings, under the module's fields. A login is offered when it has a web address and a saved password.
  • The ticket's project first: when the ticket is linked to a project (Linking a Project), or to one of its tasks, the list shows that project's tasks (and the project itself) with a filled-in login. A ticket not linked yet whose old Project code, such as CWSA-1042, is a project's or task's code works the same way. Otherwise, or to find another one, search by project or task name or code.
  • What you see: each login shows its task, its project, the web address, and the user name, with the password as dots. Choose one (action helpdesk.staging.options finds them).
  • Who can share: only the people who can see that login's password with Show and Copy: owners, admins, and people who can change the task. Others do not see it in the list, and sharing it is refused.
  • What the client gets: under your words, a box headed Staging Site for Review with the link, user name, and password, and one line saying it is a private preview of the changes and their live site is unchanged. The password is the one saved on the task when the reply goes out.
  • Logged: each share is written in the Activity Log, like a Show or Copy, as "Shared the Staging Access login for" the task "on ticket" and its number.
  • Where the password is kept: only on the task, sealed with your company's key, and in the email the client received. The waiting reply keeps only which login to share. The copy of the reply in the conversation shows the link and user name, with "(sent in the email, not kept here)" in place of the password, so it never reaches search, the history, exports, notices, or webhooks. If the login is removed before the reply goes out, the reply shows as Not sent.
  • People only: AI agents, API keys, and sign-ins marked as AI assistants never share staging access.

Anyone in your company can reply, add notes, move messages, turn off upload links and shared file links, and stop daily follow-ups. AI agents never reply, because a reply emails the customer and nothing emails a customer without a person. An AI agent can read tickets, add internal notes, move messages, turn off upload links and shared file links, and stop daily follow-ups, as the person who connected it. Assigning and the spam list stay with owners and admins.

Sharing Files

Check Share Files in Add to Reply to send files with a reply, or in New Ticket to send them with a ticket's first email (Opening a Ticket Yourself). Each file goes as a secure download link, never as an attachment, so no file is too large to send. A reply can be just the files.

  • Pick files (action helpdesk.share.options finds them): files on this ticket come first (what the client sent, and files kept on the ticket), then your newest files in the Files app. Search by name to find another. Pick up to 10.
  • Upload Files adds new files to this ticket, with a bar for each, and picks them for the reply. You can also drop files on Share Files. The files are kept on the ticket, encrypted with your company's own key (Files). It shows when the Files app is added and you can change the ticket.
  • Only files you can see: you can share a Files app file only when you can see its folder or record, and a ticket's file only from its own ticket. Anything else is refused.
  • What the reply keeps: only which files to share, never the files. Undo gives your picks back. If a file is deleted before the reply goes out, the reply shows as Not sent, and no link is made.
  • What the client gets: under your words, "Files for you", with each file's name as a link and its size, and the date the links work until. A link works for 30 days at first (change it in Helpdesk Settings) and opens the file with no sign-in.
  • The conversation shows which files were shared, by name and size, never the links.
  • Shared Files beside the conversation lists each file shared from the ticket, who shared it and when, how many times it was downloaded, and until when its link works. Turn Off ends a link at once (action helpdesk.share.off).
  • Downloads count toward File downloads on Usage. Each download of a Files app file is written in the Activity Log, saying it came through a link shared in Helpdesk.
  • People only: AI agents never share files, because a reply is always a person's. An AI agent can turn off a shared link.

Linking a Project

When your company has Projects too, each ticket can be linked to the projects it is about, so the ticket and each project show each other. A ticket can link to several projects, such as a request that touches both a website and a store.

  • Link a Project: in Details, select Link a Project. The picker lists your open projects, the ticket's company's first. Search by project name or code, such as CWSA-1042, to find any project, or one of its tasks (action helpdesk.link.options). Select Link beside one (action helpdesk.link.set). Choosing a task links its project too.
  • Create Project: beside Link a Project, Create Project makes a new project from the ticket. A small dialog starts filled in from the ticket (action helpdesk.project.draft): the name (the ticket's subject), the company and website (the ticket's), the description (the client's first message as plain text, with a "From ticket T-123" line and a link back to the ticket), and the project manager (the ticket's assignee when it is a person, else you). Change anything, then select Create Project (action helpdesk.project.create): the project is made in Projects as you, the ticket is linked to it beside any other projects, and a note on the ticket says "Project created:" with its name. Details then shows the new project as a link that opens it. The button shows only with Projects added, for people who may add projects in Projects and change the ticket.
  • Several projects: once a ticket has a project, Link Another Project opens the picker again and adds the one you choose beside it, up to 20. Each project links once, with at most one of its tasks, and a task is always in its own project; anything else is refused. Choosing a task of a project already linked sets that project's task, and choosing the project alone takes its task off. With no search, the picker offers the open tasks of every linked project.
  • In Details, each linked project shows as a link (its name and code) that opens it in Projects, with its task below it when there is one, one under the other. With more than one, each has its own Unlink, which takes that project and its task off; with one, Unlink sits beside Link Another Project (action helpdesk.link.remove, with the project, or without one to unlink them all).
  • Who: anyone who may change the ticket can link it, and only to a project or task they may see in Projects. Someone who may not see a linked project sees "A project you cannot see", never its name, and their changes leave that link as it is.
  • On the project: the project's page in Projects lists its tickets (Projects and the Home Page), with Link a Ticket. It shows only the tickets each person may see, so admin-only tickets stay with owners and admins (actions helpdesk.project.tickets and helpdesk.project.find_tickets), and the Projects home counts each project's open tickets (action helpdesk.project.counts). A ticket linked to two projects shows, and counts, on both.
  • Where the links are kept: the first project is in the ticket's Linked Project and Linked Task fields, which link to the records themselves, and each further one is in More Linked Projects, a list such as [{"project":12,"task":40}]. A ticket linked before keeps its link exactly as it was. When the first project is unlinked, the next one moves up into Linked Project. Search, exports, the API (API Keys), the history, webhooks, and automations see all of them on the ticket, and a change made there (by an API key or an automation) follows the same rules. Two events start webhooks and automations, once for each project: helpdesk.ticket.project_linked (a project is linked, or a linked project's task changes) and helpdesk.ticket.project_unlinked (a project is taken off). A project moving up is neither.
  • Turned off: with More Linked Projects turned off in Helpdesk Settings, a ticket keeps one project, and linking another replaces it.
  • The old Project field: before linking, a ticket's Project was typed text, such as CWSA-1042. That text stays as it was. A ticket whose text names a project or task works as linked for the close rule, Share Staging Access, and the Inbox search until it is linked. Link Old Project Codes in Helpdesk Settings links them all at once (Helpdesk Settings). When you unlink a project, or change its task, old text naming the project or task taken off is cleared with it (the history keeps it).
  • What uses every link: the close rule counts any linked project; Share Staging Access offers the staging logins of every linked project you may see; the Inbox search finds a ticket by any linked project's name or code.
  • A project or task with linked tickets cannot be deleted until they are unlinked, so no ticket is left pointing at nothing.

AI agents and API keys can find, link, and unlink projects as the person or key they act for, with the same checks.

Checklists and Approvals

A ticket a connected system opens for you can carry one checklist at the top (Helpdesk 0.27.0), such as a new managed website's onboarding from Website Onboarding. The system keeps it up to date in place: each step shows To Do, Waiting, Needs a Person or Needs the Client (with what to do), Done, Not Needed, or Failed, and the card says how many are done and when it was last updated. Instead of a note for every step on every pass, a short internal note is added only when a step is done or needs a person or the client.

When the system needs a change approved, such as DNS records, it shows under Changes to Approve with what it would change (now and after). Owners and admins see Approve and Decline on a change waiting for approval, and Roll Back on one that was applied (permission helpdesk.approve; action helpdesk.approval.decide). Each one asks you to confirm first. The decision is kept with who made it and when, the system makes exactly that one change, and the checklist shows what happened. A declined change is not asked again; the step is left for a person to do by hand. Members see the changes but cannot decide them, and AI agents and API keys never can.

A step can also offer Show Login, such as a website's Preview Address while the site is still behind its login (permission helpdesk.approve; action helpdesk.checklist.reveal). Only owners and admins see the button. The workspace records who asked and when, gets the login from the system that keeps the checklist, and shows it in its own pop up with Copy. The login is never stored on the ticket. AI agents and API keys can never use Show Login.

Internal Notes

Select Internal Note, write it, and select Add Note (action helpdesk.note). Notes are for your team only and are never emailed.

Assigning

Owners and admins choose a person or a group in Assigned to (action helpdesk.assign), or Not Assigned. Groups are made on the Staff page's Groups tab (Groups). The person, or everyone in the group, gets an email and a notification, and from then on they alone hear about the ticket's replies. An admin-only ticket can be assigned only to an owner or admin, or to a group, whose owners and admins alone hear about it. Assigning yourself sends nothing.

When someone sends a reply on a ticket assigned to a group, the ticket becomes theirs, and its history shows the change. Notes never change who has a ticket. Undoing the reply gives the ticket back to the group, unless someone assigned it since (Assigning Tickets).

Only people are offered: never an AI agent, an API key, or a sign-in marked as an AI assistant on the Staff page (Staff and Roles), and assigning a ticket to one is refused. When two people share a name, their email address shows beside it. AI assistants also never get Helpdesk's emails about tickets.

Moving a Message to a New Ticket

When a client writes about something new on an old ticket, select Move to New Ticket on their message (action helpdesk.split). Give the new ticket a subject, or keep the message's own. The message, its files, and any later replies to it move to a new ticket with the next number and the same client, address, and assignee. A note on each ticket says where it went. A ticket's only message from the client stays where it is.

Moving a Ticket to Another Address

Each ticket belongs to one of your support addresses, the one shown as Mailbox in Details. When a ticket came in on the wrong one, such as a billing question sent to your support address, select Move to Another Address in the ticket's header (action helpdesk.ticket.move). Choose the address in Move To and select Move. The ticket stays open on your screen, and the Inbox updates on its own.

  • Replies come from the new address from then on, with its sender name, and so do follow-ups and daily follow-ups. A reply or follow-up still waiting to go out goes from the new address too. Follow-ups keep their schedule.
  • The ticket number stays, and so does the whole conversation. When the client answers an earlier email sent from the old address, or writes to the old address with the ticket number, their message still joins this ticket.
  • Who has it: the person or group assigned to the ticket keeps it. A ticket nobody has goes to whoever the new address's New Tickets Go To names (Helpdesk Settings). Check Assign by the new address's rule to give it to them even when someone has it now. The dialog says where the chosen address sends its new tickets, and the checkbox is off for an address that sends them to nobody. A ticket in Spam is never assigned.
  • Who hears about it: whoever now has the ticket gets an email and a notification, as when a ticket is assigned to them. Never the person who moved it, and never anyone when who has it stays the same.
  • The client is never emailed about a move.
  • From the Inbox, the pop up closes when you confirm, and each moved ticket's row frosts over with Moving while it works. A ticket that could not be moved says why on its own row (Progress on a Row).
  • The conversation says so in a short line, such as "Moved from support@example.com to billing@example.com by Pat.", and the ticket's history shows the change.

Addresses for owners and admins only are theirs alone: only owners and admins see them in Move To and can move a ticket to or from one. A ticket moved to one becomes admin-only, and one moved from one to an address everyone sees is no longer admin-only; the conversation says which. A ticket assigned to someone who is not an owner or admin cannot move to an address for owners and admins until an owner or admin has it (or the checkbox gives it to one).

Anyone who can reply to tickets can move the ones their role lets them change. A merged ticket cannot move; move the ticket it went into. To move several tickets at once, check them in the Inbox and select Move. AI agents and API keys can move tickets too, with the same checks, and the history marks what they did.

The Close Rule

When Close tickets only with a project or a Not Applicable reason is on in Helpdesk Settings (it is off at first), a ticket can be closed only once it is linked to a project or task (Linking a Project), has an old Project code (such as CWSA-1042), or has a Not Applicable reason of at least 8 characters in Details, or is marked as spam. The ticket screen says so until one is added. The rule applies to Close Ticket, the Status menu, and Send and Close, which then sends nothing until the ticket can close (Send and Close). Imports of closed tickets are never blocked.

The Account Beside a Ticket

A ticket for a CRM company shows that account beside it: its people with their email and phone, its websites, its services, and its open projects and tickets. For someone whose permission group protects client records, opening the ticket is what opens the account to them (Working Access), and prices show only to people who may see them. See Client Protection.

Ask Us Anything

We’d love to hear from you!