ConnectWiz for Threads
Built — in Meta reviewThreads support is built. Meta’s review is running. Here’s exactly where it stands.
Replies under your posts and mentions of your brand, triaged in the same desk as the rest of your public surface — code-complete, tested, and waiting on Meta’s approval gates. We publish the dependency instead of a vague "coming soon".
What’s built
Everything a Threads desk needs — waiting behind the gate
Replies & mentions, triaged
Replies under your posts and mentions of your brand land in the shared comment desk — the same queue, routing and ownership as Instagram, Facebook and YouTube.
Replies with attachments
Threads is one of only two platforms where a public reply can carry media — a screenshot answering a how-do-I question beats three paragraphs, and the desk supports it natively.
Hide & unhide
Moderation uses Threads' own states — hide what deserves hiding, restore what doesn’t, from the desk.
Wiz drafts, humans publish
AI drafts grounded in your content, human approval by default — the same public-surface discipline as every other channel here.
The real status
"Coming soon" usually means "not started". Here are our receipts.
Code: complete
Connect flow, ingestion, reply publishing (text and media, with status polling), moderation and mention handling are written and tested against Meta’s API shapes.
Gate 1: App Review
Meta’s standard permission review for publishing and reading replies/mentions — a normal application process, owned by Meta’s queue, not a partner program.
Gate 2: business verification
Meta’s business verification separately gates webhooks — without it, no events flow, however approved the permissions are. It’s the slower gate, and we say so.
Status you can read
The channel reports its own permission state, per permission — because on Threads an unapproved capability fails silently with an empty list, and an empty inbox has four possible meanings. Ours tells you which.
The honest fine print
What Threads is — and what no tool can offer
There are no Threads DMs
None of the permissions Meta publishes for Threads grants private messaging — the "conversation" endpoint is a public reply tree. A tool selling a "Threads DM inbox" is selling weather on the moon.
Not a publishing studio
This channel answers conversations; composing and scheduling original Threads posts is a different product, and we’re not pretending to be it.
500 characters, counted right
Threads counts length its own way — emoji cost more than one. Our composer measures the way Threads does, so a reply that fits here fits there.
No double-posting, ever
When Threads leaves a media reply in limbo, we mark it indeterminate and stop — because retrying an unconfirmed public post is how the same answer appears twice under your post.
Better together
A Threads desk that composes, not floats
The same inbox, day one
When the gate opens, Threads replies arrive as routed conversations — departments, assignment, tags, internal notes — because the pipeline is the one every live channel already runs.
Wiz drafts in brand voice
Public replies are the highest-stakes writing a support team does. The AI drafts from your own knowledge base, and a human approves — the public record stays yours.
One person, even in public
A Threads commenter federates onto the same contact as their Instagram DMs and email — public praise and private complaints stop being strangers.
Next to Instagram, where it belongs
Threads and Instagram share Meta’s account graph and usually the same social team — one queue, one history, one set of permissions covers both.
The playbook
Working a public-only channel well
Triage in lanes
Praise, complaints and leads deserve different clocks. Routing rules split public mentions into lanes so the complaint gets the fast lane without the thank-you jamming it.
Escalate to a private channel — by link
Threads has no DMs, so the honest move for anything personal is a reply carrying a link into WhatsApp, Instagram or live chat — the thread continues privately, on the same contact, and this page doesn’t pretend otherwise.
Measure the public clock
Reply time on a public surface is marketing, not just support — the same first-response measurement the inbox runs everywhere applies to public replies too.
Be first in line when the gate opens.
Leave your email and you’ll know the day Threads goes live — meanwhile, 22 channels are ready today.