Help Desk MX for Magento 2

View Demo

A help desk built into your Magento admin. Customer emails and contact forms become tickets, routed to the right department and agent, with workflow rules, satisfaction surveys, reports and AI tools. Every ticket shows the customer's orders and earlier tickets.

  • Turn emails into tickets from Gmail, Microsoft 365 and IMAP
  • See the customer's orders on every ticket
  • Automate routing and escalation with workflow rules
  • Message third parties from a ticket
  • Get desktop notifications about new tickets and replies
  • Create custom fields
  • Manage access permissions
  • Evaluate customer satisfaction with surveys in reply emails
  • Track agent performance with built-in reports
Marketplace Approved
Hyvä
Magento Cloud
GraphQL
WCAG
Mage-OS
Compatible with:
Community:
2.3.* - 2.4.9
Enterprise:
2.3.* - 2.4.9

What does Help Desk MX do?

Help Desk MX is a help desk built into your Magento admin. Customer emails and contact forms become tickets, each ticket goes to the right department and agent, and workflow rules keep it moving until it's solved. Our own support team has handled 200,000+ tickets in Help Desk MX since 2014.

  • Turn emails into tickets from several mailboxes: Gmail and Microsoft 365 connect with OAuth, any other mailbox over IMAP or POP.
  • Route tickets to departments and agents, and set who can see and manage which tickets.
  • Reply faster with quick responses, and keep internal notes your customer never sees.
  • Write to a shipping company or supplier from the ticket, in private or public mode.
  • Automate routing, status changes, escalation and auto-close with workflow rules.
  • Ask for a rating in every reply email and see satisfaction per agent.
  • Track first reply time, resolution time and solved tickets for each agent.
  • Work tickets with AI: draft replies, summarize tickets and update statuses through AI Copilot or any assistant connected via our MCP server.
  • Connect other systems with the REST API and GraphQL, and run the storefront on Hyvä.

Tickets that already know the order

Because the help desk lives inside Magento, every ticket is linked to the customer's account. Your agent sees who is writing, the order the question is about and every earlier ticket from the same customer, without switching to another tool.

  • Customers pick the order their question is about right in the ticket form.
  • The Tickets tab on the admin order page and on the customer page lists every related ticket, and you can open a new ticket for an order from there.
  • The Other Tickets tab on a ticket shows the customer's full history, whatever the status.

There is nothing to sync with an outside service and no monthly fee per agent: tickets, customers and orders stay in your own database.

Help Desk MX at a glance

What your team gets

Every customer conversation in one queue inside Magento, routed to the right person and moved along by rules. It's the help desk our own support team works in every day.

What it takes to start

Statuses, priorities and two departments are created on install, so on day one you connect a mailbox and add your agents. Tailoring routing and rules to your process takes longer, and free installation and configuration are part of the offer.

How you'll know it works

Built-in reports show first reply time, resolution time, solved tickets and satisfaction for each agent, so you can see the change week by week.

Support for Guest Users

Any visitor can reach your support team, with or without a customer account. There are four ways to send a request:

  • The Contact Us tab, shown on every page at the side you choose.
  • The Contact Us page form.
  • The Help Desk section of the customer account.
  • An email to your support address.

Forms built with Form Builder can open tickets too.

Set your working hours and holidays, and the contact form, popup and My Tickets page show customers whether your team is online right now.

Help Desk MX contact form for guest users

Easy-to-Use Customer Interface

The ticket form asks only for the necessary fields, so a customer sends a request in a minute.

If you turn these options on, customers can choose a priority and a department for a new ticket.

Customers can attach files to tickets, which helps when they want to show your team the problem in a screenshot.

Customer ticket list in the account

Simple Ticket Management for Customers

Customers see all their tickets in their account. Replying or closing a resolved ticket takes a second.

The full ticket history is on the same screen, so nobody has to scroll through old emails.

Customer ticket view with message history

Connect your Mailboxes

Connect your support mailboxes, and Help Desk MX checks them on a schedule and turns new emails into tickets. Replies to a ticket email are added to the same ticket.

Gmail and Microsoft 365 (Exchange Online) connect with OAuth, with step-by-step setup instructions in the gateway form. Any other mailbox works over IMAP or POP.

