support privacy
Rate a Help guide
Learn how to rate a Help guide with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Every visitor can choose Helpful or Not helpful and an enumerated reason. Only identified merchants may add bounded free text or continue to chat; anonymous ratings are stored as daily aggregates.
Before you begin
- Open Help from the correct identified shop for merchant support
- Do not paste customer personal data or credentials
- Note the guide and heading where the issue occurred
Confirm the shop, current status, and intended consequence before changing anything. Use read-only status, preview, or history evidence first.
Step-by-step setup
Confirm the guide describes rating behavior for anonymous and identified visitors.
Browse the complete Help taxonomy from the persistent category navigation.
Use the setup steps to submit a rating without including private merchant data.
Navigate between feedback guidance and its examples with the page outline.
- Open the end of a Help guide for the intended shop and confirm the current record and status.
- Choose Helpful or Not helpful and an enumerated reason; identified merchants may add bounded free text or start chat, while anonymous feedback remains aggregate-only.
- Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
- Submit once, verify confirmation, and exclude credentials, customer data, catalog exports, or form values.
- Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.
Every visitor can choose Helpful or Not helpful and an enumerated reason. Only identified merchants may add bounded free text or continue to chat; anonymous ratings are stored as daily aggregates.
Juniper & Trail example
A Juniper & Trail admin follows Rate a Help guide from the correct shop. Support can see bounded Help context but never draft form values, catalog details, credentials, or customer data. The documentation fixture uses realistic products, inventory states, variants, collections, and protected exclusions so the preview exercises the same decisions as a merchant catalog.
What shoppers will see
Help activity never changes the storefront. It gives support bounded product context without collecting form contents or catalog data. Check the relevant result from product through cart where applicable. For shopper-facing work, compare desktop and mobile and verify both an eligible and an ineligible item.
Common mistakes and troubleshooting
- Acting on the wrong shop. Confirm the Shopify store and campaign before following Rate a Help guide.
- Trusting a stale preview. Refresh after catalog, schedule, discount, theme, locale, or market changes.
- Repeating a background command. Read status and History first; retry only when Badgy presents a recoverable failure.
- Skipping the consequence check. Confirm what changes for shoppers and what the end or restore path will do.
If the status reports revoked authorization, reconnect Shopify before retrying. If the result still differs from the preview, preserve the campaign ID and approximate time, then open support from this identified shop. Never send customer data, access tokens, or full catalog exports in feedback.
Related guides
Options reference
| Option | Use it when | Consequence | | --- | --- | --- | | Helpful | Guide solved task | Structured reason allowed | | Not helpful | Guide gap/problem | Structured reason required by UI contract | | Identified detail | Bounded merchant context | Free text/chat available | | Anonymous | Public rating | Daily aggregate only |
Badgy behavior in this guide is reviewed against the repository's shipped UI, service rules, and feature design documents. Shopify-owned theme, Markets, Flow, billing, and discount behavior can also depend on the store's Shopify configuration; consult the Shopify Help Center for that platform configuration.