Many customer requests still arrive by email today. To the support or sales address, or to the personal mailbox of someone on the team. When several people handle them, it easily happens that two people answer one message and nobody answers another. Helpdesk in Modulo creates tickets from incoming emails, attaches the customer's replies to them and sends the team's replies back as ordinary email. The customer does not have to install anything or sign in anywhere.

How email gets into Modulo
Modulo receives mail in two ways:
- A connected company mailbox (IMAP). Modulo downloads mail from it every five minutes, even when nobody has their mail open.
- Receiving on the domain via Cloudflare Email Routing.
Each email account has a Helpdesk tickets toggle. So a personal mailbox does not have to create tickets, while a company one does. At the same time, Modulo never creates a contact, company or deal on its own from mail sent by an unknown sender.
In Settings → Email → tickets you set a rule for each address: whom the ticket is assigned to (a person or a team), which category it goes into, which tags it gets and, for an address shared by several companies, which company it belongs to. A ticket is also created from an email that arrived as a blind copy or by forwarding.
Automatic replies, out-of-office notices, bounce messages and loops between mailboxes do not create tickets. If you add an address to the rules later, you can process older emails (3 to 30 days) in the Process mail again section. The Show what will be created button first shows a preview, and you can uncheck unwanted messages.
Customer replies go into the same ticket
When the customer replies, Modulo matches the reply to the ticket by the number in the subject, for example [#96], or by the email thread. So the customer does not have to think about anything. It is enough that they reply to the message they received.
What happens to a reply to a closed ticket depends on whether you have already invoiced it:
- A ticket without invoicing is reopened.
- A ticket that has already gone through invoicing stays untouched. A new ticket "Follows up on #…" is created with the same requester and company, and a note is added to the old one.
You reply from Modulo, the customer gets an ordinary email
The agent writes the reply in the ticket detail. The writing field has three options: Customer, Team and Only for me. Neither a team note nor a private note goes to the customer. The default option is Team, so you have to choose a reply to the customer deliberately.
The reply to the customer is sent from the mailbox that is in the agent's signature. If the agent does not have one in their signature, it is sent from the company's default address. On the customer's side, the message is placed in the same thread. If it went through the company's own mailbox, a copy is also saved in the Sent folder, so you can see it in Outlook or webmail, and the whole conversation is also in the Email module.
Under the reply, the agent chooses a personal signature or the company's team signature, for example "Support". Automatic emails about a ticket status change also get the team signature.

Categories and assignee
Ticket categories have two levels, for example "Cash registers › eKasa", and can belong to a specific company. Each category can have a default assignee or team, a priority and keywords. Based on these, Modulo recognizes the category from the subject and text of the email. The category never overwrites an assignee the ticket already has; it only suggests one.
SLA deadlines for your customers
SLAs in Helpdesk are deadlines your company promises to its customers. This is not Modulo's commitment to you. In Settings → SLA levels you create levels with a response deadline and a resolution deadline, with a calendar of when you are contractually available (days, hours, holidays), with channels and a price. You assign a level to a company or a person in the Directory.
On the ticket card, a traffic light then shows how close both the response and the resolution deadlines are. When a deadline is approaching or has been exceeded, a notification arrives. The SLA report shows how quickly you respond and resolve, by month and by level. It can be printed to PDF for a specific client, or as an anonymous overview for prospects, without names and ticket numbers. Access to levels and reports is governed by separate permissions.
You can merge duplicate tickets
A customer writes once by email and an hour later again from a different address. In the ticket detail you choose Merge with another ticket, Modulo suggests likely duplicates and shows a preview. In the list, you can also merge several selected tickets at once.
The merged ticket becomes read-only, and the customer's replies via email, portal and chat go to the ticket that remained. Tickets of different customer companies cannot be merged. Only a role with the Merge permission may merge, which by default is held by roles with the permission to delete.
Website chat is a ticket too
A website that runs on Modulo can have the Pokec chat. When a visitor writes in it, a ticket is created in Helpdesk. The team replies from the Chat window in Modulo and opens the full ticket with the Ticket button. Whether a request came by email or through chat, it is handled in one place.
A task or a deal from a ticket
When a request needs fieldwork or several steps, you create a task from the ticket. The task due date is entered and displayed in the format DD.MM.YYYY HH:MM. A task without its own due date inherits the ticket's due date. If the request could turn into a job, the Create deal button creates a deal in CRM with the ticket's company and contact. We describe how tickets connect with the other modules in the article One system for the whole company.
Try it on your own mailbox
If you want to see how Helpdesk would process your support mail, write to us. You can find more about the module on the Helpdesk page.
Sources
- Modulo changelog, version 2.110.0 (September 9, 2026) — IMAP mailboxes every five minutes, tickets from IMAP and from Cloudflare Email Routing.
- Modulo changelog, version 2.161.1 (September 22, 2026) — the Helpdesk tickets toggle on an email account.
- Modulo changelog, version 2.173.0 (September 24, 2026) — SLA levels, traffic light and SLA report.
- Modulo changelog, versions 2.186.0 (September 27, 2026) and 2.232.0 (October 12, 2026) — notifications about approaching and exceeded SLA deadlines.
- Modulo changelog, version 3.4.0 (October 15, 2026) — replies through the company's own mailbox, copy in Sent, follow-up ticket, team signatures.
- Modulo changelog, version 3.5.0 (October 15, 2026) — ticket categories.
- Modulo changelog, versions 3.5.13, 3.5.14, 3.5.15 and 3.5.17 (October 16, 2026) — Process mail again, blind copy, Settings → Email → tickets.
- Modulo changelog, version 3.9.0 (October 19, 2026) — no contact, company or deal is created from unknown mail.
- Modulo changelog, version 3.19.0 (October 21, 2026) — website chats in the Chat window.
- Modulo changelog, version 3.22.0 (October 21, 2026) — separate permissions for SLA.
- Modulo changelog, version 3.37.0 (November 3, 2026) — automatic replies and bounce messages do not create tickets.
- Modulo changelog, version 3.40.0 (November 9, 2026) — merging duplicate tickets and the Merge permission.
- Modulo changelog, version 3.41.0 (November 12, 2026) — reply from the mailbox in the agent's signature, task due date DD.MM.YYYY HH:MM.
- Modulo changelog, version 3.42.0 (November 12, 2026) — a CRM deal directly from a ticket.
- Helpdesk module: modulocms.sk/modules/helpdesk; website chat: modulocms.sk/modules/pokec.
- Status as of Modulo version 3.52.0, verified November 15, 2026.