For example, your store has Sales, Billing, Returns and Technical departments, each with its own email address. Connect each address to its department, and every email sent to it becomes a ticket in that department's queue.

Neither you nor your customer has to log in to the store to reply. Answer from your email client, and Help Desk MX adds the message to the right ticket.

Email gateway settings in Help Desk MX

Clear Backend Interface

The ticket grid shows the most important details of every ticket at once.

Filter tickets by any field, such as creation date, status, priority, store view or agent, or find them by any keyword with the search field.

Merge duplicate tickets, change status, owner or department for many tickets at once, and move them to the archive or spam folder.

Admin ticket grid

Choose which columns the grid shows, from the customer name, department and last replier to the number of replies and the order.

Desktop notifications tell agents about new tickets, new messages and assignments. When two agents open the same ticket, each sees who else is there and who is typing a reply, and unsent replies are saved as drafts.

Ticket grid with custom columns

Fully Featured Ticket Cards

The General tab shows the key information on a ticket and lets the agent act at once:

  • reply to the customer;
  • set the ticket status and priority;
  • assign the ticket to another department.

The customer is the default recipient, but the agent can send the message to a third party instead. For example, you need to check delivery options with a shipping company. Help Desk MX lets you exchange messages with any third party in private or public mode.

Another example: you need to ask a colleague about a technical detail. Choose Internal Message, and the customer won't see the note.

The Other Tickets tab lists every ticket this customer has created, whatever its status.

Admin ticket card

The Additional tab shows the ticket history and other details, such as the channel the ticket came from. This helps if you measure how customers contact you.

For example, you may be surprised to find out that most tickets in your shop come from the native contact form, though you had assumed customers use the Contact Us tab most often. That's a good reason to revise your store processes.

An agent can also change the ticket subject and add comma-separated tags to find the ticket quickly next time.

Additional tab with ticket history and channel

Customer Satisfaction Surveys

Help Desk MX adds a short satisfaction survey to the footer of reply emails, so customers rate the answer in one click.

Ratings are saved with each reply, and the reports show satisfaction for every agent.

Advanced Reports

Built-in reports show how your support team performs, by period and by agent:

  • new and changed tickets;
  • replies and solved tickets;
  • first reply time, first resolution time and full resolution time;
  • satisfaction ratings and response rate.

Custom Fields

Add your own fields to the ticket form to get the details you need up front. For example, add a date field or a list of reasons for contacting you.

Show each field on the contact form, in the customer account or only on the admin ticket, and make it required for customers, for staff or for both.

Workflow Rules

Workflow rules handle the routine work. Each rule starts on an event (a new ticket, a reply from the customer, staff or a third party, an assignment, a ticket update or an hourly check), checks conditions such as the channel, the tags, who replied last or how many hours have passed, and then acts: it changes the status, priority, department or owner, adds tags, archives the ticket or sends a notification.

Most of our own rules route tickets. New tickets from each mailbox go straight to the agent responsible for it, and when a customer replies, the ticket goes back to the agent who handles that product line.

Other useful rules:

  • change the ticket status to In Progress when the support team sends the first reply;
  • if a customer has waited 4 hours for an answer, raise the priority and notify the team lead;
  • close a ticket automatically if the customer hasn't replied for 30 days;
  • bring a ticket back from the archive when the customer writes again.

Access Permissions

Set which departments and tickets each admin role can see and manage, right in the admin.

This helps when your support divisions have separate roles. For example, your store has Sales, Billing and Technical departments, and each one should manage only its own tickets.

Spam Protection

Add as many spam patterns as you need and check each one against the email header, subject or body. Matching emails go to the spam folder instead of the ticket queue.

Auto-replies are filtered out so they don't loop back as new tickets, and Google reCAPTCHA protects the contact forms.

Follow-Ups

Schedule a follow-up on a ticket. At the time you set, it changes the status, priority, department or owner and sends a reminder to the address you choose, so a promised callback or a pending answer doesn't slip.

Integration with RMA

Help Desk MX converts tickets into RMA requests.

Say a customer emails [email protected]. Help Desk MX receives the email and turns it into a ticket.

The support manager converts the ticket into an RMA request by clicking Convert to RMA. From then on, emails about this request go to the RMA, and the conversation continues there.

Integration with Knowledge Base

Help Desk MX works with the Mirasvit Knowledge Base extension.

