The answer is in the handbook. Now it’s in the chat.
Connect your SOPs, policies and docs. Staff ask in plain language on their phone; Gyaany answers and shows the source. New hires ramp faster; your ops team stops repeating itself.
The handbook provides 12 days of casual leave per calendar year. Requests should be submitted to the reporting manager before the leave date.1
Staff stop waiting for someone to find the document.
From scattered SOPs to one source of truth.
A space for every department
Keep Operations, HR, Training and Client Precedents separate, with access granted by role or person.
Answers for staff on the move
Outlet and field teams get a simple mobile view with no access to model or knowledge controls.
Access that follows responsibility
Editors curate their assigned spaces. Members see and ask only what they have been granted.
Connect the tools you already use
Keep documents synced instead of uploading another copy.
Know what people need
See top questions, unanswered gaps, active members and usage before the next training update.
Your material stays yours.
Workspace and vector retrieval are isolated by tenant.
Bring your own provider key or use a managed model.
India data region is the default path.
Audit logs record member, source and settings changes.
Customer data is never used to train a model.
What people ask before they start.
Can departments have separate spaces?+
Yes. Access can be granted by role or individual, with all-member access as the simple default.
Where is our data stored?+
India is the default region. EU and US region choice is planned for teams with residency requirements.
Can we use our own provider key?+
Yes. OpenAI, Anthropic, Gemini, OpenRouter and compatible APIs are supported. Managed access is also available.
Is there an API?+
The internal engine is API-first. A customer-facing public API is planned after the core member experience.
Put the handbook where people actually ask.
Start with one SOP or handbook and invite your team.