How can we help?

Before you begin: you need a ThreadPilot account, access to the Facebook Page you want to use, and an existing Messenger audience for that Page. A purchased list or imported contact is not permission to message someone. If a control is unavailable for your role, ask your workspace owner or admin.

This guide follows Campaign Studio: Page → Message → Audience → Replies → Review. You can prepare and save a draft before deciding to schedule it.

1. Connect and check your Page. In Getting started, choose Connect Page and complete Facebook authorization. If your Page is already saved, use Manage Pages instead. Confirm that the intended Page appears in Pages; a saved connection alone does not prove current sending permission. Resolve connection problems.
2. Prepare your audience. Open Contacts for that Page and review the contacts you intend to reach. Have a saved customer group available to select. “Reachable” is a current estimate, not a delivery promise; check holds and exclusions before continuing. Understand who you can message.
3. Choose the Page and message. Open New campaign. At Page, choose the Facebook Page. Use Continue to message; select the approved first message when required, or write the message where the builder permits it. Enter a Campaign name so you can find this draft later. If no message is ready, follow the offered next action or ask your owner/admin; do not treat a pending message as approved. When template approval applies.
4. Choose who receives it and how replies are handled. At Audience, select the intended Customer group and read its reach breakdown. At Replies, review what happens after a customer replies. Replies wait in Inbox unless a selected Page flow continues the conversation. Check that any selected flow is the one you intend.
5. Save a draft first. In Review, under Save or schedule, choose Save as draft and use the save action shown. After saving, confirm the campaign is listed as a draft in Campaigns. Saving a draft sends nothing. Returning to Getting started may offer Resume saved draft; review that saved work before creating another campaign.
6. Review before scheduling. Open your saved draft in Campaigns and choose Edit Campaign. In the editor’s Review step, set Start at using the displayed timezone and check Repeat (use One time for a single run), then choose Save Changes. Saving timing does not give the draft permission to run. Back on the campaign, choose Open Review, check the Page, message, audience, replies and timing, and resolve any named blockers. Choose Schedule campaign only when the review confirms readiness, you are authorized to schedule, and you intend it to run. If your role cannot schedule, ask an authorized teammate to review it. Scheduling does not guarantee delivery; recipients are checked again at send time. Resolve a blocked campaign.

After confirmation: check the campaign’s saved status and timing in Campaigns. Review recorded outcomes in Reports and customer replies in Inbox. If an outcome is uncertain, check it before retrying. If you cannot proceed, send support the named reason without credentials or customer message contents.

Workspace links require sign-in and your existing permissions. Request a demo and assisted setup if you do not have an account yet.

Open Pages in your workspace and check the connection message for the affected Page. A connection or permission problem can prevent sending.

If ThreadPilot asks you to reconnect, complete Facebook authorization using an account with access to that Page. Then review the connection status again. Reconnecting does not override Facebook restrictions or campaign safety checks.

If the reason remains unclear, contact support. Never send passwords or access credentials in a support message.

Check the conversation’s sending status in Inbox. The customer’s messaging window, consent, or your Page connection may prevent a reply.

Follow the reason shown beside the reply action. A saved conversation is not proof that a new message can be sent. Do not switch campaigns or repeatedly retry to get around a closed window.

If a previous reply has an uncertain outcome, check its status before trying again: it may already have reached the customer.

The offered trial lasts 14 days, covers one Page, and requires no credit card; a no-card trial does not create an automatic charge. During beta, trial expiry, payment failure, cancellation and exhausted allowances do not automatically stop messaging. Consent, opt-outs and provider restrictions still apply.

Review your actual plan, billing source, period, usage and available payment evidence in your workspace. A checkout return or an active subscription alone does not prove an invoice was paid. Stripe plan changes show the amount before confirmation; existing arrangements are not automatically replaced. Contact support from your workspace for a billing discrepancy.

Compare plans and trial limits. Your contacts and campaign records remain in your workspace; see data deletion to request removal.