With this enabled, customers search your knowledge base right in the feedback popup before creating a ticket.

If no article answers the question, the same popup invites them to create a ticket.

With the integration disabled, customers open a ticket first instead of reading the FAQ.

Free Migration from Another Help Desk

Moving from another help desk? We migrate your tickets and message history for free, so you keep the full history.

We have ready-to-use migration scripts for Freshdesk, Zendesk and most Magento 2 help desk extensions.

Install Help Desk MX and answer every customer from one queue in Magento.
No hidden fees
Our developers install the extension on your store and configure it for your setup, free of charge.
Lifetime access to source code
Access to free support and updates for 1 year
Updates and support prolongation - $180

Pay today $299 for the first year.

Then $180 for updates and support services per year.

Cancel anytime.

30 days money back guarantee
See it in action!
Pick a quick tutorial to learn about various aspects of this extension
Customer Reviews 119
Earn points for your review about this extension modules. $1 = 10 points
Write Your Own Review

check-circle You submitted your review for moderation.

BBMC Verified Buyer
From Carol Stream, United States
Using the module for over 3 years
A genuine Magento help desk rather than a basic contact form
Help Desk MX gives Magento a proper customer support system that is deeply integrated with the store.

Email can be incorporated into the ticket workflow, while administrators have access to templates, customer groups, priority levels, reminders and notification options. Both the store and customer retain a useful communication history, and third parties can be included when a ticket requires outside involvement.

The interface is easy enough for both customers and administrators while still providing a large amount of configuration.

Because we also use other Mirasvit customer-service extensions, the integration between them is a major advantage.

One improvement I would like is greater control over customer notifications, including the ability to disable certain ticket notifications rather than requiring them in every situation.
Also installed:
Knowledge Base,  Full Page Cache Warmer,  Advanced Product Feeds,  Follow Up Email,  Reward Points,  Promo Banners,  Elastic Search Ultimate and 28 more
Tim Verified Buyer
From Tampa, United States
Using the module for over 3 years
A Better Customer Experience
We have used this extension for several years now and it has been great. You can easily see all communications with a customer within Magento interface. Predefined responses make customer service easier for reps. Help Desk is much easier than setting up an external crm system and trying to integrate.
Also installed:
Elastic Search Ultimate,  Advanced Product Feeds
Guillaume Verified Buyer
From Lamonzie, France
Using the module for 5 months
Great extension to manage our customer service
Great extension to manage customer service! Thre is lots of different feature very usefull to work as a team and the assistant AI mirsavitextension integrate into it is a great value for optimize and increase our efficiency. i anticipate further development that will make this app a definit must.
Also installed:
Advanced Reports,  Affiliate,  Google PageSpeed Optimizer,  Follow Up Email,  AI Assistant,  Google Tag Manager,  Improved Asynchronous Reindexing and 11 more
Paolo Verified Buyer
From Gandino, Italy
Using the module for over 3 years
The Help Desk MX extension for Magento 2 is a solution designed to improve customer support in Magento-based online stores.
The Help Desk MX extension is ideal for those who want to offer high-level customer support in a simple and effective way, reducing the risk of errors or oversights. The ability to automate processes and collect customer feedback is particularly useful for constantly improving operational efficiency.
Also installed:
Product Kits ,  Automatic Related Products,  RMA,  Follow Up Email,  Reward Points,  Elastic Search Ultimate,  Advanced Product Feeds and 25 more
Matt Verified Buyer
From Carol Stream, United States
Using the module for over 3 years
Unified communications with customers
The biggest feature of the help desk is its ability to integrate with the RMA, Knowledge base, and Magento systems.

This way everything is tied to the customers' account. Orders, other tickets, returns, and previous communications. It also shows answered from the FAQ extension when submitting tickets.

I wish they would add some more control functionality over automated emails to prevent specific responses from notifying the customer automatically when we reply. Right now, every time you reply to a ticket, the customer is notified no matter what.

I also wish there was an edit function so if a mistake was made when replying, that you can go back and correct it.

Last feature request would be to include capture and include the customers IP from the device they send a message on.

There is so much more it can do and is an essential Magento extension.

Also installed:
Knowledge Base,  Full Page Cache Warmer,  Advanced Product Feeds,  Follow Up Email,  Reward Points,  Promo Banners,  Elastic Search Ultimate and 28 more
Manual & Support
Need more help?

