Is the Claw Messenger number shared, or do I get my own number?
On self-serve plans you don't bring your own number: each account gets a sending number assigned automatically, shared across accounts. On Agency, each sub-tenant gets its own visible sending number, distinct within your account but not reserved for you alone.
The short answer
If you need a number reserved for your business alone, Claw Messenger's public plans don't sell one. Sendblue, Photon, and Blooio sell a number of your own from $100 to $289 a month per line. If a shared sending number is fine, Claw Messenger starts at $5 a month.
- Best for
- An agent that texts its owner, a family, or a small set of known contacts, or a reseller that needs a separate visible number per client.
- Not for
- A brand that needs a number only it uses, or a verified business name in the thread.
At a glance
| Self-serve number | Assigned automatically, shared across accounts |
|---|---|
| Agency number | Its own visible number per sub-tenant. Distinct within your account, not reserved for you alone. |
| Bring your own number | No |
| Pick the area code | No |
| Who reaches your agent | Only phone numbers registered to your account |
| Registered contacts | Trial 1 · Base 1 · Growth 5 · Plus 20 · Pro 50 · Agency 10,000 per sub-tenant |
| One contact, one account | A phone number can be registered to one Claw Messenger account at a time |
| Other customers see your threads | No |
Which number does each plan send from?
| Plan | Price | Messages / month | Sending number | Registered contacts | Group chats |
|---|---|---|---|---|---|
| Base | $5/mo | 250 | Assigned automatically, shared across accounts | 1 | No |
| Growth | $15/mo | 2,000 | Assigned automatically, shared across accounts | 5 | Yes |
| Plus | $25/mo | 6,000 | Assigned automatically, shared across accounts | 20 | Yes |
| Pro | $50/mo | 15,000 | Assigned automatically, shared across accounts | 50 | Yes |
| Agency | $199/mo per sub-tenant + $250 once | 1,000 per sub-tenant, then $0.005 each | Its own visible number per sub-tenant: distinct within your account, not reserved for you alone | 10,000 per sub-tenant | Yes |
| Enterprise | Custom | Custom | Agreed after a scope review | Custom | Custom |
Messages count inbound and outbound texts. Group chats need at least two registered contacts, so trial and Base accounts can't open one. Full plan details are on plans and limits.
What does a shared sending number mean for you?
You don't bring your own number. Each account gets a sending number assigned automatically (shared across tenants), and when you register an end-user's number, messages between them and that sender route straight to your API.
- Your conversations stay yours. A contact's replies go only to the account that registered that contact. Other customers can't read your threads or receive your contacts' messages.
- Recipients see a phone number. The thread shows the sending number, not your company name. Your agent can introduce itself in the first message.
- The number normally stays the same. If the sending number can't send, messages move to a backup number so conversations keep going. Recipients then see that number. If a number has to be replaced, recipients may get a short note that the agent is writing from a new number.
Why do only registered contacts reach your agent?
Registration is how a reply finds the right agent. When someone texts the sending number, Claw Messenger looks up which account registered that person's phone number and delivers the reply there. That is also why a phone number can be registered to one account at a time: each person's thread has to belong to exactly one agent.
It does two more jobs:
- Strangers can't command your agent. Numbers you haven't registered don't reach it. If your agent can act on texts, only the people you chose can ask it to.
- It keeps use conversational. The contact allowance grows with the plan, from 1 on Base to 50 on Pro. That fits an agent talking with people it knows, not a mailing list.
Register contacts in the dashboard or with POST /api/routes. When your agent texts a new number first, that number is registered for replies automatically, if a contact slot is free. Release one with DELETE /api/routes/{phone_number}. If a number is already registered to another account, the request returns a conflict error.
Agency: its own visible number per sub-tenant
Agency is for resellers and teams that run a separate workspace per client. Each sub-tenant has its own API key, contacts, usage, and visible sending number. The number is different from your other sub-tenants and from the self-serve number. It is distinct within your account, not reserved for you alone.
A sub-tenant costs $199 a month from the moment you create it and includes 1,000 messages, then $0.005 per message. Agency onboarding is $250 once, and access is by request after a use-case review. Volume limits apply per sending line and count all traffic on that line; see Agency line limits. Read the Agency docs for the provisioning API.
How do other iMessage APIs handle numbers?
| Provider | Shared-number plans | Own-number plans | Source |
|---|---|---|---|
| Claw Messenger | Base to Pro, $5 to $50/mo. Sending number assigned automatically, shared across accounts. | Agency, $199/mo per sub-tenant: its own visible number, distinct within your account, not reserved for you alone. No number reserved for one customer on public plans. | Pricing |
| Sendblue | Free Sandbox, $0: shared number, up to 10 verified contacts, no outbound messaging. | AI Agent, $100/mo per line with its own number, inbound-first. Enterprise, custom, with full outbound. | sendblue.com/pricing |
| Blooio | Starter, $39/mo (5 new contacts/day). Commercial Shared, $89/mo (15/day). | Own-number commercial plan, $289/mo per line. Inbound, $98/mo, reply-only. | blooio.com/pricing |
| LoopMessage | Shared sender, $20/mo, starting with 50 monthly contacts. Can't start conversations. | Light from $59.99/mo per sender. Starting conversations is a paid add-on. | loopmessage.com/pricing |
| Photon | Free (up to 10 users) and Pro, $25/mo (up to 100 users), on managed shared numbers. | Business, $250/mo per line with its own number, up to 50 new contacts/day. | photon.codes/pricing |
When another option fits better
- You need a number only your business uses. Choose a per-line plan from Sendblue, Photon, or Blooio.
- You need your verified brand name in the thread. Look at Apple Messages for Business; see our Apple Messages for Business guide.
- You want your own Apple ID and already run a Mac. BlueBubbles is free software; see BlueBubbles vs Claw Messenger.
Common questions
Do I get my own phone number on Claw Messenger?
Not on self-serve plans. You don't bring your own number. Each account gets a sending number assigned automatically (shared across tenants), and when you register an end-user's number, messages between them and that sender route straight to your API. On Agency, each sub-tenant gets its own visible sending number.
Is an Agency number reserved for my company alone?
No. Each Agency sub-tenant's number is distinct within your account: different from your other sub-tenants and from the self-serve number. It is not reserved for you alone.
Can I bring my own number or choose the area code?
No. Numbers are assigned for you, so you can't port in a number or pick an area code.
Can another Claw Messenger customer see my conversations?
No. A contact's phone number can be registered to one Claw Messenger account at a time, and that contact's messages route only to that account.
What if a contact is already registered to another account?
The registration is refused with a conflict error. If you think that is wrong, email clawmessenger@mail.tin.computer.
Will my contacts always see the same number?
In normal operation, yes. If a sending number can't send, Claw Messenger moves messages to a backup number so conversations keep going, and recipients then see that number. If a number has to be replaced, recipients may get a short note that the agent is writing from a new number.
Related pages
A shared sending number works for your agent? Start with one contact and prove the reply path.
Start the 7-day trial