Skip to content
TPThreadPilotMessenger operations for local businesses

Campaigns & replies for Facebook Messenger

Your Messenger campaigns and replies, together.

Plan messages, see who is eligible to receive them, and handle replies in one workspace for your Facebook Page.

For businesses with customers who already message their Page. Not for purchased lists or cold outreach.

FacebookMessengerYour Page. Your conversations.

Start with a demo and assisted setup. Self-service activation is not open yet. Email admin@threadlabs.tech to arrange your walkthrough.

14 days. Up to 10,000 total trial messages. One Page. No credit card required.
Try ThreadPilot free for 14 days. No charge unless you select a paid plan.

Everything below happens to one campaign.

01Dashboard02Campaigns03Inbox04Operations05Reports

Your working day

Less guesswork. More clarity.

See who you can reach, what happened to your campaign, and which reply needs you next.

You sent the promo on Friday.

By Monday you still cannot say how many messages were actually recorded as sent, how many were held, or whether the Page was healthy while it ran.

Every attempt stays attached to the campaign, including the ones that did not go out.

You are about to message your whole list.

Nothing tells you who is still inside the Messenger reply window, who opted out last month, or whether this Page is in a state where sending is safe.

Readiness is decided before the send, and a failed check names itself.

Someone replied on Saturday.

The reply is in one place and the campaign that prompted it is in another, so it is found on Tuesday if it is found at all.

The conversation and the campaign that started it stay in the same record.

One campaign, from start to finish

From your first draft to a clear result.

From message and audience to scheduled sending, replies, and results. Choose a stage or play the fourteen-second walkthrough.

Protected sending controls

A safety check can stop a send.

Check consent, timing, sending speed, and your Page connection before a campaign goes out. If a check fails, you can see why.

Sending starts gradually in week one. Opted-out contacts stay excluded. Understand the sending checks.

Eligible sends are subject to platform rules, consent, message windows, and account safety limits. Delivery is never guaranteed, and ThreadPilot does not claim otherwise. Customers remain responsible for their connected Pages, content, audience consent, and Meta/Facebook account standing.

Audience story

Know who you can reach right now.

See who is eligible now, who opted out, and who is outside the messaging window before you prepare a campaign.

Explore audience management · Understand Messenger eligibility

ThreadPilot is not for purchased lists, scraped contacts, or cold outreach. It is built for businesses with an organic Messenger audience from people who already messaged their Page.

Audience preview1,345contacts evaluated
1,204
Reachable now

Eligible in this preview and available for the next readiness decision.

Illustrative product walkthrough. No customer data or live provider activity.

Reachable now, 1,204. Eligible in this preview and available for the next readiness decision.

Who this is for

Built around your business day.

For businesses with a Facebook Page and customers who already message it.

Restaurants and cafes

A quiet Tuesday evening.

Which regulars can I message about tonight, right now?

The audience preview separates who is reachable now from who is held or outside the window.

Salons and spas

A two o’clock cancellation.

Who can I tell about the open slot without breaking consent or sending too fast?

Consent and sending speed are checked before the message is prepared, not after.

Gyms and studios

Members who stopped coming in.

Which lapsed members am I still allowed to contact?

Opt-outs and closed messaging windows are excluded and counted, with the reason named.

Multi-Page operators

Five Pages, one morning.

Which campaign needs me first, and which Page is not healthy enough to send?

Each Page keeps its own contacts, limits and reporting, and Page health is visible before dispatch.

Getting started

Connect your Page. Prepare your first campaign.

Connect your Page. Prepare your message. Review before you send.

Read the setup guide · Explore the full product workflow

