Kisi Mobile, Wallet, Visitor and Intercom Planning
Kisi supports mobile credentials, physical badges, temporary visitor methods, wallet-based credentials and intercom workflows. The best mix depends on user populations, identity lifecycle, reception procedures, accessibility, privacy and fallback access.
Select the complete system, not one headline feature
Match devices, software, licensing, infrastructure, retention, integrations and support to the operating requirement before finalizing the design.
Define user and visitor populations
Classify employees, contractors, residents, vendors, delivery personnel and unannounced visitors. Define onboarding authority, allowed doors, schedules, expiration, escort and emergency procedures. Include people without compatible phones or corporate wallet enrollment in the fallback design.
Discovery should identify protected areas, users, schedules, response procedures, privacy expectations, existing equipment and the party who will administer the finished system. Product claims only become useful after they are translated into measurable coverage, capacity, availability and response requirements.
- Employee and contractor lifecycle
- Visitor and delivery workflows
- Phone/wallet eligibility
- Fallback and accessibility
Choose credentials and enrollment
Choose mobile, wallet, Kisi Pass, tag, fob, QR or visitor link by assurance, convenience and administrative effort. Document enrollment, replacement, lost-device and revocation workflows. Avoid permanent shared credentials and confirm how temporary access expires automatically.
Coordinate network addressing, PoE or low-voltage power, pathways, environmental ratings, mounting, door or camera interfaces and backup power. Verify exact model compatibility and supported software before ordering; similar product names can conceal different capacity, license or integration limits.
- Credential assurance and convenience
- Enrollment and revocation
- Temporary expiration
- Badge and replacement policy
| Method | Typical user | Planning focus |
|---|---|---|
| Mobile app | Managed recurring user | Enrollment and device lifecycle |
| Wallet badge | Eligible employee | Provisioning and replacement |
| Kisi Pass/card/fob | Physical-credential user | Issuance and revocation |
| QR/link/intercom | Visitor or delivery | Expiration, host and release authority |
Integrate identity, intercom and video
Map SSO, SCIM or directory workflows, host notifications, reception, badge printing and video surveillance integration. For intercom, define who receives calls, after-hours handling, call escalation, privacy and door-release authority. Test audio/video quality over the actual network.
Use named administrators, least privilege and multifactor authentication where supported. Establish backup, update, health-monitoring and escalation ownership. Firmware and software should come from the manufacturer portal after compatibility and release-note review, with rollback or recovery prepared before change.
- SSO/SCIM and directory
- Reception and host notification
- Intercom call routing
- Video and privacy policy
Operate, audit and recover
Review access groups, inactive accounts, visitors, audit exports and administrator roles on a schedule. Test lost phone, expired visitor, offline reader, intercom failure and recovery cases. Keep user data, recordings and audit exports within approved retention and access controls.
Acceptance should test normal use, denied or alarm conditions, loss of network or power, notification, audit history and administrator recovery. Deliver protected configuration records, licenses, serials, diagrams, test evidence, support links and clearly owned exceptions.
- Periodic access review
- Audit and retention
- Lost-device response
- Offline and support procedure
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Discover
Document people, assets, workflows, risks and existing systems.
Design
Select the supported architecture, devices, licenses and integrations.
Install
Stage, label and commission through controlled changes.
Validate
Exercise operating scenarios and deliver lifecycle records.
Information to gather before design
Good decisions are easier when the project team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Operational use cases and response
- Device and software compatibility
- Power, network and physical interfaces
- Licensing, identity and cybersecurity
- Acceptance, support and lifecycle
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Must every user install the Kisi app?
No. Supported physical, wallet and temporary credential options can serve other populations.
Can visitor links be permanent?
They should be time- and scope-limited according to the visitor policy.
Does an intercom automatically grant access?
No. Define who can answer and authorize door release.
Where are current credential and firmware instructions?
Use Kisi’s official documentation and support portals.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Discuss a commercial security project
Tell us about the doors, buildings, users, existing equipment, operational requirements and desired completion date. We will help organize the right discovery and design conversation.