Social Media Marketing

Sendible

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Sendible Ltd · sendible.com

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Community Manager v1.0 · The Agency Lead v1.0 · The Brand Governance Officer v1.0 · The Analyst v1.0 · The Data Protection Officer v1.0 · The Skeptic v1.0 · rubric v1 · evaluated 22 Sep 2026

Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Skeptic

Weighted verdict

Counts the network logos, then asks which are official API integrations and what each one cannot do. Has watched a platform change break a feature overnight, and wants to know what the vendor did last time and whether the archive survived it.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Skeptic

Publishing & calendar

How this is scored

Scheduling across networks: per-network formatting, the calendar as a working surface, bulk operations, and what happens when a post fails at 3am.

0 — One post to several networks at once with no per-network variation and no calendar.

3 — A calendar with scheduling and basic per-network text variants; failures are discovered by noticing the post never appeared.

5 — Per-network content, media and first-comment variants, drafts, a usable calendar with drag-and-drop, and failure notifications with a retry.

8 — Bulk upload and CSV import, evergreen or queue-based scheduling, link shortening with UTM rules, preview matching each network's actual rendering, and stories, reels or shorts supported where the API allows.

10 — Publishing is dependable at volume: hundreds of scheduled items across many accounts without collision, best-time recommendations from the account's own history, and every failure surfaced with the platform error and a one-click recovery.

Report an error

The Skeptic

The captured page names a Publishing module and one concrete capability — a bulk importer with profile tags, locations and hashtags for scheduling a month of content. Beyond that we found no public information on a calendar, per-network formatting, previews, or what happens when a scheduled post fails overnight. 1

Report an error

Engagement & community inbox

How this is scored

Comments, mentions and messages in one queue — the half of the job that is customer service wearing a marketing badge.

0 — No inbox; engagement happens in each native app.

3 — Mentions and comments listed per network with no assignment, no status and no history.

5 — A unified inbox across the connected networks with assignment, status and internal notes, and the conversation history visible per person.

8 — Direct messages included where the API allows, saved replies, SLA timers, sentiment or priority flags, spam and hidden-comment handling, and escalation to a helpdesk.

10 — The inbox is a service desk: every public and private interaction in one queue with ownership and response-time reporting, moderation rules that act automatically, and a per-person history spanning networks.

Report an error

The Skeptic

We found no public information on any inbox — no comments, mentions or messages capability appears in the module list. I count engagement features from what is shown, and nothing is shown. 1

Report an error

Analytics & reporting

How this is scored

Measurement across networks with different metrics and retention windows, plus the reporting an agency hands a client.

0 — Per-network vanity counts pulled live; no history kept.

3 — Basic post and profile metrics with a short history and no cross-network comparison.

5 — Metrics stored beyond the networks' own retention, cross-network comparison, competitor benchmarking, and scheduled exports.

8 — Custom dashboards, white-label client reporting, paid and organic combined where the API allows, UTM-based attribution into web analytics, and audience demographics over time.

10 — Reporting answers what worked and why: metrics normalised across networks with the differences documented rather than hidden, full historical retention independent of platform windows, and exports an agency can hand over unedited.

Report an error

The Skeptic

An Analytics module is named and that is the whole of it; we found no public information on which metrics are collected, retention, cross-network comparison, or exports an agency could hand a client. A label is not a measurement. 1

Report an error

Approvals, roles & brand safety

How this is scored

How a team of several people and an agency publish to a brand account without an accident — and who can be shown to have approved what.

0 — Shared login, no roles, no approvals.

3 — Separate users with a coarse admin split and an optional single approval step.

5 — Roles per network and account, multi-step approval workflows, comments on drafts, and an activity log.

8 — Client or brand workspaces with strict separation, configurable approval chains including legal review, content locking after approval, and an audit trail of who changed and published what.

10 — Governance a regulated brand could pass an audit on: complete audit trail of edits, approvals and publications, enforced approval before anything reaches a network, granular permissions per account and action, and no shared credentials anywhere in the design.

Report an error

The Skeptic

A Collaboration module is named, with no public information on roles, approval steps, comments on drafts, or an audit trail. I cannot tell who approved what, and the captured page does not either. 1

Report an error

Network coverage & API resilience

How this is scored

Which networks are supported through official APIs, how quickly the vendor follows platform changes, and what the customer keeps when a network breaks or leaves.

