User Guide
  • Intro
    • Welcome
      • About DotApparel
      • What is DotApparel?
      • Where is it hosted?
      • What platform(s) do we support?
      • How does syncing work?
      • Solution architecture
      • Definition of “Instance”
      • Security Overview
    • Implementation
      • Google Cloud and Firebase
  • Quick Links
  • Core
    • Overview
    • Dashboard
    • Orders
      • Mappings
      • Integrations
    • Returns
      • Mappings
    • Products
      • Mappings
        • Default mapping rules
      • Translations
      • Markets
      • Publishing products
    • Inventory
      • Mappings
        • Examples
          • Ignore Sync
          • Inventory Buffer
          • Keep Items Sold Out
          • Unlimited Inventory
    • Customers
    • Rewards
    • System Alerts
    • Settings
      • Shopify Locations, DotApparel Locations and Inventory Buffers
      • ERP credentials
      • Product images
      • Fulfillments
      • Payment gateways
      • Gift cards
      • Refunds
      • Notifications
      • Harmony Integration with DotApparel
    • Modules
      • Ship From Store
      • Local Pickup/Click & Collect
      • Shopify Markets
      • Returns
        • Australia Post (AusPost)
        • Loop Returns
      • Auto-Refunds
        • Refunding Shopify Orders from POS (In-Store)
      • Integrate with Brauz (app)
      • Integrate with The Wishlist (app)
    • Release Notes
    • Troubleshooting
      • FAQs
      • How to raise a support ticket for an issue
      • Good and bad examples of a problem ticket
      • Want to enable a new omnichannel feature?
      • Want to integrate a marketplace using DotApparel?
  • Customers
    • Overview
      • Email Examples
    • Getting Started
      • Understanding Customer Setup in your ERP
      • Data Sync
      • Configuration
      • Testing
    • Data Export Approaches
      • Option A: Consultant
      • Option B: In-House
    • Apparel21 Export Templates
    • Apparel21 Export Changelog
    • Dashboard
    • Customers
    • Orders
    • Translations
    • Mappings
    • Settings
    • Support
  • Loyalty
    • Overview
    • Getting Started
      • Terminology
    • Data Sync
      • Workflows
    • Front-End Implementation
    • Rewards Redemption
    • Rewards Emails
    • Things To Know
Powered by GitBook
  1. Core
  2. Troubleshooting

Good and bad examples of a problem ticket

We love it when merchants provide context and actionability in a support ticket. This allows our support team to focus on solving the problem quickly and efficiently, ultimately leading to a better customer experience. Here’s a bad and good example:

Bad ❌
Good ✅  Why? It provides context and is actionable

Hello,

It’d be great if you could take a look at our store, seems like a sync issue. Thanks

Hello,

I'm having an issue with DotApparel. I'm hoping you can help me out!

So far, I've looked into the issue and noticed that [summary of what you've done to solve the problem]. I've attached [any relevant screenshots] so you can get a better idea of what's going on. I was under the impression that [briefly explain your understanding]. However, the problem I'm experiencing is [describe the issue]. Can you please assist me with resolving this issue? Let me know if there's any additional information you need from me or if there are any steps I should take on my end. Thanks for your help!

PreviousHow to raise a support ticket for an issueNextWant to enable a new omnichannel feature?

Last updated 1 year ago

Was this helpful?