Aivah brings employee setup, conversations, reusable resources, deployment controls, content creation, and results into one workspace. Start with one job and check its answers against information your team trusts.
Before you begin
Choose an owner for the first employee and a small, current source of information. You do not need a voice, character, or connected service to begin a text test.
Steps
1. Choose one purpose
Define who the employee helps, the repeated task it should handle, and a result your team can check. Use Choose your first job to write that definition.
2. Identify approved business knowledge
Prepare the documents, website pages, or text the employee should use. Employees contains the hiring form and each employee's Knowledge section. Source processing and answer accuracy are separate checks.
3. Define instructions and boundaries
Instructions describe the employee's job, permitted sources, boundaries, and handoff to a person. Persona describes its tone and working style. Neither replaces factual source material.
4. Decide how it should appear and act
The employee is the configured role. A model handles conversation responses; a voice provides speech; a character provides the visual appearance. Browse characters, backgrounds, and voices in Library.
Connected tools give an employee access to outside services. Review selected tools before hiring and begin without tools when the job only requires answers.
5. Test privately in Chat
Open Chat, choose the employee, and ask questions with known answers. Also ask questions the source cannot answer. Check facts and boundaries before adding more capabilities.
6. Prepare a deployment and review the result
Deploy contains website experiences, phone numbers, messaging channels, meetings, and scheduled tasks. Create contains Content studio, Live podcast, and Aivah Code. Insights contains conversation and activity views. Each area has its own setup and testing requirements.
Expected result
You can distinguish the employee, its sources and instructions, its conversation settings, and the places where it can be used. You have a focused first task to build and test.
Status meanings
An employee or source marked Completed has finished its displayed processing stage. It still needs answer testing. A loading or connecting state does not confirm a usable conversation or deployment.
Usage credit impact
Conversation, generation, and other supported activity may use credits. Review the current balance and any feature-specific notice before an extended test.
Information stored or shared
Employee configuration, supplied sources, conversations, and generated work can contain business information. A deployment or connected action can make information available beyond the private conversation. Use approved material and review the relevant sharing controls.
Limits and permanent actions
Keep launch decisions separate from setup status. Check dependencies before deleting an employee, source, character, or connected resource.
Common problems and recovery
- The first job is too broad: choose one audience, task, and source.
- The answer sounds confident but is wrong: compare it with the source and record the mismatch before revising.
- You cannot find a feature: use the workspace tour to find its current area.
Help Center