Guide
Branded Support and Help Content
Configure storefront help articles, contact forms, policies, and escalation.
SoundSync
Support settings
| Area | Purpose |
|---|---|
| Public identity | Support email/phone, business address, contact name/label, response guidance, and availability |
| External links | Documentation, FAQ, refund policy, terms, EULA, and optional support-page override |
| Help articles | FAQ, install, activation, download, compatibility, policy, known issue, and troubleshooting articles |
| Product scope and order | Show the relevant article for the intended products and page order |
| Contact form | Enable the form, choose destination and supported fields, and review customer context |
| AI assistance | Configured tone and escalation when uncertain; not autonomous financial decisions |
Make the help match the product
Write installation and activation guidance for the product the customer owns, including platform, format, version, and known limitations. Keep policy links current and route billing/privacy questions to the appropriate SoundSync contact.
A response-time label is your published guidance, not a platform-wide response-time guarantee. Use a destination you monitor and test the supported contact path before relying on it.
Plugin support is a separate surface
Storefront help articles and contact forms do not automatically replace every support button bundled in HISE or JUCE. Inspect the generated package support path and regenerate where required.
Keep personal customer data, serials, and credentials out of public articles and screenshots. AI assistance should escalate uncertain licensing, refund, or sensitive account matters.