Guide
Branded Support and Help Content
Configure storefront help articles, contact forms, policies, and escalation.
SoundSync
Choose the information customers can use
| 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 |
SoundSync
Customer support
SoundSync
Filter requests and record the next support state
The current inbox shows status filtering, notification outcome, Reply by email and a separate status update. This is the shipping interface with illustrative requests; names, addresses, messages, IDs and counts are pixel-blurred. No reply was sent or request changed.
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.
Who can change global support settings
Owners and administrators can save global support configuration, including the contact-form destination and whether the public support page is enabled. Customer Support staff retain their existing support access but cannot change these workspace settings. Saving requires settings.manage and all-products scope in addition to support read access; this restriction does not disable the public support page or contact form.
Support routing and notification history
A branded support form routes to the configured private destination; a public reply-to or support address is a separate presentation choice. Owner/admin settings access controls configuration without disabling ordinary customer support permissions.
Recorded notification outcomes and message history distinguish queued, sent, skipped and failed work. A saved request is not proof of inbox delivery. Keep customer addresses, full names, serials and private message content out of public screenshots.
Keep private routing separate from published help
The form-delivery address stays private and must be valid when the form is enabled; it is not a public contact field. Review page availability, visible contact details and the hosted or external support destination after saving. A failed preview image can be retried without changing its saved URL.
Draft help stays unpublished. Published answers need content and can be reordered for their product scope. Availability and response-time text describe your support practice, not a SoundSync response-time guarantee. Owners and administrators control global settings; a support teammate can handle permitted requests without changing the global destination or disabling the page.
SoundSync
Work through the customer request inbox
| Action | Purpose |
|---|---|
| Filter and load | Open Customer support requests. Filter New, Open, Waiting on customer or Closed; use Load more requests for another page and Refresh requests to reload. The displayed count is the number of requests loaded, not the total inbox size. |
| Review the notification | Email pending, Email accepted and Email notification failed describe the notification attempt, not whether a customer reply was read. |
| Reply by email | Open your own email application to respond. Replies sent there are not tracked as a conversation inside SoundSync. |
| Update status | Choose the current state after following up. If the request changed elsewhere, reload before saving again. Closing a request does not refund or revoke a purchase. |
SoundSync
Automate the inbox carefully
Support Content API
Read paginated requests, protect status updates and keep customer messages private.
