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
  • 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
On this page

Was this helpful?

Export as PDF
  1. Core
  2. Troubleshooting

How to raise a support ticket for an issue

PreviousFAQsNextGood and bad examples of a problem ticket

Last updated 8 months ago

Was this helpful?

  1. Step 1: Issue is discovered

  2. Step 2: If you notice a system alert, simply navigate to the alert within the app to find instructions to solve it. Alternatively, you can refer to our

  3. Step 3: If our FAQs don’t cover the issue you’re experiencing, you can contact us through the in-app support widget. We’ll get back to you within 24 hours but if it’s urgent, it’ll be much sooner than that.

In the DotApparel app, you'll see a Support widget. Raise a ticket directly here to get in touch with our team for help. .

Access your tickets using our support portal

View all tickets in our support portal:

If you haven't already done so, make sure to register for a support portal account to access your tickets. Simply Sign up to create an account.

If you'd like to view all of your historical tickets (resolved or closed), simply click on this button.

detailed FAQs for more info.
Here's an example of raising a good problem ticket
support.dotapparel.com.au