AI Assistant · Platform capability
Talk to your building. Get things done.
The Duall Master AI Assistant lets operators ask the system to do things — onboard a new employee, revoke a lost card, invite a visitor for tomorrow — in plain language, with full preview, confirmation, audit, and role-based authority. Every action runs with the operator's own login and permissions, so the assistant holds no write access of its own and can never exceed what the operator is allowed to do.
Speak English or Tiếng Việt today; Korean rolling out across the assistant's domain vocabulary. The assistant understands your building's terms, maps them to the right action, shows you exactly what will change, and waits for your confirm.
Operator prompt
"Onboard Kim Min-jun in the Marketing department and give them access to Floor 3."
→ Preview shown · operator confirms · 2 records created · audit logged.
What makes it different
Search is table stakes. Action is the line.
Most platforms in this space ship some flavor of natural-language search. Duall Master goes further — the same assistant that answers "how many visitors today?" can also onboard the new hire, revoke the lost card, and invite tomorrow's guest.
Pillar 01
It speaks your building's language.
"Access rules" → access groups. "Block someone" → disable user. "Lost badge" → revoke credential. Domain vocabulary ships for English and Vietnamese today; Korean rolling out.
Pillar 02
It can act, not just answer.
Seven shipped action tools today — onboarding, access changes, visitor invitations, credential revocation. Every action goes through explain → preview → execute.
Pillar 03
It can't go rogue.
The assistant holds no write access of its own. Every action runs with the operator's own login and permissions. High-risk actions require a PIN re-confirmation.
Ask
How many visitors today? Which devices are offline right now? Who entered Floor 3 in the last hour?
Summarize
Incident summaries and shift handoff drafts grounded in permissioned system records.
Find
Find user by name across the tenant. Find zone by location. Find door by partial match.
Investigate
Recent access events, attendance summaries today, parking occupancy, active emergencies.
Disambiguate
When a name matches two people, the assistant asks — it never silently picks.
Stay grounded
Answers come from tool results, not from the model's memory. If we don't have the data, the assistant says so.
The three-mode contract
Every action tool answers the same three questions.
Tap any layer to see how it helps a buyer evaluate the platform.
Signal
Doors, visitors, cameras, intercoms, parking, and devices generate live operational signals instead of isolated alerts.
01Signal
Doors, visitors, cameras, intercoms, parking, and devices generate live operational signals instead of isolated alerts.
02Context
Each signal becomes useful because operator, person, role, site, zone, policy, and related module records are shown together.
03Action
Teams approve, deny, review, escalate, annotate, or link evidence without leaving the command surface.
04Audit
Every decision keeps the who, what, when, why, and related evidence needed for handoff, reporting, and investigation.
Operators always know what the assistant is about to do. Nothing is committed without an explicit confirm — and HIGH-risk actions add a PIN re-auth gate.
Multilingual by design
One assistant. Operator language, native vocabulary.
Operators in different regions run the same workflow in their own language. The vocabulary mapping is shared, so "access rules" and "quy tắc truy cập" both resolve to access groups. Korean domain vocabulary is rolling out next, alongside the wider EN+VI+KO product UI.
→ Maps to disable_user · preview shows scope · operator confirms with PIN.
English
High-riskDisable user An Nguyen Van?
- · Revokes 3 credentials (1 card, 1 face, 1 PIN)
- · Blocks all 12 access points
- · Removes from 4 access groups
Tiếng Việt
Rủi ro caoVô hiệu user An Nguyễn Văn?
- · Thu hồi 3 chứng thực (1 thẻ, 1 khuôn mặt, 1 PIN)
- · Chặn toàn bộ 12 điểm ra vào
- · Gỡ khỏi 4 nhóm quyền
The action catalog
Seven actions shipped today.
We grow this list deliberately — every new action goes through a security review, gets a risk tier, and ships with the same preview / confirm / audit contract.
Each tool is a self-contained capability that can be called by the assistant when the operator's request matches it. The assistant never invents an action — it picks from this catalog.
Standard · operator confirms
Create access group
Create a new group, attach access points, and assign it — in one confirmed step.
Assign user to access group
Add people to a group, with optional start/end dates. Names resolve against your live directory.
Create user
Onboard a person, optionally creating their login account and sending the welcome email.
Create visitor invitation
Schedule a visit with host, purpose, and arrival time. Sends the QR if the guest has email.
Onboard employee (composite)
Creates the user and assigns their groups in one confirm — and aborts cleanly if anything is wrong.
HIGH-risk · confirm with PIN
Revoke credential
PIN requiredRemove one card, face, fingerprint, PIN, or QR. Lists the user's other credentials before confirming.
Disable user
PIN requiredBlock all access for one person across every credential and device — the "they left the company" button.
Roadmap (planned): door unlock with proposal pattern · lock-down · emergency activation · attendance adjustment · shift assignment · custom-per-tenant composites.
Safety + governance
Helpful — but never reckless.
We took the constraints seriously. The assistant is designed so that a perfectly-jailbroken model would still be unable to take an unsanctioned action against your tenant.
Assistive, not autonomous
The assistant never executes a write without a human confirm in the UI.
No standing access
The assistant holds no access of its own — every action runs as the operator who asked.
Your permissions are the authority
The same role and scope rules that govern manual operations govern AI-driven ones.
Every action audited
Both the preview and the execute land in the audit log under the operator's identity.
High-risk needs a PIN
Destructive actions (revoke credential, disable user) require a PIN re-confirmation — being logged in isn't enough.
Data residency enforced
Cloud AI is refused in production sites that require on-premise inference.
Bring your own intelligence
Cloud AI, on-premise AI, or no AI at all.
The assistant is provider-agnostic. Tenants choose their inference posture based on data-residency requirements — and Duall Master refuses to start with a cloud AI in a production tenant that's policy-bound to on-premise.
Cloud
Cloud AI
Default for the operator console. Strongest reasoning for ambiguous requests.
Self-hosted
On-premise AI
For sites that must keep all inference inside the data center.
Sandbox
Test environment
For CI, integration tests, and rehearsal environments.
Platform-wide reach
One assistant. Every module.
The AI Assistant isn't a module — it's a capability layer that already touches access control, visitor management, identity, attendance, parking, video, and intercom. New modules inherit it automatically.
Next step
See the AI Assistant in action
Walk through the seven action tools and the explain → preview → execute contract on a sandbox tenant with the Duall Master team — your own questions, your own building vocabulary.