Communication / In development

Push-to-Talk & Field Communication

Give authorized field teams company-scoped communication channels, transmit permissions and a controlled turn to speak.

Customer Super AdminSupervisorRider / DeliveryField SalespersonCollection Officer

What it is designed to manage

  • Company-scoped channel directory and membership
  • Separate channel access and transmit permissions
  • Short speaking-turn lease and holder-only release
  • Rider app channel selector and secure sign-in foundation
  • Planned voice media and field-team app coverage
  • Connectivity modes with clear online and local-range requirements
FieldPro Push-to-Talk & Field Communication design concept
Design concept with sample records; not a live ERP screenshot.
Channel access and speaking-turn control exist in source batches. Live microphone audio is not implemented. Internet over Wi-Fi can work without cellular coverage; offline Bluetooth/Wi-Fi Direct is planned and local-range only. Longer-range offline use requires suitable relay or radio hardware.
Feature-by-feature availability

What is in source, planned or awaiting integration.

  • Channel administration and permissionsSource added

    Channel listing, members, creation, grant and revoke are recorded in the source batch; active company context is required.

  • One speaker at a timeSource added

    Company/channel speaking-turn controls use a 15-second lease and a holder-only release.

  • Rider channel selectorSource scaffold

    Initial Flutter sign-in, secure token storage and read-only channel selection exist. Role mapping and platform project generation remain pending.

  • Live voice audioPlanned / integration required

    Microphone capture, an independently authorized media service and live audio delivery remain to be implemented.

  • Supervisor, sales, delivery and collection app coveragePlanned

    PTT is intended across these field apps; a separate finished implementation for each is not established.

  • Local offline communicationPlanned / hardware dependent

    Bluetooth or Wi-Fi Direct has local range; no 1–2 km or long-distance offline voice capability is claimed.

Permissions & security requirements.

  • Only granted company channels are visible. Transmit permission defaults off.
  • Company Super Admin manages channel grants and revocations. The speaking-turn holder alone can release it.
  • Voice media authorization, permission refresh, signaling rate limits and audit completion remain integration work.

Related role applications.

Module access follows assigned rights. Application package releases and live connections are separate.

A practical view of the process

How the work moves.

01

Select an authorized company

02

Open a granted channel

03

Check transmit permission and acquire a speaking turn

04

Send voice through the configured media service when available

05

Release the turn and clear company state on sign-out

Information coming in

  • Authorized company membership
  • Channel grant and transmit rights
  • Configured media infrastructure

Records & handoffs coming out

  • Permitted channel list
  • Speaking-turn state
  • Voice capability readiness status
Connected departments

Where this module connects.

In development. Release availability requires the relevant implementation, integration and validation work. The visual above is illustrative.

Start with your business

Map your teams.
Connect your workflow.

Explore the departments and handoffs that match your operation, then prepare a product enquiry around your company structure.