Save time by starting your support request online and we'll connect you to an expert.

Frequently asked questions
chevron-down chevron-right

Does Help Desk MX include live chat?

No, Help Desk MX doesn't include a live chat window. It works with any live chat you already use: when the chat sends offline messages and transcripts by email to a mailbox connected to Help Desk MX, they become tickets and follow your routing rules. That's how our own support team handles chat messages.

Customers can also reach you through the Contact Us tab on every page, the contact form, their account or email, and agents get desktop notifications about new tickets.

chevron-down chevron-right

Do I need a separate help desk service, or does Help Desk MX work inside Magento?

Help Desk MX works inside your Magento admin, so you don't need a separate service. Tickets are linked to customer accounts and orders, agents see the order and the customer's earlier tickets on the ticket page, and there's nothing to sync and no monthly fee per agent.

chevron-down chevron-right

Which mailboxes can Help Desk MX fetch emails from?

Gmail and Microsoft 365 (Exchange Online) connect with OAuth, so they work even where basic authentication is turned off. Any other mailbox connects over IMAP or POP. You can connect several mailboxes and send each one to its own department.

chevron-down chevron-right

Can other systems create tickets in Help Desk MX?

Yes. The REST API lets other systems, such as a chatbot, a CRM or an ERP, create and update tickets, add messages and attachments, and read custom fields. GraphQL covers customer tickets for headless and PWA storefronts.

chevron-down chevron-right

Can I use AI with Help Desk MX?

Yes. With AI Copilot, or any AI assistant connected through our MCP server, you can draft and send replies, get an overview of open tickets and update statuses, priorities, departments and tags by asking in plain language.

chevron-down chevron-right

Can I see if another agent is already working on a ticket?

Yes. When two agents open the same ticket, each sees who else has it open and who is typing a reply. Unsent replies are saved as drafts, so nothing is lost if the page is closed.

chevron-down chevron-right

Can Help Desk MX escalate tickets that nobody has answered?

Yes, with workflow rules. For example, a rule can check every hour for tickets where the customer has waited longer than 4 hours, raise their priority, reassign them and notify the team lead.

chevron-down chevron-right

Can I migrate tickets from my current help desk?

Yes, and we do it for free. We have ready-to-use migration scripts for Freshdesk, Zendesk and most Magento 2 help desk extensions, and our team moves your tickets and message history so you keep the full history.

chevron-down chevron-right

Is there a free version or a trial?

Help Desk MX is a paid extension. You can try the frontend, backend and Hyvä demos on this page before buying, and every purchase comes with a 30-day money-back guarantee.

