Choose a support category and write a specific subject. Include the affected workflow, approximate time and the action that failed. Useful context might be a publishing record reference or the platform involved. Never put social passwords or API secrets in a ticket.
Follow the conversation
Review Open, Resolved and Unread summaries, search tickets and filter by status. Open the ticket to read replies and add missing details in the same conversation. Keep related observations together so support can understand the sequence of events.
Confirm the outcome
Retry the affected action after following the response and report the observed result. Ticket history helps distinguish a resolved connection problem from a new publishing issue. Support availability and service terms follow the current offering; this page does not promise a response time.
Your completion checklist
Category and subject identify the issue
Affected action and time are included
No passwords or secrets are attached
Follow-up stays in the original ticket
Questions before you start
Can I read previous replies?
Yes. Open the ticket to review its conversation history and add a follow-up.
What should I include for a failed post?
Include the relevant post reference, platform, approximate time and visible error. Exclude credentials and private access tokens.
Choose capacity around your work
Review connected accounts, team seats, monthly publishing volume, storage and included credits. Feature availability follows your plan and workspace permissions.
Network capabilities depend on account type, permissions and platform APIs. AI and paid API usage consume credits. Renewal, taxes and payment terms are shown at checkout.