Blocked means a requirement prevents the campaign or affected send from proceeding. Read the named reason before taking another action. A blocked state does not prove that earlier attempts sent nothing; check recorded outcomes too.

Check these in order:

• The correct Page. the campaign must use a connected Page you have permission to access.
• Message readiness. if this message type requires an approved template, a draft, pending or rejected one cannot be used. See template status.
• Reachable audience. your group may contain contacts that cannot currently receive this message. Review the reasons shown for holds and exclusions.
• Account limits and timing. a soft quota is a usage allowance: sending can continue past it, subject to other checks. An enabled hard cap can block sending when that allowance is used. Trial expiry and other account restrictions are separate. Check your current plan and usage, the named blocker and the scheduled time; exceeding a quota alone does not always mean sending stops.

Resolve the named requirement, then review the campaign again. A connection fix or plan change does not bypass consent, opt-outs or messaging-window rules. Get help if the reason is unclear.

List membership does not establish consent, eligibility, an active reply window, or provider readiness. Every recipient is checked individually at send time, and any one check can hold that message back.

Common checks that can reduce a send:

• Duplicate protection. recorded sends are checked to help prevent sending the same campaign again. Check uncertain outcomes before retrying.
• Opt-out. a revoked consent is permanent until the customer opts back in.
• Reply window. Free-form Messenger messages require an open messaging window. Other permitted message types have their own requirements; an approved template does not make every contact eligible.
• Cooldown and per-customer limits. your own pacing rules, protecting the Page from over-messaging.

A smaller eligible count than your Audience size is the system working. The count is reported as what it is, never rounded up to match the list.

A template is a reusable message submitted for approval where the selected message type requires it. These statuses apply to those provider-reviewed messages, not every draft campaign or every free-form reply. Follow the requirements shown for your Page and chosen message type.

• Draft. saved locally but not approved for use as an approved first message.
• Pending. submitted and awaiting a provider decision. Waiting is not approval.
• Rejected. the provider declined it. Edit and resubmit; resending does not appeal it.
• Approved. approved as of the last synchronization ThreadPilot performed.

That last qualifier matters. An approved status is a locally synchronized record of a provider decision, and provider state can change after the check that recorded it. Check the last synchronization information where shown; an unavailable or old check is not a live approval. Approval applies to that message and Page, not to the campaign or every recipient.

Uncertain means ThreadPilot did not receive enough authoritative evidence to call the operation successful or failed. It is deliberately not reported as either one.

Failed and uncertain need different checks:

• Failed. the provider rejected the operation. Review the named failure and the available next action before trying again.
• Uncertain. the outcome is unknown. The message may have been delivered. Do not assume a retry is safe, because retrying a delivered message sends it twice.

Duplicate protection covers sends ThreadPilot recorded. It cannot cover a delivery it never received confirmation of, which is exactly why uncertain is kept as its own state instead of being folded into failed.

Unreachable is several different situations that need separating before you treat any of them as a fault.

• Opted out. consent was revoked. This is honored permanently and is not a defect.
• Blocked or undeliverable. the provider refused delivery to that person, commonly because they blocked the Page. Consent is untouched.
• Excluded. held back by platform hygiene rules or imported without a usable contact point.
• Missing a contact point. no Messenger identity or no phone number, depending on the channel.
• Out of Page scope. the contact belongs to a Page this campaign does not target.

Each is recorded as its own status rather than a single unreachable bucket, so a consent decision is never mistaken for a delivery problem you could fix by retrying.

Scheduled, externally recorded, provider-confirmed, failed, and uncertain are five different outcomes, and the surface showing you the result should also show which one it is.

• Scheduled. accepted by ThreadPilot, not yet attempted.
• Externally recorded. logged by you as done elsewhere. ThreadPilot is repeating your claim, not verifying it.
• Provider confirmed. the provider acknowledged it. This is the only one that means published.
• Failed. the attempt was rejected.
• Uncertain. no authoritative answer was received.

If a screen cannot tell you which of these applies, treat the result as unknown rather than published. Unknown is reported as unknown throughout the product, and never shown as a zero or a success.