Cognivision by corteXolutions
Your cameras record.Nobody watches.
We read the streams in the store and send an alert to the nearest colleague: a customer waiting at the counter with nobody near, a queue building, a busy zone left uncovered. Anonymous positions only. No face images stored.
- Your existing cameras, checked first
- Processed inside the store
- Alerts on staff phones
Cognivision, nowwaiting 0:00
Customer at the consult desk, nobody nearby.
Nearest free colleague: main floor.
rule: waiting > 90 s, no staff within 3 m
Colleague is on the way. Greeting time is logged for the weekly report.
A customer who waits, gives up and leaves leaves no trace in the till.
- Mystery shoppers sample a few hours a month.The other 300 opening hours are a guess.
- Reports arrive after the fact.Footfall dashboards tell the ops director what went wrong last week, not the staff what to do now.
- The cameras are already there.Recording around the clock for security, and watched only after something is stolen.
From the camera to the right person, in seconds.
No new app for customers, nothing for staff to learn beyond a notification.
- Step 1
Connect your cameras
A small device in the store reads the streams your CCTV already records. We check streams and angles before the pilot and tell you which ones work.
- Step 2
Anonymous positions
The device sees visitors and staff as moving dots. No faces, no images kept, no identity.
- Step 3
Alerts to staff
When a rule is broken, the nearest colleague gets a notification on their phone or the store tablet.
- Step 4
Weekly floor report
Ops sees time-to-greet, waits, walk-outs and footfall per store, compared week on week.
Alerts staff act on, not dashboards nobody opens.
Rules are set per store and per zone. Thresholds shown are examples.
Alerts
Unattended customer
Someone lingers at a counter or display while no staff member is within reach.
waiting > 90 s
no staff within 3 mQueue building
Call a second colleague to the till before people put the product down and leave.
queue > 3 people
or wait > 4 minZone uncovered
Footfall in a zone is up and its assigned colleague is elsewhere.
4+ visitors in zone
0 staff for 2 min
Reports, included
Time to greet
How fast each visitor is approached, per store, hour and zone. The number mystery shoppers estimate, measured every day.
Footfall and conversion
Visitors in, against tickets out. Combine counts with your POS data to see conversion by hour and store.
Heatmaps and dwell
Where people stop, and for how long, for layout and staffing decisions.
Anonymous by design.
The store keeps almost nothing: positions and counts. Video is analysed on a device in the store and does not leave it.
- Forgotten after the visit. A visitor's track ends when they leave. We do not recognise returning customers.
- About customers, not staff scores. Alerts are about serving visitors. We do not rank or monitor individual employees.
- Paperwork included. Your DPO gets our impact-assessment template and in-store notice text before install. Check the setup with your DPO and national authority.
Kept
- Anonymous positions on the floor plan
- Counts per zone and hour
- Alert times and greeting times
Never stored
- Face images or face templates
- Video sent to us or to a cloud
- Who a visitor is, or whether they came before
- Scores for individual employees
The weekly floor report, before you commit.
Open the demo to see alerts, rules and the report on a sample store. Positions are simulated; nothing is recorded.
| Zone | Visitors | Time to greet | Walk-outs |
|---|---|---|---|
| Main counter | 412 | 0:38 | 6 |
| Display A | 268 | 1:12 | 9 |
| Consult desk | 97 | 2:40 | 14 |
Consult desk: slowest greet of the week. Staff coverage is the gap, not footfall.
One store. Four weeks. Measured.
We install in one of your stores, run alerts for staff, and show you the before and after on time-to-greet, waits and walk-outs. You decide on the other stores with the numbers.
- Week 0
Camera check and install
A few hours, outside opening time.
- Week 1
Silent baseline
We measure, nobody gets alerts.
- Weeks 2 to 4
Alerts on
Alerts on for staff. Rules tuned with the store manager.
- Review
Before and after
Report by zone, walked through with your ops team.
Questions
Do we need new cameras?
Often not, but we do not assume it. We check your camera streams and angles before the pilot and tell you which ones work and which need adjusting.
What about GDPR?
We keep only anonymous positions and counts, processed in the store. Your DPO gets our impact-assessment template before install. Check the setup with your DPO and national authority.
Will staff feel watched?
Alerts are about customers waiting, not about who did what. There are no per-employee scores. We recommend introducing it to the team as a tool that sends help where it is needed.
How do staff get alerts?
On their phones or a store tablet. We agree the channel with you during setup.
What does it cost?
A monthly fee per store, agreed after the pilot once you have seen the numbers. Pilot terms are set per chain.