Deployment

Push it to the phones. Reps install nothing.

The agent is an Android app delivered through managed Google Play. Google Workspace, Intune, or any Android Enterprise MDM installs it and hands it three configuration values. This page says what is required and what to check before rollout.

Requirements

Managed devices only

The phones must be company-owned and enrolled as fully managed devices. On a personal phone with a work profile the agent cannot see calls made from the personal dialler, and that is where normal calls land. A work-profile deployment will show an empty board.

iOS is not supported. iPhones do not expose the call log to apps. If part of the team is on iPhone, a network-side product from the carrier is the only route for those handsets.

Steps

Through Google Workspace

Other MDMs follow the same shape: private app, forced install, managed configuration.

  1. 01
    Create a fleet enrolment code

    In your workspace, open Phones and create an enrolment code for the whole fleet.

  2. 02
    Add the app as a private app

    In the Google Admin console, add the agent through managed Google Play as a private app and assign it to the organisational unit the phones sit in, as a forced install.

  3. 03
    Set the managed configuration

    Open the app's settings in the Admin console and set the three keys below.

  4. 04
    First launch on each phone

    Each rep opens the app once and taps Allow call access and Keep running in the background. The phone then appears on the Phones page and you assign a rep name.

Managed configuration

Three keys

server_url
https://<workspace>.<your base domain>Your workspace address. Shown on the Phones page.
enrolment_code
fleet code from the Phones pageOne code for the whole fleet. Revoke and reissue any time.
tracked_sim_slots
0, or blank0 tracks the first SIM only. Blank tracks every SIM. Use 0 on dual-SIM phones so personal calls stay out.
Before rollout

Check these

Google Play permission review. The agent needs the phone and call log permissions. Public listings must be the default dialler or hold an exception; private enterprise apps get a lighter review. Confirm the current rules for your listing before you depend on it.
Pre-granted permissions. Check whether your MDM can pre-grant the phone and call log permissions for private apps. If it can, step 04 becomes optional. If not, each rep grants them once.
SIM filtering. Some handsets do not record which SIM a call used. If filtering by SIM drops every call, leave tracked_sim_slots blank.
Background limits. Live state depends on the foreground service. Some makers (Samsung, Oppo, Xiaomi) stop background apps aggressively. The Keep running in the background exemption is what makes it reliable.
Where you operate

Notice and consent rules by country

Pick the country and state or region your staff work in. The same notice appears inside the workspace once it is created.

Before you monitor phones in Iowa, United States

Before you enrol phones in Iowa, United States: Written notice to staff before monitoring starts is recommended. Tell staff what is collected (call times, durations and numbers, no audio), why, and where it is stored (Australia). Record the date the notice went out on the Settings page.

Notice to staff
Recommended before monitoring starts
Privacy law
Federal Electronic Communications Privacy Act; state privacy laws vary
Call recording (not live)
One-party consent
Data hosted in
Australia

No state statute requires advance notice of monitoring on company-owned phones here, but a written policy and notice before monitoring starts is standard practice and strengthens the reasonable-expectation position. Check with counsel.

This is a summary, not legal advice.

Detail for Iowa, United States

Callboard records call metadata (direction, time, duration and the other party's number) from company-owned phones. It does not record audio, contacts or messages. That is employer monitoring of company devices in Iowa, United States: Written notice to staff before monitoring starts is recommended. Customer numbers are personal information under the Federal Electronic Communications Privacy Act; state privacy laws vary; storing them hashed and masked (the default) reduces what is held, and your privacy notice should cover them.

Call recording (One-party consent). Federal law and this state are commonly treated as one-party consent: a party to the call may record it. Calls into all-party states may still need every party's consent. Check with counsel.

Privacy. There is no federal comprehensive privacy law. State consumer privacy laws (Virginia, Colorado, Connecticut and others) mostly exempt employee data but may cover the customer phone numbers you collect. Check with counsel for your state.

Hosting. Kept in Australia. No US federal data-localisation rule applies to this data, but say where data is stored in your privacy policy and check any sector or contract requirements.

  • Electronic Communications Privacy Act, 18 U.S.C. 2511
  • State wiretap and consent statutes

This is a summary, not legal advice.

Privacy and compliance

What is collected, and what is not

  • Notice to staff

    No state statute requires advance notice of monitoring on company-owned phones here, but a written policy and notice before monitoring starts is standard practice and strengthens the reasonable-expectation position. Check with counsel. Have your HR or legal team handle this before rollout.

  • Numbers

    Phone numbers are stored as a keyed hash (so a call back can be matched) plus the last three digits for display. A workspace can choose to store full numbers, and should only do so once the notice covers it.

  • Not collected

    No call audio, contacts or SMS. The phone shows a persistent notification while the agent is reporting.

  • Removing a phone

    Removing a phone in the workspace revokes its token. It cannot re-enrol with the fleet code until restored.

  • Hosting

    Each workspace has its own database, kept in Australia.

Ready

Create a workspace, then push the agent

Start free trialAsk about rollout