Product and version
Which High Caliber app was used, which version, and whether it was a release build or local preview.
Customer support
Recovery customers often arrive with urgent, personal, or business-sensitive files. High Caliber support should make the next step clear without asking for private source data by default. The support route should start with product details, safe diagnostics, clear issue categories, and realistic expectations.
First support intake
Which High Caliber app was used, which version, and whether it was a release build or local preview.
macOS, Windows, or Linux details, device type, and whether the customer used a supported path.
Install, opening a file, scan, export, report generation, re-download, licence, or refund/delivery question.
Exact error text, screenshots with private content hidden, and non-sensitive generated reports where the app provides them.
Support boundaries
High Caliber can help customers understand product fit, safe setup, export options, and known limitations. It should not promise complete recovery, password/access bypass, official-platform affiliation, professional advice, professional advice, or forensic certainty.
Private source files should not be requested by default. If a real file is ever needed for diagnosis, the process must be opt-in, minimal, reviewed, and covered by approved privacy wording first.
Delivery and refund questions should route to the delivery draft and refund draft once those are final.
Future phone route
High Caliber should use a dedicated business support number rather than a personal mobile. The intended first step is a UK business VoIP support line with voicemail and opening-hours routing. AI/Hermes call handling, recording, transcription, helpdesk integration, and customer-record lookup stay off until separately approved, tested, and covered by privacy wording.