Most small-store support happens in email, and email is a bad place to keep a conversation that matters.
The customer loses the thread. You ask them to quote an order number they do not have. They reply to a three-week-old message about something else. Nobody can see the current state of anything, and the phrase "as per my last email" starts appearing.
A portal fixes the state problem. The conversation has one place to live, and both sides can see it.
For your account holders
A customer with an account gets their support history in one place. Open tickets with the current status, so they can see you have it and are not chasing. Closed ones too, because "what did you tell me last time" is a real question.
They can reply to an existing ticket without starting a new one, and raise a new one with a form rather than composing an email and hoping it reaches the right place.
If they were talking to the AI assistant and it escalated, the conversation is already there. They do not re-explain.
Guests get in too
This is the part most portals get wrong.
Plenty of your customers checked out as guests. They have no account and they are not going to create one to ask where their parcel is. A support portal that requires a login excludes exactly the people most likely to need it.
Helpie lets a guest back in to the ticket they raised. They enter its ticket ID and the email they used, and Helpie sends a single-use link to that ticket. Any email Helpie has already sent them carries the same kind of link, so most of the time they just click the one already in their inbox. No password to create, no account to remember.
A guest link opens the one ticket it was minted for, not a history. That is deliberate: the look-up form is open to anyone who can type an email address, so it never puts a stranger in front of somebody else’s support.
On the My Account page
For WooCommerce stores, the portal registers itself as a My Account tab. Support sits next to orders, addresses and downloads, where a customer would look for it.
That is where people already go when something is wrong with an order. Putting support somewhere else and hoping they find it via the footer is optimistic.
Putting it on the page
A shortcode, or a native Bricks element if that is what you build in. Drop it on a page called Support and it works.
Emailing themselves the conversation
Customers can email themselves a transcript of an AI chat. It sounds minor and it removes a specific annoyance: the customer got a useful answer, closed the tab, and now cannot remember the third step.
It is rate-limited so it cannot be used to send mail to arbitrary addresses, and for logged-in customers it always goes to their account email rather than whatever they type.
Why a portal rather than just email
Email still works and Helpie fully supports it. Replies thread back into tickets automatically, so a customer who never visits the portal has a perfectly normal experience.
The portal is for the other half: the customer who wants to check status without bothering you, the one who lost the email, and the one with three separate things going on who needs to see which is which. It reduces the "any update?" messages, which is time back for whoever answers them.