Dispatch schedules and publishes LinkedIn posts for agencies and in-house teams. What makes it different is what travels with the post: the figure, the publisher, the date, the sentence it was taken from — and a check that keeps running after the post is live.
We took apart 35 tools before writing a line: 16 social suites and 19 LinkedIn-specific products. Not one attaches a source to a claim. Their approval workflows approve copy. Nobody approves the evidence.
The demonstration account, rendered exactly as Dispatch renders it. The figures and the flag are seeded demo data, not a claim about any quarter.
Three things happen to a post here that happen nowhere else. The rest — calendar, queue, approvals, client links, analytics — works the way you already expect it to.
Sources are gathered and read first: publisher, title, date of publication and the exact sentence a figure came from. The post is written against them, not decorated with them afterwards.
A figure in the body with nothing behind it is flagged before anyone is asked to sign off. Approval needs a named person and is bound to a fingerprint of the exact text — edit an approved post and the approval falls away, including when the edit puts the words back.
Cited pages are re-fetched on a schedule and compared with the sentence recorded at the time. When a page changes, the live post resting on it is named, with the old figure, the new one and the date of the check.
Every feature we expected to find, we found: white-label domains, multi-stage approvals, no-login client review, scheduled first comments, bulk import, best time to post. Most of what a scheduler does is table stakes and we say so. Then there is this.
| Capability | 16 social suites | 19 LinkedIn tools | Dispatch |
|---|---|---|---|
| A research step before writing | none | none | yes |
| A citation attached to a claim | none | none | yes |
| Verification of a statistic | none | none | yes |
| A currency check — this figure was superseded | none | none | yes |
| A check the cited page still says it | none | none | yes |
| A claim-level risk flag: opinion or evidence | none | none | yes |
| Slop detection — while all 35 ship AI generators | none | none | yes |
XONIK teardown, September 2026: 35 products checked feature by feature — 16 social management suites and 19 LinkedIn-specific tools. Every row above was absent from all of them.
In July 2026 LinkedIn discontinued its own “enhance your post” AI writer and shipped a proofreader in its place, beside a reader-facing “seems like AI slop” control — over a million uses in three weeks, and roughly 40% fewer views on the posts it flags. The platform moved from generation to assistance. Thirty-five third-party products did not.
In agency retainers scheduling takes one to two hours of a seventeen to twenty-eight hour month; research and content take ten to fifteen. And clients who leave name delivery and value, not price — while three quarters of agencies believe they left over budget. A tool should defend the ten hours, not automate the one.
Photographed against the demonstration account while it was running.





