Support Tickets (Help Desk)

VIDEO WALKTHROUGH

Support Tickets (Help Desk): setup guide

2:34

Recorded on version 1.0.4 · Narrated walkthrough · English captions

Jump to a chapter 8 chapters

1. 0:00Set up Support Tickets (Help Desk)
2. 0:13Open settings and choose scope
3. 0:35Enable the help desk
4. 0:53Configure the Luma help button
5. 1:10Set attachment limits
6. 1:28Set notifications and test the workflow
7. 1:51Save and verify your setup
8. 2:12Your setup checklist

Read the full video transcript

Support Tickets (Help Desk) 1.0.4 — Magento Admin setup

00:00:00 — Set up Support Tickets (Help Desk)
Welcome to the Agentic Ecom Support Tickets (Help Desk) Admin guide. We'll walk through the main setup screens and the checks to make before using the module. This guide assumes the extension is already installed.

00:00:13 — Open settings and choose scope
Start in Magento Admin and open Stores, Configuration. Choose Support Tickets (Help Desk). Check the Scope selector before editing. Use the appropriate website or store view where the setting supports it. The screen values here are a demonstration; enter the settings and service details that belong to your own store.

00:00:35 — Enable the help desk
In General, enable Support Tickets and decide whether guests may raise tickets. Review the reference prefix and starting number. The Admin workspaces are under Help Desk: Tickets, Departments and Canned Responses. Configure the help desk for the team who will actually answer customers.

00:00:53 — Configure the Luma help button
Open Storefront Popup and choose whether to show the help button. Set its wording, heading, introduction, position and accent colour, and review mobile visibility. Use a short message that makes it clear what customers can ask and what response they should expect.

00:01:10 — Set attachment limits
Review allowed file extensions, maximum file size and maximum files per message. Enable only the types your support team can handle. Check Spam Protection and any reCAPTCHA details before exposing a public form. Those credentials belong to your own storefront domain.

00:01:28 — Set notifications and test the workflow
Configure the agent address, sender and notification templates. Review S L A Targets for each priority and the optional satisfaction rating. After saving, raise a disposable storefront ticket, open it in Help Desk, and check a reply and its email delivery. A separately built headless frontend must provide its own ticket interface.

00:01:51 — Save and verify your setup
When your required settings are complete, use the screen's Save control and wait for Magento's confirmation. Then reopen the record or configuration and check the saved values at the intended scope. If the storefront still shows earlier settings, refresh the relevant caches. Test your own configuration before using it with customers.

00:02:12 — Your setup checklist
That's the Admin setup walkthrough for Support Tickets (Help Desk). Check permissions and scope, review the module-specific settings, then save and verify a small staging example. Use the written guide at user guides dot Agentic Ecom dot net for installation details, complete field references and any separate storefront integration steps.

Download videoEnglish captionsDownload transcript

Turn every “Contact Us” form into a real helpdesk. Customers raise a ticket from a floating Help & Support popup, choose a topic (Pre-Sales, After-Sales or Product Tech Support), and you handle the whole conversation from one admin screen — with departments, canned responses, SLA timers, satisfaction ratings, file attachments and email notifications.

The popup works on Luma. A separate headless/Astro storefront can use the module’s GraphQL API but must build its own support form and ticket pages.

This guide covers the stable Support Tickets 1.0.4 buyer package. Its Admin settings use an independent configuration tab, so the page opens without AgenticEcom Core installed.

Install

Install Support Tickets (Help Desk) with Composer using your AgenticEcom licence key (find it on your My Licences page — one key unlocks every module you own):

# 1. Register the AgenticEcom repository (once per store)
composer config repositories.agenticecom composer https://repo.agenticecom.net
composer config --global --auth http-basic.repo.agenticecom.net <YOUR-LICENCE-KEY> x

# 2. Require this module
composer require 'agenticecom/module-support-tickets:^1.0.5'

# 3. Apply it
php bin/magento setup:upgrade && php bin/magento setup:di:compile && php bin/magento cache:flush

Have the whole platform?

Install every module in one command with composer require agenticecom/suite — see Install the complete suite.

Compatibility

Magento

Check the exact release against your Magento Open Source version.

PHP

Check the exact package requirements and test your PHP version.

Storefront

Luma popup; GraphQL API for a separately built headless frontend.

Who can ask

Guests and logged-in customers (guest access is configurable).

