ZapHRMS • Zap Assistant

Ask your
HRMS.

Not AI for the sake of AI. Zap Assistant helps users find and work with workforce information conversationally — on top of your HR data, with your permissions.

We introduce it after the core platform — because AI should extend a solid HRMS, not replace it.

Natural queriesPermission-awareAction where supported
◆Zap AssistantDEMO
Zap Assistant: Try — “Who is absent today?” or “Show employees whose probation ends this month.”
Positioning

AI that works
with your HRMS.

Zap Assistant is placed after you understand the platform — it’s an accelerant, not the product.

Find quickly

Locate employees, attendance, leave, documents by asking — not hunting through menus.

Respects permissions

Answers are scoped to the user’s role and tenant — same controls as the rest of the platform.

Do, not just show

Where supported, the assistant can navigate or trigger the underlying workflow — not a chatbot façade.

What we don’t claim: Generic “AI-powered” buzzwords, fake automation demos, or data beyond your tenant. Examples above are only capabilities actually supported.

Example interactions

You
Who is absent today?
Zap Assistant → “Today, 6 people are marked absent. 3 on approved leave, 2 not checked in, 1 on shift off. Want the list?”
You
Show employees whose probation ends this month.
Zap Assistant → “12 employees have probation ending in August 2026. By department or manager?”
Integration, not isolation
The assistant reads the same people/time/payroll data you already see in screenshots — dashboard.webp, people.webp, payroll-dashboard.webp — not a separate AI store. If a user can’t see a field in the product, they can’t ask it via assistant.
Dashboard People
Policy RAG • Knowledge Base

Ask policies. Get answers
from your documents.

Upload company policies — leave_policy, handbooks, compliance docs — to your tenant’s knowledge base. Zap Assistant then answers employee questions grounded in your documents via RAG, not generic AI.

1 — Upload document

Service Employee • Document type leave_policy • Choose file → Upload document. Accepted: PDF, DOCX, TXT, HTML, MD, MARKDOWN, ZIP, PNG, JPG, JPEG, WEBP. Tenant-isolated: employee-api • 0 documents → becomes searchable knowledge.

2 — Ask in chat

Employees ask in natural language — “What’s my leave_policy for sick leave?” — and get grounded answers. Streaming responses, permission-aware, no cross-tenant leakage.

RAG, not hallucination

Retrieval-Augmented Generation: chunks your policy docs, retrieves relevant passages, then generates answer with context. If not in docs, assistant says so.

How it works
Documents → chunk → embed → tenant KB → query → retrieve → generate. Knowledge stays in your tenant. Upload via Documents modal; chat via Zap Assistant dock on any page (e.g., My Attendance).
Tenant KBGroundedCitations readyStreaming
Documents — Policy upload • leave_policy
Policy document upload — Service Employee, Document type leave_policy, Choose file, Upload document
Knowledge base • Upload policy docReal UI • 59KB WebP

Upload to employee-api knowledge base (right) → ask via Zap Assistant dock — RAG-grounded, tenant-isolated.

See Zap Assistant with your data.

Book a short walkthrough — we’ll demo the assistant on an anonymised dataset, not a scripted video.

Book a Demo →Explore Platform