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.

Setup we handle for you

A few settings live at the workspace level — they apply to every project at once — and are applied by Togenar rather than edited per project. Open a ticket with what you need; it is set on your workspace and takes effect on the next viewer load, with no redeploy and no change to anything you have already shipped.

• Workspace brand default — one logo and colour set that every project inherits, with the option to keep chosen fields fixed so no project drifts from the brand. See Branded QR.
• Embed domain allowlist — the domains your embed is allowed to run on; every other origin is refused. See Domain allowlist.
• Additional workspaces — a separate container per client or brand, each with its own team, catalogue and plan. See Workspaces.

Send the values themselves in the ticket — the logo file or link, the brand colours, the domain list — and there is nothing further to configure on your side.

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).