Support and community
Choose the right Runner help channel and include the information needed to resolve a problem.
Use documentation for known workflows, community for shared learning, and support for account-specific or reproducible product problems.
What this covers
You will know where each help action opens, how to book a demo or send feedback, and what to include when you need support.
Availability and prerequisites
- You must be signed in to use the workspace or project avatar menus.
- Send Feedback appears only in desktop workspace or project views that expose the feedback action.
- Book a Demo uses an external scheduling service inside Runner and needs a working network connection.
- The mobile avatar sheet has a smaller action set than the desktop avatar menu.
Entry paths
| Entry | What happens after you select it |
|---|---|
| Workspace sidebar → Help center | Opens Runner documentation. |
| Workspace sidebar → Community | Opens the Runner community in its current destination. |
| Workspace sidebar → Blog | Opens educational and company articles. |
| Workspace sidebar → Changelog | Opens recent Runner product updates. |
| Desktop avatar menu → Book a Demo | Opens the scheduling panel inside Runner. |
| Desktop avatar menu → Send Feedback | Opens the feedback form when that action is available in the current view. |
| Desktop avatar menu → Help | Opens Runner documentation. |
| Project avatar menu → Community, Blog, or Changelog | Opens the selected resource; Changelog stays inside Runner, while Community and Blog open their current destinations. |
| Documentation → Support | Opens the configured support email action. |
Book a demo
- On desktop, open the avatar menu and select Book a Demo.
- Wait for the scheduler to load.
- Choose an available date and time, then complete the contact details requested by the scheduler.
- Confirm the booking in the scheduler.
- Wait for Runner's success message and for the panel to close.
Closing the panel before the scheduler confirms the meeting does not create a booking. If the scheduler stays blank or reports that it is unavailable, close it, check the connection, and try once more. Use the documentation Support action if it repeatedly fails.
Send feedback
| Control | What happens after you use it |
|---|---|
| Describe your feedback | Records the required explanation. Submit stays unavailable until this field contains text. |
| Usability Issues / Missing Features | Adds an optional category so the report is easier to route. |
| Screenshot upload | Attaches an optional image to the report. Use the remove control to discard the attachment before sending. |
| Submit | Sends the report. While it is sending, the action cannot be submitted again. |
| Close | Closes the form without sending a new report. |
Describe one behavior, the page where it happened, and what you expected. Add a screenshot only after removing customer information, emails, payment details, credentials, and other private data. After a successful submission, Runner shows a confirmation and closes the form. If submission fails, keep the description, check the attachment and connection, and retry once.
Mobile avatar menu
On mobile, the project avatar opens Profile & Settings. It includes Language, Inbox, Help, Community, Blog, Changelog, and Logout. Book a Demo and Send Feedback are not listed in this mobile sheet. Use a wider desktop view for those two actions, or use the documentation Support action for a private problem.
Send a useful support report
Include:
- The workspace and store name, without secrets.
- The page and exact entry path.
- What you selected and what happened.
- What you expected instead.
- The visible status or error text.
- Whether the issue repeats after one reload.
- A screenshot with customer data, emails, payment details, and secrets removed.
For a Runner task, include the conversation and task state. For publishing, include preview status, publication state, and whether the live URL changed. For an app, include the provider and displayed connection state, but never credentials or API keys.
Choose the channel
| Need | Best starting point |
|---|---|
| Learn a normal product workflow | Search these guides. |
| Compare approaches with other users | Community. |
| Follow a released product change | Changelog. |
| Resolve access, billing, data, repeated errors, or private project behavior | Support. |
Troubleshooting
| State | Meaning and next step |
|---|---|
| Demo scheduler is loading | Wait for its date and time controls before interacting. |
| Demo confirmed | Runner shows a success message and closes the panel. Check the confirmation details sent by the scheduler. |
| Feedback Submit is unavailable | Add the required description, or wait for the current submission to finish. |
| Feedback upload fails | Remove the attachment and retry with a supported, privacy-safe image, or send the text without it. |
| Feedback submission fails | The report was not confirmed. Keep the text and retry once before using Support. |