01iPhone
Prioritized queue
Review assigned tickets, SLA pressure, status, priority, client, and site context in one focused queue.
View product detail →QueueRove capabilities
Finish more of the ticket while you are still there.
QueueRove gives HaloPSA field technicians a focused native path from assigned work to notes, evidence, status, and service time.
Capability guide
Product truth, down to the platform.
The native apps share QueueRove identity, licensing, and direct HaloPSA principles. Feature labels identify where the current public capability has been verified.
- iPhoneVerified in the current iPhone workflow and product demonstrations.
- AndroidVerified specifically against the native Android implementation boundary.
- BothAvailable across both native platforms, with implementation details that may differ.
Field workflow
Move from assignment to a complete service record.
QueueRove keeps the essential HaloPSA work close to the technician, with focused mobile interactions for the moments that usually send someone back to a laptop.
02iPhone
Ticket context
Read the issue, customer and site details, and recent ticket history before arriving or taking the next action.
View product detail →03iPhone
Public and private notes
Capture the service narrative while details are fresh and choose the appropriate HaloPSA note visibility.
View product detail →04Both
Field photos
Attach visual evidence through a native mobile flow. Android photo input uses CameraX and the system Photo Picker.
View product detail →05iPhone
Status updates
Move the ticket forward from the field and leave HaloPSA ready for the next person who touches the work.
View product detail →06Both
Direct HaloPSA connection
Each native app connects to the customer-configured HaloPSA environment instead of copying ticket data into a QueueRove ticket cloud.
View product detail →Resilient capture
Keep work visible when the network is not.
QueueRove is designed for field conditions. Platform labels make the current behavior explicit instead of implying identical offline capabilities.
01Both
Cached working context
Previously loaded iPhone ticket information remains available when connectivity drops. Android maintains local working state in Room.
View product detail →02iPhone
Visible offline queue
Supported notes, photos, status changes, and time entries remain visibly queued on iPhone until synchronization completes.
View product detail →03iPhone
Synchronization status
See when queued iPhone work reaches HaloPSA so technicians can verify progress before repeating an action.
View product detail →Time and context
Recover time without adding another end-of-day chore.
QueueRove brings time capture and optional on-device assistance into the same ticket workflow.
01iPhone
Ticket timer
Start and stop service time from the ticket and keep the active timer visible while moving through the app.
View product detail →02iPhone
Lock Screen visibility
Keep active service time visible from the iPhone Lock Screen so an in-progress timer is harder to leave behind.
View product detail →03iPhone
Completed time entry
Finish the time record in the field and review the day’s captured time from the Today summary.
View product detail →04iPhone
Generate Briefing
On supported Apple Intelligence devices, summarize ticket history already on the iPhone without sending it to QueueRove or a third-party AI service.
View product detail →05Both
Named technician access
Each active technician uses a personal QueueRove identity, organization membership, and named license assignment.
View product detail →06Both
Usage without activity fees
One product edition includes every released feature, with no per-ticket, note, photo, timer, login, or synchronization-operation fee.
View product detail →Direct by design
HaloPSA stays the system of record.
QueueRove is a mobile productivity and revenue-recovery layer for the PSA your MSP already operates—not another ticket database.
- DirectNative apps connect to the customer-configured HaloPSA environment.
- ProtectedHaloPSA credentials use platform-backed secure storage and are not relayed through a QueueRove server.
- AccountablePersonal QueueRove identities, organization membership, and named access determine who may use the apps.
Next step
Choose the native path for your technicians.
Compare the verified platform capabilities, then review the named-technician plan.