Support software is where small stores quietly start paying per-seat pricing for something they use twelve times a month.
The alternative most shops fall back on is a shared inbox. It works right up until two people reply to the same customer, or somebody needs to know what was promised three months ago, or the person who handled it is on leave and the history is in their sent items.
Helpie puts a proper ticket system in the admin you already log into.
What a ticket holds
Every ticket carries the things you need to actually resolve it rather than just record it:
- A status, so anyone can see whether it is waiting on you or on the customer. Statuses are yours to define rather than fixed.
- An assigned agent, so a ticket has one owner and nothing sits in the gap between two people who both assumed the other had it.
- A threaded conversation. Customer messages and agent replies in order, with the customer seeing only the public ones.
- Private internal notes. The part you write for your colleague rather than the customer: "this is the third time, authorise the refund if she asks again."
- Attachments, because half of support is a photo of the damaged item.
- A full event history. Who changed the status, who reassigned it, when it was created and how. Not for surveillance, for the moment three weeks later when somebody asks what happened.
Where agents work
Two surfaces, for two different situations.
The admin screens are the full experience: the ticket list with filters, the detail view, assignment, internal notes, status changes.
The frontend agent dashboard exists for the staff you do not want to give WordPress admin access to. It drops onto any page with a shortcode, or as a block. Casual support staff get the tickets and nothing else, which is the right amount of access for someone who answers questions two afternoons a week.
Where tickets come from
Three ways in, and all three land in the same queue:
Customers raise them from the support portal on your site. They arrive by email, replying to a thread or writing in fresh. Or the AI assistant escalates one when it cannot answer, carrying the conversation with it so the customer does not have to explain themselves twice.
That last one matters. The common failure of a chatbot is that giving up wastes the customer’s time entirely. Here the failed conversation becomes the ticket body, and the agent picks up knowing what was already asked.
Attached to the order, where relevant
On a WooCommerce store, a ticket can be linked to an order. Do that and two things happen: the order edit screen grows a panel showing the linked ticket and its current status, and refunds issued in WooCommerce post themselves into the ticket thread as a private note recording the amount, who did it, and the reason given.
The person looking at the order can see there is an open support conversation. The person looking at the ticket can see the money already moved. Neither has to go and ask.
Your data, your server
Tickets are rows in your database. Customer conversations, internal notes, order links, all of it in the same place as your orders and customers.
That is a practical point rather than an ideological one. It means support history is in your backups. It means you can query it. It means the day you change how you do support, the record of the last three years comes with you rather than expiring with a subscription.
Turning it off
Helpie can run as a chatbot with no helpdesk at all. The ticket system is a feature you can switch off, in which case escalations go to your email and no ticket screens appear.
Plenty of shops want the AI assistant and already have somewhere else that support lives. Making the helpdesk optional means they are not carrying a queue nobody looks at.