Customer AI vs Employee AI — same platform, different boundaries
· 2 min read
Customer AI and Employee AI share Qefro’s workspace technology — but they differ in audience, channels, identity, and what knowledge is safe to expose.
Side-by-side
| Dimension | Customer AI | Employee AI |
|---|---|---|
| Audience | Visitors, shoppers, ticket askers | Organization members |
| Channels | Website widget, WhatsApp | Internal Portal |
| Auth | Widget token; optional identify() | Session JWT + Teams / RBAC |
| Knowledge | Customer-safe FAQs and policies | Internal runbooks and HR/IT |
| Risk if mixed | Internal docs leak publicly | Unnecessary customer tools on staff chat |
Full concept page: Customer AI vs Employee AI.
Configure once, deploy twice
In the Admin Console you:
- Create separate workspaces for Support vs HR/IT.
- Ingest the right corpus into each.
- Bind the widget / WhatsApp to Support.
- Grant portal Members access to internal workspaces via Teams.
That is the “configure once, deploy everywhere” model without forcing a single shared index.
Where to go next
- Customer path: Customer AI → Website Widget → WhatsApp
- Employee path: Employee AI → Internal Portal → RBAC
- Guides: Build AI Customer Support, Create Employee AI