For the complete documentation index, see llms.txt. This page is also available as Markdown.

Tips for contacting support

Use this page when you are not sure how to reach Brickspace or what to include so the team can answer quickly.

Where to open a request

Brickspace documents each product in this help center (Paper, Space, Keystone, Slab, Pallet). Searching the hub for your theme name plus a feature (for example “Keystone variant images”) often surfaces a guide immediately.

What to put in your first message

Incomplete tickets slow everything down. Include:

  • Store URL (myshopify.com domain is fine).

  • Theme name and version if you know it (Online Store > Themes > > Edit theme code header, release notes, or the email receipt).

  • Whether the theme was customized (you or a developer edited Edit code, or apps inject scripts). If yes, say what changed at a high level.

  • Steps to reproduce the issue, starting from your homepage.

  • Screenshots or a short video, especially for layout bugs on mobile.

If you use a chat widget or AI assistant

Automated flows sometimes ask you to “create a ticket” without opening a text box clearly. Scroll the widget, look for Message or Reply, and paste the bullet list above. Sending a blank submission does not create a useful record, and the team cannot follow up.

Grant access when support asks

If support needs to view your theme settings, use the store access process described in Store access request. Do not post passwords in email.

What to expect

Response times and scope are summarized in Contact support, including what Brickspace covers versus what requires a developer or Shopify.

  • Test responsive layouts without publishing the theme.

  • Recover from third-party theme code changes.

  • Support policy for modified theme code.

  • How third-party apps affect theme styles.

Last updated

Was this helpful?