Social Media Marketing
HeyOrca
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by HeyOrca Inc. · www.heyorca.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
HeyOrca at a glance
- Vendor
- HeyOrca Inc.
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates HeyOrca 3/5, the mean of 6 judges. HeyOrca is a social media marketing platform from HeyOrca Inc. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
HeyOrca is a social media marketing platform from HeyOrca Inc. that schedules to seven networks — Facebook, Instagram, LinkedIn, Pinterest, Threads, TikTok and YouTube — with per-platform customization, bulk creation with individual edits, and best-time picks drawn from each account's own history. Publishing scores cluster at 7; analytics and reporting and collaboration governance both sit at 7–8, backed by custom cross-channel reports with stated retention windows, information icons explaining how each number is calculated, and multiple custom approval workflows with an audit trail recording who changed what, when, and previous versions. The engagement inbox scores 5–6: comments, mentions and DMs from four networks in one queue, but we found no public information on assignment, internal notes or SLA timers. Sovereignty scores 0–2 — no sovereignty attributes are on record — and pricing transparency scores 0–1, with Free, Basic and Pro tier names, unlimited users with no per-user fees, and a free trial without a card stated, but no price figures. No criterion showed a genuine split among the judges.
Speaks for it
- Publishes to seven networks with per-platform customization, bulk creation with individual edits afterward, and best-time picks drawn from the account's own posting history.
- Multiple custom approval workflows let clients approve, reject and leave feedback without ever logging in, backed by an audit trail of who changed what, when, and previous versions.
- Custom cross-channel reports state retention windows outright — Facebook and Instagram up to 2 years, LinkedIn up to 1 year — with information icons explaining how each number is calculated.
- A unified inbox with a separate inbox per client, resolve and hide states, bulk moderation, and AI reply suggestions that are editable before sending.
- The X discontinuation was handled in public with a dated conversion to placeholder accounts that kept approval flows and notification publishing alive, and other networks were unaffected.
Held against it
- We found no public information on hosting location, the contracting entity, subprocessors, or a data processing agreement — no sovereignty attributes are on record.
- We found no public information on assigning inbox conversations to owners, internal notes, SLA timers, saved replies, or a per-person history across networks.
- Workspace admins can override a post's status manually at any point in the workflow, and we found no public information on content locking after approval or granular permissions per account.
- The inbox connects to four networks — Facebook, Instagram, LinkedIn and TikTok — while the publishing list covers seven.
- We found no public information on export of the engagement archive; the calendar exports to XLS.
Best for
- You run an agency with many clients and need each client in its own workspace, with approval workflows where clients approve, reject and leave feedback without ever logging in.
- You hand performance reports to clients and need cross-channel custom reports with competitor benchmarking, white-label branding and scheduled PDF delivery.
- You schedule content in bulk across the major networks and want per-platform customization plus full error codes when a post fails.
Avoid if
- You still need to publish to X (formerly Twitter) — that integration was discontinued and profiles were converted to placeholder accounts that require manual publishing.
- Your approval process must be tamper-resistant — workspace admins can override any post's status manually at any point in the workflow.
- You need to manage engagement on networks beyond the four the inbox connects to — Facebook, Instagram, LinkedIn and TikTok.
The scores
| Criterion | Panel median |
|---|---|
| Publishing & calendar | 3.5 of 5 |
| Engagement & community inbox | 3 of 5 |
| Analytics & reporting | 3.5 of 5 |
| Approvals, roles & brand safety | 3.5 of 5 |
| Network coverage & API resilience | 3.5 of 5 |
| European sovereignty | 0.5 of 5 |
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
Bulk creation with per-post edits, bulk status changes and copy-or-move on the calendar, per-platform customization, and Best Times to Post drawn from the account's own history make the calendar a real working surface, and failed posts surface full error codes in the audit trail — exactly what I want at 3am. We found no public information on CSV import, evergreen queueing, UTM rules on the link shortener, network-accurate previews, or any retry and one-click recovery on failures. 1 2 3 9 11
The Agency Lead
Bulk creation, per-platform customization and a bulk actions menu for status changes across the calendar cover how my team actually works, and Best Times to Post draws on each account's own history. Failed posts surface with full error codes, but we found no public information on automatic retry, CSV import, evergreen queues or previews matched to each network's rendering. 1 2 3 9
The Brand Governance Officer
Publishing spans seven networks with per-platform customization, bulk creation and editing, best-time recommendations drawn from the account's own history, and failed posts diagnosable with full platform error codes. I found no public information on CSV import, evergreen or queue-based scheduling, render-accurate previews, or one-click recovery when a post fails — and no statement that a scheduled item is locked once it has been approved. 2 3 9 10
The Analyst
Bulk post creation with individual editing, per-network customisation, a link shortener and best-time suggestions drawn from the account's own history are all documented, and failed posts surface with full error codes. But we found no public information on CSV import, queue-based or evergreen scheduling, UTM rules on shortened links, previews matched to each network's rendering, or a one-click retry after failure. 1 2 3 9
The Data Protection Officer
Scheduling covers per-network customization, bulk creation with per-post edits, bulk status and copy-or-move actions on the calendar, and a Best Times feature built on the account's own performance history; failed posts can be diagnosed with full platform error codes. We found no public information on CSV import, evergreen or queue-based scheduling, previews matching each network's rendering, or a one-click retry after a failure. 1 2 3 9
The Skeptic
Per-platform customization, bulk creation with individual edits afterward, best-time picks drawn from the account's own posting history, and failed posts diagnosed with full error codes make the calendar a genuine working surface. We found no public information on CSV import, evergreen or queue-based scheduling, previews matched to each network's rendering, or a retry after failure, and the same for UTM rules on the link shortener. 1 2 3 9 11
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
Comments, mentions and DMs from Facebook, Instagram, LinkedIn and TikTok land in one queue per client, with resolve and unresolve, hide, bulk actions, filters and editable AI-drafted replies — the shape of the inbox I want. But we found no public information on assigning a conversation to an owner, internal notes, saved replies, SLA timers, sentiment or priority flags, escalation to a helpdesk, or a per-person history spanning networks, and those are the parts that make a queue survive a team. 1 4 5
The Agency Lead
A unified inbox across Facebook, Instagram, LinkedIn and TikTok handles comments, mentions and DMs with resolve status, hide-comment moderation and batch actions, and each client gets a separate inbox — exactly the separation twelve brands need. We found no public information on assigning conversations to owners, internal notes, SLA timers or per-person history across networks, so it is not yet a service desk. 4 5
The Brand Governance Officer
A unified inbox covers comments, mentions and direct messages across Facebook, Instagram, LinkedIn and TikTok with resolve states, hidden-comment handling, bulk moderation and a separate inbox per client. I found no public information on assignment or ownership of a conversation, internal notes, SLA timers or sentiment flags, so nothing shows who was responsible for a given reply. 1 4 5
The Analyst
The unified inbox covers comments, mentions and direct messages across four networks with resolve states, hide handling, batch moderation and AI-drafted replies with an editable brand voice. We found no public information on assignment to teammates, internal notes, saved replies, SLA timers, sentiment or priority flags, or a per-person conversation history spanning networks. 4 5
The Data Protection Officer
Comments, mentions and DMs sit in one inbox across Facebook, Instagram, LinkedIn and TikTok, with hide-and-resolve moderation, batch actions, per-client inboxes and AI-drafted replies the team edits before sending. We found no public information on assignment, internal notes, SLA timers, automatic moderation rules or a per-person conversation history — and nothing on where the AI reply generator sends the comment text it processes, which is my standing question for any inbox vendor. 4 5
The Skeptic
Comments, mentions and DMs land in one queue across Facebook, Instagram, LinkedIn and TikTok, with resolve and hide states, bulk actions, filtering, and AI reply suggestions editable before sending. We found no public information on assigning conversations to owners, internal notes, per-person history across networks, SLA timers, saved replies, or escalation to a helpdesk — and while publishing lists seven networks, the inbox connects to four. 2 4 5
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
Custom cross-channel reports with per-network graphs, competitor benchmarking on Facebook and Instagram, scheduled PDF delivery to clients, shareable links, AI summaries, and information icons explaining how each number is calculated — documented differences rather than hidden ones, which I respect. Retention is stated honestly per network (up to two years on Facebook and Instagram, one on LinkedIn), but we found no public information on UTM-based attribution into web analytics or audience demographics tracked over time beyond Instagram. 6 7
The Agency Lead
Custom cross-channel reports, competitor benchmarking, scheduled PDF delivery and shareable no-login report links cover the client hand-off, with data windows up to two years for Facebook, Instagram and TikTok post insights documented per network. Facebook views split organic and paid and Instagram demographics break down by age, location and gender, though we found no public information on UTM-based attribution into web analytics. 1 6 7
The Brand Governance Officer
Custom cross-channel reports with selectable per-network metrics, white-label branding, scheduled PDF delivery, competitor benchmarking, documented retention windows and calculation explanations are what an agency can hand over unedited. I found no public information on UTM-based attribution into web analytics, and audience demographics are evidenced for Instagram only, which caps this below the top band. 1 6 7
The Analyst
Cross-network custom reports, competitor benchmarking, scheduled PDF delivery, Instagram demographics and information icons that document how each number is calculated put this in the strong tier, and retention is stated as up to two years per network. Retention is bounded rather than independent of platform windows though, and we found no public information on UTM-based attribution into web analytics or white-labelled report handover. 6 7
The Data Protection Officer
Post insights are retained up to two years for Facebook, Instagram and TikTok and one year for LinkedIn, with cross-channel custom reports, competitor benchmarking, scheduled PDF delivery, shareable links and information icons explaining how each number is calculated. We found no public information on UTM-based attribution into web analytics, and the reporting retention tables are the only archive statement we could find anywhere. 6 7
The Skeptic
Per-network metrics are documented down to named graphs with retention windows stated outright — Facebook and Instagram up to two years, LinkedIn one — alongside custom and cross-channel reports, competitor benchmarking, scheduled PDF delivery, shareable links, Instagram demographics, and paid-versus-organic splits on Facebook and Instagram. The information icons explaining how each number is calculated are the honesty I reward; retention, though, is capped at those windows rather than independent of the platforms', and we found no public information on UTM-based attribution into web analytics. 6 7
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
Multiple custom approval workflows with staged rules, reminders at 24 hours, 3 days or 7 days, sign-off tracking on the post status, an audit trail of who changed what and when with previous versions, and clients approving and leaving feedback without ever logging in — that is genuinely strong governance for an agency setup. We found no public information on roles or granular permissions per account and action, or on content locking after approval; the admin manual override is documented but not the enforcement behind it. 1 2 8 9
The Agency Lead
Each client sits in its own workspace with in-progress posts hidden, clients approve, reject and leave feedback without ever logging in, and custom workflows chain internal and external stages where either any one or all named approvers must sign off, backed by an audit trail of who changed what and when. We found no public information on content locking after approval or granular permissions per account and action, and workspace admins can override a post's status manually at any point. 1 2 8 9
The Brand Governance Officer
Multiple custom approval workflows with per-stage sign-off rules, approval notifications and reminders, a stage status showing who has signed off, and an audit trail recording who changed what, when, and the previous versions — this is genuinely close to auditable. But the design explicitly allows workspace admins to override a post's status at any point in the workflow, and I found no public information on content locking after approval or granular permissions per account and action; enforced sign-off before anything reaches a network is not shown. 1 2 8 9
The Analyst
Multiple configurable approval workflows with stage-level rules, approver notifications and reminder intervals, clients giving feedback without logging in, per-client workspaces, and an audit trail capturing who changed what and when with previous versions — this is a well-evidenced governance story. We found no public information on granular permissions per account and action, a legal-review stage, or locking content after approval. 1 8 9
The Data Protection Officer
Multiple custom approval workflows with configurable stage rules, reminders at fixed intervals, and external client sign-off without a client login, plus an audit trail recording who changed what, when, and prior versions — a defensible record of who approved a publication. We found no public information on granular permissions per account or content locking after approval, and workspace admins retain a manual override of any post's status. 2 8 9
The Skeptic
Multiple custom approval workflows with internal and external stages, a choice of approval rules, reminder intervals, and an audit trail recording who changed what, when, and previous versions — plus clients approving without ever logging in and drafts hidden from them until ready — make a serious governance story. It stops short of audit grade: we found no public information on granular roles or permissions per account and action, or on content locking after approval, and workspace admins can override a post's status manually at any point in the workflow. 1 2 8 9
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
Seven networks scheduled including Threads, the X discontinuation communicated with a date, placeholder accounts that keep approval flows and notification publishing alive, and confirmation that other networks were unaffected — that is a platform change handled in public, with System Status and Release Notes listed as resources and TikTok specs documented in unusual depth. The calendar exports to XLS, but we found no public information on exporting the engagement archive or on official partner status with any network. 2 10 11
The Agency Lead
Seven networks including Threads publish through auto-publish where the API allows, TikTok's spec limits are documented in detail, and when X was discontinued existing profiles converted to placeholder accounts that preserved approval flows and notification publishing — a graceful way to keep a client's process alive. Release notes and a system status resource are public and calendar content exports to XLS, though we found no public information on export of the engagement archive. 2 10 11
The Brand Governance Officer
Seven networks including Threads, TikTok publishing governed by that platform's own API requirements, and a dated public notice converting departing X profiles into placeholders that still support approval flows and notification publishing, with other networks unaffected. Release Notes and a System Status page exist in the help centre. I found no public information on official partner status, on per-network capability documentation beyond TikTok, or on export of the engagement archive rather than calendar content alone. 2 10 11
The Analyst
Seven networks including the newer ones are supported, TikTok constraints are documented in unusual detail, and the X discontinuation was handled with a dated conversion to placeholder accounts alongside calendar export and a system status page. We found no public information on official API partner status, an integration-specific status page, advance notice commitments, or export of the engagement archive. 2 10 11
The Data Protection Officer
Seven networks including Threads are supported, per-network API limits such as TikTok's logged-in connection and notification publishing for carousels are documented, and the X discontinuation converted profiles to placeholder accounts that kept approval flows and manual publishing working. We found no public information on advance notice of deprecations, official partner status, or export of the engagement archive — the calendar exports to XLS, but we found nothing on exporting the conversations themselves. 2 10 11
The Skeptic
I count seven networks on the publishing list — Facebook, Instagram, LinkedIn, Pinterest, Threads, TikTok, YouTube — but the inbox and the documented report metrics cover four, and we found no public information on which connections run on official APIs; TikTok is the only network with a capability page of its own, specifying file formats, frame rates and the carousel workaround through notification publishing. The one platform break on record, the X discontinuation, was handled with a dated conversion to placeholder accounts that kept approval flows and manual publishing alive, with calendar content exportable to XLS — but we found no public information on export of the engagement archive, official partner status on any network, or capability pages for Pinterest, Threads and YouTube. 2 4 7 10 11
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
We found no public information on where the archive and the community conversations are processed, which entity contracts, or which subprocessors touch them — hosting, contracting entity and subprocessors are all unstated on the captured pages, and no sovereignty attributes are on record. For a tool holding my communities' comments and DMs, that silence is the whole answer for now. 1
The Agency Lead
We found no public information on where the archive and community conversations are hosted, on the contracting entity, on subprocessors, or on any certification or data processing agreement — nothing in the captured pages addresses the handling of network message content, even with AI reply features in the product. 1 4
The Brand Governance Officer
We found no public information on where the archive and the community conversations are hosted, on the contracting entity's jurisdiction, on any subprocessor list, or on a data processing agreement addressing the personal data arriving from the networks in comments and messages. For a tool that holds a brand's comment and direct-message history, that silence decides the score. 1 4
The Analyst
We found no public information on where the archive and community conversations are hosted, the contracting entity's jurisdiction, any subprocessor list, or a data processing agreement covering personal data arriving from the networks. Nothing on record lets me say more than that the captured pages are silent on the whole chain. 1
The Data Protection Officer
No sovereignty attributes are on record: we found no public information on hosting location, the contracting entity's jurisdiction, subprocessors, a data processing agreement, or retention of the conversation archive. The AI reply generator and AI report summaries process comment and report text with no stated destination, safeguard or legal basis — for a tool ingesting comments and DMs from the networks, that absence is decisive. 4 7
The Skeptic
We found no public information on where the archive and the community conversations are hosted, who the contracting entity is, or which subprocessors — the AI reply generation that reads your community's comments included — touch any of it. The vendor name carries an Inc. suffix and no European attributes appear on record in the captured pages. 1 4
Pricing transparency
not rated — the vendor publishes no price
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
No price figures appear anywhere: a free trial without a card, tier names like Free, Basic and Pro, unlimited users with no per-user fees — but not one number I could use to compute an annual invoice, nor account limits or the tier where approvals and the inbox begin. Every real cost question stays a sales conversation. 2 5 6
The Agency Lead
The captured pages name Free, Basic and Pro plans and state unlimited users with no per-user fees, but we found no public information on any price, billing period, included account counts, or the tier where approvals and the inbox begin. The real annual invoice for a small client cannot be computed from what is public. 2 5 6
The Brand Governance Officer
The captured pages name free, basic and pro tiers with unlimited users and a free trial without a card, but we found no public information on the price of any paid tier, the billing period, the social accounts included, or the tier at which approvals and the inbox begin. No annual invoice can be computed from these pages. 2 5 6
The Analyst
We found no public prices on any captured page — no per-user or per-account figures, billing periods, tier boundaries, or the cost of an extra account. Only a card-free trial, a free plan with limited metrics, and advertising of unlimited users are stated, so a team cannot compute an annual invoice from public information. 2 5 6
The Data Protection Officer
We found no public prices at all; the only pricing-adjacent facts are a free trial without a card, a free plan with limited metrics, and unlimited users with no per-user fees. A team cannot compute an annual invoice from these pages, nor locate the tier where approvals and the inbox begin. 2 5 6
The Skeptic
Tier names surface only in passing — a Free plan with limited metrics, Basic and Pro — and the vendor publishes that users are unlimited with no per-user fees, but no price figure, billing period, account limit or add-on cost appears anywhere in the captured pages. A team cannot compute even a rough annual invoice from public information. 2 5 6
Questions about HeyOrca
Is HeyOrca European?
Not determined: the vendor’s pages as captured do not say where HeyOrca is based.
Where does HeyOrca store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does HeyOrca have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to HeyOrca?
As of 21 Oct 2026, the panel rates Swat.io (3.5/5), Hootsuite (3/5) and Agorapulse (3/5) highest among the other 28 Social Media Marketing products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Swat.io (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: HeyOrca alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- 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.
- 22 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
- 4 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
- 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 data 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
- 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 (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.heyorca.com Checked 13 Oct 2026 Details →
- 2 Publishing & calendar — found from sitemap www.heyorca.com Checked 13 Oct 2026 Details →
- 3 Publishing & calendar — found from sitemap help.heyorca.com Checked 13 Oct 2026 Details →
- 4 Engagement & community inbox — found from sitemap help.heyorca.com Checked 13 Oct 2026 Details →
- 5 Engagement & community inbox — found from sitemap www.heyorca.com Checked 13 Oct 2026 Details →
- 6 Analytics & reporting — found from sitemap www.heyorca.com Checked 13 Oct 2026 Details →
- 7 Analytics & reporting — found from sitemap help.heyorca.com Checked 13 Oct 2026 Details →
- 8 Approvals, roles & brand safety — found from sitemap help.heyorca.com Checked 13 Oct 2026 Details →
- 9 Approvals, roles & brand safety — found from sitemap help.heyorca.com Checked 13 Oct 2026 Details →
- 10 Network coverage & API resilience — found from sitemap help.heyorca.com Checked 13 Oct 2026 Details →
- 11 Network coverage & API resilience — found from sitemap help.heyorca.com Checked 13 Oct 2026 Details →