Your customer clicks one button. Your support agent logs in. Nobody sees a password.
TrustedLogin brokers the WordPress login between your support team and your customer’s site, so your team fixes things instead of describing them. The exchange is encrypted before it leaves the customer’s server. TrustedLogin cannot read the credential it delivers. Whenever a customer asks, your team is in there in minutes.
“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
Today, getting into a customer’s site means a password in a ticket
A customer replies to a support ticket with their WordPress username and password, typed in plain text, sitting in your help desk forever. Or your team asks them to create a temporary account and walks them through creating one in their Users screen over email, then waits. Either way, a working password now sits in your help desk: anyone with access to the inbox can use it, it never expires on its own, and it is often the same password the customer uses elsewhere.
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 asks for a password again, and nobody has to maintain a bridge you built yourself out of WordPress Application Passwords.
How it works: one click, a temporary account, no password
1
Your customer clicks Grant Support Access, a button our free SDK code puts inside your plugin.
2
Your plugin creates a new WordPress account on their site for this request alone, with the role you asked for.
3
The login secret is encrypted before it leaves the customer’s server, with a key that lives on your own site, inside the Connector plugin. TrustedLogin’s servers relay and store it encrypted; they hold nothing that opens it.
4
Your support agent logs in from Help Scout or the TrustedLogin dashboard. Access ends on the schedule you configured in the SDK: a day at the shortest, a month at the longest.
5
Every login is on the record: which customer site it went to, when it happened, and whether it worked.
Sixteen hours of email, replaced by one click
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.