Schedule WhatsApp Messages from Claude: One Sentence, Approved First, Sent from Your Own Number (2026)

You hang up with a client at 16:50 and think: I need to confirm tomorrow's 2pm, but at 9am, not now. So you send it now, or you make a mental note and lose it. With the Blueticks connector you say that sentence to Claude once, read the draft, say yes, and the message is queued from your own WhatsApp number for the time you named.

Can Claude schedule a WhatsApp message for later, not just send it now?

Yes. You can schedule WhatsApp messages from Claude with the Blueticks WhatsApp MCP connector: the scheduled_messages_write tool sends a message now or later with a send_at time and updates or cancels what is queued, and scheduled_messages_read lists it. It runs from your own WhatsApp number as a WhatsApp Web linked device, not the Meta Cloud API, and you approve each send yourself.

The Blueticks MCP page answers: "Yes. The scheduled_messages_write tool sends or schedules text, media or polls and edits or cancels them, and scheduled_messages_read lists them, so Claude can schedule from your own number."

Blueticks is not the first WhatsApp MCP. The open-source personal-account servers, lharries/whatsapp-mcp and WAHA among them, came first, and the MCP page says Blueticks uses the same transport family, your number linked as a device. What Blueticks adds is the hosted part: one URL and a login. Landscape: our comparison of the best WhatsApp MCP servers and hosted WhatsApp MCP services compared.

Why schedule from Claude instead of opening an app?

Because the message occurs to you mid-conversation, not at the moment it should go. You think of Thursday's reminder on Monday and either send it at the wrong time or forget it. Telling Claude in the chat you already have open turns that thought into a queued send without switching apps, opening a calendar or filling in a form.

The plumbing is MCP, the Model Context Protocol, which lets a model call outside tools through one shared interface; an MCP WhatsApp server implements the tools part of the MCP specification. For a non-technical operator that is the appeal: AI-ops without the ops.

Prefer a form? The manual route is in how to schedule WhatsApp messages. This page is the Claude route.

What can Claude do with scheduled messages, audiences and campaigns?

The work splits across scheduled_messages_write, scheduled_messages_read, audiences and campaigns. The first sends now or later with send_at, with text, media or a poll, and updates or cancels; the second lists, gets and checks delivery. The audiences tool manages reusable contact lists. The campaigns tool schedules an audience for paced bulk delivery, with pause, resume and cancel. A utils tool can return the current date and time.

Per the Claude WhatsApp integration docs, describe the scheduling actions as "send (now, or later with send_at; text, media, or poll), list, get, update, cancel, ack". On the hosted server they sit in two tools: scheduled_messages_write (send, update, cancel) and scheduled_messages_read (get, list, ack). The MCP page calls audiences "Reusable contact lists used as targets for messages and campaigns" and gives campaigns one job: "Schedule audiences for paced bulk delivery."

You never type send_at; the docs say Claude picks the action from your request.

How do you connect Claude to your WhatsApp number?

Two pieces, no code. Link your WhatsApp number in Blueticks by scanning a QR code, as for WhatsApp Web. Then, in Claude, open Settings, then Connectors, choose Add custom connector, paste https://api.blueticks.co/mcp, click Connect, sign in and click Authorize. Enable it in a conversation and check WhatsApp is connected before you schedule WhatsApp messages from Claude.

Link your number. Scan the QR code in Blueticks. The Blueticks MCP page adds: "The WhatsApp connection has to be online for any client to read or send."
Add the connector. Settings, then Connectors, then Add custom connector. Name it Blueticks and paste https://api.blueticks.co/mcp.
Connect and authorize. Click Connect, sign in on the consent screen if asked, and click Authorize. Deny cancels and nothing is shared.
Enable it in a conversation.

The sign-in uses OAuth 2.0 with PKCE: per the Claude WhatsApp integration docs, Claude never sees your Blueticks password or an API key, and you disconnect by removing the connector. The click-by-click is in how to connect WhatsApp to Claude.

First test: ask Claude whether your WhatsApp is connected. The docs say tools that talk to WhatsApp fail with "No WhatsApp engine is connected" until it is, and the engine tool's status action tells you the state. If not, scan the QR code again first.

How do you schedule one message from Claude, approved first?

Paste one prompt that names the recipient, the time with its time zone, the text, and a draft-first instruction. Claude may look up the chat and the current date, shows you the draft and the resolved time, and waits. You say yes, approve the tool call, and the message is queued with a send_at time. Then ask for your scheduled list.

The prompt, with a recipient and text you replace:

"Schedule a WhatsApp message to Dana Levy for tomorrow at 9:00am, my time (Europe/London): 'Morning Dana, confirming our call at 2pm today. I will bring the revised quote.' Show me the draft and the exact date and time you will use before you schedule anything, and wait for my yes."

Name the recipient as it appears in your chats, or as a full international number. State the time zone. Keep the draft-first instruction.

Paste the prompt with the Blueticks connector enabled.
Claude may read before it writes. It may check the current date and time (the utils tool's current_date_time action) and may look up the chat (the chats_read tool's search action). Both are reads, and whether it makes them is Claude's choice.
Read the draft and the resolved date and time. If the time is wrong, correct it in one line before you approve.
Say yes and approve the tool call when Claude asks. That is one scheduled_messages_write send with a send_at time.
Ask: "List my scheduled WhatsApp messages." The message appears with the time you set. That is your confirmation it was accepted.

The Blueticks MCP page on approval: "Reading and sending are separate tools. Sending goes through chats_write, scheduled_messages_write and campaigns, and works only while your WhatsApp is linked and online. Approve each call yourself and avoid 'Allow always' for Blueticks." The docs add that on a read-only grant, write actions "are not offered at all", so this recipe needs the full grant, and you read every call before you allow it.

