Get a human answer with useful context.

Email support is available for account, product, billing, privacy, and security questions. Using the right address helps route your request without forwarding sensitive context.

For payment-method, invoice, charge, or refund help, use billing management in Verisual or email billing@verisual.com.

These are service targets, not guaranteed service levels. Support is monitored on business days, with urgent security and broad availability incidents prioritized.

For a faster diagnosis, include:

• workspace and project name;
• run ID, pull-request number, and approximate UTC time;
• expected behavior and what actually happened;
• the exact error text with credentials removed;
• steps that reproduce the issue, if known.

Never email API keys, GitHub private keys, OAuth tokens, browser storage state, passwords, payment-card details, or unredacted environment variables. Verisual support will not ask for them.

Workspace owners and billing members can open billing management from Verisual. The secure billing portal provides invoice access, payment-method updates, cancellation, and available plan changes.

If you cannot access the workspace, email billing@verisual.com from the checkout email address. Include the transaction or subscription ID if available, but do not send payment-card details.

See the Refund Policy before requesting a refund.

Workspace owners may request an export or closure. Privacy-rights requests should be sent to privacy@verisual.com. We may verify your GitHub identity, email, and authority over the workspace before acting.

Deleting an account may not immediately remove records that must be retained for billing, fraud prevention, legal obligations, dispute resolution, or time-limited backups. See the Privacy Policy for details.

Send suspected vulnerabilities privately to security@verisual.com. Include affected URLs or components, impact, reproduction steps, and any request IDs. Use a minimal proof and avoid accessing customer data or degrading the Service.

Do not publish an unpatched vulnerability or include live credentials in the report. We will acknowledge actionable reports and coordinate remediation and disclosure where appropriate.

• Confirm the run is pinned to the expected commit and baseline.
• Check that GitHub Actions OIDC claims match the repository, workflow, ref, and SHA.
• Confirm project and member limits have not been reached and that monthly comparison or hosted-runner minute usage remains available.
• For hosted URL runs, confirm the target is default-port HTTPS, matches an exact or explicit wildcard host, and any login navigation uses a configured exact authentication origin.
• Confirm every enabled hosted journey has an activated version whose exact digest completed validation, and all referenced secret names still exist.
• For PR previews, confirm the GitHub App is reauthorized, the signal comes from the project's locked provider/context, exactly one open pull request still has that head SHA, selected journeys are active, and the default target has an approved hosted baseline.
• A preview that returns 401 or 403 is skipped without consuming minutes. V1 supports public preview URLs and does not accept a provider protection-bypass secret; reset the provider source from project settings if the wrong integration was locked.
• If a Playwright ZIP is missing a baseline, run its documented local snapshot-update command and review the generated image. Supply your own storage-state file for an authenticated journey; never send that file to support.
• For billing, confirm the subscription email matches the verified workspace email.
• Retry only after preserving the original run ID and error details.