For teams, founders and agencies
One US number for the whole team's 2FA. Sharing is free.
Put the verification codes for your company accounts on one real US mobile line. Everyone you invite sees each code the moment it arrives, and nobody has to text the founder at 2am for a login.
The problem, in one story
Your payment processor, ad accounts, domain registrar and bank all text their codes to one person. That person is asleep, on a plane, or has left the company. The team waits. Most companies that grow past one founder have this problem, and most solve it with “can you send me the code?”
What a Cleat line does for a team
- One real US mobile line, owned by one verified person at your company.
- A shared inbox. Every text lands there the moment it arrives, for everyone in the workspace.
- Each teammate picks how it reaches them: by email, in their own Telegram chat, or just in the inbox. The workspace owner can also send every text to your own tools by webhook.
- Invite your whole team at no extra cost. Remove someone from the Team page and they stop seeing texts immediately.
- $24.99 a month for the line. That's the whole price.
How it compares with other ways teams share codes
| Approach | Number type | Team access | Price | Owner verification |
|---|---|---|---|---|
| Someone's personal phone | Mobile | Whoever holds the phone | Free | Not applicable |
| Authenticator codes in a shared password vault | No phone number | Through vault sharing | Part of your password manager plan | Not applicable; works where a service offers authenticator apps (1Password) |
| VoIP shared-inbox tools | VoIP; MultiMFA: “Some platforms reject VoIP numbers” (MultiMFA) | Yes | MultiMFA: from $5/month (MultiMFA) | Not stated |
| Daito | “mobile phone numbers from Germany” (Daito) | Yes | A plan plus “$49/month per number” (Daito) | Not stated |
| JoltSMS | Real-SIM US numbers | 10 seats | “$50/month per number” (JoltSMS) | Not stated |
| Cleat Line | Real US mobile line, not VoIP | Your whole team, free | $24.99/month | Government ID and selfie, or ID-only reviewed by a person, for the line's owner |
Our honest recommendation: where a service offers an authenticator app, keep those codes in your password manager's shared vault. Use a Cleat line for the services that insist on text messages or want a US mobile number on file.
Setting it up
- Pick the owner. An officer or ops lead who will verify their identity. The line belongs to that person's workspace.
- Subscribe and get the number. It's live right away. Invite the team by email from the Team page.
- Move accounts one at a time. Change the phone number on your payment processor, registrar, bank and ad platforms, and test each with a login.
- Route codes to where the team already looks. Each person can keep email forwarding on or connect Telegram. To post codes into a chat tool, point a webhook at your own endpoint or automation; see webhooks and the API.
- Write down who has access. Remove people from the team the day they leave.
Guardrails, stated plainly
One line, one verified owner. Teammates can read texts; they don't own the line. Cleat isn't for running lots of numbers, for accounts in someone else's name, or for a number nobody can trace. If a client wants an account in their own name, the client should own the line. Why every owner verifies · Acceptable use.
For agencies
For client ad accounts, stores and social accounts, the clean model is that the client owns the Cleat line and invites your agency as teammates. When the engagement ends, the client removes you and your access stops right away. Ownership stays where it belongs.
Related guides
Why some numbers get refused for codes in the first place: what is a non-VoIP number? Sharing a login that texts a Google Voice number? Read Google Voice and verification codes. The full price and billing rules are on pricing.
Questions
How many teammates can I invite?
Your whole team, at no extra cost. Each person chooses whether texts also reach them by email or Telegram.
Can teammates reply to texts?
No. Cleat Line receives texts; nobody can send from it today. When a service reads a code out over an automated call instead, the call is transcribed and the transcript appears in the shared inbox like a text, but nobody can answer or return the call.
Who has to verify their identity?
The person who buys the line. Teammates create an account and accept the invite sent to their email address.
Can we have one line per client?
Each line is its own subscription. For client accounts, we recommend the client owns the line and invites you.
Does it work with Slack or Microsoft Teams?
Not directly. Point a Cleat webhook at your own endpoint or automation and post from there, or use the REST API. Email and Telegram are built in.
Is sharing an SMS number allowed by the services we use?
Giving your team read access doesn't change who owns the account or the line. Check each service's terms. Cleat's terms make the account holder responsible for who they invite.
Sources
Facts about other companies come from their own pages, checked in September 2026.
- 1Password Support, one-time passwords https://support.1password.com/one-time-passwords/
- MultiMFA, shared SMS verification number https://multimfa.com/shared-sms-verification-number
- MultiMFA https://multimfa.com/
- Daito, 2FA via SMS https://www.daito.io/2fa-via-sms/
- Daito pricing https://www.daito.io/pricing/
- JoltSMS pricing https://joltsms.com/pricing