Support

Reach support with enough context to solve the real problem

Support works best when it starts from the workflow you used. PreviewShip supports browser upload, CLI, MCP, Cursor, and VS Code deploy paths, so a useful support request should name the workflow, the exact step that failed, and the preview URL or artifact context if available.

Email support

For product issues, workflow questions, or feedback, email support directly.

[email protected]

Fastest self-serve path

Most setup questions are answered faster by the focused docs pages.

CLI MCP Cursor VS Code

Before you email

Name the workflow

Say whether the issue happened in browser upload, CLI, MCP, VS Code, or Cursor.

Include the failing step

State exactly where the problem appeared: authentication, upload, deploy, or preview access.

Include identifiers

If a preview URL exists, include it. If not, include the command, editor action, or environment that failed.

FAQ

What should I include in a support request?

Include the preview URL if one exists, the workflow you used (CLI, MCP, editor, or browser upload), and the exact point where the issue appeared.

Can support help with CLI, MCP, and editor setup?

Yes. Those are core product workflows and should be part of the support surface.

Should I read the docs before emailing?

For setup questions, yes. The focused docs pages often answer installation and configuration issues faster than an email round trip.

New here?

If you are still evaluating the product, start with the guides hub. It explains where PreviewShip fits before you commit to a workflow.

Browse guides