The 1.0.4 package passed install/upgrade, DI compilation, Admin configuration display/save and restricted-role checks on Magento Open Source 2.4.9 / PHP 8.5.10 without Core. The 1.0.3 Luma guest submission and cacheability checks and earlier GraphQL guest ticket/reply checks remain relevant, but those flows were not repeated for every configuration. Other combinations should be tested on your own staging site. Configure Magento mail transport before relying on notifications.

Quick start

1. Enable the module: Stores → Configuration → AgenticEcom Support Tickets → Support Tickets (Help Desk) → General → Enable Support Tickets = Yes.

2. The three default departments — Pre-Sales, After-Sales and Product Tech Support — are created for you. Adjust them under Help Desk → Departments.

3. Visit your storefront. A floating Help & Support button appears bottom-right. Raise a test ticket.

4. Open Help Desk → Tickets in the admin, click the ticket, and reply. If Magento mail transport is configured, the customer receives an email. They add threaded replies through the ticket page or private guest link.

Where to find it

The admin home for the helpdesk is the top-level Help Desk menu (Tickets, Departments, Canned Responses, Configuration). Storefront URLs live under /support/….

How customers raise a ticket

The floating button opens a popup that adapts to the chosen topic:

• Pre-Sales asks only for the essentials — name, email, subject and message.
• After-Sales and Product Tech Support also reveal an Order number and an optional Product field, so your team has the context they need immediately.

For logged-in customers, the popup hides the name and email fields; Magento uses the signed-in account identity when the ticket is submitted. Guests provide their own name and email and receive a secure link to follow the conversation.

The site-wide popup is cacheable in 1.0.3, so it does not disable Magento full-page caching. Customer login state is read privately in the browser rather than embedded in cached HTML.

Spam protection built in

Every submission is screened by a hidden honeypot field, and you can optionally add Google reCAPTCHA v3 keys (Configuration → Spam Protection) for a second layer. Both fail closed — a misconfiguration never silently lets spam through. reCAPTCHA uses your own Google account; Google’s usage limits or charges may apply.

Departments

Departments are fully admin-configurable under Help Desk → Departments.

Field	What it does
Name	The label customers see in the popup.
Code	Unique identifier (auto-generated from the name).
Description	Short helper text shown to customers.
Routing Email	Where new tickets in this department are emailed. Falls back to the global address, then the store’s general contact.
Ask for an order number	When Yes, the popup reveals the Order number + Product fields.
Default Assignee	An admin user automatically assigned to new tickets in this department.
Active	Hide a department without deleting its history.

Working a ticket

The ticket screen is a complete conversation view: the full thread on the left, and everything you need to act on the right.

From here you can:

• Reply to the customer (they’re emailed instantly), or add an Internal note that only your team can see.
• Insert a Canned response with one click (see below).
• Attach files to your reply.
• Change the Status, Priority and Assigned agent — all saved with the same button.
• Jump straight to the linked order in Sales.

Status workflow

Statuses move automatically as the conversation flows, and you can always set them by hand.

Status	Meaning	Set automatically when…
New	Just raised, not yet opened.	A ticket is created.
Awaiting Support	The ball is in your court.	A customer replies.
Awaiting Customer	Waiting on the customer.	An agent replies.
Open / On Hold	In progress / parked.	You set them manually.
Resolved	Sorted — triggers the satisfaction request.	You mark it resolved.
Closed	Finished.	You close it (a customer reply re-opens it).

Canned responses

Save your common replies once under Help Desk → Canned Responses, then insert them into any reply with the Insert canned response dropdown. Responses can be global or scoped to a single department, so agents only see the macros that are relevant to the ticket they’re on.

SLA tracking

Set a first-response target (in hours) per priority under Configuration → SLA Targets. Each new ticket gets an SLA due time, shown on the ticket and as a sortable column in the grid, so nothing slips through the cracks.

Customer satisfaction (CSAT)

When a ticket is Resolved, the customer is invited (by email and on the ticket page) to rate the support they received from 1–5 stars, with an optional comment. Ratings appear on the ticket in the admin.

Attachments

Customers and agents can attach files (screenshots, photos of a faulty item, documents). For safety, every upload is checked against an allow-list of extensions and a size cap before it is stored, and files are saved under random names so the originals can never collide or be guessed. Configure the allow-list under Configuration → Attachments.

Email notifications

The module sends transactional emails through Magento’s configured mail transport. Incoming replies to those emails reach your support inbox; they are not imported into the ticket thread. Customers should use their ticket page or guest token link to add a threaded reply. Every email has its own template you can customise under Marketing → Email Templates:

