Contact support and share feedback
Ask for help from the AI chat in Pineapple, then review a support request before sending it to our team. After sending, choose View conversation to read replies and add details. Your Support conversations page is the saved inbox for these requests.
Start a request
Describe what you were trying to do and what happened. For example: “Publish keeps spinning in Chrome after I reload. Can the support team help?” The AI can gather details and offer a human support handoff.
To start manually, type /support and select Support from the skills menu. For an idea or suggestion, type /feedback and select Feedback. The dashboard Feedback button also opens the feedback flow.
You can also open your support conversations and choose New support request or Share feedback. Sign in with the account you used for the request.
In the editor, open AI Assistant, type /support, select Support, then describe your issue. Use /feedback for a suggestion.
Review and send
Choose Contact support on the AI handoff card, or Review feedback for a suggestion.
Check the request type and summary. Correct anything that is missing or inaccurate.
Read the sharing notice. An AI handoff can include account details and relevant chat context; the review form explains what will be shared.
Choose Send support request or Send feedback.
Look for the received confirmation, then choose View conversation.
A prepared summary has not been sent. The receipt confirms your request was saved; it does not mean someone has read or resolved it yet.
Example of a direct request. Check the summary and sharing notice, then choose Send support request. This example has not been sent.
Give us useful details
Include the affected website or page, what you expected, what you saw, the exact error text, and what you already tried. Your browser and whether the problem affects the editor or published website can help us investigate. Add screenshots or files when they help explain the issue.
Do not include passwords, API keys, payment-card details or information you do not want shared with support.
Read replies and follow up
Open View conversation or open your support conversations. When the team replies, you can read the message and add a follow-up in that same conversation. Use Attach files for additional evidence and Send reply to submit it.
An email notification links back to your conversation when support replies. Use that link to continue; the notification email inbox is not monitored. If the email is missing, check your spam folder and open your conversation directly.
Your conversation can show Waiting for support, Support has replied, or Resolved. Use Mark resolved when you are finished, or Reopen request if you still need help. Human replies are asynchronous; submitting a request does not promise an immediate response.
A real product screenshot using labelled test messages, not a customer case. Read the team’s reply, attach a file if useful, and continue with Send reply.
Recover an interrupted request
Saved conversations remain available when you leave the app. Unsent drafts can recover after a refresh on the same browser and account; they are not a cross-device backup and expire after seven days. Review the recovered draft before sending.
If a send fails or its result is uncertain, use the recovery or retry option shown. Check for a receipt or saved message before starting a duplicate request. Refreshing a draft does not send it automatically.
Which chat is this?
This flow contacts the Pineapple support team about using Pineapple. The website chat feature lets visitors contact your own business and has its own dashboard inbox.
