I work on OnePassApps, so this is our own product, and everything below is a measurement of the live site at app.onepassapps.com/support, taken on 4 November 2026 - signed out, in one browser, on one build.
Most support pages are a textarea and a Send button. Ours is a small workflow: three tabs, four fields, two dropdowns, a character counter, and a "what we store" note that tells you what happens to what you type. I opened every part of it and wrote down what it actually says, because no channel here has covered the support desk itself.
The three tabs
The page opens with the headline "Let's sort it out." and the line "Help, bug reports and feedback, all in one place." Below that are three tabs:
- New request - the form
- My requests - the list of what you have sent
- Report a bug - a different, smaller form
Two of them are worth reading carefully.
The request form, field by field
How can we help? is the first section, and its first control is a dropdown labelled "I'd like to…". It opens to seven options, and the default is "Help or question":
Help or question / Report a bug / Billing / Account or sign-in / Privacy or data / Share feedback / Suggest a feature
That first dropdown is the whole routing table for a support request. "Billing" is a peer of "Report a bug", and "Privacy or data" is a peer of "Share feedback" - so the desk sorts a refund question and a "your tool uploaded my file" question through the same seven-item list, not through separate inboxes.
Replies to is a required email field with the placeholder you@example.com. Under it sits the sentence that decides who can follow a request:
Sign in to keep requests with your account. Guest tracking is saved only in this browser.
Subject is optional - the page says "Optional" next to it - with the placeholder "A short summary".
Your message is required, and it carries a live counter that read 0 / 5,000 on an empty page. I typed into it and the counter moved with me: thirty characters in, it read 30 / 5,000. So the limit is five thousand characters, counted as you type. Under the box, the page says: "Leave out passwords and private details."
App & other details is a collapsed section. Opening it adds two dropdowns and nothing else:
- App or area - defaults to "OnePassApps"
- How much is it affecting you? - defaults to "Minor issue or question", and opens to four levels: "I cannot continue", "Something is not working", "Minor issue or question", "Suggestion or idea"
Then the line "Sent to OnePassApps support only." and a Send request button.
The dropdown nobody expects: 23 areas
"App or area" is the interesting control, because it lists twenty-three names - and they are not the nine apps the home page counts.
I read the full list off the open dropdown: OnePassApps, NewsFlow, MovieMatcherAI, PDF Organiser, CV Builder, Email Signature Builder, Chart Maker, Subtitle Workbench, Browser Teleprompter, Screen & Cinema Planner, Label & Card Maker, Social Preview Designer, Citation Formatter, Calendar Maker, Password Generator, Word Counter, Focus Timer, QR Code Maker, Ambient Noise Mixer, Time Zone Planner, Invoice Maker, Signature Maker, Screen Recorder.
Twenty-three areas, against a home page that counts nine apps. The home page's four counters read All 9, Live 2, Tools 0 and Studios 7, and its grid holds the two hosted apps and the seven studios.
So I checked what those extra names are. Outside the browser, plain HTTPS requests:
-
Fourteen of them answer HTTP 200 at
/apps/<slug>, each with its own title and its own meta description.CV Builder - Create and print a resume - OnePassApps.QR Code Maker - Static QR codes for links, Wi-Fi and contacts - OnePassApps.Chart Maker - CSV to bar, line and scatter charts - OnePassApps. Different titles, different byte counts - not one page served twenty times. -
Six of them answer 404 under the slugs I tried: PDF Organiser, Email Signature Builder, Browser Teleprompter, Screen & Cinema Planner, Label & Card Maker and Social Preview Designer. I tried both
/apps/and/studios/and two spellings each; the paths may simply be different from the names.
Here is the part that matters, and it is not what the status codes say. Those 200 pages carry noindex, nofollow, none of them appear in sitemap.xml (16 URLs, none of them these), and when I opened /apps/cv-builder in the browser, the running app did not show a CV Builder - it sent the visitor to the home page. The served HTML has the title and description; the app shell has no route for it.
Which makes the support dropdown the widest catalogue of OnePassApps apps anywhere on the site - wider than the app grid, wider than the nav menu, wider than the sitemap. The desk can take a request about a QR Code Maker that the rest of the product does not currently show you.
"My requests", and what it means to have sent something
The second tab is titled "My requests", sits under a small heading that reads "IN THIS BROWSER", and on an empty account it says:
No requests yet
Your reports and replies will appear here.
There is a "Refresh requests" button next to it, and the same guest-tracking sentence as the form.
The "How support works" panel on the form side is three numbered notes, and the third one is the one worth reading twice:
01 Before you write - The Help centre covers every app, billing, privacy and troubleshooting. The app guides walk through each app.
02 What we store - We store your message and contact email in our support system.
03 Replies - Replies appear under My requests. Guest tracking is saved only in this browser. Clearing site data removes that access, but does not delete the request. Keep your request reference: from another browser, email info@onepassapps.com with it. Sign in to keep requests with your account.
That is a specific promise and a specific limitation. The request itself is not deleted when you clear site data - you lose the thread, not the ticket - and the way back in is a reference you are told to keep. Underneath the form: "Can't use this form, or can't sign in? Email info@onepassapps.com."
"Report a bug" is a different form
The third tab opens a dialog rather than a page, and it is not the request form with a different title. It has a What happened? field with a 0 / 2,000 counter - two thousand characters, not five - an optional What you expected field, a collapsed Include technical details section, and a Report as control with two choices:
With replies
Anonymous
There is an Email for replies field next to it. So a bug report can be filed anonymously with no email address at all, which the general request form cannot do - there, the email is required. That asymmetry is deliberate and worth stating: the general request form asks who to reply to, the bug form lets you decline to say.
Both forms carry the same instruction, in slightly different words: "Leave out passwords and private details." on the request form, "Keep passwords and private details out." on the bug form.
Two small things that are easy to miss
A direct link can pick the category for you. The home page's plans band links "Contact support about billing or a refund" to /support?kind=billing, and that query string does what it says - I opened it and the "I'd like to…" dropdown was already set to "Billing" rather than "Help or question".
The support page is deliberately out of the index. Its robots meta reads noindex, nofollow, and it is not in sitemap.xml. It is still reachable and linkable - the home page's plans band links straight into it with Contact support about billing or a refund - but it is not something the site asks a crawler to list.
Honest limits
- One build, one browser, one day (4 November 2026), signed out. I did not sign in, so anything behind an account - stored requests, replies, the reference history - was not seen.
- I did not send a request. Everything above is what the page does before you press "Send request"; what happens afterwards is the app's side of it, and I did not test it.
- The character counters were read on an empty field and once at thirty characters. I did not paste five thousand characters to find the ceiling.
- The fourteen 200 responses are server responses. What a person sees at those URLs in a browser is the home page, because the app shell has no route for them.
- Six of the twenty area names did not resolve under the slugs I guessed. That is a statement about my guesses, not proof that those pages do not exist.
If you want to see the desk itself, it is at app.onepassapps.com/support, and the per-app walkthroughs are at app.onepassapps.com/guides.
I work on OnePassApps. This is our own product and every number above came from our own live build on the day I wrote it.
Top comments (0)