# White-Label AI Self-Service HR Portal (Ask-HR Chatbot) - Tool: AI Implementations - Last updated: June 2026 ## TL;DR Three paths: subscribe to Moveworks or Leena AI (enterprise quote-based, no true WL reseller tier), hire RapidDev for $13K–$25K to build a multi-tenant Ask-HR chatbot with real HRIS integration, or DIY on Lovable for $25 plus ~$30 in API credits for a working FAQ-over-handbook demo in one weekend. The decisive variable: a pure FAQ chatbot over a handbook is a genuine weekend Lovable build. The moment you need live PTO balances, paycheck history, or benefits enrollment via real HRIS APIs, the hire-agency path wins. ## Frequently asked questions ### How much does it cost to build a white-label Ask-HR chatbot? A FAQ-only chatbot over a handbook — multi-tenant, with sensitive-topic escalation and an HR admin panel — runs $13,000–$25,000 at RapidDev's standard band over 6–10 weeks. Adding live HRIS integration (BambooHR, Rippling, Gusto OAuth for PTO balance and paycheck history) adds $5,000–$15,000 and 6–8 additional weeks depending on which HRIS you are integrating with. Workday integration adds more — typically $10,000–$20,000 — due to Workday's more complex API and authentication model. ### How long does it take to ship this? An FAQ-only chatbot with multi-tenant handbook RAG can ship in 6–10 weeks. A full HRIS-integrated Ask-HR portal with live PTO balance, sensitive-topic escalation, and Slack-native delivery takes 12–18 weeks. The scoping decision that most affects timeline is which HRIS(s) you integrate with — BambooHR is 1–2 weeks of integration work; Workday is 4–6 weeks. ### Can the chatbot answer questions about an employee's personal PTO balance or paycheck? Only with HRIS integration. A language model should never infer or estimate PTO balances from general knowledge — that data must come directly from the HRIS via an authenticated API call. The architecture uses OAuth to make an authenticated call to the specific employee's HRIS record and format the result into a conversational response. Without HRIS integration, the chatbot should respond: 'To check your current PTO balance, log in directly to [HRIS name] — I do not have access to your personal account information.' ### Does an AI HR chatbot need to comply with the EU AI Act? Yes for two distinct requirements. Article 50 (chatbot-is-AI disclosure) applies to any conversational AI system from August 2, 2026 — you must clearly tell EU-based employees they are talking to an AI. Annex III (workers-management high-risk) does NOT apply to a pure FAQ chatbot, but it does apply if the chatbot begins approving PTO requests, making leave decisions, or influencing employment decisions. The architecture must enforce a hard line: informational answers are fine; automated approvals are Annex III high-risk and require human oversight built in. ### Can RapidDev build this for my company? Yes. RapidDev has shipped 600+ applications including HR portals, HRIS integrations, and multi-tenant SaaS platforms. We recommend scoping the specific HRIS integration target and the sensitive-topic escalation workflow with your HR client before starting the build — both have more nuance than they appear in the spec stage. Book a free 30-minute consultation at rapidevelopers.com to discuss your target market (IT-services agency, PEO, or standalone HR-tech) and the HRIS ecosystem you are targeting. ### How do sensitive questions get handled — does the AI answer them? No. The architecture pre-screens every question with a sensitive-topic classifier before any handbook search or LLM call. If the question mentions harassment, discrimination, hostile work environment, termination, mental health crisis, or legal threats, the chatbot immediately responds with the escalation message and creates a ticket in the HR team's queue. The LLM never attempts to answer sensitive questions. This is both an ethical decision and a liability protection — an AI's response to a harassment disclosure or a mental-health crisis cannot satisfy the duty of care that a human HR representative can. ### What makes this different from a simple ChatGPT wrapper over a PDF? Four things: (1) per-tenant handbook isolation — each company's handbook is stored separately in a row-level-secured table, so Company A's employees can never receive answers from Company B's handbook; (2) sensitive-topic classification that routes away from the LLM entirely for any question involving harassment, mental health, or legal matters; (3) HRIS integration for live data retrieval rather than hallucinated answers about personal account information; (4) a fallback instruction that tells the LLM to acknowledge when it cannot find an answer in the handbook, rather than generating a plausible-sounding but potentially wrong policy explanation. ### Does the employer have access to read employee conversation logs? By design, the employer HR admin has access to aggregate analytics (question categories by count, handbook gaps, escalation rates) but not to individual employee conversation content. The only employee conversation content visible to HR is: (1) conversations that were escalated as sensitive (visible to HR because HR needs to respond); (2) conversations that the employee explicitly shared with HR as context. This design choice protects employee trust in the chatbot — employees who believe their manager reads their HR questions will not ask honest ones. --- Source: https://www.rapidevelopers.com/ai-implementation/ai-driven-self-service-hr-portal-ai-white-label © RapidDev — https://www.rapidevelopers.com/ai-implementation/ai-driven-self-service-hr-portal-ai-white-label