No. Claw Messenger works on any platform — Linux, Windows, VPS, Docker. We handle the iMessage infrastructure.
iMessage, RCS, and SMS. Your agent falls back gracefully depending on the recipient's device.
Not currently. Claw Messenger supports text messages and generic media attachments from HTTPS URLs, not voice calls.
Claw Messenger supports text messages and generic media attachments from HTTPS URLs. Native iMessage voice-note bubbles are not verified today, including waveform rendering, duration metadata, and transcription fields. An audio file sent as a generic attachment is not native voice-note parity.
Base is $5/mo (250 messages and 1 registered number), Growth is $15/mo (2,000 messages and up to 20 registered numbers), Plus is $25/mo (6,000 messages and up to 20 registered numbers), and Pro is $50/mo (15,000 messages and up to 20 registered numbers). All plans include a 7-day free trial, iMessage, RCS, SMS, tapbacks, and read receipts.
Each inbound or outbound text counts as one message. Tapbacks, typing indicators, and read receipts are free.
Yes. Upgrade or downgrade anytime from the billing page. Changes take effect immediately with prorated billing.
Your agent stops sending and receiving messages until the next billing cycle. You'll get an SMS notification. Upgrade anytime to increase your limit.
Yes. All plans include a 7-day free trial. Card required for the 7-day trial. You won't be charged until the trial ends. Cancel anytime during the trial and you won't be billed.
Yes, anytime. No contracts, no cancellation fees.
Sign up, subscribe, register your phone number, then paste the setup prompt to your OpenClaw agent. The whole process takes about one minute. See the full setup guide.
Personal builders continue to self-serve billing. Agency builders can enter the request-only dedicated visible-number review at $199/month per provisioned subtenant plus a one-time $250 onboarding fee, subject to fit and number availability. A request or onboarding payment does not reserve a number, start monthly billing, or begin provisioning. Existing shared-line Agency accounts keep their current setup. Product builders use the managed rollout intake to define audience, routing, and timing; Product does not include a dedicated-number promise.
Base includes 1 registered number. Growth, Plus, and Pro support up to 20 registered numbers. You can register numbers in the dashboard or programmatically using your API key. See the docs.
Self-serve plans support no more than 20 registered numbers. Email clawmessenger@mail.tin.computer to discuss a managed rollout.
No. Numbers are assigned from our pool, so you can't pick the area code.
See the Hermes setup guide for the full walkthrough.
On the dashboard after signing in. A key is auto-generated when you subscribe. The full key is only shown once — save it immediately.
Make sure your phone number is registered — either on the Phone Numbers page or via the API. Only registered numbers can reach your agent. Also check that your gateway is running and the plugin is enabled. See common fixes.
No. Only numbers you have registered can reach your agent. Messages from unregistered numbers are ignored.
First check the send status. ok: true means the request was accepted or reached a non-error send state, but it is not final delivery proof on its own. If the status is failed, correct the request before trying again. If the status is not_confirmed, do not call the message delivered yet. For your first setup test, send one message to a phone you control, reply from that phone, and confirm the reply reaches your agent, webhook, or backend. See the quickstart.
No. ok: true means the send request was accepted or reached a non-error send state. It is not final delivery proof on its own. Use the status field when it is available: accepted means the request started, failed means the message was not sent, delivery_confirmed means delivery was confirmed by available status evidence, and not_confirmed means final delivery is not confirmed from the available evidence.
For the first controlled test, usually leave service out and let Claw Messenger choose the available channel for that recipient. Set service only when you specifically need to test a channel. If an explicit channel returns an accepted response but the message does not arrive, do not treat that as delivered. Try the same controlled test without service, then email clawmessenger@mail.tin.computer with the timestamp and a redacted response if it still does not work.
A successful first test has two parts: your agent sends one plain message to a phone you control, then the recipient replies and that reply reaches your agent, webhook, or backend. The outbound send is useful setup feedback. The reply is the proof that your agent can participate in a normal text thread. See the docs quickstart.
We can set up multi-tenant configurations for agencies and resellers. Email clawmessenger@mail.tin.computer.
Email clawmessenger@mail.tin.computer and we'll get back to you quickly.