Archived Support policy
QueueRove support
Route product/account, billing, or security questions with a QueueRove-specific category. Never send a secret, card data, or live HaloPSA customer record.
- Version 2026-07-17-draft.1
- Effective date: Pending Texas counsel approval
- SHA-256
1a4e3e89de1817bc87b5fa0d965378afd1febe42b4a721787224b13c779580a5
Archived draft status
Technical draft pending Texas counsel review; production collection and charging also require tax/accounting signoff and explicit launch approval.
This repository-local document is not provider, deployment, counsel, tax, or production evidence. It makes no approval or launch claim.
The content hash is derived from the versioned structured source rendered on this page. Material changes require a new version, archive entry, and the approved reacceptance process.
View the current stable route → · View all archived documents
1. Contact and routing
The monitored public inbox is support@itecsonline.com. Use QueueRove support, QueueRove billing, QueueRove security report, QueueRove privacy request, or QueueRove 50+ sales as the subject/category so QueueRove records and automation remain logically separate from MSPRanked.
Email is not action authority
Support can explain, triage, and route. A message cannot authorize role or ownership changes, refunds, billing mutations, exports, deletion, impersonation, or access to HaloPSA contents. Sensitive actions require the approved authenticated workflow and authority checks.
2. Authenticated structured intake
Structured support intake belongs only in the authenticated QueueRove control panel, where server-side handling binds the verified user and active organization. It collects a category, approximate time, affected surface, and short redacted description, and accepts no attachments. This public page does not expose that form. Privacy and deletion requests must use their dedicated workflow.
3. Safe details to provide
- A short redacted description, approximate time, affected QueueRove surface, category, app/browser and OS version, and non-sensitive error text.
- Whether the issue concerns product/account access, billing, or security. Use the dedicated privacy/deletion paths for those requests.
- Never provide passwords, MFA/recovery codes, API secrets, HaloPSA tickets or customer records, card data, private keys, or unredacted screenshots.
- V1 support intake does not accept attachments.
4. Business hours and response targets
Business hours are Monday through Friday, 8:00 a.m. to 5:00 p.m. Central Time, excluding U.S. federal holidays.
| Inquiry | Initial response target |
|---|---|
| Account takeover or critical security | 4 business hours |
| Product support, access, or billing | 1 business day |
| Privacy or deletion | 2 business days; deletion completion target remains 28 days |
| 50+ sales | 2 business days |
Targets are not resolution SLAs
These targets describe an initial response, not resolution or remediation. A signed agreement may supersede them.
5. Product availability and provider evidence
The repository may contain staging-oriented account, organization, billing, invitation, privacy, and support code, but code and local tests do not prove provider configuration or production availability. Checkout and charging remain closed until all provider, counsel, tax/accounting, staging, and launch gates are recorded.
The iPhone client remains in private beta preparation and Android remains in development/internal validation unless a separately verified release record says otherwise. No unverified App Store or Google Play listing is published.
Related resources
Questions may be sent to support@itecsonline.com with the subject “QueueRove support”.