Hold the key.
The whole team hears you.
DuskLine puts every crew on one push-to-talk channel, with dispatch, live location and man-down alerts in the same console. And the channel is not only for people: AI agents join it as members, hearing what is said and acting on it.
Built for security, mining, transport and emergency crews across the Middle East and Africa. Runs on rugged Android handsets, ordinary phones and iOS, and bridges to the radios already on the belt.
Press and hold the button, or hold the space bar while it has focus.
What DuskLine does
One key, one channel
Press to talk and every connected member hears it. No ringing, no waiting for anyone to pick up.
Radios stay in the mix
LMR endpoints join channels alongside handsets, so crews can move over without dropping the fleet they have.
Location on the same screen
Dispatch sees who is where while they are talking — positions, route history and zone breaches in one view.
Safety events raise themselves
Man-down, no-movement and low-battery conditions open an event without anyone reaching for a handset.
The channel isn't only for people
Every other platform here moves voice between humans. DuskLine also puts software on the talkgroup.
A voice or text agent joins a DuskLine channel the way a person does. It appears in the roster, it hears what is said on the talkgroup, it answers out loud, and it can act on what it heard — open an event, place a call, write to a system of record.
Agents are built per customer, against your procedures, your vocabulary and your systems. That is the work: a guarding company and a refinery need different agents, and neither needs a general-purpose chatbot wired to a radio. Tell us the routine your crews repeat every shift, and that is the one we automate first.
Agents hold a seat on the channel, so anything that reaches the channel reaches them.
Shift log
Listens to the talkgroup and writes the incident log as it happens, so the report is finished when the shift is.
On-channel interpreter
A crew speaking Arabic, French and English on one talkgroup, with the agent interpreting between them as they talk.
Roll call
Calls every member at shift start, confirms who is on post, and flags the ones who did not answer.
Lone-worker check-in
Calls a worker on a schedule, takes the reply by voice, and escalates to a supervisor when nobody responds.
Procedure lookup
Answers “what is the isolation procedure for pump three” on the channel, without anyone stopping to find the manual.
Escalation
Watches for a man-down or a spoken keyword, then makes the calls and sends the notifications the runbook asks for.
Who works on it
The same platform, configured for what each kind of crew actually spends the shift doing.
Private security and facilities
Guards on patrol, spread across sites, mostly alone. Itinerary playback and the heatmap show whether a round was actually walked. No-movement catches a guard who has stopped. The emergency key is the panic button, and it carries a location.
Agent: roll call at shift start, checkpoint confirmation by voice.Mining and industrial sites
Lone workers in pits, plants and shafts, where a fall is a reportable incident. Man-down raises itself, geofences mark the zones people should and should not be in, and a whole site shares one channel without a repeater on every level.
Agent: scheduled check-ins, procedure lookup on the talkgroup.Transport and logistics
Drivers, yard crews and port operations strung along a corridor. A corridor geofence follows the route instead of drawing a circle around a point, so a convoy that leaves the road is flagged where it happens.
Agent: automatic trip logging, driver check-in on long runs.Public safety
Fire, police and emergency response, where accountability matters as much as the call itself. Every transmission is recallable, every event carries an initiator and a timestamp, and radios stay in the channel while a fleet transitions.
Agent: incident log written as the call runs.Run every channel from one screen
Dispatchers monitor joined groups, spin up temporary channels for an incident, and keep a call record without leaving the console.
Standing and temporary channels
Keep permanent groups for shifts and open a temporary channel for an incident, then close it when the call clears.
Who is on, who is missing
The roster shows connected members with their priority level, and hides offline teammates and dispatchers when the list gets long.
Everything is recallable
Messages, recall recordings and the call record sit under the channel, so a supervisor can replay what was said.
See the crew, not just the channel
Location monitoring works four ways over the same map. Switch between them without losing the channel you are listening to.
Live positions for everyone on the selected channel. A man-down flag turns the marker red and pushes the member to the top of the info panel with their last known address.
Overlay where a member actually spent the shift. Tracked points are timestamped and addressed, so a route can be reconstructed after the fact.
Draw a zone three ways: a radius around a point, a polygon traced around a building footprint, or a buffered corridor along a route for convoy work.
Follow one member's itinerary point by point, with the stops and times that produced it listed beside the map.
The events that can't wait in a queue
Safety events open themselves, carry a priority and a location, and stay ongoing until somebody resolves them.
Reach one person without leaving the room
The directory carries duty status, handset state and group membership, and a call starts from the same row.
Nine members, three on duty, one off the network. Battery and connection state sit next to the name, so dispatch knows whether a silent handset is a problem.
Start a private voice or video call from the roster when a transmission on the open channel is the wrong place for it.
A keypad for the numbers that aren't in the directory — a desk line, a mutual-aid partner, a radio talkgroup.
In gloves, in the dark, in the rain
The handset app is built around one big target and a hardware key. Everything else gets out of the way.
Push to talk
One target, thumb-sized, with the channel and connected count above it.
Channels
Switch groups with the side keys without looking at the screen.
Critical alert
A teammate's man-down takes the screen, with call, locate and message on it.
Emergency countdown
A held key starts the count, so an accidental press can still be cancelled.
Voice call
Full-duplex when the conversation needs both people talking.
Video call
Show the scene when describing it over the radio isn't enough.
Channel chat
Addresses, plate numbers and unit IDs, written down where they won't be misheard.
Contacts
The same roster as the console, with duty status carried through.
Sign in
Company ID and credentials, with server switching for agencies that run their own.
Set up the way the room works
Dispatchers work a console for whole shifts. It should match the desk, the headset and the hands already on it.
Shortcuts
Bind transmit, mute-all and channel navigation to the keys the operator already reaches for. A dispatcher should not have to find a button with a mouse while somebody is talking.
Audio routing
Send one channel to the left ear and another to the right, pick the headset, and keep a separate sound for emergencies.
Appearance
Dark for a night watch floor, light for a bright room, and a text size that survives an eight-hour shift.
Bring the radios with you
Almost nobody replaces a radio fleet in one weekend. Handsets and radios share a channel so the transition can take as long as it needs to.
TETRA and P25, over the standard
Interworking runs through 3GPP IWF, the interface written for this job, rather than a radio taped to a gateway. Calls, identities and talking-party signalling cross intact.
Other fleets over RoIP
Digital and analogue systems that do not speak IWF, DMR among them, connect through a RoIP gateway and appear on the channel as members.
A radio is a member
An LMR endpoint sits in the roster like anyone else. Dispatch sees it, the channel hears it, and nobody has to track which network a given person is on.
Where it runs
A guarding company and a ministry do not have the same answer to where their data sits, so there are three.
Shared cloud
The fastest way on. Hosted in France on European infrastructure, monitored around the clock. Right for teams who want users provisioned this week.
Dedicated instance
Your own instance, isolated from other customers, placed in the region you need. For organisations whose policy is about tenancy rather than geography.
On-premise
The platform inside your own data centre, active-active or active-standby, on your network. Where a tender specifies in-country data residency, this is the answer.
We install and operate deployments ourselves today. Where you would rather work through a local partner, we will bring one in.
What protects the traffic
The parts that can be stated precisely, and one that has to be stated plainly.
Group calls encrypted end to end
Group traffic is encrypted end to end rather than only to the server. Keys are generated, distributed and retired by a key management service built to 3GPP TS 33.180, the specification written for mission-critical encryption.
Identity stays yours
Users authenticate over OpenID Connect against your own identity provider, so accounts, password policy and multi-factor stay where you already manage them.
A record of what was said
PTT, group, video, broadcast and emergency calls can be recorded in real time, and key-material requests are written to external syslog. What is kept, and for how long, is set per deployment.
What we do not claim: DuskLine was founded in 2026 and holds no security certifications yet. We would rather say so here than have it surface during due diligence. An architecture and security overview is available for review on request.
What ships
The console and the handset app, covering the capabilities shown above.
- Voice
- Group and individual push-to-talk, full-duplex voice calls, and video calling from the console or the handset.
- Channels
- Standing groups and temporary incident channels, per-member priority levels, simultaneous select across channels, and mute all.
- Location
- Live member positions, itinerary playback, heatmap overlay, and radial, polygon or corridor geofences.
- Safety events
- Man down, no movement, emergency call, property damage and low battery, each with priority, initiator, timestamp and location.
- Directory
- Duty status, battery level, network state, priority and group membership, searchable and exportable.
- Messaging
- Channel and direct messages, recall recordings and a per-channel call record.
- Endpoints
- Rugged Android handsets from vendors including Hytera, Crosscall and Telo, standard Android from version 12, iOS, a browser-based dispatch console, and LMR endpoints joining channels as members.
- AI agents
- Custom voice and text agents provisioned as channel members, built per customer against your procedures, vocabulary and systems.
- Standards
- 3GPP MCX — MCPTT, MCData and MCVideo over 4G and 5G. Key management to 3GPP TS 33.180. Interworking with TETRA and P25 through 3GPP IWF, other fleets through RoIP.
- Deployment
- Shared cloud hosted in France, a dedicated single-tenant instance in the region you need, or on-premise with active-active or active-standby redundancy.
- Security
- End-to-end encrypted group communications, OpenID Connect authentication against your own identity provider, real-time call recording and external syslog accounting.
- Support
- Around the clock for cloud deployments. Working-day support with any-hour escalation for on-premise, in English, French and Arabic.
- Console setup
- Per-channel audio routing and levels, configurable keyboard shortcuts, light and dark appearance, and server switching for self-hosted deployments.
Working with DuskLine
We are new, and you would rather hear that from us than find it in a search.
Who we are
DuskLine is a communications company founded in Tunisia in 2026, building for the Middle East and Africa. We ship in English, French and Arabic because that is what the region runs on, and we are close enough to be on site when a deployment needs somebody in the room.
Start with a pilot
Instead of a reference list we have not earned yet, take a pilot: a channel with your call signs, your handsets, your network and your dispatchers, for thirty days. If it does not hold up on a real shift, you have lost a month and nothing else.
Support runs around the clock for cloud deployments. On-premise gets support through your working day with escalation at any hour when a service is down, in English, French or Arabic.
Questions we get asked
The ones that come up in every first call, answered before you have to ask them.
Can we keep the radios we already have?
Yes. TETRA and P25 systems interwork through 3GPP IWF, and other digital or analogue fleets connect through a RoIP gateway. Radios appear on the channel as members, so a fleet can move across over months rather than in a weekend.
What is an AI agent on a channel, exactly?
A voice or text agent that holds a seat on a talkgroup like a person does. It hears what is said, answers out loud, and acts on what it heard — opening an event, placing a call, or writing to a system of record. Each one is built for the customer that needs it, against your procedures and your systems.
Where is our data stored?
The shared cloud runs in France. A dedicated instance can be placed in the region you require, and an on-premise deployment keeps everything inside your own data centre. Where a tender specifies in-country hosting, on-premise or a dedicated instance is the answer.
Is DuskLine ISO 27001 certified?
Not yet. The company was founded in 2026 and holds no security certifications at this point. We publish an architecture and security overview instead, and we would rather tell you plainly than let it come up in due diligence.
Is this a proprietary system?
No. DuskLine implements 3GPP MCX — MCPTT, MCData and MCVideo — the same standards written for national mission-critical networks, with key management to 3GPP TS 33.180.
How are group calls encrypted?
End to end, with keys generated and distributed by a key management service built to 3GPP TS 33.180. Group traffic is not decrypted at the server on the way through.
Do we have to replace our identity system?
No. Users authenticate over OpenID Connect against your existing identity provider, so accounts, password policy and multi-factor stay where you manage them today.
What devices does it run on?
Rugged Android handsets from vendors including Hytera, Crosscall and Telo, standard Android phones from version 12, and iOS. Dispatchers work in a browser, with nothing to install.
How is it licensed?
Per user. What it comes to depends on the deployment model and the size of the fleet — tell us your headcount and we will put a figure against it.
Can we try it before committing?
Yes. A thirty-day pilot on your own network, with your own handsets and your own dispatchers.
Put it on a real shift.
We will set up a channel with your call signs, connect a handset and a console, and let your dispatchers run an hour on it.