For support, trust and safety, and fraud teams

Your support bot can hand over an account.

Rightful holds every email, phone, payout and SIM change your AI agent makes until an independent check, and a person for the risky ones, signs that exact change. Everything else your bot does stays fast.

We'll email you about Rightful early access, and occasionally about Seconded. Unsubscribe anytime.

Or try a held change first · works alongside your support-agent vendor

Rightful · account changessample

add_recovery_email
account ••4821
new: maya.r.new@mailbox.example

recovery changeproposed by support agent
  1. Support agent (vendor A)proposed
  2. Independent check (vendor B)4 risk signals
  3. Owner, via email on fileasked
Held. The bot can't approve its own change.

Why now

In June 2026, attackers asked a major platform's AI support assistant to add their email to other people's accounts. It did.

The assistant added the new address as part of its normal password-reset flow, then sent the reset code to it. Reporters described high-profile accounts taken over this way before the platform shipped a fix. Sources: KrebsOnSecurity, Malwarebytes.

Carriers and fintechs already make their human agents run strong checks before changing how an account is recovered or paid out. An AI agent with the same account-change permissions needs the same checks, and it shouldn't be the one deciding whether it ran them.

A rule in the prompt

"Always verify before changing an email." A persuasive, urgent customer can talk a model out of its instructions.

The bot checks itself

If the model that wants to help also decides whether the request is safe, one bad conversation gets both votes.

A person on every change

Safe, but slow. Customers wait in a queue for a display name fix, and the reason you added an AI agent is gone.

Try it

Work a held change.

A customer on a new device asks your support bot to add a new email to an account. The bot is happy to help and drafts the change. Rightful holds it. Try approving it as the bot, then ask the real owner. Or switch to a display name change and watch it go straight through.

Support chat · account ••4821synthetic data

    Simulated for illustration. The customer, account and addresses are made up, and the owner's reply is scripted. Records are signed with real Ed25519 keys generated in your browser and verified on the spot. Nothing from the demo leaves this page.

    How it works

    Let the bot answer. Make account changes need a second key.

    01

    Hold the change tools

    Your support agent calls Rightful instead of the account API for email, phone, payout and SIM changes. Rightful holds the credential that makes the change.

    02

    Independent check

    A check from a different vendor than your bot reads the request and your risk signals: device, network, recent changes, urgency, step-up status. It signs its verdict over that exact change.

    03

    Risk tiers

    Low-risk edits go through in the conversation. Recovery changes need the owner to confirm through a channel already on file. Payout and SIM changes also need a person on your team.

    04

    A signed record

    Every change, allowed or blocked, gets a record: who asked, what the check saw, who confirmed, and the exact change. Your fraud team can verify it later.

    Default tiers

    passDisplay name, notification settings, address typocheck signs, instant
    ownerAdd or replace recovery email or phoneowner confirms on existing channel
    personPayout account, SIM or eSIM transfer, removing two-factorowner confirms, then your reviewer
    blockCheck flags a likely takeoverheld for your fraud queue

    You set the tiers and the signals. These are starting points, not rules we impose.

    • The bot never approves itself. The agent that proposes a change can't be the one that approves it, whatever the conversation says.
    • Confirmation goes to what's on file. Never to the new email or number the requester just gave.
    • Bound to the exact change. Each signature covers a digest of the account, the field and the new value. Change any of them and it stops matching.
    • Normal requests stay fast. Most support requests never touch a recovery channel, so most never wait.

    For support-agent vendors

    Ship account changes a fraud team will sign off on.

    If you sell an AI support agent that can take actions, your customers' trust and safety teams will ask what stops it from handing over an account. Embed Rightful and show them.

    • One call per change. Your agent proposes; Rightful returns allow, hold or block, with the reason.
    • Independent by design. The check runs on a different model vendor from the agent it's checking.
    • Your customer's policy. Each customer sets its own tiers, signals and reviewers.
    • Records they can verify. Signed records your customer can check without trusting you or us.

    Keep the bot. Keep the account with its owner.

    Early access is free while we build it. Leave a work email and we'll be in touch.

    We'll email you about Rightful early access, and occasionally about Seconded. Unsubscribe anytime.