How a tap travels.
A physical point carries context: where it is, who owns it and what it is for. A tap opens the right next step with no app to install. The platform records what happened; each product decides what it means. We connect; we do not replace.
Where a tap starts: a phone, a tag and a place.Six steps, the same in every product.
The blue step is the tap. The steps around it are what make a tap trustworthy: context before, a record after.
A physical point
A sticker, a stand, a puck or a card is placed where the service belongs: a table, a classroom door, a gate, a help point.
Tap or scan
The phone opens the address carried by the tag over NFC, or the QR code printed on most tags. Nothing to install.
Context
tap2 resolves the tag to its organisation, its place and its purpose, and applies the checks that product needs: who, where, when.
Record
The tap is recorded once, with its time and place. Where a product allows corrections, they are added on top, with who decided and why.
Workflow
The product takes over: a guard sees a valid pass, a roster updates, a request reaches a waiter, an alert reaches the site’s response team, feedback becomes a case.
Visibility
Live boards show what is happening now. Reports and exports show what happened.
Your place, your systems, and tap2 in between.
Four kinds of point, one pattern.
Most points carry the QR code on the same surface, so a phone without NFC still works; attendance checkpoints can be NFC-only.
Sticker
For windows, tables, packaging and doors. The quickest way to put a place online.
tap2link · tap2say · tap2shopStand or puck
For counters and tables, and for places where the tag should be seen before it is tapped.
tap2link · tap2say · tap2visitCard or badge
Carried by a person rather than fixed to a place: the business card, the event badge.
tap2idFixed checkpoint
Rugged, fixed to a wall, a pillar or scaffolding. Designed to support secure (NTAG 424 DNA) tags where a deployment requires them.
tap2work · tap2attend · tap2alertWhat the built products share, and where they differ.
Arabic and English
Right-to-left Arabic and English in tap2work, tap2attend (also German), the tap2say form and the tap2alert console.
Multi-tenant, multi-location
One organisation, many sites, with roles and permissions per site and per person.
Records that are not rewritten
In the attendance and presence products, every tap is recorded once. Corrections are added on top, with who decided and why.
No app to install
People use the phone they already have. A tap or a scan opens the right page in the browser. Staff and students sign in with an access code or a one-time code.
Boards, reports, exports
Live boards for now; reports and exports for what happened: PDF, Excel and CSV in tap2work, PDF and Excel in tap2say, CSV in tap2alert.
Role-based access
Admins, dispatchers, managers, professors and guards each see what their role needs.
Stated carefully, confirmed in writing.
Fixed tags carry no personal data. A fixed tag identifies a place and its purpose; a tap2id card or badge links to the profile of the person who carries it. The checks happen on the server, against the rules each organisation sets.
Where data is hosted is stated per product, in writing, before any agreement; dedicated environments are on the roadmap. Integrations with sign-on, student and HR systems, and with public control rooms, are scoped per project.
Secure tags where required. tap2 is designed to support secure (NTAG 424 DNA) tags where a deployment requires them.
tap2alert complements emergency numbers and fire-alarm systems. It does not replace them. Anyone in danger should also call the local emergency number.
The physical world is your new digital interface.
Any physical touchpoint can become a digital service gateway. Start with one place, and grow from there.