Template	Sent to	When
New Ticket	Agents	A ticket is raised
Ticket Received	Customer	A ticket is raised
Customer Replied	Agents	The customer replies
Agent Replied	Customer	You reply
Status Changed	Customer	The status changes
Rate Your Support	Customer	A ticket is resolved

The customer’s account

Logged-in customers get a Support Tickets entry in their account navigation, listing every ticket with its status and a link into the full conversation.

Headless / GraphQL

A headless storefront uses the same engine through GraphQL. Build its support form, ticket list and reply screens separately; the Luma popup does not appear automatically on Astro. The phone input on createSupportTicket is optional in 1.0.3 (introduced in 1.0.2).

Read the config + departments

{
  supportConfig {
    enabled
    allow_guests
    popup_enabled
    button_text
    heading
    accent_color
    csat_enabled
    recaptcha_site_key      # public key only — the secret is never exposed
    departments { id name description requires_order }
  }
}

Create a ticket

mutation {
  createSupportTicket(input: {
    department_id: 3
    subject: "Battery won't charge"
    message: "The 4.0Ah battery stopped charging after two weeks."
    priority: "high"
    name: "Aoife Byrne"          # omitted for logged-in customers (taken from the account)
    email: "aoife@example.com"
    # phone is optional
    order_increment: "000000123"
    product_sku: "FD-CD18"
  }) {
    success
    reference        # e.g. SUP-100002
    token            # store this — guests use it to view/reply
    ticket { status messages { author_type message } }
  }
}

View & reply

# View — guests pass the token; logged-in customers can omit it for their own tickets.
query {
  supportTicket(reference: "SUP-100002", token: "the-secure-token") {
    reference subject status_label priority_label
    messages { author_type author_name message attachments { file_name download_url } }
  }
}

# Reply
mutation {
  replyToSupportTicket(input: {
    reference: "SUP-100002"
    token: "the-secure-token"
    message: "Tried that — still flashing red."
  }) { status messages { message } }
}

# The logged-in customer's own tickets (requires a customer token)
query { customerSupportTickets { total_count items { reference subject status_label } } }

Access is always enforced

A ticket can only be read or replied to by its owning customer (matched on the auth token) or by anyone holding the secure access token. A wrong or missing token returns an authorization error — tickets never leak to anonymous callers.

Configuration reference

All settings live under Stores → Configuration → AgenticEcom Support Tickets → Support Tickets (Help Desk).

Group	Key settings
General	Enable, allow guest tickets, reference prefix & start number.
Storefront Popup	Show the button, button text, heading, intro, position, accent colour, mobile visibility.
Attachments	Enable, allowed extensions, max size, max files per message.
SLA Targets	First-response hours per priority.
CSAT	Enable the satisfaction rating.
Spam Protection	Honeypot, reCAPTCHA v3 keys, minimum score.
Email Notifications	Enable, agent address, sender identity, and a template per email.

Security at a glance

• Every admin controller is gated by granular ACL (reply, delete and configuration are separate privileges).
• Guest tickets are protected by a 64-character secure token compared with hash_equals.
• Attachments are extension-allow-listed, size-capped and stored under random names.
• Stored messages are saved as plain text and escaped on output (no stored XSS).
• The reCAPTCHA secret is encrypted and never exposed; only the public site key reaches the storefront.

FAQ

Do customers need an account? No. Guests can raise tickets (if allowed) and follow them via the secure link in their emails. You can require login under General → Allow Guest Tickets.

Does it work with my headless storefront? Yes — supportConfig, supportDepartments, createSupportTicket, replyToSupportTicket, rateSupportTicket, supportTicket and customerSupportTickets cover the whole flow.

Where do attachments go? Under pub/media/agenticecom/support/<ticket>/… with randomised filenames; they’re only downloadable by someone who can access the ticket.

Can I route departments to different inboxes? Yes — set a Routing Email on each department. It falls back to the global notification address, then the store’s general contact.

Will an email reply appear in the ticket thread? No. It reaches the configured support inbox. Use the ticket page or private guest link for a threaded reply.

What does a purchase include? A one-time purchase grants a perpetual licence to use the eligible purchased version, with 12 months of updates and priority support. Renewal is optional and never billed automatically. Read the AgenticEcom licence and your order terms; contact support@agenticecom.net for help.