Prove you can actually do a skill or procedure, not just say you can. Joy asks scenario questions, scores your answers against the standard, and hands back a scorecard: what's solid, what needs work, and a clear pass or needs-review read.
Test me on [handling a customer refund request] — ask me a few scenario questions and score how I did against the standard.
Un ejemplo ilustrativo: tu resultado dependerá de tus fuentes, datos y peticiones.
You worked through five scenario questions on the refund procedure, and I scored each answer against the standard in your Knowledge Center. You're solid on the core — eligibility, refund method, and how you handled the customer — and two edge-case areas came in under the pass line.
Five scenario questions, scored one by one against the Refund Procedure standard. You're comfortably over the 70% pass line on the core steps and short on two areas — the edge cases, where a refund most often goes wrong.
Score by competency area (pass line 70%)
Here's the read by area, with a note on what each score came from.
| Competency area | Result | Note |
|---|---|---|
| Eligibility check | Solid | You checked the purchase window, the receipt, and the item condition before offering a refund. |
| Refund method & timeframe | Solid | Refund to the original payment method inside the stated window — correct against the policy. |
| Customer communication | Solid | Calm and clear, and you set the right expectation for when the money lands. |
| System processing steps | Needs work | You skipped the reason code, which the policy requires logged on every refund. |
| Exceptions & escalation | Needs review | On the out-of-window scenario you approved the refund yourself instead of routing it for manager sign-off. |
What's solid. On the core of the procedure you're in good shape. You verified eligibility before acting, picked the right refund method and timeframe, and walked the customer through it clearly — the three areas that carry most of a refund done right.
What needs work. Two areas came in under the 70% pass line. On system processing you left off the reason code the policy requires on every refund, and on the out-of-window scenario you approved the refund yourself rather than routing it for manager sign-off. Both are the edge cases, which is exactly where a wrong call costs the most.
The overall read. At 74% you pass on the core steps, but the two edge-case areas sit below the pass line, so it's a needs-review on exceptions before you handle them on your own. Firm up the reason-code step and the escalation rule, re-run the check, and you'll be set.
Want me to re-check just the edge cases once you've reviewed them, or pull the escalation steps from the procedure so you can study them first?
Skills Verification runs a short chat-based assessment. Joy asks scenario and knowledge questions about the skill, you answer in your own words, and Joy evaluates each answer against the competency's criteria. You get a scorecard by area: what's solid, what needs work, and a clear pass or needs-review read.
Point Joy at the procedure, skill definition, or competency criteria in the Knowledge Center so it knows what a correct, complete answer looks like.
Ask Joy to test you on the skill. It asks scenario and knowledge questions one at a time, and you answer in the chat in your own words.
Joy evaluates each answer against the criteria and returns a scorecard by competency area, flagging what's solid and what needs work, with an overall pass or needs-review read.
Copy the scorecard into your development plan or your next one-on-one, then re-run the check once you've closed the gaps. Joy points to what to review; you decide what to work on.
Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.
Joy asks real questions and scores your answers, so the read reflects what you can actually do, not how you rate yourself.
Every answer is judged against the competency's criteria in your Knowledge Center, so a pass means the same thing for everyone.
You get a breakdown by competency area, not a single number, so you know exactly which part needs work.
Run the check again after you've practiced to watch the shaky areas move, on demand whenever you want a fresh read.
A manager has Joy check a new team member on a core procedure before clearing them to handle it solo.
Verify people still know a policy or safety procedure well after the training, not just the day they took it.
Ask for tougher scenario questions to stretch an experienced person, or gentler ones for someone new to the skill.
Run the check across several related procedures in one sitting and get a scorecard that covers each.
Ask Joy to assess you on a skill or procedure. It asks scenario and knowledge questions one at a time, you answer in the chat, and it scores each answer against the competency criteria in your Knowledge Center. You get a scorecard by area with a clear pass or needs-review read you can copy into your development plan.
A self-assessment is you rating yourself. Here Joy actually tests you: it asks questions, you answer in your own words, and it scores those answers against the standard. The read reflects what you demonstrated, not how confident you feel.
No. It's an on-demand scorecard that shows where you stand against the competency's criteria. It doesn't award a certificate or update your LMS. Use it to check readiness and guide development; formal certification stays with whatever system your organization uses for it.
Yes. Tell Joy how many questions you want and how tough, and it drafts to that. Ask for harder scenario questions to stretch an expert or gentler ones for someone new, and re-run the check whenever you want a fresh read.
The scorecard is shown in the chat for you to read and copy where you want it, such as a development plan or a one-on-one note. Joy doesn't file it anywhere or report it on its own; you decide what to share.
Únete a la lista de espera y sé de los primeros en probar este flujo de trabajo cuando JoySuite se lance.