Features / Self-serve
Where your customers see their own requests
A signed-in space where a customer can see everything they have reported and what happened to it, alongside your roadmap, changelog and help center.
Northwind support
Enter your email and we will send you a link. No password to forget.
Link sent. Opening…
What it does
Without it
“Any update on that?”
Third one this week. Nothing has changed since your last reply, but you still have to find the thread, read it back, and write four sentences confirming that nothing has changed.
Four surfaces, four vendors, none of them yours
Help center on one tool, roadmap on another, status page on a third, and the actual conversation buried in email. Your customer keeps track of none of it, and honestly neither do you.
The account nobody wanted to create
You ask someone to pick a password so they can look at a request they already sent you. Half of them never finish, and the other half reset it every single time they come back.
How it works
They sign in with an emailed link
No password to choose, forget, or leak. Signed-in devices are listed on their account page and they can revoke any of them without asking you.
What that includes
Everything customer-facing lives at one address
Their requests, your roadmap, your changelog, the help center, notifications and their account settings, all served from your portal address, resolved from the domain they arrived on.
What that includes
Their requests are theirs, and private
Signed out, the request list shows nothing at all rather than a teaser. Signed in, it shows their own conversations with the real status and when each one last moved.
They manage their own notifications
Which optional emails they want is a setting they control, per category, on their own account page. Unsubscribing is a click, not a support request that lands back in your queue.
It looks like your product
Your name, logo, accent color and font. On paid plans the Tore badge comes off, so the customer never has to think about which vendor is behind the page.
What that includes
What it means for you
The “any update?” email stops arriving.
Because the answer is already somewhere they can look, with a timestamp on it, and they trust the timestamp.
One link instead of four
You stop maintaining a mental map of which tool holds which public page, and your customer stops asking you where the status page went.
Nobody has to create an account to be your customer
An email address is the whole signup. The friction you removed is friction that used to arrive in your inbox as a ticket about signing in.
The honest limit: The portal runs on a Tore address today. Serving it on your own domain is a paid feature whose settings screen exists but is not yet checking real DNS records, and the status page inside the portal is not reading live monitors yet.