What QueueRove delivers today.

Yes. The native iPhone app supports queue triage, ticket context, notes, photos, status, and service time. QueueRove confirms the supported version and distribution path during organization onboarding.

Yes. The native Android app provides a field workflow connected directly to the customer-configured HaloPSA environment and protects credentials with platform-backed secure storage. QueueRove confirms supported version details during onboarding.

App access and supported-version details are coordinated during organization onboarding. QueueRove displays a public store badge only after its destination has been verified.

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.

On iPhone, 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 keeps local working state in Room; confirm synchronized work in HaloPSA before repeating an action or clearing local state.

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.

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.

Yes. Each person uses an Auth0-backed QueueRove identity for organization membership, role grants, named technician access, and entitlement. HaloPSA credentials remain separate and do not create or expand QueueRove access.

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.

Review the authoritative USD catalog on the Pricing page, then contact QueueRove for direct organization and subscription setup. The public pricing page does not collect payment.

The standard catalog is an organization-level subscription priced in USD by active technician using graduated tiers. Monthly pricing is $49 total for the first two technicians, $24 for each technician from 3–14, and $21.60 for each technician above 14 through 49. Annual pricing is $456 total for the first two, $228 for each technician from 3–14, and $205.20 for each technician above 14 through 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@queuerove.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.