OCMLABS/MODULE-SUPPORT-TICKET · STOREFRONT PORTAL

The customer-facing Support Tickets experience on the storefront

  • Magento
  • Adobe Commerce
  • Hyvä

Customers interact with the Support Tickets module entirely through their Magento account area. Everything is scoped to the logged-in customer - anonymous visitors cannot create or view tickets, and no customer can access another customer’s tickets.

How-to: opening a ticket as a customer, 1:02

My Support Tickets

After installation, a Support Tickets link appears in the customer account navigation. It opens the My Support Tickets page, which lists every ticket the customer has opened in the current store view, newest first, with the ticket number, subject, date opened, priority, and status.

Customer ticket list

From the list, the customer can:

  • Click View on a ticket to open the ticket view and see the full comment thread
  • Click Open New Ticket to start a new ticket on the Open a Support Ticket page

The list is filtered to the current store view, so on multi-store installations customers do not see tickets they opened under a different store.

Creating a ticket

The Open a Support Ticket form asks the customer for a product, a subject, and a message, plus an optional category and priority.

Customer new ticket form

  • Select Product - Required. The dropdown lists products from any of the customer’s orders that are not canceled or closed; customers cannot submit a ticket against a product they have never purchased. The customer does not pick an order: the module links the ticket to the matching order from their purchase history.
  • Subject - Required, plain text.
  • Category - Optional. Billing, Shipping, Product Issue, General, or Other.
  • Priority - Optional. Defaults to Medium.
  • Message - Required. This becomes the first entry in the ticket’s comment thread.

On submission, the module:

  1. Creates the ticket with status Open.
  2. Stores the message as the first comment in the thread.
  3. Sends a confirmation email to the customer.
  4. Sends an alert email to the configured admin notification address.

Viewing a ticket

The ticket view page shows the full conversation thread plus the current status, priority, category, and related product (if any).

Customer ticket view

From this page the customer can:

  • Read every message in the thread chronologically
  • Add a reply using the reply form at the bottom of the thread (open tickets only)
  • Click Mark as Resolved when they are satisfied

Adding a reply

Customers type a reply and click Send Reply. The module adds the comment to the thread, moves an In Progress ticket to Pending (Open and Pending tickets keep their status), and sends a notification email to the admin.

Resolving a ticket

The customer can click Mark as Resolved on the ticket view page and confirm when they are satisfied with the outcome. The ticket is set to Resolved and a resolution email is sent to the customer confirming the close. Admins can also resolve tickets from the backend; an admin status change does not send an email.

NOTE /

Resolved tickets cannot be reopened by the customer. The thread stays readable, but the reply form is hidden and replies are rejected. The customer sees a message with an Open New Ticket button to start a new ticket instead.

The product page Support button

Product pages show a support button whose behavior depends on the visitor:

  • Logged in and has purchased the product: an Open a Support Ticket button opens a popup form (Subject, Category, Priority, Message) with the product already attached. The ticket is created without leaving the page, and the popup offers a link to view it.
  • Logged in but has not purchased the product: a disabled Support Ticket (Purchase Required) button is shown.
  • Not logged in: a Log in to Open a Support Ticket link takes the visitor to the login page.

This gives buyers a one-click path from a product they have a question about to a ticket scoped to that product, without asking them to re-enter SKU or product name.

Questions that arrive as tickets again and again belong on the product page instead: a FAQ tab from FAQ & Product Questions answers them before the customer reaches for the Support button.

The button works with full page cache enabled (since 1.0.7): the product page stays cacheable, logged-out visitors get the login link straight from the cached page, and for logged-in customers the button state is looked up after the page loads. On Hyva, companion 1.0.4 also works with Hyva’s strict Content Security Policy build.

Permissions and security

  • Scoped to the current customer. Every frontend controller verifies that the session customer owns the requested ticket. Requests for another customer’s ticket redirect back to the ticket list with a “Ticket not found” message.
  • Scoped to the current store view. Customers on a multi-store installation only see tickets they opened under the current store.
  • Purchase-gated products. The product dropdown and server-side validator both check the customer’s order history, so tickets cannot be opened against products the customer has never bought.

See also

Related pages

In this module