E-commerce Order Support

Order support for an online store: tracking, shipping and returns in tickets, public product Q&A and a VIP lane.

  • 6 categories
  • 30 channels
  • 11 roles
  • Medium
Download Discord JSON

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

STOREFRONT

  • store-info

    What we sell, where we ship and how to reach us. Pick your alert roles here.

  • store-policies

    Returns, exchanges, shipping times and warranty, in plain language.

  • support-hours

    When agents are online and how long a ticket usually takes.

  • new-arrivals

    New products and collections as they go live.

  • promo-codes

    Current codes and their expiry. Only the store posts here.

  • restock-alerts

    Sold-out items coming back. Mentions Restock Pings.

ORDER HELP

  • before-you-open-a-ticket

    Have your order number ready. Tracking updates can take 24 hours to appear.

  • order-tickets

    Where is my order, wrong item, missing item. Open a ticket from the panel.

  • shipping-tickets

    Carrier problems, address changes and customs questions.

  • returns-ticketsHidden from @everyone

    Exchanges and refunds. Visible once your purchase is verified.

PRODUCT Q&A

  • product-questions

    One thread per question. Name the product in the title.

  • sizing-help

    Measurements, fit notes and comparisons between lines.

  • how-to-use

    Setup, care and troubleshooting for what you bought.

  • wishlist-and-requests

    Products, sizes and colours you want us to make or stock.

VIP CUSTOMERS

  • vip-lounge

    Our best customers and the team. Ask us anything.

  • early-access-dropsHidden from @everyone

    Drops open here first. Mentions Drop Pings.

  • vip-conciergeHidden from @everyone

    Priority tickets for VIP customers. Open one from the panel.

  • VIP Room

COMMUNITY

  • customer-chat

    Talk about the products, not about your order. Orders go in a ticket.

  • share-your-haul

    Photos of what arrived. One post per delivery is plenty.

  • Customer Lounge
  • Live Drop
  • AFK

SUPPORT TEAM

  • agent-chat

    Who has which ticket, what is waiting on fulfillment, what is waiting on the customer.

  • order-lookups

    Paste the order number and what you found. Keeps lookups out of tickets.

  • carrier-updatesHidden from @everyone

    Carrier delays and service alerts, posted by fulfillment.

  • refund-approvalsHidden from @everyone

    One message per refund: order, amount, reason. The manager replies in thread.

  • ticket-archiveHidden from @everyone

    Vetox posts closed-ticket transcripts here.

  • store-logsHidden from @everyone

    Vetox posts moderation, join and message logs here.

  • Agent Huddle

Roles

  • Store OwnerAdministrator
  • Store ManagerAdministrator
  • Community ModeratorModerator
  • Support AgentModerator
  • Fulfillment Team
  • VIP Customer
  • Verified Customer
  • Restock Pings
  • Drop Pings
  • Muted

Overview

Made for a store that sells online and answers customers on Discord: a clothing label, a peripherals brand, a print shop or a specialty food seller. Anything that involves an order number happens in a ticket, and the panels are split so the queue tells the agent what the customer needs before the first message: #order-tickets for where-is-my-order, #shipping-tickets for carrier problems and address changes, #returns-tickets for exchanges and refunds. Questions that help everyone stay public: Product Q&A is a forum tagged by Sizing, Materials, Compatibility and Care, with #sizing-help and #how-to-use beside it so an answer can be found twice. Storefront is read-only and carries #store-policies, #support-hours, #promo-codes and #restock-alerts, each with a role customers can opt into. VIP Customers is a hidden category with #vip-concierge, a priority ticket channel, #early-access-drops and their own voice room. The Support Team category is invisible to customers and holds #order-lookups, the #carrier-updates feed, #refund-approvals for the manager's sign-off and #ticket-archive.

When to use it

Your store's Discord started as a fan community and turned into the support inbox: order numbers get pasted into public chat, returns are negotiated in DMs nobody else can see, and a customer who has bought ten times waits behind a first-time buyer. This layout puts every order conversation behind a ticket panel sorted by problem type, keeps product knowledge public where it saves the next customer a question, and gives VIPs a concierge channel the rest of the store never sees.

What makes it different

  • Three ticket panels - orders, shipping, returns - so each queue arrives pre-sorted for the agent picking it up.
  • Product Q&A is a public forum tagged Sizing, Materials, Compatibility and Care, so answers are found again.
  • #returns-tickets is visible only to Verified Customers, which stops return requests from unknown buyers.
  • VIP Customers is hidden and holds #vip-concierge, a priority ticket channel with its own queue.
  • #refund-approvals gives the Store Manager a sign-off step before an agent issues money back.

Recommended Vetox setup

  • Tickets

    Create three panels in #order-tickets, #shipping-tickets and #returns-tickets, plus a priority panel in #vip-concierge that only VIP Customers can see.

  • Self-Roles

    Post a Self-Roles panel in #store-info with Restock Pings and Drop Pings so #restock-alerts and #early-access-drops mention only customers who asked.

  • Auto-Mod

    Enable Auto-Mod link filtering in #customer-chat and #product-questions so fake discount links cannot sit next to your real #promo-codes.

  • Embed Messages

    Use Embed Messages for the policy cards in #store-policies and #support-hours so return windows and response times read the same way every time.

Questions

How does a customer become a Verified Customer?

They open a ticket in #order-tickets with their order number; the agent checks it against the store and grants the role. From then on #returns-tickets is visible to them, and the next return request skips the identity step.

Why is there a separate refund approval channel?

Money leaving the store should have two sets of eyes. An agent posts the case in #refund-approvals, the Store Manager approves in the same thread, and the agent then completes the refund from the ticket. The archive shows both steps.

Can the public product forum replace tickets?

For questions about the product, yes, and it should: a sizing or compatibility answer in #product-questions helps every future buyer. Anything that names an order, a payment or an address belongs in a ticket, which is why both exist.

Common mistakes

  • Letting customers paste order numbers and addresses in public chat, which is a privacy problem before it is a support problem.
  • Running returns from DMs, so nothing is on record when a refund is disputed and no second agent can pick the case up.

Consider instead

  • Product Support Hub You sell software or a service rather than shipped goods and have no orders, carriers or returns to track.

Do you have any doubts?

Our team is there for you

0.0k

Servers

0+

Commands

0

Users

0

Languages