Support tickets

Support runs through tickets inside the panel — no external helpdesk account needed.

The flow

1. Create a support ticket describing the issue.
2. Track its state: waiting on support → answered → closed. You can reply to continue the thread, and close the ticket yourself once resolved.

What to include

The difference between a one-reply fix and a week of back-and-forth is usually the first message. Include:

• The project ID (and product, if configurator-related).
• Where it happens — panel, editor, published viewer, embed on your site, AR.
• The page URL where you see the problem, and for embed issues the URL of your page hosting it.
• A browser console screenshot for anything visual or loading-related.
• What you expected vs. what happened.

Before opening a ticket

The Troubleshooting page covers the most common integration issues — empty embeds, 403 domain errors, AR not opening — each with its cause and fix. Billing questions go through the workspace owner (see Plans & billing).