What QueueRove is—and is not—today.

The native iPhone app is in private beta preparation. There is no verified public App Store listing URL. Invited testers should follow the requirements provided with their exact build.

The native Android app is in active development and internal validation. It is not publicly available, has no Google Play listing, and has no promised release date.

QueueRove does not show a store badge until the corresponding public listing URL has been verified. A badge without a working destination would misstate availability.

You need a reachable customer-approved HaloPSA environment, its exact instance address, and customer-issued API credentials with permission for the records and actions your role needs. QueueRove does not create or expand HaloPSA access.

The iPhone app stores them in iOS Keychain. The Android app uses Keystore-backed AES-GCM protection and stores ciphertext in private no-backup app storage. Neither app relays credentials through a QueueRove server. Never send a Client Secret or access token to support.

The approved website control plane does not ingest either app's HaloPSA records. Each mobile app uses network access to connect directly to the customer-configured HaloPSA environment. The iPhone app keeps its cache and pending supported actions on the device; the Android app holds local state in Room.

In the current iPhone build, cached information remains available and supported notes, photos, status changes, and time entries can remain visibly queued on the device until synchronization completes. Offline tolerance is not a backup; confirm important work in HaloPSA. Android's Room local state remains under internal validation, so no broader public Android offline-behavior claim is made.

Check the synchronization state and HaloPSA first. Repeating an action can create a duplicate. If a queued action remains after connectivity returns, follow the support troubleshooting steps.

On supported Apple Intelligence devices and OS versions, it processes ticket history already on the iPhone. Ticket content is not sent to QueueRove or a third-party AI service for this iPhone feature. Exact device and OS support must be checked against the build; this is not an Android availability claim.

During internal validation, CameraX and the Android Photo Picker support photo input, camera access is optional, and network access connects directly to the customer-configured HaloPSA environment. The app requests no broad media, location, contacts, or call-log permission and does not send HaloPSA customer records through the website control plane, analytics, advertising, a crash SDK, billing, or a remote-AI service.

The approved v1 website control plane uses one Auth0-backed human account for organization membership and administration. Provider configuration and production deployment require separate evidence. Mobile login and entitlement integration remain deferred; a HaloPSA credential is not a QueueRove account or entitlement.

Use authenticated privacy controls when you can sign in. If you are locked out or uninstalled a client, use the non-enumerating account-deletion intake. Identity must be verified before QueueRove reveals or changes state. Device-local data and HaloPSA records use the separate paths on Privacy choices.

No. The Pricing page publishes the authoritative USD GA catalog for the planned organization-level subscription, but production checkout, collection, and charging are not open. Repository code, a configured catalog, or a local test does not make enrollment live; provider, counsel, tax/accounting, staging, and launch gates must be recorded first.

The GA catalog is an organization-level subscription priced in USD by active technician. Monthly pricing is $49 total for one or two technicians, $24 per technician for 3–14, and $21.60 per technician for 15–49. Annual pricing is $456 total for one or two, $228 per technician for 3–14, and $205.20 per technician for 15–49. Standard self-service applies only to U.S. business customers with 1–49 active technicians. Non-U.S. opportunities and organizations with 50 or more technicians require human review and do not create a standard self-service transaction. An active technician is a named technician authorized during the billing period; non-technician administrators do not consume seats.

This website makes no partnership, certification, sponsorship, or endorsement claim. QueueRove is described as a companion built to work with the customer's HaloPSA environment. HaloPSA is a third-party service.

No. V1 permits only essential identity, session, invitation, security, and checkout cookies for enabled features. It has no analytics, advertising, tracking pixels, or other non-essential cookies, so there is no performative marketing-cookie banner. Public sales and deletion forms collect only their displayed routing fields.

Email support@itecsonline.com with “QueueRove support” in the subject and include non-secret app, OS, timing, network, and error details. The initial product/account/billing response target is 1 business day during the hours published on Support. It is not a resolution SLA. Structured intake is available only in the authenticated product flow, where it can be bound to the user and active organization.