Devices
Current operational health, network transport, agent rollout state, and queue status. Battery is a present-time gauge, not an endurance measurement.
Fleet inventory
Current state reported by each enrolled agent.
Onboard a device
Create an Android Device Owner provisioning code and enrollment identity directly from the dashboard.
127.0.0.1 URL only works on this computer, not on a new phone.Provisioning details
Saved as defaults after successful QR creation.
Provisioning QR
Complete the provisioning details to generate a one-time enrollment QR code.
Cluster QR
One reusable code for a whole rack. Every phone it enrols waits for your approval.
Failed enrolments
Phones that reached the server and were turned away. An empty list while a phone "fails to onboard" means it never called at all - the problem is on the handset.
Recent onboarding codes
Routines
Build repeatable phone workloads. Saving does not run or enable a routine. The scheduler master switch must be Running for enabled routines to fire. Queued calls and routine jobs share each device queue; raising the dial budget reduces routine throughput.
New routine
Steps run in the order shown below on each target device.
Saved routines
Run once, edit, or explicitly enable a schedule.
Human dialing
Each eligible phone owns an independent next-call time, personal contacts, and stable peer affinities.
Dialing policy
Saving updates policy only. Enable explicitly; keep dry-run on while reviewing distribution.
Independent schedules
Next-call times and the latest queued or dry-run intentions.
Client accounts
Each account signs in with a username and password and sees only the clusters assigned to it. Scoping is enforced by the server, so a client cannot reach another cluster's data by calling the API directly.
New client login
Passwords are stored hashed and are never displayed again.
Existing accounts
Reassign clusters, reset a password, or disable access.
Onboard / offboard
Every device that has joined or left the fleet. Offboarding deletes a device's identity and job history, so this log is kept separately and is never rewritten - it stays accurate after the device itself is gone.
History
Newest first.
Messaging
Text messages run on their own budget and schedule, independent of calling - a phone out of calls for the day can still text. Peers are other fleet phones; external numbers pass the same E.164 and blocked-prefix checks as call targets.
Messaging policy
Saving updates policy only. Keep dry-run on while reviewing.
Per-device state
Next message times and recent intentions.
Activity
Recent commands, results, usage measurements, and failures across the fleet.