Support

The Support page (/support) is where your team sends product feedback from inside the console. Use it for bugs and improvement ideas—not for how-to questions covered in Documentation.

Owner, Editor, and Viewer roles can all open Support and submit tickets.

The Support route has two areas:

• Support center hero — short intro and a “Before you send” aside with quick tips
• Ticket form — type selector, summary, rich-text description, optional screenshots, and submit

The hero aside reminds you what helps the team act faster:

• Bug — steps to reproduce
• Idea — problem and desired outcome
• Screenshots or logs — when they add context

You do not need to paste project IDs or your user email—the console attaches that automatically when the ticket is created (see below).

1. Under What do you need?, choose Report a bug or Suggest an improvement.
2. Enter a Short summary (required)—one line is fine; use the description field for detail.
3. Write the Full description in the rich-text editor (required). Formatting is supported.
4. Optionally add up to 5 screenshots (PNG, JPG, GIF, or WebP)—especially useful for UI issues or error states.
5. Select Send to support.

A confirmation note at the bottom explains that you will see on-page confirmation when the ticket is created.

On success, the form is replaced by a confirmation screen with the ticket number. The product team uses it to track your report.

Select Submit another report to reset the form and send additional feedback without leaving the page.

Bug reports

In the full description, include:

• Steps to reproduce (numbered, in order)
• Expected behavior vs what actually happened
• Where in the console it occurred (e.g. Audience → Segments, Messaging → Broadcast)
• Browser and OS if the issue is UI-related
• Approximate time the issue last occurred, if intermittent

Feature requests

In the full description, include:

• The problem you are trying to solve
• Who benefits (your team, end users, both)
• The outcome you want—not only the UI you imagine
• Any workaround you use today

Each ticket includes context from your session so you can focus on the issue itself:

• User — account ID and email
• Project — project ID, name, and plan
• Screenshots you upload in the form

• Documentation — setup guides, console features, and API Reference
• Blog — product updates and announcements (sidebar link)
• Getting Started — in-console checklist for new projects
• Settings → Payment & Billing — subscription and invoices (Owner only)
• Settings → Members — invite teammates or change roles

Support is not live chat and does not replace reading the docs for configuration questions.

• Owner / Editor / Viewer — can open Support and submit tickets with the same form