SUPPORT & GETTING STARTED

A useful next step,
wherever you are.

Prepare for your first demo, understand a product workflow or send the team a clear description of an issue.

TROUBLESHOOTING

Help us understand
what happened.

A concise report is more useful than a large upload of project data.

What should I include in a support request?

Include the product name, app version, Windows version, the step you were performing, the error text and whether the issue repeats. A screenshot of the relevant interface can help after removing private information.

A connected service is not available. What should I check?

Check your connection, service account access and any usage limits. Reopen the connection using the product’s normal account controls. Do not share your password, API key or browser cookies with support.

How should I handle an interrupted project?

Keep the project and source files in place. Check the application’s saved progress or recovery state before starting a replacement project. Tell support where the workflow stopped.

The AI output is not ready to use. What next?

Review the input and context, correct the specific issue, then repeat the relevant part of the workflow if needed. Check the edited output before distribution.

Can I send a confidential project?

Do not include confidential project files in an initial request. Describe the issue using a small, non-sensitive example first. Agree a suitable support process with the team if more information is needed.

STILL NEED HELP?

Talk to the team.

Choose “Support / existing access” in the contact form.

Contact support
Product screenshot