Customer support is the foundation of a strong business-customer relationship. That is a reason to use the Magento 2 helpdesk tool to improve the customer support experience and reduce the number of inbound support tickets.
M2 Helpdesk extension is about solving clients issues on the basis of simple and user-friendly help desk interfaces. The module provides easy-to-use ticketing system and reliable support request management.
Ultimately, M2 Helpdesk extension offers many benefits both for users and support stuff.
Easy for customers:
- Submit, review and customize help requests.
- Handle tickets at Account page, Contact Us page or custom Helpdesk form.
- Check the ticket status as well as track the issues resolution process.
- Enjoy positive communication with a customer service team.
Easy for support team:
- Create tickets from the backend and reply to the tickets via email.
- Easily handle email storages, department and tickets in Magento 2 admin panel.
- Distribute different request types between different departments.
- Create email storage for 2-way communication channel within the support process.
- Free installation
- Activate up to 10 times
- All extensions $79
- Approved on Magento Marketplace
Magento Open Source Compatibility
Magento Community 2.4.9, Magento Community 2.4.8, Magento Community 2.4.7, Magento Community 2.4.6, Magento Community 2.4.5, Magento Community 2.4.4
Adobe Commerce Compatibility
Adobe Commerce 2.4.9, Adobe Commerce 2.4.6, Adobe Commerce 2.4.5, Adobe Commerce 2.4.8, Adobe Commerce 2.4.7
Installation instructions and manuals
General settings to manage the workflow
Helpdesk as Magento 2 support module comes with a robust feature set to help your support team accomplish issues resolution process easily and quickly. Through the module configuration, you can activate the cron task, set an email notification about ticket update both to admin and user, and even create a blacklist for email spammers. The extension provides the extended ticket forms where your customers could attach files of different extensions. Among other features, there is captcha on ticket submit form and permission to create a support ticket by guests.
Support ticket management system
The M2 Helpdesk extension enables automating issues resolution process with ticket management. The module includes a user-friendly interface to help you manage tickets and answer them from the admin interface. You can easily create tickets on the Order page, customer information page or from tickets listing interface. You can also reply to the tickets via email. The module allows your clients to create tickets from their account pages, Contact Us or custom Helpdesk form. The KnowledgeBase with quick answers based on predefined templates is coming soon.
A dedicated support service via departments
The option to assign a ticket the dedicated department helps to avoid forwarding a customer query again and again, and therefore save time in resolving the issue. The M2 Helpdesk extension enables the creating multiple departments and redirects the different types of requests between various groups of the support team. That way you manage customer support requests in the most efficient manner. The module comes with accurate email settings. All admins assigned to a department will receive email notification on every new ticket created or updated in this department.
Two-way email integration
M2 Helpdesk extension provides an easy way to set a two-way communication between customer and support team. The faster communication, the more efficient issue resolving process. The module includes email storage interface to help you create multiple storages and assign them to appropriate departments or stores. That way the customers' messages will be assigned to different tickets. The communicating will be continued through the ticket only. That allows keeping responses pulled in together in the same place. As well it makes it easier for admin to follow up with a customer.
Helpdesk 1.4.11
16th of October 2026- Security: Medium — strengthened message rendering while preserving template processing for trusted backend messages.
- Upgrade note: existing messages use conservative rendering behavior after updating.
- Security: Medium — strengthened attachment upload authorization, request validation, and abuse protection.
- Security: Medium — strengthened attachment access controls, link protection, content disposition, and preview isolation. Attachment link expiration is now configurable; reducing the lifetime also applies to existing links.
- Security: Medium — strengthened handling of staff replies received by e-mail. They remain internal by default, with a new option to deliver them to customers when required.
- Added: simplified secure guest access from customer notification links, including existing tickets.
- Security: Low — strengthened visitor-aware abuse protection, attachment inspection logging, and administrative access controls. Upload logging is now more resilient.
- Improved: inbound e-mail deduplication and fault isolation, so repeated messages do not create duplicate tickets and one failure no longer stops remaining pickup.
- Fix: improved attachment filename compatibility and hardened preview and uploader error handling.
- Fix: malformed attachment uploads now return consistent errors instead of server failures.
- Fix: the auto-close cron no longer notifies staff as if the customer had updated the ticket.
- Documentation: expanded guidance for securing inbound e-mail. Sender authentication must also be enforced by the mail infrastructure.
- PHP 8.4 compatibility: an implicitly nullable test parameter is typed explicitly.
Helpdesk 1.4.10
14th of October 2026- Security: High — strengthened ticket reply authorization.
- Security: High — strengthened security for replies received by e-mail.
- Improved: inbound email processing is more resilient, so one malformed message does not interrupt remaining mailbox pickup.
Helpdesk 1.4.9
8th of October 2026- Security: High — strengthened protection of helpdesk files.
- Security: High — strengthened validation of attachments submitted with tickets and messages.
- Improved: inbound email — the mailbox pickup is now skipped with a log message when the required mail library is not installed (Magento 2.4.8 no longer ships it).
laminas/laminas-mailis now a suggested package.
Helpdesk 1.4.8
18th of May 2026- Fix: show error message when attachment file is missing instead of throwing an exception (close #63).
Helpdesk 1.4.7
15th of May 2026- PHP 8.5 compatibility.
- Minimum PHP version requirement updated to 8.1
Helpdesk 1.4.5
2nd of April 2026Fixes:
- Fixed deprecated functionality for PHP 8.4 compatibility.
- Fixed file upload security: validate MIME type and content before saving attachments — rejects polyglot files, fake PDFs, and invalid images.
- Fixed safe default extensions fallback — returns
['gif','jpeg','jpg','png','txt','pdf']whenallowed_extensionconfig is empty.
Helpdesk 1.4.4
2nd of April 2026Fixes:
- Fixed false positive "Mass Assignment attack" security log entries on every legitimate admin ticket save — split forbidden fields into context-aware lists: frontend vs admin.
- Fixed
TicketDataFilterto use emptyFORBIDDEN_ADMIN_FIELDS(whitelist is the actual defense in admin context). - Fixed missing keys in
ADMIN_ADDITIONAL_FIELDSthat caused admin replies to never createTicketMessagerecords.
Helpdesk 1.4.3
2nd of March 2026Fixes:
- Fixed: Admin replies to tickets never created a
TicketMessagerecord and never sent email notifications to customers —swissup_helpdesk_ticket_message,http,website, andftpkeys were silently stripped byfilterAdminData()before reachingResourceModel. - Fixed: Saving an existing ticket from the admin panel failed with a "field is required" validation error — required-field check now runs only when creating a new ticket, not on every edit.
- Fixed: Enricher no longer overwrites
store_id,status, andprioritywhen editing an existing ticket. - Fixed: Removed rate-limit remaining count from the ticket creation success message.
Helpdesk 1.4.2
2nd of March 2026Fixes:
- Fixed: False positive "Mass Assignment attack" log entries on every legitimate admin message save —
message_idandemail_message_idare expected hidden form fields and must not be treated as forbidden (the whitelist filter already blocks them).
Helpdesk 1.4.1
2nd of March 2026Fixes:
- Fixed: Admin replies via AJAX form did not send email notifications to customers —
user_idfrom the backend auth session is now set before saving the message so theCustomerNotificationobserver fires correctly. - Fixed: Apply
MessageDataFilterwhitelist to admin AJAX message save to prevent mass assignment of forbidden message fields; forbidden field attempts are logged viaSecurityLogger.
Write Your Own Review