Before you contact support
Support body copy placeholder. Describe what visitors should verify before opening a ticket, which products use separate checkout flows, and where self-serve answers live.
Link visitors to the FAQ template for common pre-purchase questions and to feature guides such as the first feature template when modules need context.
Information to include in every ticket
Ticket checklist placeholder — order email, product name, OS build, and error text. Replace with fields your vendor or internal team requires.
Reference guides like the requirements template or setup template when troubleshooting install steps.
Response expectations
Response-time placeholder. Document business hours, weekend delays, and spam-folder reminders for license email.
Refund placeholder — clarify that payment disputes stay with the checkout partner on the customer receipt.
Feature and pricing questions
Point buyers to the review template and module pages for feature lists. Checkout runs through the checkout hub placeholder once affiliate URLs are configured.