Support / Contact / Review
The public support path for payments, activation, uploads, and result-delivery issues
If you are not running a heavier helpdesk yet, this page should still make the support entry point, issue categories, manual-review boundaries, and required evidence completely clear.
Submit a request
On-site support form
Submit support directly on the site. The form posts to the API, creates a tracked request, and automatically sends a confirmation email to your contact inbox.
Successful checkout without activation code, return-path issues, duplicate charge concerns, or manual review.
If automated email is temporarily unavailable, you can still write directly to support@scoretransposer.com
Support categories
Classify the issue first, then move into manual review
Payment and order issues
Use this route when checkout succeeds but no activation code appears, when the return path looks incomplete, or when an order needs manual review.
Activation and entitlement issues
Use this route when redemption fails, access does not activate, entitlement dates look wrong, or support needs to verify account scope.
Upload and result issues
Use this route when PDF upload fails, jobs stall, downloads break, or a final-vs-draft outcome needs human context.
What to include
Manual support usually moves faster when the request includes enough detail
Contact email or account email
Purchase time, payment provider, and payment screenshot
Activation code, order id, job id, or file name when available
Error screenshot, trigger steps, and approximate time of the issue
Support boundary
Support covers the current live workflow, not future scope that is not launched yet
A commercial site loses trust not only when it lacks features, but when it accidentally sells future scope as if it were already live.
Live support
Current release
Account, checkout, activation, upload, job, and result-delivery issues.
Do not promise yet
Later modules
Reverse conversion, in-browser editing, complex transposition, or perfect automatic output for every score.
Manual review
Available
Order review, redemption issues, download anomalies, and deletion requests.
After submission
The point of the support form is to move the user back onto the right path
After the form reaches the API, it generates a request reference and sends a confirmation email to the contact inbox; if transactional email is not configured yet, a preview is still written to logs.
Public support entry point
A good commercial baseline is to keep one clear public support entry point and make FAQ, About, Privacy, Terms, and Checkout all flow back here when needed.
support@scoretransposer.com