Support

Before you get in touch

Most issues resolve in a couple of minutes with Troubleshooting, which is organised by symptom rather than by feature.

How to reach us

Use the Support button in the corner of any page here, or the same button inside the Sledge dashboard — both reach the same team and search the same help articles.

For questions about plans, pricing or whether Sledge fits your store, see the Sledge site.

Reporting a problem

Include these and we can usually answer on the first reply:

• Your store URL and the exact page where the problem appears.
• What you expected and what happened instead.
• The theme you are using, and whether the problem appears on other themes.
• Whether custom code is involved — if you have Custom CSS or JavaScript configured, try disabling it briefly to narrow things down.
• A screenshot, if it is visual.

If a widget is not appearing, tell us whether it is configured and enabled for that surface — that is the single most common cause and knowing you have checked it saves a round trip.

Reporting a gap

If the only way to achieve something was to reach into a widget's shadow root and match internal class names, that is a gap in the supported API, not just a workaround. Tell us what you were trying to do. Those reports are how the supported surface grows.

Same for missing events: if you had to use a MutationObserver because nothing was dispatched at the moment you needed, we would like to know.