Comment tracking direction
Part of the Hey Tasky direction for agent-assisted social scheduling, native account publishing, and reviewable workflows.
Feature cluster
Social media comments API
Comments are useful, but they come after Hey Tasky has the posting engine nailed down. First ship the train, then add cupholders.
Roadmap. Native account strategy. Agent-first scheduling.
Best for
Who this page is for.
Community managers
Creators managing replies
Support-adjacent social teams
Capabilities
What Hey Tasky is built to handle.
Post-level context
Part of the Hey Tasky direction for agent-assisted social scheduling, native account publishing, and reviewable workflows.
Agent triage potential
Part of the Hey Tasky direction for agent-assisted social scheduling, native account publishing, and reviewable workflows.
Future inbox surface
Part of the Hey Tasky direction for agent-assisted social scheduling, native account publishing, and reviewable workflows.
Network-specific limits
Part of the Hey Tasky direction for agent-assisted social scheduling, native account publishing, and reviewable workflows.
Honest limits
What we are not claiming.
These pages are SEO assets, not a license to hallucinate features. Groundbreaking concept, apparently.
Not live today
Permissions vary by network
Direct messages and auto-replies are gated backlog
FAQ
Questions people ask before choosing a scheduler.
Will Hey Tasky auto-reply to comments?
Not in the urgent plan. Auto-reply belongs in the gated backlog until the publisher is stable.
Why build comments later?
Because publishing and status tracking have to be reliable first.
Related pages