For fraud and support teams

Verified Accounts.

The actions that matter wait for the account holder.

Your customers enroll once, with a passkey and one verified mobile number. Then a new plan, a new payee or a new address waits for their yes, on their own phone.

No ID uploads. Your sign-in stays as it is.

Live today: enrollment, and requests from your AI agent. In pilots: the window for your support team.

The BotShield app: a request from Northline to change the plan, showing what changes, with Confirm with Passkey and Decline
What your customer sees. Northline is an example company.
Enrollment · Live today

Enroll once. In under a minute.

  1. On your site or appThe Get BotShield Verified button: No ID Upload, No ChargeTap Get BotShield Verified.
  2. Tap 1Create your BotShield ID: continue with Apple or GoogleSign in with Apple or Google.
  3. Tap 2Your yes, in one tap: Create PasskeyCreate a passkey.
  4. Tap 3Your number is verified: stored safely, never given to anyoneVerify the number, once.
Under a minute · on the web or in the app · no ID upload
After that · your AI agents live today

A stolen password can sign in. The actions that matter still wait for the account holder.

  1. The askYour agent asks.Or your support team, in pilots.
  2. The termsChange your plan?FromUnlimited 5GToUnlimited 5G PlusPrice$95/moOn their own phone.Who is asking, and what will change.
  3. The answerConfirm with Passkey.Or decline. No code to type.
  4. The recordA signed yes.Or a plain no. Nothing changes until then.
Your people · in pilots · BotShield Verify

One small window, beside the ticket.

BotShield Verify: a customer opened from the company’s CRM, with Change the plan picked and Send
  1. Your team opens the customer and picks a reason.
  2. The customer confirms with their passkey. No code is texted at a request, and they read nothing back to you.
  3. Your screen turns to Verified.

Drawn from the design. Illustrative data.

The verified number

One verified number. It keeps the account BotShield Verified.

Every BotShield ID stands on one mobile number, confirmed once with a texted code at set-up. BotShield stores it encrypted and never sends it to you; you hold a pairwise BotShield ID instead. A new phone or a new number? Your customer verifies it again in the app.

With you
The number you have on file.You send it for one account.
same number?
The answer
Yes: BotShield Verified.No: refused, and your customer contacts you. We never send a number back.
same number?
On their phone
The number they verified.Once, when they set up their passkey.

Alongside the sign-in you already use.

Passkey or password, nobody migrates. BotShield reaches the account holder for the actions that matter, even when they aren’t the one signed in.

For stores

Know the agent ordering belongs to a verified customer.

At each order, one call to the BotShield Signal API answers verified, true or false. Nobody is asked: the customer already told their own agent what to buy.

BotShield Signal API  →

A store’s own order screen, drawn for illustration.

Pilots

Bring us your hardest account‑change problem.

Consumer companies with accounts worth protecting: credit unions, banks, carriers, insurers and subscription businesses. Your support team or your AI agent changes customer accounts today, and you want the account holder’s own yes on the changes that matter.

We reply with a 20-minute call and a live demonstration on a test account. How pilots work  →

What you get
  1. Set up with our team, on your real flow.
  2. Your use case shapes what ships next.
  3. A signed record of each answer, for your fraud team.
What we ask
  1. One flow: a support queue or one AI agent, and one button on one signed-in page.
  2. A named owner on your side, and a short weekly check-in.
  3. Your results, shared with us. If it works, your name as a reference.
What you will know at the end of the pilot
  1. How many of your customers became BotShield Verified when offered.
  2. How many changes they approved, and how many they declined.
  3. How long confirming a caller took, before and after.

Questions

What does my customer have to do?
Press Get BotShield Verified, once, behind your own sign-in. The first time, they set up BotShield on the web or in the app: a passkey, and their mobile number confirmed with one texted code. It takes under a minute. After that, nothing is texted: each change you send waits for their passkey, on their own phone. At the next company that uses BotShield, they already have a BotShield account, and getting BotShield Verified is one passkey tap.
Where does a request go?
To the account holder’s BotShield app, as a notification, never by text. With BotShield Verify, in pilots, your support team asks by the phone number on file, and the account holder also picks the two digits your team reads out before answering with their passkey.
What does my company get back?
A signed approval, or a plain no, for each change you ask about. For an order an AI agent places, the BotShield Signal API answers verified, true or false, and your customer is not interrupted.
What does verified mean?
The account holder confirmed in the BotShield app, on their own phone, with their passkey, and that account is BotShield Verified with your company. It says the account holder is the one answering. It is not a check of a document or of who the person is.
Do customers upload an ID?
No. BotShield never asks for an ID: no document, no selfie. The passkey on your customer’s own phone answers, and their identity never travels to make the check.
Do we replace our sign-in?
No. Your sign-in stays exactly as it is, and no customer list moves to us. Customers who have not pressed Get BotShield Verified keep the process you have today.