Ask how any internal process works (expense approvals, PTO requests, deployment steps) and get a clear answer that cites the exact procedure it came from, without pinging the one person who happens to know.
Using our documented processes in the Knowledge Center, answer how-to questions from the team. Start with: how do I [submit an expense report] for [a client dinner over the limit]? Cite the procedure and section your answer comes from.
Un exemple illustratif. Votre résultat dépendra de vos sources, de vos données et de vos demandes.
This comes from the Expense & Reimbursement Policy (v4, updated May 2026) in the Knowledge Center, plus the Manager Approval Matrix it references. A client dinner over the per-head limit is covered, with one extra approval step.
A client dinner counts as billable meals & entertainment, so it follows the standard expense flow with one added approval because it's over the limit.
Once both approvals are in, reimbursement is released in the next payroll run, usually within two weeks (Section 6.3). If the dinner ran over $150 per head, Finance also asks for a short written justification before releasing it (Section 5.2).
Want me to list the approval steps for expenses over $150 per head, or pull the receipt requirements for international meals?
Process Q&A lets anyone ask how a process works in plain language and get an answer grounded in your own documented procedures. Joy, the JoySuite assistant, reads the relevant procedure at ask time and replies with the steps, plus a citation to where it found them.
Upload SOPs, policies, and how-to guides to the Knowledge Center, or connect the wiki where they already live. Joy indexes the full text so it can find the right passage.
Anyone on the team asks Joy how a process works, in their own words. No need to know which document holds the answer or what it's titled.
Joy replies with the steps that apply and cites the exact procedure and section, so the person can open the source and confirm before acting.
Ask a follow-up to narrow the case ('what if it's over the limit?') then copy the answer into your reply, ticket note, or wherever you're working.
Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.
Each answer names the procedure and section it came from, so people can verify before they act.
Ask in everyday words and Joy locates the relevant step even when the document is titled something else.
Role-based permissions mean people only get answers from the documents they're allowed to read.
Update the source procedure and the next answer reflects the change, with no separate FAQ to maintain.
Point it at your finance policies so 'can I expense this?' gets a consistent, cited answer.
Let new starters ask where things live and how routine tasks get done without booking time with a manager.
Answer 'how do I request access to X?' from your IT runbooks and setup guides.
Give frontline staff quick answers from the operations manual while they're on the floor.
Search returns a list of documents to read; Process Q&A reads the relevant procedure for you and answers the specific question, citing the section it used so you can confirm. You ask in plain language instead of guessing keywords.
Only from the procedures and policies you've added to the Knowledge Center or connected. Joy reads them at the moment you ask and won't invent steps that aren't documented. If the answer isn't on file, it tells you.
Update the source document and the next answer reflects it. There's no separate FAQ to maintain, so people never get steered by a stale copy.
Yes. Role-based permissions scope answers to the documents each person is allowed to read, so sensitive procedures stay with the right audience.
In the chat interface your team already uses. People ask on demand and get an answer back. There's nothing scheduled and no standing presence to manage; the answer comes when someone asks.
Rejoignez la liste d'attente et soyez parmi les premiers à essayer ce workflow lors du lancement de JoySuite.