Stop asking customers for their passwords.
Every password pasted into a ticket is a breach you haven’t had yet — and a support queue that moves at the speed of screenshots. TrustedLogin puts your agent inside the customer’s site in one click, with access you can scope, revoke, and prove.
“We’ve implemented TrustedLogin at LearnDash and the team and customers LOVE IT. Such a great UX. We had so many awkward back and forths [to get site logins] previously, and now it’s just BOOM, DONE, and secure all at the same time.”
Matt Cromwell, then Senior Director of Customer Experience, StellarWP
No more “Can you send us your admin login?”
The customer types their password into a reply. In plain text. It sits in your help desk forever. Nobody deletes it. Agents leave; the password stays. And the day that customer gets breached, your ticket history is where their credentials were found.
With TrustedLogin there is no password in that thread to leak, and nothing left behind on the customer’s site to remember to delete. Your customer clicks a button inside your own product, your agent is in the site, and the account disappears when the window you set runs out. Nobody on your team ever asks for a password again.
The professional way into a customer’s site.
A Grant Support Access button inside your own plugin. One click creates a temporary account with exactly the role you need, encrypted before it leaves their server, expiring on a schedule the customer controls. No password ever exists to leak.
Asking for wp-admin credentials says “hobby project.” A support-access button in your plugin says you take their site as seriously as they do.
Customer clicks once → your agent is in → access expires on its own. Free SDK, Help Scout integration, a record of every login.
Support that can’t log in can only guess.
At GravityKit, before TrustedLogin, a ticket that needed site access ran like this: customer submits a ticket overnight, 8 hours to first response.
Support determines it needs site access and emails the customer asking them to create a login, 8 hours 15 minutes.
The customer responds with credentials, hours later, 12 hours.
The login doesn’t work; another round of emails, 16 hours.
Sixteen hours in, the bug is still a description in a ticket, because nobody has seen the site yet. Those are four bounces your team stops making: the customer grants access from your first reply, your agent opens the site, and the fix lands in the exchange that used to ask for a login.
Built by a support team that still runs on it
GravityKit built TrustedLogin for its own support desk and still runs on it every day: 2,589 logins across 1,789 customer sites, roughly 38 a month. Plugin companies and agencies run it the same way.
When a customer asks who can see the login, the answer is: your team, and no one else
Sooner or later a customer’s security review asks what your support team can reach, and who else can see it. The answer is your own support team, and no one else: the login is sealed on the customer’s site with a key that only your site holds, so TrustedLogin passes it along and cannot open it, and nothing readable ever sits in a ticket. Access ends on a schedule the customer reads before granting it, and they can cut it short from their own WordPress admin. If we were unreachable, the button inside your plugin sends them to your own support page rather than failing with no explanation. If we went out of business, the SDK in your plugin is open source and the Connector on your own site ships its source through WordPress.org, so neither stops working.
One-time secrets
Send a password without leaving it in the ticket
Sometimes the ticket needs one value rather than a login: an API key, a database password, a third-party token. Type it into the thread and it sits in your help desk for as long as the ticket does. Send a one-time link instead: it is destroyed on first read, or at an expiry you choose up to 30 days, and TrustedLogin can’t open it either. Nothing is left in the ticket to leak, and nothing reaches our servers to breach.
AI agents are next, under the same rules
We’re extending the same access rules to AI agents next: a scoped account that expires on schedule and can be revoked like any other session.
Two or three support people usually fit the $49 plan
Support teams of two to three people typically run on the $49/mo Support plan.