0 — A few networks, some through unofficial means, with no statement about API status or platform changes.

3 — The major networks through official APIs, but feature gaps undocumented and platform changes communicated after they bite.

5 — Official API integrations across the main networks with the per-network limitations documented, and a changelog when platform behaviour changes.

8 — Broad official coverage including the newer networks, a public status page for integrations, advance notice of deprecations, and full export of the customer's own publishing and engagement archive.

10 — Platform dependency handled as an engineering commitment: official partner status where it exists, per-network capability documented and kept current, rapid response to API changes with the history to show it, and an archive that stays the customer's whatever a network does next.

Report an error

The Skeptic

I count network logos first, and this capture shows me none: we found no public information on which networks are supported, whether through official APIs, per-network limitations, or any changelog when platforms change. An Integrations module name without a single network identified, and no statement about API status, is everything the page offers. 1

Report an error

European sovereignty

How this is scored

Where the archive and the community conversations are processed, who the contracting entity is, which subprocessors touch them. Independently sourced by the sovereignty pipeline. Note that the networks themselves are non-EU by definition — this criterion judges the tool, not the platforms it talks to.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed.

3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — AI features, analytics, support tooling — are non-EU without an explained safeguard.

8 — EU or DACH hosting on named infrastructure, EU contracting entity, complete subprocessor list published, and the handling of message content from the networks described with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a DPA that squarely addresses the personal data arriving from the networks in comments and messages.

Report an error

The Skeptic

The only address on record is 82 Great Eastern St, London — a United Kingdom, not European Union, entity — and no sovereignty attributes are on record. Hosting location and subprocessors are unstated in the captured page. 1

Report an error

Pricing transparency

How this is scored

Whether a team can compute the real annual invoice for their account and user count — including the tier where approvals and the inbox begin — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A per-user headline exists, but the number of social accounts included, or the tier where approvals and the inbox appear, is unstated.

5 — Per-user or per-account prices public with billing period stated, but at least one commonly needed capability (inbox, approvals, reporting) sits in an unpriced tier.

8 — Every tier priced publicly with account and user limits, feature boundaries, the cost of an extra account or seat, minimum term and VAT treatment stated.

10 — Complete price computability: annual invoice derivable for a given number of social accounts, users and client workspaces, with every add-on priced.

Report an error

The Skeptic

We found no public prices at all — no tiers, no per-user figure, no account limits — and the captured page's call to action is "Book a demo". A team cannot begin to compute an annual invoice from anything shown. 1

Report an error

European sovereignty — proven facts

1 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Legal entity	Incorporated in GB	1/3 pts	2 Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	Not determined	—	uncited Report an error
Subprocessors	Not determined ⚠ unverified	—	uncited Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Subprocessors. Not confirmed on the vendor’s own pages as captured.
AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

15 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
14 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
12 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
10 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
6 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us

Do you know more about Sendible? Tell us Report an error on this page

Sources (13)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

1 Vendor page sendible.com Checked 22 Sep 2026 Details →
2 Terms of service — found from the homepage www.sendible.com Checked 30 Sep 2026 Details →
3 Privacy policy — found from the homepage www.sendible.com Checked 30 Sep 2026 Details →
4 Publishing & calendar — found from sitemap www.sendible.com Checked 1 Oct 2026 Details →
5 Publishing & calendar — found from sitemap www.sendible.com Checked 1 Oct 2026 Details →
6 Engagement & community inbox — found from sitemap www.sendible.com Checked 1 Oct 2026 Details →
7 Engagement & community inbox — found from sitemap www.sendible.com Checked 1 Oct 2026 Details →
8 Analytics & reporting — found from sitemap www.sendible.com Checked 1 Oct 2026 Details →
9 Analytics & reporting — found from sitemap www.sendible.com Checked 1 Oct 2026 Details →
10 Approvals, roles & brand safety — found from sitemap www.sendible.com Checked 1 Oct 2026 Details →
11 Approvals, roles & brand safety — found from sitemap www.sendible.com Checked 1 Oct 2026 Details →
12 Network coverage & API resilience — found from sitemap www.sendible.com Checked 1 Oct 2026 Details →
13 Network coverage & API resilience — found from sitemap www.sendible.com Checked 1 Oct 2026 Details →