Plain contact name for reply handling. Do not request sensitive identity documents.
Customer enquiry readiness · static only
The enquiry route is now designed before we switch it on.
This page gets HighCaliberTrading.co.uk ready for a future customer enquiry form without collecting anything today. It defines the minimum fields, triage buckets, consent wording, privacy checks, and launch gates needed before a real form, inbox, CRM, ticketing system, or automation is connected.
No live form tag, form handler, CRM, analytics, email automation, phone publication, or customer data collection is connected. Public page can describe the future route; interactive systems remain approval-gated and local systems are not published.
Routing standard
One form shape, separate handling lanes.
The future Trading-site enquiry route should sort requests into customer support, provider/merchant review, and software-asset review without promising instant support or collecting unnecessary private material.
Initial support should ask for safe text details only: product name, platform, version, issue category, order/reference if already known, and a short description. Private files, backups, libraries, databases, and screenshots should only be requested later through a reviewed support route.
Business-asset and provider enquiries should stay separate from app support so ordinary customers are not pushed into acquisition, merchant, or legal-review language.
Future field map
The fields are planned, but not live.
These are visual placeholders, not input boxes. They are included so the future form can be built deliberately and safely.
Used only for the enquiry response. Add consent and retention wording before this goes live.
Customer support, provider review, software asset review, partnership/licensing, or general question.
High Caliber Apps product, customer portal, provider readiness, or business-asset review.
Mac, Windows, Linux, Android, iPhone/iPad, app version, or browser route if known.
Text-only summary. No private file uploads in the first contact step.
Consent and privacy wording
Wording to approve before activation.
Draft activation wording: “By sending this enquiry, you agree that High Caliber Trading Ltd may use the details you provide to respond to this request. Please do not include passwords, payment-card details, private files, full backups, or sensitive personal material in this first message. We will only ask for additional diagnostic material if it is needed and a safe support route has been agreed.”
This is a draft readiness note only. It still needs final privacy/legal review before a real form is enabled.
Launch gates
What must be approved before this becomes a real form.
- Approved recipient inbox or ticketing destination with secure access and retention rules.
- Final privacy wording, consent wording, response-time wording, and no-private-files warning.
- Spam protection that does not add analytics/tracking without approval.
- Clear customer-data storage location, deletion route, and backup policy.
- Manual test submission with dummy data only, followed by a live-form go/no-go decision.
Privacy and retention summary
Draft wording is ready for solicitor review.
Future enquiry forms should collect only the minimum information needed to reply, route support, and protect the business: name, reply email, enquiry type, product or route, safe technical context, and a short text message. First contact should not request passwords, payment-card details, private files, full backups, identity documents, or sensitive personal material.
Routine pre-sales enquiries are proposed for deletion or anonymisation after up to 12 months; support enquiries after up to 24 months; order, refund, complaint, dispute, or required business records for longer where legally or operationally needed. The full draft notice remains subject to solicitor review before any live form is enabled.