What does 'tomorrow at 9am' resolve against?

Against the date and time Claude works from, which is why the prompt states the time zone. The utils tool has a current_date_time action, so Claude can check the current date and time. Whether it makes that call is its choice; the draft-first instruction means you see the resolved date and time before anything is queued.

How do you confirm the send was accepted?

Step 5 is the confirmation: the scheduled_messages_read tool's list action returns what is queued, and your message appears with the time you set. Receipts the next morning are in checking scheduled WhatsApp messages with Claude; moving or cancelling it is in rescheduling and cancelling with Claude.

Does the first result fit the free plan?

Yes, with a call to spare. A timed send is one scheduled_messages_write call plus whatever reads Claude chooses, so the recipe costs at most 4 tool calls: up to 2 optional reads, 1 scheduled send and 1 list. The Claude WhatsApp integration docs set the ceiling: "On the free plan, the MCP server and the REST API share one quota of 5 requests per 6-hour window" and "every tool call Claude makes counts once." Then: "When it runs out, tool calls fail with a rate-limit error until the next window." And: "Paid plans are unlimited."

The connector works on any plan. The Blueticks MCP page says it "has no extra charge and works on any plan" and that "paid plans have no request limit"; plan details are on the pricing page.

What breaks: if the window is used up, the send fails with a rate-limit error and nothing is queued. Do step 5 before you close the window.

Schedule your first WhatsApp message from Claude. No bridge to run, no API key to copy: one URL, a login, your own number, and every send approved by you. Start free at blueticks.co/signup.

How do you run one paced campaign to people who expect to hear from you?

Point Claude at an audience you already have, give it the message, and ask it to pause the campaign before it starts. The campaigns tool schedules an audience for paced bulk delivery; you resume or cancel by asking. It costs more calls than one send, at least an audience read plus a campaign create, so it is the natural paid-plan step.

The prompt, in the shape of the docs' own example:

"Create a campaign to my Clients audience with this message: 'Our November price list is ready. Reply here if you would like it sent over.' Show me the audience count and the message first, and pause it before it starts so I can check."

An audience, per the Blueticks MCP page, is one of the "Reusable contact lists used as targets for messages and campaigns"; a campaign's job is to "Schedule audiences for paced bulk delivery." Building the audience is its own recipe: build a WhatsApp contact list with Claude.

On "people who expect to hear from you", the MCP page's line is "Consent and opt-out for anyone you message are your responsibility." Clients who asked for your price list, yes. A list you bought, no, whatever tool sends it.

What breaks: ask for the campaign without the pause instruction, approve the create call, and it starts. Keep the pause instruction in the prompt.

What can't it do, and where does a scheduled send actually run?

It is not the Meta Cloud API and not an official Meta product. It cannot promise your number will never be restricted. It does not message anyone on its own; Claude acts on your instruction. And where the queued send runs depends on your plan: in your browser on Basic and Standard, cloud-hosted on Pro.

Not the official API. The Blueticks MCP page describes an unofficial WhatsApp Web automation engine, says it "is not the Meta Cloud API, and Blueticks is not affiliated with or endorsed by WhatsApp or Meta", and adds: "If you need Meta's official Business Platform, that is a different product."

No ban promise. The same page, verbatim: "We cannot promise that WhatsApp will never restrict a number. Consent and opt-out for anyone you message are your responsibility."

Claude acts on your instruction. It does not message anyone on its own.

Any plan, with a free allowance. The connector works on any plan; the free plan allows 5 requests per 6 hours, shared with the API, and paid plans have no request limit. The pricing page answers where the send runs: "On Basic and Standard, Blueticks runs in your browser. On Pro, your agent, schedules and campaigns are cloud-hosted and keep working even when your computer is off."

What breaks: on a browser plan, a closed laptop at 9am means the 9am message does not go. Leave WhatsApp Web open, or treat Pro as the price of not thinking about it.

FAQ

Can Claude actually schedule a WhatsApp message for later? Yes. The Blueticks MCP page: "The scheduled_messages_write tool sends or schedules text, media or polls and edits or cancels them, and scheduled_messages_read lists them, so Claude can schedule from your own number."

Do I need to know how to code? No. Blueticks runs a hosted MCP server at https://api.blueticks.co/mcp; add it to Claude once and, in the docs' words, "Claude can act on the WhatsApp account connected to your Blueticks account", with no API key to copy and no server to run.

Does it send from my own number? Yes. You link your own number the way you link WhatsApp Web, by scanning a QR code, and the transport is a WhatsApp Web linked device on that number.

Is this the official WhatsApp Cloud API? No. It is not the Meta Cloud API and not an official Meta product, and Blueticks is not affiliated with or endorsed by WhatsApp or Meta.

Will scheduling from Claude get my number banned? Blueticks makes no such promise. In its words: "We cannot promise that WhatsApp will never restrict a number. Consent and opt-out for anyone you message are your responsibility."

How much can I do on the free plan? The MCP server and the REST API share one quota of 5 requests per 6-hour window; every tool call Claude makes counts once, and when it runs out tool calls fail with a rate-limit error until the next window. Paid plans are unlimited.

Schedule your first WhatsApp message from Claude

That is how you schedule WhatsApp messages from Claude: one sentence, one draft you read, one yes, and the message is queued from your own WhatsApp number for the time you named. The WhatsApp Claude pairing is one hosted URL and a login. The first time you send WhatsApp from Claude at a set time, approve it yourself and check the list before you close the window.