Branch Queue and Footfall Analytics
Turn existing branch CCTV into anonymous counts of footfall, queue length and counter wait times, so branch and regional managers can plan staffing and act on long queues.
- Capability:
- Computer Vision
- Industry:
- Banking
Who it is for
- Head of Branch Banking
- Regional Branch Manager
- Branch Operations Excellence Lead
- Chief Information Security Officer
The problem
Branch managers know their busy days, but rarely have data on how long customers queue at cash counters, how footfall shifts across the month or which branches are short-staffed at pension and salary peaks. Token systems record service time only once a ticket is issued, and many customers never take one.
No measure of real waiting time
Queue management systems miss walk-ins who wait without a token, and nothing records customers who leave before being served.
Staffing based on habit
Counter staffing follows old rosters rather than observed demand by hour, day and month-end peaks.
CCTV used only after incidents
Branch cameras record continuously, but the footage is reviewed only when there is a security event.
Privacy concerns block analytics
Banks rightly hesitate to run video analytics that could identify customers or monitor individual employees.
What we build
We build an edge analytics service that reads the video streams your branch cameras already produce and outputs only anonymous counts. A detection model counts people entering, estimates queue length in defined zones such as the cash counter, passbook printer and enquiry desk, and derives approximate wait times from queue movement. No faces are recognised, no identities are stored and video does not leave the branch network; only aggregated numbers reach a central dashboard. Regional managers see footfall and queue patterns by branch and hour, and branch managers get alerts when a queue passes a threshold they set, so they can open another counter.
- People counting at entrances from existing CCTV, processed on an edge device in the branch
- Zone-based queue length and wait-time estimates for cash, enquiry and service counters
- Counter open or closed status from zone occupancy, without identifying staff
- Configurable queue alerts to branch managers by app or SMS
- Hourly, daily and month-end demand patterns across branches for rostering
- Optional after-hours ATM lobby occupancy alerts for the security team
How it works
- 01Map the branchFor each camera we mark entry lines and queue zones with the branch team, and record which areas are excluded.
- 02Process video on siteAn edge device reads camera streams over the branch network and runs detection without storing video.
- 03Count and estimatePeople crossing entry lines and standing in queue zones are counted, and wait times are estimated from queue movement.
- 04Check thresholdsWhen a queue or wait estimate passes the branch threshold, an alert goes to the branch manager.
- 05Branch manager actsThe manager opens a counter or redirects customers, and marks the alert as useful or not.
- 06Plan centrallyAggregated counts feed regional dashboards and staffing plans.
Architecture
- Cameras and network
- Existing IP cameras or NVR streams over RTSP
- Isolated branch network segment for the edge device
- Edge processing
- Person detection model on an edge device
- Zone and line configuration per camera
- Queue length and wait-time estimator
- In-memory processing with no video storage
- Alerts
- Threshold engine per branch and zone
- Branch manager notifications by app or SMS
- Central reporting
- Aggregated metrics store
- Regional and branch dashboards
- Device health and model monitoring
- Governance
- Privacy configuration register
- Customer notice and signage templates
Inputs and outputs
Inputs
- Video streams from existing branch IP cameras or NVRs
- Branch layout and counter map
- Counter opening hours and staffing rosters
- Queue management token data, where available
- Alert thresholds set by branch and regional managers
Outputs
- Hourly footfall counts per branch
- Queue length and estimated wait time per zone
- Queue alerts and manager responses
- Demand patterns for staffing and rostering
- Device and data-quality health reports
Where people stay in control
Branch managers decide how to respond to every alert, and regional teams decide staffing changes from the trends. People set and approve zone layouts and thresholds, and any change to what the cameras are used for goes through the bank's information security review.
Integrations
- Branch CCTV and NVR systems
- Queue management or token system
- HRMS or rostering tool
- BI dashboard tools such as Power BI
- Bank SMS gateway or internal messaging app for alerts
Guardrails
- No face recognition, identity matching or individual tracking
- Video processed in memory on site; only counts leave the branch
- Strong room, locker area and staff-only zones excluded by configuration
- No metrics on individual employee productivity
- Branch notice telling customers that cameras support anonymous queue counts
Compliance notes
- Designed for data minimisation under the DPDP Act 2023: no identification, no video export and aggregate output only.
- Edge devices are managed under the bank's IT governance and information security controls.
A typical pilot
Duration: 4 weeks
Two or three branches with different footfall profiles, using existing cameras, with counts checked against manual observation on selected days.
Deliverables
- 01Camera and zone mapping for the pilot branches
- 02Edge devices running anonymous counting
- 03Branch and regional dashboard
- 04Accuracy report against manual counts
- 05Roll-out plan with hardware and cost per branch
What we measure
- Footfall count accuracy
- Automated entry counts compared with manual tallies over sampled hours.
- Queue length estimate accuracy
- Estimates compared with observed queue lengths at set intervals.
- Alert usefulness
- Branch managers mark each alert as useful, too early or not needed.
- Edge device reliability
- Uptime and stream availability logged per device.
FAQs
01Do you use face recognition?
No. The system detects that a person is present and counts them, without recognising faces or linking detections to identities. Nothing that could identify a customer is stored.
02Do we need new cameras?
Usually not. Most branch IP cameras are adequate if they cover the entrance and counter areas. During setup we assess each camera's angle and resolution and suggest repositioning where a zone is not visible.
03Are staff monitored?
No. We report counter open or closed status from zone occupancy, never individual identity, attendance or productivity. This is fixed in configuration and recorded in the privacy register.
04What hardware is needed?
A small edge device per branch, connected to the camera network. The specification depends on the number of cameras and is confirmed during the pilot.
Related use cases
- Banking
Cheque Image and Signature Mismatch Flagging
Compare inward CTS cheque images with specimen signatures, mandates and Positive Pay data, and rank cheques by risk so verification officers look first where it matters.
- Banking
Multilingual Voice Agent for Banking Service Requests
An inbound voice agent that authenticates callers and handles card blocking, statements, cheque books and status queries in Hindi, Hinglish and regional languages, with clean handover.
- Banking
Customer Complaint Triage and Routing
Classify complaints from email, branches, social media and RBI CMS, spot urgent cases such as unauthorised transactions, route them to resolver teams and draft acknowledgements.

Founded by Akhilesh Mittal. 8 years building a security platform for a New Zealand company. IIT ISM Dhanbad and IMT Ghaziabad. Builds production agentic AI.
Pick one banking process and test it with evidence
Book a discovery call to choose a narrow pilot, from KYC file checks to voice-agent red-teaming, and see measured results on your own documents before any wider roll-out.