0
How many come in, how many reach the counter.
By the hour and by the day, with staff separated from customers. The gap between those who came in and those who were served is demand the branch didn’t meet.
Vizor for banks and branches
The customer who walks out of the queue doesn’t show up in any report.
We count how many customers come into the branch on the cameras you already have, how many reach the counter and how long they wait until then. You see the hours when the queue builds up, how many counters were open and how many left without being served. No new hardware. We only recognise the employees you register; customers remain silhouettes, with no name and no profile.
Branches, agencies and service centres · across MoldovaCentral Branch · cam 1 · top viewlive simulation
walk-ins today0
served0
left unserved0
on the floor0
customerservedleft unservedstaff, not counted
What Vizor sees in a branch
The queue system counts tickets. Not the people who gave up waiting.
A customer who sees the queue from the door and leaves never takes a ticket. One who takes a ticket and gives up after twenty minutes stays an uncalled number. Neither shows up as a problem in the branch report. Vizor counts them both.
Entries vs served
9 customers waiting · 2 counters open
How long a customer waits to reach the counter.
Above the threshold, the branch manager gets a phone alert with the time and the number of people in the hall. Ten minutes at the cash desk means a customer who comes back tomorrow, or goes to another bank.
Where people stand and what they bypass.
The waiting hall, the cash desk, the consultants’ offices, the payment terminals. A terminal nobody walks past takes no payments off the counters.
Branch dashboard
Queues, counters, waiting. For every branch.
The dashboard layout from the real installation. Switch branches and go through Dashboard, Alerts, Analytics and Reports. The numbers are illustrative; in an installation they come from the branch’s cameras.
app.vizor.md · bank · dashboard
V
Vizor
On the phone
The same numbers, with the branch manager.
In a branch, the decision is made in the next minute: who opens another counter. The app is for that minute.
- The alert reaches the lock screen, with the location, zone and minute.
- Entries, customers served and waiting time, for the current day.
- The evening report takes a minute to read, at closing.
- The day’s numbers reach your phone, without customer names.
Analysis examples · banks
Three scenarios, three decisions.
Our first real installations, in production, are in pharmacies in Moldova, where customers also wait at a counter. We don’t yet have a publicly named bank client, so the scenarios below are modeled on the patterns measured there.
⚠ Modeled scenariosThese are not results reported by clients. We measure your numbers in the pilot.
Modeled scenarioBranch · city centre
In the first days of the month, the queue built up at the same hour.
- Problem
- Customers complained about queues in the first working days of the month, but the queue system only showed the people who had taken a ticket.
- What it showed
- Between 10 and 13, 2 of 6 counters were open, and up to 14 people waited in the hall. One customer in four left before reaching the counter.
- Decision
- In the first five days of the month, two consultancy counters switch to cash operations between 10 and 13. The same number of people.
+16 ppcustomers served between 10 and 13, in the first days of the month
customers served, by hour · before / after%
Modeled scenarioBranch · residential area
The payment terminal stood behind a pillar.
- Problem
- Simple payments took up the cash desk, even though the branch had a payment terminal in the hall.
- What it showed
- 9 in 100 customers reached the terminal. It stood behind a pillar, out of sight from the entrance, and the path led straight to the queue-ticket machine.
- Decision
- Terminal moved next to the entrance, with a sign. The effect measured over two weeks before and two weeks after.
×2.3customers using the payment terminal
of 100 customers, how many reach the terminalbefore / after
Modeled scenarioBranch · retail customers
The consultants sat in offices. The customers waited in the hall.
- Problem
- Customers who came for a loan stood in the same queue as those at the cash desk, and some left before reaching a consultant.
- What it showed
- 58% of the waiting time was spent in the cash-desk hall, in zone C. The consultants sat in the back offices, in zone E, where customers rarely got.
- Decision
- A consultant in the hall at peak hours, who finds out why the customer came and sends them straight to the right office.
−30%average waiting time, after three weeks
where people wait · time spentA – F
Our reference installation
The first location measured daily, with manual counting in parallel and an automatic report every evening. The method is the same for a bank branch; only the numbers differ.
How it works in a branch
One day per branch. Without closing the counters.
01
Your current cameras
A branch already has cameras that see the entrance, the hall and the counters. We read their image without changing the bank’s surveillance system.
zero investment02
Zones, drawn together
We mark the hall, the cash desk, the consultants’ offices and the terminals. Staff are taken out of the count, so they aren’t counted as customers.
one day03
Numbers, not identities
Images can be processed on a server installed in the bank; the report gets numbers. Customers are not identified.
data minimization04
Linked to the queue tickets
If the queue system exports tickets by the hour, we put them next to the counted entries: you see how many left without a ticket and how many left with the ticket in hand.
entry → counterPrivacy in a bank
We measure the hall, not the customers.
The system produces numbers by zone and by hour. Employees you register, with notice to them, are recognised by face so they aren’t counted as customers. No identity is built for customers, and nothing is read from screens or documents. Images can stay on a bank server.
Bank pilot
Three branches. Three months. Numbers checked together.
A large city-centre branch, a neighbourhood one and, if you have one, a branch in a shopping centre. In week three we count by hand in parallel, at hours you choose. The pilot can be stopped at any time, with no penalty.
New cameras
We work on your existing cameras. Where coverage falls short, we fill the gap.
Your staff’s time
Installation takes one day and doesn’t stop service. We draw the zones together, in an hour.
Long contract
Three months. Stop at any time. Your branches’ numbers stay yours.
Access to the bank’s systems
We don’t connect to the core banking system. For the queue tickets, a daily file is enough.
Calculator · what more customers served are worth
Every customer who walks out of the queue is a lost transaction, product or customer. Here we calculate conservatively, with whatever figure you choose. A mathematical estimate, not a promise.
Extra revenue per month90,000 MDL
extra customers served / month600
per year1,080,000 MDL
Calculation: visitors × days × percentage points × average revenue × branches.
Check my branch →Read also
Related pages.
Video analytics for pharmacies
How many come in, how many are served at the counter and how long they wait. Real installations in pharmacies in Moldova.
Read →Video analytics on existing cameras
What video analytics measures, which cameras it works on, what it costs and how accurate it is.
Read →Law 195/2024 and video cameras
What Moldova’s new personal data law requires from a business with cameras: legal basis, notice, records.
Read →Video cameras in the workplace
What is allowed, where it is forbidden, what the sign must say and how long footage is kept, under Law 195/2024.
Read →Frequently asked questions
Questions from banks.
What does Vizor measure in a bank branch?
How many customers come in, by the hour; how many reach the counter and how long they wait until then; how many counters were open when the queue formed; how many left before being served. Plus attention by zone: the hall, the cash desk, the consultants’ offices, the payment terminals. All on the cameras the branch already has.
Does it use the bank’s security cameras?
Yes, the ones that see the entrance, the hall and the counters. We read their image without changing the surveillance system and without stopping its recording. Where coverage falls short, we add one or two ordinary cameras.
Does footage leave the bank?
There’s no need. Images can be processed on a server installed in the bank, and only numbers go to the dashboard: how many came in, how many were served, how long they waited. The Vizor-server option remains possible where the bank’s policy allows it.
Do you identify the bank’s customers?
No. Customers remain counted silhouettes, with no name, no profile and no history. We recognise by face only the employees you register yourself, with notice to them, so they aren’t counted as customers. We don’t read screens, documents or amounts.
Can it be linked to the queue-ticket system?
Yes, if the system exports the tickets issued and called by the hour. We put them next to the counted entries, and you see how many left without a ticket and how many took a ticket but never reached the counter. If a direct export isn’t possible, a daily file is enough.
What does Law 195/2024 require of a bank with cameras?
The same principles as for any operator with cameras: a written purpose, a legal basis, notice to customers and employees, and a retention period for the footage. Counting produces aggregate numbers from which no one can be identified. We prepare the technical part and the notice text; for the bank’s specific situation, ask the bank’s lawyer.
How long does installation take?
One day per branch, without closing the counters. We draw the zones together, in an hour.
How do we start?
With a three-month paid pilot at three locations, which you can stop at any time, with no penalty.
Contact
Show us a branch. We’ll tell you what we can measure.
We don’t ask for an hour-long meeting. You pick a branch, we look at the existing cameras and the hall layout, and we reply within 24 hours, in writing.
What happens next
Three steps, no pressure.
1We reply within 24 hours, in writing, with what can be measured at your location.
2Thirty minutes on a single location: together we look at what your existing cameras cover.
3If it makes sense for you, we propose a pilot on three locations. You can stop it at any time, with no penalty.