Book a Walkthrough

Unique visitors, not tickets.

For service branches: a second visit looks like a new one. See each visitor's journey, wait and mood.

For service branches in government and banking that need to know when a customer comes back for the same service. A Pulses Vision device on the ceiling over the waiting hall, the counters and the back office shows each visitor's journey, wait and mood. Pulses CX shows the same visitor across visits and branches, mood per zone tied to the wait that caused it, and the unhappy few by counter, service and wait. Pulses Ops tells the branch supervisor on WhatsApp, Teams, SMS or email when a wait nears its target. Anonymous Unique FaceID is derived on the device, can't be turned back into a picture and holds no personal data. Processing happens on the device and only anonymous metadata leaves; the platform runs in your own tenant or fully on-premise.

Pulses OS Second visits and the back office screen: visitors back for the same service this week, by branch, and back-office presence and flow room by room

From the hall to your team.

  1. 01

    Pulses Vision above halls and counters

    A Pulses Vision device on the ceiling, over the waiting hall, the counters and the back office.

  2. 02

    Unique visitors, mood and waits

    The same visitor, recognised across visits and branches, even back for the same service. Mood per zone, tied to the wait that caused it, and the unhappy few by counter, service and wait. Presence and flow in the back office, not a score for any person. Anonymous Unique FaceID is made on the device, can't be turned back into a picture, and holds no personal data.

  3. 03

    Told before the SLA breaks

    When a wait nears its target, the branch supervisor is told on WhatsApp, Teams, SMS or email, the channels the team already answers.

By design Processing happens on the deviceOnly anonymous metadata leavesNo identity is keptRuns in your own tenant or fully on-premise

The hall, on three screens.

Pulses OS Second visits and the back office screen: visitors back for the same service this week, by branch, and back-office presence and flow room by room 01 / 03

Second Visits

The same visitor back for the same service, even at another branch, and the back office room by room.

Pulses OS Mood and wait screen: mood per zone tied to the wait, unhappy visits by how long they waited, and the unhappy few by counter, service and wait 02 / 03

Mood and Wait

The unhappy few, by counter and wait: mood per zone, tied to how long people waited.

Pulses OS Before the SLA screen: each service's wait against its target, who is told, on which channel, and when the alert was acknowledged 03 / 03

Before the SLA

Each service's wait against its target, who was told, and when they acknowledged.

Pulses OS Second visits and the back office screen: visitors back for the same service this week, by branch, and back-office presence and flow room by roomPulses OS Mood and wait screen: mood per zone tied to the wait, unhappy visits by how long they waited, and the unhappy few by counter, service and waitPulses OS Before the SLA screen: each service's wait against its target, who is told, on which channel, and when the alert was acknowledged

Inside the service hall.

Transcript

In a busy service hall, each visitor's journey is their own. Yet a second visit often looks like a new one. Pulses. AI for the physical world. A Pulses Vision device on the ceiling understands unique visitors, mood and waiting times. The same visitor is recognised again, even at another branch. Anonymous Unique FaceID: made on the device, with no personal data. Find the unhappy few, by counter, service and queue time. When waiting time nears its target, a supervisor is told. The back office is no longer a black hole. Over one hundred and fifty million journeys counted, across Pulses deployments. Designed and made in the UAE. See the full showcase.

Take it to your team.

Questions from branch teams

How can I tell whether customers come back for the same problem?

Pulses shows the same visitor back for the same service, even at another branch, as one journey rather than a new ticket. Pulses CX lists these second visits by service and branch, so the team can see which services bring customers back. It works through Anonymous Unique FaceID, derived on the Pulses Vision device; no identity is kept and only anonymous metadata leaves the device.

Why are some customers unhappy when the overall happiness score is high?

An average hides the few. Pulses CX reads mood per zone with no surveys and ties it to the wait that caused it, so you see the unhappy few by counter, service and wait. A branch with a good overall score can still show one counter where long waits and low mood meet. The team sees that counter and that service, not a score for any person.

Can AI alert staff before a queue breaches its service level?

When a wait nears its target, Pulses Ops tells the branch supervisor on WhatsApp, Teams, SMS or email, the channels the team already answers. Pulses OS shows each service's wait against its target, who was told and when they acknowledged it, so the supervisor can act while customers are still in the hall.

Is there an on-premise AI vision platform that keeps all data inside the UAE?

Pulses runs in your own tenant or fully on-premise on the Pulses Appliance, so where the data sits follows your hosting choice. Either way, processing happens on the Pulses Vision device and only anonymous metadata leaves it: no image leaves, and no identity is kept. Your IT and data teams set the hosting shape with ours during the project.

Walk your branch with us.

A real visitor-by-visitor journey, read while they're in the hall.

How it works in other industries