Support protocol
Contact + Support Policy
Official channels, required intake, and self-healing steps. Built to keep support premium for customers and scalable for HyperUp Suite.
Purpose
This page defines the official support channels and support rules for HyperUp Suite. It is written to reduce disputes, protect your account, and keep support privacy-safe and scalable.
Include your purchase email, order ID, environment details, and your Support Hex or Verify Summary (if available). Most technical issues resolve faster when self-healing steps are completed first.
Company contact
- Business name
- HyperUp Suite
- Address
- P.O. Box TBD, Natchitoches, LA 71457
- Website
- www.hyperupsuite.com
- Admin
- admin@hypersuite.com
- Support
- support@hyperupsuite.com
- Billing
- billing@hyperupsuite.com
- Privacy
- privacy@hyperupsuite.com
- Security / abuse
- security@hyperupsuite.com
The HyperUp support standard
Support is designed to be high-signal and privacy-safe. We prioritize structured intake over long message threads, and we use self-healing steps first when applicable.
- Machine-readable intake: We diagnose from structured signals (order details, version, environment, error text).
- Self-healing first: Most issues resolve via built-in repair steps (Verify → Fix).
- Live-aware notices: Known issues are communicated on status pages or in-product when available.
- Verified access: We confirm eligibility to protect customers from fraud and piracy.
Support Hex is a non-sensitive diagnostic summary designed to help reproduce issues without sharing private datasets. If a product provides a Support Hex, include the latest value for technical support.
How to contact support
For the fastest resolution, contact support using one official channel. Requests should be sent from the email used at checkout or include order details for verification.
We do not provide support via social DMs. This protects your privacy and reduces fraud.
Support hours and response targets
- Support hours: Monday–Friday, 9:00 AM – 5:00 PM (Central Time)
- Weekends / holidays: Limited coverage or closed
- First response target: 24–48 business hours
- Resolution: Depends on issue complexity, third-party constraints, and your response speed
Submitting a complete request using the required intake template substantially reduces back-and-forth.
Required intake
To open a ticket, include the following. For technical issues, Support Hex or a Verify Summary is required when your product provides it.
- Full name
- Purchase email
- Order ID / receipt number
- Product name and version (if shown)
- Environment (browser and OS)
- Issue summary (what happened vs. expected)
- Error message or code (copy/paste exact text)
- Support Hex / Verify Summary (required for technical support)
If you cannot generate a Support Hex due to a blocker, send order details and a screenshot of the blocker. We will provide an alternative verification path when feasible.
Self-healing first
Before contacting support for technical issues, complete these steps in order. Include the result of Verify → Fix and your latest Support Hex if available.
- Re-open in a fresh browser session
- Confirm you are logged into the correct account (if applicable)
- Disable platform-affecting extensions (ad/script blockers)
- Confirm permission prompts are granted
- Run Verify → Fix
- Check in-product notices/help
- Try Incognito / Private mode
What support covers
- Access and delivery issues
- Installation/onboarding steps described in product instructions
- Bugs or errors occurring within the product as delivered
- Clarifying intended use of documented features
What support does not cover
- Custom consulting or done-for-you implementation (unless purchased separately)
- Custom feature development or bespoke automation requests
- Debugging unrelated third-party tools outside the product scope
- Restoring files you deleted (you are responsible for backups/version history)
- Guaranteeing specific outcomes, rankings, revenue, or results
Live status and global system notices
Some products rely on third-party platforms (Google, payment processors, hosting). We do not control those platforms. Before emailing about widespread outages or slowness, check the status page if available and any in-product notices.
Security, abuse, and account verification
We may request verification (purchase email, order ID). We will never ask for your passwords. If you suspect abuse, report it to security.
Refunds and billing questions
Billing questions should be routed to billing. Refunds are handled under the published refund policy.
Support conduct and auto-pause rules
We are committed to respectful, helpful support. We may refuse service or terminate communications for harassment, threats, hate speech, or abusive conduct.
Technical tickets may be paused until required intake is provided, including Support Hex/Verify Summary where applicable.
Updates to this policy
We may update this policy from time to time. We will update the “Last Updated” date when changes are published.
Trust and contact
We aim for minimal data sharing during support. When diagnostics are needed, provide only what is necessary to reproduce the issue.
Preferred: Email support with the required intake template.
Privacy note: We do not need your private datasets to help you. If a screenshot is necessary, redact sensitive personal data before sending.
We store non-PII attribution for 7 days to improve support and analytics.