Social Media Marketing
Sendible
Provenance unknown Report an errorPanel 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
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 panel's verdict
Sendible is a social media marketing product whose judged record is a single captured vendor page, and the bench's scores track that. Publishing leads at 2-3, grounded in a bulk importer with profile tags, locations and hashtags that schedules a month's worth of content in minutes. Engagement inbox and pricing transparency both sit at 0 with a range of 0: we found no public information on comments, mentions or messages in the published modules — Dashboard, Publishing, Collaboration, Analytics, Integrations, Content Management, Share Button — and the only route to detail on the page is booking a demo or joining a webinar. Analytics and collaboration governance score 1-2 and 1 respectively on module names alone, and we found no public information naming the supported networks behind the Integrations module. Sovereignty scores range 0-1 against a record carrying no sovereignty attributes and a legal address at 82 Great Eastern St, London EC2A 3JF. The bench computed no notable disagreements among the judges' scores, so the spread reflects thin public evidence rather than opposing readings.
Speaks for it
- A bulk importer with profile tags, locations and hashtags can schedule a month's worth of content in minutes
- Publishing scored 2-3, the highest range in the bench's scoring
- The published page names its full module list, from Dashboard to Share Button
- Demos and webinars are offered for detail the public page does not carry
Held against it
- Engagement inbox scored 0 with no spread, as no inbox, comment or message capability appears in the published modules
- Pricing transparency scored 0 — no tiers, per-user figures or account limits are public, and the call to action is "Book a demo"
- We found no public information naming the supported networks behind the Integrations module or their API status
- No sovereignty attributes are on record, and the sole legal address — 82 Great Eastern St, London EC2A 3JF — is a United Kingdom rather than EU entity in the judges' reading
- Analytics scored 1-2 and collaboration governance 1, on module names alone, with no public information on metrics, retention, roles or approvals
Best for
- You need high-volume scheduling — a month's worth of content in minutes through bulk import — as your core workflow
- You weigh publishing most heavily and are ready to ask about networks, metrics and approvals in the offered demo or webinar
Avoid if
- You need an engagement inbox for comments, mentions and messages — the bench scored that criterion 0 with no spread
- You must compute an annual invoice from public prices before speaking to sales
- You need evidence of roles, approval workflows and an audit trail before adopting — collaboration governance scored 1 with no spread
The scores
Publishing & calendar
Show reasoningHide reasoning
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.
The Community Manager
A bulk importer with profile tags, locations and hashtags is published, along with a Publishing module — so scheduling at some volume exists. But I found no public information on the calendar as a working surface, per-network variants, previews, or what happens when a scheduled post fails overnight, and for someone who lives in the failure notifications, that silence decides it. 1
The Agency Lead
The vendor's page names a publishing module and a bulk importer that schedules a month of content with profile tags, locations and hashtags — real bulk evidence, but nothing more. We found no public information on a working calendar, per-network variants, previews, or what happens when a scheduled post fails overnight, which is exactly where my twelve client brands would live or die. 1
The Brand Governance Officer
The captured page confirms scheduling and a bulk importer that tailors posts with profile tags, locations and hashtags, which is real publishing capability. We found no public information on the calendar as a working surface, per-network variants, or what happens when a scheduled post fails overnight — and an unattended failure with no visibility of who attempted what is precisely what I need to see described. 1
The Analyst
The vendor's page names a publishing module and a bulk importer — "schedule a month's worth of content in minutes" with profile tags, locations and hashtags — which is genuine volume-scheduling evidence. But we found no public information on the calendar as a working surface, per-network variants, previews, or what happens when a post fails overnight, so this sits near the floor. 1
The Data Protection Officer
The captured page shows a bulk importer with profile tags, locations and hashtags for scheduling a month of content in minutes, which is genuine bulk-scheduling evidence. We found no public information on a calendar working surface, per-network variants, or what happens when a scheduled post fails overnight — the failure path is exactly where notification content becomes a processing question for me. 1
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
Engagement & community inbox
Show reasoningHide reasoning
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.
The Community Manager
The published modules are Dashboard, Publishing, Collaboration, Analytics, Integrations, Content Management and Share Button; I found no public information on an inbox, comment or mention handling, assignment, saved replies or per-person conversation history. This is the half of my job that is customer service wearing a marketing badge, and the public pages say nothing about it. 1
The Agency Lead
We found no public information on a unified inbox, comments, mentions or direct messages; the module list covers publishing, collaboration and analytics with nothing on engagement. That is the customer-service half of my job, and the captured pages show none of it. 1
The Brand Governance Officer
The seven modules named on the captured page include publishing, collaboration and analytics, and we found no public information on any unified inbox, assignment, status or conversation history. With comment and message handling entirely unevidenced, I can only score the baseline. 1
The Analyst
We found no public information on an inbox, comment or mention handling, assignment, saved replies, or conversation history; the module list names a dashboard and collaboration but nothing on the customer-service half of the job. Nothing in the captured page evidences engagement management of any kind. 1
The Data Protection Officer
We found no public information on any inbox, comment queue, or message handling; the module list names Dashboard, Publishing, Collaboration, Analytics, Integrations, Content Management and Share Button, and none of it evidences engagement management. Every comment and message arriving from the networks would be personal data this company processes, and I cannot see where that conversation archive lives or how long it is retained. 1
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
Analytics & reporting
Show reasoningHide reasoning
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.
The Community Manager
Analytics appears in the published module list, and that is the entire public detail: I found no information on which metrics are measured, how long history is kept, cross-network comparison, or client-ready exports. A module name doesn't tell me what an agency hands a client. 1
The Agency Lead
The analytics module is named and nothing else; we found no public information on which metrics are kept, cross-network comparison, retention windows, or white-label reports a client could be handed. From these pages I cannot evidence the reporting an agency invoices for. 1
The Brand Governance Officer
An analytics module is named and nothing more: we found no public information on which metrics are stored, for how long, or whether cross-network comparison and client-ready exports exist. A module name on a navigation bar is not measurement I can put before a board. 1
The Analyst
An analytics module is named, and that is the whole of it: we found no public information on which metrics are stored, retention beyond the platforms' own windows, cross-network comparison, or UTM attribution into web analytics. For a buyer who needs normalised figures with the differences documented, there is nothing here to assess. 1
The Data Protection Officer
Analytics appears only as a module name, and we found no public information on which metrics are captured, how long history is kept, or what export formats exist. Retention on the archive is the question I ask of any measurement store, and nothing public answers it. 1
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
Approvals, roles & brand safety
Show reasoningHide reasoning
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.
The Community Manager
A Collaboration module is advertised; I found no public information on roles per user or account, approval workflows, comments on drafts, or an audit trail of who approved and published what. Several hands on one brand account is exactly the scenario the public pages don't speak to. 1
The Agency Lead
A collaboration module is named, but we found no public information on client workspaces, roles per account, approval chains that include the client, content locking or an audit trail — the strict separation my twelve client brands demand. The module name is the entire basis I have. 1
The Brand Governance Officer
A collaboration module is named on the captured page, and that single word is the entire record on the question I care most about. We found no public information on approval workflows, roles, per-account permissions, an audit trail of who wrote and published what, or how credentials are handled — for a brand account this dimension is essentially undescribed, and I will not credit governance I cannot see. 1
The Analyst
A collaboration module is named, but we found no public information on roles, approval workflows, comments on drafts, content locking, or an audit trail showing who approved and published what. A module name alone leaves the governance mechanics this criterion asks about entirely unassessed. 1
The Data Protection Officer
Collaboration is named as a module, which hints that more than one person can work here, but we found no public information on roles, approval steps, or an activity log showing who approved and published what. Without an evidenced audit trail I could not reconstruct an incident after the fact. 1
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
Network coverage & API resilience
Show reasoningHide reasoning
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.
The Community Manager
An Integrations module is the only published signal; I found no public information on which networks are supported, official versus unofficial API access, per-network limitations, an integration status page, or export of our own publishing and engagement archive. I want to hear about an API change from the vendor before it bites, and nothing public speaks to that. 1
The Agency Lead
An integrations module is listed, and we found no public information on which networks are supported, whether through official APIs, on per-network limitations, or on export of my clients' archive if a network changes. None of the resilience story an agency depends on is visible. 1
The Brand Governance Officer
An integrations module is named while we found no public information identifying the supported networks, their API basis, a status page or changelog, or export of the customer's publishing and engagement archive. What a brand keeps when a network changes course is unanswered in everything captured. 1
The Analyst
An integrations module is named, yet we found no public information naming the supported networks, whether they connect through official APIs, any integration status page, or export of the customer's publishing and engagement archive. How the vendor follows platform changes is equally unevidenced. 1
The Data Protection Officer
An Integrations module exists, but we found no public information on which networks are supported, whether through official APIs, or what the customer keeps of their publishing and engagement archive when a network changes or leaves. The export question matters doubly for me because that archive is the customer's record of processing personal data. 1
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
European sovereignty
panel opinion
Show reasoningHide reasoning
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.
The Community Manager
The published legal address is 82 Great Eastern St, London — a United Kingdom entity, outside the EU — and I found no public information on hosting location, subprocessors, certification or a data-processing agreement. From public pages I cannot tell where the community's conversations would be processed or who else would touch them. 1
The Agency Lead
The only confirmed detail is a London legal address — a non-EU contracting entity — while hosting is unstated and we found no public information on subprocessors; the record carries no sovereignty attributes at all. For my EU clients this is the weakest possible starting position. 1
The Brand Governance Officer
The only corporate fact published is a London legal address, outside the EU. We found no public information on hosting location, the contracting entity's data-processing terms, or the subprocessors that would touch the archive and community conversations — from a sovereignty standpoint, nothing is evidenced. 1
The Analyst
The sole relevant fact is a legal address at 82 Great Eastern Street, London — a non-EU contracting entity — and the sovereignty attributes on record are otherwise empty. We found no public information on hosting location, named infrastructure, subprocessors, or a DPA addressing the personal data arriving from the networks. 1
The Data Protection Officer
The contracting address is 82 Great Eastern Street, London — a UK entity rather than an EU one — and we found no public information on hosting location, a subprocessor list, or a data processing agreement addressing the personal data arriving from the networks. My three standing questions — DPA scope over comments and messages, retention on the conversation archive, and where any sentiment analysis sends the text — all go unanswered publicly. 1
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
Pricing transparency
Show reasoningHide reasoning
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.
The Community Manager
The captured page invites visitors to book a demo or join a webinar; I found no public prices, tier boundaries, account or user limits, or billing terms. A team can't compute even a rough annual invoice from public pages alone. 1
The Agency Lead
We found no public prices of any kind — no per-user or per-account figures, no tier boundaries showing where approvals or the inbox begin — and the only route offered is booking a demo. I cannot compute even an approximate annual invoice for one client, let alone twelve. 1
The Brand Governance Officer
The captured page shows a demo booking prompt and we found no public information on tiers, per-user or per-account prices, user and account limits, or the level at which approvals and the inbox would begin. A team cannot compute an annual invoice from what is published here. 1
The Analyst
We found no public prices at all: no per-user or per-account figure, no billing period, and no public information on which tier approvals or the inbox sit in. The only pricing-adjacent signal is an invitation to book a demo, so a team cannot compute its real annual invoice from public pages. 1
The Data Protection Officer
We found no price figures of any kind on the captured page — only invitations to book a demo or join a webinar — and no statement of account or user limits, tier boundaries, or where the inbox and approvals would begin. A team cannot compute even a rough annual invoice from public information. 1
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
European sovereignty — proven facts
1 of 4 dimensions provenBuilt 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
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 →