See setup, sending, and recovery details
  1. 01 · Connect

    Link your Facebook Page

    Authorise the Page through Facebook. ThreadPilot stores the resulting Page credential and never shows it back to anyone, including you.

    The Page credential is stored and never shown back. This screen reports token validity without displaying the token.

  2. 02 · Know

    See who you can reach

    Contacts are grouped by engagement, recency, and VIP status, and separated into who is reachable right now and who is not, with the reason attached to each.

    2 of 3 contacts are reachable. The third is named as outside Meta’s messaging window, not silently dropped from the count.

  3. 03 · Prepare

    Write it and choose the audience

    Message, audience, readiness, then schedule, in that order, because what readiness says can change when you send. A review of the whole campaign renders above the button that commits it.

    Readiness is asked before scheduling, because a Page that cannot send today makes send-now the wrong answer.

  4. 04 · Send

    Paced, not dumped

    Delivery runs inside per-second and per-minute limits with a burst-and-pause cycle. If the error rate climbs, the run pauses itself rather than continuing into a problem.

    This run paused itself when the error rate crossed its threshold, rather than continuing into a problem.

  5. 05 · Watch

    See it while it happens

    Replies, delivery outcomes, and Page health while the run is live, with recorded outcomes marked as recorded and unconfirmed ones marked as unconfirmed.

    Recorded outcomes are labelled recorded. An outcome the provider has not confirmed reads as unconfirmed, never as zero.

  6. 06 · Recover

    Stop it, and pick it back up

    Stop a run mid-flight. Expired Page tokens, held sends, and failed batches each surface with what happened and what to do next. Duplicate-send safeguards help prevent repeat sends. Check uncertain delivery outcomes before considering a retry.

    A reply that cannot be sent says which rule stopped it, so the next action is visible without opening a log.

You are not doing this alone. Tell us about your business and Page when you request assisted setup, then use the in-app checklist to see what is still outstanding. Ask us for help.

Your first fourteen days

Make your first campaign a clear one.

No credit card required. Guided setup. One Page. The trial ends with a clear picture of your audience and recorded outcomes, not an automatic charge.

Up to 10,000 total trial messagesRequest a demo
TrialExplore your audience and resultsChoose a plan

Paid plans

Choose the monthly volume you need.

Every paid plan includes unlimited connected Pages. Ask us about the offered trial during assisted setup, then choose a plan in your workspace.

Starter

$99/month

200,000 eligible sends/mo

Unlimited connected Pages

For smaller campaign volumes.

Request a demo

Pro

$349.99/month

1,000,000 eligible sends/mo

Unlimited connected Pages

For higher campaign volumes.

Request a demo
What counts as an eligible send?
Only a message that passes consent, the messaging window, and eligibility checks. Held and skipped messages do not count against your plan.
What happens when I reach the quota?
During beta, reaching an allowance does not automatically stop messaging. Trial, payment and quota cutoffs are not currently enforced. Consent, opt-outs and provider restrictions still apply. Review your actual plan and usage in your workspace. For capacity beyond your plan, talk to us.
How am I billed?
Monthly, per plan. There is no annual term. Plan changes are handled through Stripe, which shows the exact amount before you confirm.
What happens on day 15?
A no-card trial does not create an automatic charge. During beta, trial expiry does not automatically stop messaging. Review the arrangement for your workspace before choosing a plan. Your contacts, campaigns, and recorded outcomes stay where they are.

Delivery is never guaranteed. Review your workspace’s actual billing arrangement and contact support about discrepancies or refunds. Extra message allowance is not a cash refund. ThreadPilot fees are separate from Meta/provider charges; ad publishing and advertising spend are not included.

Before you decide

Clear answers, before you connect a Page.

Can Meta still restrict my Page?

Yes. No tool can promise otherwise. ThreadPilot reduces operational risk through consent, pacing rules that limit sending speed, opt-out suppression, and Page-health controls. You remain responsible for your Page, content, and audience consent.

How do opt-outs work?

Natural-language opt-outs are recorded and excluded from future campaigns. Nothing silently re-subscribes a contact.

How fast does a campaign send?

It depends on Page state and provider limits, so ThreadPilot reports pace instead of promising speed and slows when the available evidence requires it.

Can I manage more than one Facebook Page?

Yes. Every paid plan includes Unlimited connected Pages. Each Page keeps its own contacts, campaigns, limits, and reporting. The trial covers one Page.

Do I need a card to start the trial?

No. Signup collects no payment details, so a no-card trial does not create an automatic charge. During beta, trial expiry does not automatically stop messaging; review your workspace’s actual plan and contact us about continuing.

What happens to my data if I stop?

Your contacts, campaigns, and recorded outcomes stay in your workspace. You can request removal at any time through data deletion.

Bring your Page to ThreadPilot

Plan the message. Keep the conversation going.

Prepare a campaign for your existing audience, manage replies, and follow recorded results in one workspace.

Questions about volume or onboarding? Talk to Sales.

delivery evidence
  • “The recipient had opted out, so ThreadPilot did not send.”
  • “The Messenger reply window had closed, so ThreadPilot did not send.”
  • “ThreadPilot skipped this recipient during the configured contact rest period.”
  • “ThreadPilot prevented a duplicate send.”
  • “No usable Messenger recipient identity was available.”