# Social Comment Sync Coverage Map

Explain possible missing-comment coverage from channel, account type and where a post was created.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Post/channel IDs, personal or business account type, organic/paid category, original publishing tool and dated capability documentation.

## Workflow
1. Keep channel, account type and post origin separate.
2. Compare each combination to the dated documented coverage table; do not infer account access.
3. Mark known unsupported combinations separately from a supported but unverified sync.
4. Return a source-backed coverage note without claiming zero comments or reconnecting accounts.

## Output contract
post_id | channel | account_type | origin | content_category | documented_coverage | sync_unverified

## Fictional acceptance test
Fictional LinkedIn personal post was published outside Planable. Its missing comments cannot prove nobody replied. TikTok personal account also differs from documented business-account coverage. An eligible post still needs actual sync evidence.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://help.planable.io/hc/en-us/articles/29213177431836-Managing-your-Social-Inbox

Checked October 9, 2026. Oct 9 live AIS Search Console through Oct 6: marketing Copilot 37 impressions, Planable/Claude 33, Planable/ChatGPT 23, campaign brief 12, investor agent 19. Social-review/reporting topics follow these parent-query leads. Other professions follow documented workflow needs, not measured exact search intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.