Every other product in this category puts a box on the screen and sends whatever is in it to a model. This one will not draft at all until it has something true to build from, and it tells you what is missing rather than filling the gap itself.
A draft is assembled from the facts somebody has confirmed about the business, and from nothing else. Where a fact is missing the draft says so and names who has to supply it — it is never invented.
A figure in the body has the publisher, the date and the sentence it came from attached to it. A figure with nothing behind it is flagged before anybody is asked to sign off.
The draft is compared with this account's own published posts before you see it. A repeated opening or a figure used three months ago is named, with the earlier post, rather than quietly rewritten.
Anything a model helped write carries the label wherever the person who will publish it can see it — the panel, the client's approval link, the notification, the export and the report.
It arrives on the screen where it is approved, every edit is kept as a version with a name against it, and approving is a separate act from writing.
A comment on your own post can be answered with a draft, and a message to one person you name can be drafted from what you typed about them. Both go through the same checks a post does. Neither has a send button, and there is no integration that becomes one: the text is yours to copy and send from wherever you normally send things.
There is no path from drafting to the queue. Approval by a named person is the only one, and editing an approved post drops the approval — including when the edit puts the words back.
Ten client brands in one account, each isolated: its own destinations, voice, sources and media, with nothing shared by accident. A monthly report that shows the work rather than describing it.
One brand, its founder's profile and the people who speak for it. Company pages are coming to the Enterprise plan. Sign-off sits with a named person. When a board, a customer or a regulator asks where a figure came from, the answer is one click and it is dated.
Opens a link, sees the post as it will appear with its sources underneath, approves it or sends it back with a reason. No account, no password, no seat to pay for.
Every plan is hosted by XONIK: nothing to install, nothing to patch. Pay monthly, or yearly and save about 35%. Every plan runs on your own AI key, so we never sell you tokens or credits.
On the hosted edition there is nothing to install and nothing to keep patched. It runs on XONIK's own LinkedIn application and publishes to people's profiles — a founder, a partner, the people whose names are on the work. Limits are counted per account rather than per brand, enforced by the software, and a post's slot is handed back when it is pulled or fails for good. Change plan or cancel whenever you like: your plan runs to the end of the period you paid for, and on a yearly plan the months you did not use come back.
Printed here rather than discovered on the Connections tab, because an account opened by somebody who cannot connect the page they meant to post to is an account that is never opened twice.
The connection is authorised by a person, and this network only offers the page to somebody who already administers it. A colleague who is an admin can connect it instead; it does not have to be you.
Page verification is what this network asks for before it will grant a developer application access to publish for an organisation. It is done on the network, by the company, and not by this product.
Posting as yourself is authorised by you signing in, so a founder or a consultant publishing under their own name can start without either of the two above.
You put your own key in, from whichever vendor you have an account with. It is tested the moment you paste it and sealed before it is stored. The model bill is yours and goes to you from your vendor: we do not resell model access, we do not mark it up, and we could not — the calls leave under your key, not ours. If you stop paying us, the key keeps working; it was never ours to switch off.
Larger accounts will be able to run on their own LinkedIn developer application, with their own rate limits and company-page access. This is coming to the Enterprise plan; until then every account runs on ours, which needs nothing from you.
Monday to Friday, 09:00 to 18:00 India Standard Time, excluding Indian public holidays. A person reads what you send. There is no queue and no ticket number. Outside that window nobody is watching a screen: what there is instead is a product that holds a post rather than losing it, tells you when a connection has failed, and never publishes twice. There is no response-time promise and no uptime commitment — neither has a measured history behind it yet, and a promise nobody can keep is worse than none.
Signing up puts you in a sandbox: a seeded account with published posts, their sources attached, and a draft written to trip the repetition guard on purpose so you can watch it catch one. Nothing in it reaches the network — publishing goes to a mock — and every surface says so. No destination to connect, no key to paste, nothing under your name. A live account is set up afterwards, in a conversation.
The application and the evidence layer, proved by automated checks that include the panels driven in a real browser.
Publishing to a person's own profile uses a permission the network grants without a review. That is the hosted edition, and it works from the first connection.
Company-page access, which the network reviews separately and over weeks. Nothing about profiles waits on it.
500 calls a day for the application and 100 per member — the development tier's limits. The software budgets for those rather than for the larger allowance, so a tier change can only give it more room than it planned for.
No scraping, no automated connection requests, no automated messages, no scraped lead database.
No customer results, case studies or ROI figures. There are none yet, and a product about evidence cannot open with an unsourced number.
No. Dispatch publishes to LinkedIn profiles through XONIK's approved LinkedIn application, so you connect your profile and start. Company pages are coming to the Enterprise plan.
Dispatch re-fetches the page on a schedule and compares it with the sentence recorded at the time. When it differs, the live post resting on it is named, with the old figure, the new one and the date of the check. It flags; it never edits or deletes a published post.
No. They open a signed, expiring link scoped to one brand, see the post as it will appear with its sources underneath, and approve it or send it back with a reason.
No. Every row carries the brand it belongs to and every query is filtered by it. Cross-account reads are the failure most likely to end a company, so isolation is proved by a dedicated suite of automated checks rather than by convention.
Never without an approval carrying a name. Approval is bound to a fingerprint of the exact text, so editing an approved post drops the approval — including when the edit puts the words back.
No, and the line is drawn at sending rather than at writing. No scraping, no automated connection request, no automated message, no scraped database of people. Dispatch will draft a reply to a comment on your own post, and a message to one person you have told it about, because both are writing. It sends neither, and it keeps no record of who you wrote to: a lead database plus automated outbound is what gets a platform application revoked, and that stops every customer publishing rather than only the one who wanted the feature.
Hosted plans run from a free trial to an agency plan, billed by the year, with limits counted per account rather than per brand, enforced by the software, and a post's slot handed back when it is pulled or fails for good. The licensed edition is a licence fee instead: higher in the first year because it includes the installation, lower each year after for the licence, the updates and the support window. One licence covers one person and one company; a second company is a second licence rather than a bigger one. Both editions run on your own model key, so neither has a token allowance we sell you.
On a hosted plan, cancel from the panel at any time. Inside 14 days of a first payment we refund it in full, no reason needed. After that we refund the months you have not begun, less what the payment provider kept — three months into a year, nine come back. A licence is a term rather than a subscription: what it costs to end one early is in the licence agreement, which you read before you sign it rather than after.
Yes, and it is the part of this nobody else does. Your headline is read beside every comment you make and in every search result you appear in, and nothing has ever checked it — a post carrying a figure is flagged here before anybody approves it, and a headline carrying the same figure has been checked by nothing, by anybody, ever. So paste your headline and your About section in and they go through the same checks a post does: every figure against its source, every claim against what is confirmed about the business, every line against what you have already published. Then it is watched — a year on, it says so, because it is the one piece of published text nothing re-reads. Two things it will not do: it cannot read your profile, because the network does not hand that text to an application and we will not pretend to have looked; and it gives you no score, because there is nothing measured behind one.
You do. Research briefs and drafts are assembled with the help of a language model, and everything generated is labelled as such and waits for a person to approve it.
Run it, yes — that is the licensed edition, and it is what most people mean. It is installed on your own server, under your own name, on your own LinkedIn application, and the database never leaves your machine. The source, no: the software is licensed and not sold, ownership does not move, and source escrow is what we arrange when the worry is what happens should XONIK stop. Your model key is your own in both editions, so your model spend never depended on our goodwill either.
Whose LinkedIn application the post leaves under, and that decides what can be posted to. Hosted runs on ours and publishes to people’s profiles. A company page needs the network’s Community Management access, which it grants to one application for its own pages, so a page is reachable only from an installation holding that access for itself — the licensed edition, on your application. That access is something you apply to the network for and it reviews over weeks; it can refuse. A profile needs no review at all. Everything else is the same software.
It warns for thirty days first, on every screen, and names the date. If the date passes, publishing stops and nothing else does: you can still sign in, read every post, every source and every approval, and export them. The data is kept for the period in the licence agreement and is then destroyed. Renewing at any point in that window starts publishing again with nothing lost.
Yours, and it goes to you from your own vendor. You put your own key in; the calls leave under it. We do not resell model access and we do not mark it up. If you stop paying us, the key keeps working — it was never ours to switch off. Your access to the network, your model spend and, in the licensed edition, your data do not depend on our goodwill.
Yes. Signing up puts you in a sandbox with seeded posts and their sources, where publishing goes to a mock and nothing reaches the network. Every surface says so. A live account is set up afterwards, in a conversation.
Never. It does not like, comment, message or connect on anybody's behalf, it does not scrape feeds or profiles, and it does not run inside LinkedIn through a browser extension. It publishes only posts a person has approved, through LinkedIn's official API.
No. The trial runs for 14 days with one brand and ten posts, and nothing is charged until you choose a plan.
The trial takes an email address and posts five times. If the evidence layer is not worth it by the fifth post, nothing has been spent.