Help CenterUse this guide after creating an employee and whenever knowledge or instructions change. You will verify readiness, test expected and unexpected requests, and make evidence-based improvements.
Before you begin
Gather the employee's job definition, approved sources, handoff path, and a test set. Include questions that should be answered, questions that are absent from the sources, one refusal, and one handoff.
Steps
1. Find the intended employee
Open Agents. Search by name or sort the list before opening the employee. Use clear employee names so test and production versions are easy to distinguish.
2. Review preparation details
Open the employee and check its overall status plus the status of each website, file, or written source. Do not begin important work while preparation is pending, processing, or failed.
3. Retry a failure at the right level
If the whole employee failed, use the main retry action. If one source failed, retry that source from the details.
For a repeated source failure, confirm the source opens, remove access restrictions, reduce an unusually large file, use a simpler format, remove duplicate or damaged content, and upload a clean replacement.
4. Edit one controlled change
Edit the name, instructions, personality, or knowledge sources as needed. After a knowledge change, wait for preparation and test again.
5. Run the private test
Choose Test in Playground or start a new conversation and select the intended Agent. Test at least:
- Five questions answered directly by the sources.
- Three questions not answered by the sources.
- One request the employee should refuse.
- One request that should be handed to a person.
- Every approved connected action and confirmation.
- The opening message, voice, and appearance.
- A mobile-sized screen if the employee will be public.
6. Test supported presentation quizzes
For a presentation employee with a quiz, open the Quiz action from the employee list or conversation toolbar. Complete the questions and use the explanations to find material that needs clarification.
7. Improve one cause at a time
When a test fails, identify whether the cause is missing knowledge, conflicting knowledge, unclear instructions, a connection problem, or an unsuitable appearance or voice. Change one item, wait for readiness, and run the same test again.
8. Remove an employee carefully
The list can allow one or more selected employees to be deleted. Before a bulk action, clear search, confirm every selected row, and remember that a selection can remain active while the visible list changes.
Expected result
The employee shows completed preparation, passes the agreed test set, handles unsupported questions honestly, follows the handoff, and confirms connected actions before outside effects.
Status meanings
| Status shown | Meaning | What to do |
|---|---|---|
| Pending or Processing | The employee or a source is still being prepared. | Wait, refresh later, and review source details. |
| Completed | Preparation finished. | Run the full private test. |
| Failed | The employee or a source needs attention. | Open details, correct the cause, and retry. |
Usage credit impact
Private conversations, voice, quizzes, connected actions, and other supported test activity may use usage credits. The guide does not define an exact formula. Check the workspace balance and keep the test set focused but complete.
Information stored or shared
Employee changes and conversation tests are stored in the relevant workspace areas. A connected service receives information needed for a tested action when that action is invoked. Use non-sensitive test data whenever possible.
Limits and permanent actions
The original category, Presenter choice, and connected tools may not be fully editable. Create and validate a replacement when a required change is unavailable.
Removing a source can take effect immediately. No recovery path for a deleted employee is documented, so confirm the name, selection, public uses, and source ownership before deletion.
Common problems and recovery
- Preparation never completes: refresh, open details, and look for one failed source.
- The wrong employee answers: start a new conversation and select the intended Agent.
- Answers are wrong or unsupported: check the sources, remove conflicts, add an explicit “information unavailable” rule, and retest.
- A bulk selection looks wrong: clear search and selection, then select the intended rows again.
- A quiz result is weak: review explanations and clarify the presentation material before another attempt.
Next step
Learn the full private testing surface in Use Playground, then complete the launch and improvement checklists.