Contact support effectively

Overview

A good support ticket includes enough context for the team to reproduce the issue or understand the account state without asking several follow-up questions.

Include this context

Key points

• The email address on your BaseStack account.
• The site title, slug, or custom domain involved.
• What you expected to happen and what actually happened.
• The last action you took before the issue appeared.
• A screenshot if the issue is visual, but do not include secrets or private credentials.

For security or abuse reports

Key points

• Choose the Security category when opening the ticket.
• Include the public URL, account email if known, and a short description of the concern.
• Do not test destructive behavior against another user account or public page.
• Do not send passwords, API keys, recovery codes, or service-role credentials.

Keep secrets out of tickets

BaseStack support will never need your Supabase service role key, Stripe secret key, domain registrar password, or one-time login code.