Changelog
Version 1.7.2Nov 4, 2026
⚠️ Help Desk MX now requires Mirasvit Reports 1.4.79 or later (mirasvit/module-report) — Composer updates it during the upgrade. It is the first version that applies the Help Desk report's access check described below.
Security: guest ticket links could open other customers' tickets — A crafted guest ticket link could open, reply to, or download attachments from tickets whose link the visitor never had. A crafted satisfaction link could rate or comment on any message. Only the exact link from the email works now.
Security: the GraphQl mstHelpdeskCreateTicket mutation exposed customer data to guests — Without a customer token, a caller could enter any email and get back the profile of the account registered under it, plus the order the ticket was linked to. Guests now get customer, order_id and order_label as null. Logged-in customers still get their own data.
Security: a ticket could be linked to someone else's order — When creating a ticket in the storefront or through GraphQl, any order id was accepted, so the ticket page showed that order's number, date, total and status. An order is now linked only when it belongs to the customer: placed from their account, or a guest order placed with their email.
Security: [[ticket_url__N]] in a customer reply showed other tickets' subjects — Only staff messages (merge notes, quick responses, agent replies) can now link another ticket. In any other message, the variable links the message's own ticket. The ticket subject in the link is now HTML-escaped.
Security: CMS directives ran in customer messages when "Use WYSIWYG Editor in backend" was on — {{block}}, {{widget}}, {{customVar}} and {{config}} in a customer reply, contact form, GraphQl ticket or inbound email were run on the server. Directives are now run only in staff replies written in the admin or posted through the REST API. Anything else, including an email sent from a staff address, is shown as plain text.
Security: department permissions were not applied to every ticket action — An admin role limited to some departments could still save, reply to, move, archive, spam, restore or delete tickets of other departments, download their attachments, and include them in mass actions (change status or owner, merge, delete). Every ticket action now applies the role's department permissions. Mass actions skip tickets outside the role's departments.
Security: the Help Desk report API ignored report permissions — Any admin role could query the Help Desk report API and read data from other report tables, such as customer emails. The API now requires the same Help Desk Reports permission as the report page.
Version 1.7.1Oct 26, 2026
⚠️ Help Desk MX now requires Mirasvit Core 2.0 and the new mirasvit/module-geo-location package — Composer installs both during the upgrade. Help Desk no longer uses the core text, variable-parsing, date and serializer helpers that Core 2.0 removed. Run bin/magento setup:upgrade after updating so that Mirasvit_GeoLocation is enabled.
Older Help Desk data still saved in the old PHP-serialized format is converted to JSON once, during setup:upgrade. This covers ticket activity, channel data, drafts, the names of statuses, priorities, departments, custom fields and schedules, department notification emails, custom field values and working hours. It runs in batches, so stores with large ticket histories can upgrade without running out of memory.
The messages returned by the GraphQl API are now translatable and ship in all 16 supported store languages.
Clicking Save or Save & Send twice on a ticket in the admin no longer sends the reply twice — The first click locks the save buttons until the page reloads. If validation stops the save, the buttons unlock again. They also unlock when you come back to the page with the browser's Back button.
Mass status change and merge in the ticket grid now require the Tickets permission — Before this fix, any admin user could run them, even if their role had no access to tickets.
Version 1.7.0Oct 20, 2026
Hyvä support now ships with the extension — The companion package mirasvit/module-helpdesk-hyva is gone: the contact button and popup, the Contact Us form, the customer's tickets (list, ticket page, new ticket) and the satisfaction pages are now part of Help Desk MX itself. There is no second package to find and keep in step, and on a Luma store the Hyvä part simply stays dormant. Composer removes the companion package by itself when you upgrade.
GraphQl support now ships with the extension — mirasvit/module-helpdesk-graph-ql is gone; the mstHelpdeskTickets, mstHelpdeskStatuses, mstHelpdeskPriorities, mstHelpdeskDepartments and mstHelpdeskCustomFields queries and the create-ticket, add-message and close-ticket mutations used by headless and PWA storefronts are part of Help Desk MX itself. The GraphQl module now also loads on PHP 7.4 (Magento 2.3.7), where the separate package failed with a syntax error.
One set of storefront templates and one script for both themes, so a fix or a new option reaches Luma and Hyvä at once.
⚠️ Hyva_MirasvitHelpdesk and Mirasvit_HelpdeskGraphQl — Hyva_MirasvitHelpdesk is gone, not renamed; Mirasvit_HelpdeskGraphQl keeps its name and now installs with Help Desk MX. You only need to act if you referenced them yourself: in a custom di.xml, a layout file, or a deployment script that enables modules by name.
⚠️ If you customised the storefront pages, review your changes — The templates Hyva_MirasvitHelpdesk::*.phtml are now Mirasvit_Helpdesk::*.phtml, shared with Luma. The inline RequireJS code of the contact, ticket and satisfaction templates, Mirasvit_Helpdesk::js/view/validation.js and Mirasvit_Helpdesk::js/view/contacts/schedule/status.js were replaced by Mirasvit_Helpdesk::js/helpdesk-storefront.js. A theme override aimed at the old files is simply not read any more, with no error to say so.
Help Desk MX now requires Magento's GraphQl package — magento/module-graph-ql, which every standard Magento install already has. Its GraphQl module is installed with every Help Desk install, and the Help Desk GraphQl queries work only while Magento_GraphQl is enabled.
After upgrading a Hyvä store, run bin/magento hyva:config:generate and rebuild your theme's Tailwind CSS.
Saving a department, status, priority or custom field for one store view no longer changes its All Store Views value — When the default value was still empty, a value saved for a single store view (a department's notification email, for example) was also written as the All Store Views value and so applied to every store. A store-view save now touches only that store view. Clearing a store-view value makes that store view fall back to the default instead of showing a blank; blank store-view overrides saved before this fix are read as the default too.
The new-ticket form on Hyvä always attached an order — It listed the customer's orders without the "-- Select an Order --" choice, so the first order was sent with every ticket. The choice is back, as on Luma.
The 1.6.2 fixes for empty Priority and Department dropdowns now apply on Hyvä — The Hyvä new-ticket form still showed a required dropdown with nothing to pick.
On Hyvä, quoted email text in a ticket did not fold, and the Contact Us page showed no live working-hours status — Both now work as on Luma. The folding also no longer relies on an inline style, so it works on stores with a strict Content Security Policy.
Paging through attached images in a ticket no longer freezes on quick clicks — An image the browser already holds switches at once. One it does not hold (some browsers, or the developer tools with the cache disabled, re-download every attachment) is downloaded once, one at a time with the one you clicked last first, and kept, so quick paging no longer waits behind a queue of downloads. A spinner shows over the dimmed current image while the next one is still loading. Same on Luma and Hyvä.
Date custom fields on Hyvä had no calendar and lost typed text — The field was a plain text box: it accepted any text, and a ticket sent with text in it saved the field empty. Date fields are now the browser's own date picker on both themes, and accept only a date.
A date custom field was saved one day early and shown two days early — On a store whose timezone is behind UTC (the default, America/Los_Angeles, among them), picking October 28 saved October 27 and showed October 26. The day you pick is now the day that is saved and shown. Dates already saved keep their stored day.
Required custom fields on the new-ticket form had no red asterisk — They were validated but not marked; now they show the asterisk like the other required fields.
A long word in the help text or a custom field description ran out of the form — On a phone, the Contact Us page, the contact popup and the new-ticket form now break it onto the next line.
A long satisfaction comment left a wide gap before the rating icon — The comment now fills the pill up to the icon and ends with an ellipsis, on both themes.
On Hyvä, "Choose Files" looked like plain text — The file field's button is styled as a button again.
Going Back after sending a form showed the sent message again — After a ticket, reply or contact message was sent, the browser's Back button returned to the form with the text, the chosen files and a hidden Submit button still there, which invited sending it twice. A sent form now comes back empty and ready. Same on Luma and Hyvä.
On a Luma phone, the contact popup sat off the right edge of the screen — It now keeps the same margin on both sides, as on Hyvä.
The Hyvä Contact Us page looked unlike Luma's — The working-hours heading and table were unstyled, with the days running into the hours, the block sat tight against the content above it, and the help text was much larger. They now match Luma.
On a phone, the Hyvä new-ticket and Contact Us pages scrolled sideways — Long order names and the file field pushed the form past the screen edge. The forms now fit, and a wide ticket list scrolls within itself.
⚠️ GraphQl: replying to and closing a ticket are limited to the ticket's own customer — Before, a logged-in customer could reply to any ticket by its id, and a guest could reply to or close any guest ticket. Replying now needs the logged-in customer who owns the ticket, or for a guest a guest ticket filed with the email given. Closing now needs the logged-in customer who owns the ticket, so guests can no longer close tickets through GraphQl.
A working-hours value stored in an unexpected format no longer breaks the Working Hours grid and the schedule status — The admin Working Hours page failed with "Cannot access offset of type string on string". Such a day is now treated as closed; re-save the schedule to fix its hours.
GraphQl: a ticket without a priority, status or department no longer fails the tickets query — Those fields now come back empty.
Version 1.6.3Oct 12, 2026
Separate API permissions for reading tickets and for drafts — two new role resources under Help Desk, "View Tickets (API)" and "Ticket Drafts (API)", let you give an integration or API user read-only access to tickets, messages, attachments, activity, history and reply templates, and let it save reply drafts, without allowing it to reply to customers, create, edit or delete tickets (these still require the Tickets permission). On upgrade, every existing role and integration automatically gets the new permissions wherever it already had access to Tickets, so current API connections keep working.
The admin order view opens much faster on stores with many tickets. Its Helpdesk Tickets tab looked up the order's tickets without an index, so every order page scanned the whole ticket table (about 5 seconds on a store with 130,000 tickets).
⚠️ REST API: the read endpoints (GET /V1/helpdesk/ticket/:code, /tickets, /ticket/:code/message, /activities, /history, /attachments, /attachment/:attachmentId, /attachment/:attachmentId/body, /template/:templateId, /templates) now require Mirasvit_Helpdesk::helpdesk_ticket_view, and the draft endpoints (/V1/helpdesk/ticket/:code/draft) require Mirasvit_Helpdesk::helpdesk_ticket_draft instead of Mirasvit_Helpdesk::helpdesk_ticket. Existing roles are migrated by setup:upgrade; roles or integrations you create afterwards must be granted the new resources explicitly.
⚠️ DB schema: a new index MST_HELPDESK_TICKET_ORDER_ID is added on mst_helpdesk_ticket.order_id. Run bin/magento setup:upgrade after updating.
Hardened the database queries behind the helpdesk search and the customer's other-tickets list, so search terms and customer email addresses are now escaped by the database itself. Search results are unchanged.
Connecting a Microsoft 365 gateway no longer fails with "Need admin approval" in tenants that require admin consent, even when consent was already granted. On Windows PCs signed in to Microsoft, the sign-in also no longer picks the Windows account automatically, so you can now choose the shared support mailbox you are setting up. Gmail gateways are unchanged.
Gmail and Microsoft 365 gateways now work on servers without the PHP IMAP extension. These gateways fetch mail over HTTPS and never use IMAP, but connecting or fetching still failed with an "enable the IMAP extension" error, and the Gateways page always showed that warning. The warning now appears only when an active IMAP gateway actually needs the extension.
Attachments on incoming emails are no longer lost on stores that keep media files in remote storage such as Amazon S3. Attachments are now saved, opened and deleted through Magento's media storage instead of the local disk.
The admin ticket page no longer fails to open on servers without a GeoLite location database (for example a second web node or a container). The customer's local time is simply left out instead.
PDFs and other files attached to incoming emails no longer go missing when the sending system labels them with only a file name. Automated mailers, such as billing systems, often send attachments this way. These files were silently dropped and never appeared on the ticket; they are now saved with the ticket like any other attachment.
The customer picker on the admin ticket form now finds customers by first and last name. Results are also ranked by how well they match: an exact match comes first, then names that start with the search term, then partial matches. The ranking now happens before the 20-result limit is applied, so weaker matches no longer push the customer you want off the list.
The quick view in the admin ticket grid now always shows a ticket's first and latest messages. Which messages appeared there depended on the order the database happened to return them in, so the preview could show the wrong ones.
When several working-hours schedules are active for a store at the same time, the storefront now shows the one with the highest Sort Order. If the Sort Orders are equal, the newest schedule wins, the same order the upcoming-schedules list uses. Before, the Sort Order set in the admin was ignored and the most recently created schedule was shown.
Version 1.6.2Sep 28, 2026
Customers can again submit and reply to support tickets from the storefront helpdesk forms.
The ticket form's Priority and Department dropdowns now show their default options on every store view, including store views added after installation.
The storefront ticket and contact forms no longer break when a required Priority or Department dropdown has no options to show.
Fetching incoming support emails from large mailboxes is now much faster.
Helpdesk notification emails now send correctly on Magento installations that report a non-standard version.
Reasons to choose Mirasvit
Client focusing and satisfaction

These are our primary. A major portion of our new clients come from referrals from our existing clients. Our professional team of developers, marketers and support staff have invested the best knowledge and experience in the field into our work, so you know you can come back to us again and again.

Remarkable support

One year free and high quality support. We go to great lengths to provide maximum satisfaction with every module you have purchased in our store. By helping you with installation, configuration, answering your every question, we do all our best to eliminate any possible problems.

Risk-free Investment

30-days money back guarantee. If you are not satisfied with our extension performance for any reason, we provide a full refund.

Constant improvements and upgrades

We constantly add new features to all our modules, and are always interested in hearing your opinion and implementing your suggested features in our future developments.

Comprehensive Documentation

We provide an expanded user guide for every aspect of our extension, so you can find answers for all your burning questions.

Unencrypted source code of our products

You can customize extension according to your needs and requirements.

Usability and Performance

The Module is easy to install and upgrade, just follow our step-by-step user guide. Additionally, the extension is ready to use with the Hyvä theme.

Ready for Magento Cloud

No core modifications. The extension has been tested in a Magento Cloud environment and is fully compatible with it.

Loading...