AivahHelp CenterGo to Aivah
⌘K
No guide matched “”

Try fewer words or contact support for help.

Contact support

Create your first AI employee

Create a focused AI employee from a curated role or a blank setup, then wait for it to be ready.

Who this is forAccount owners, content managers, and team members creating an AI employee in Agents

You will achieveCreate an AI employee with a clear job, instructions, personality, approved knowledge, and only the connected actions it needs.

Before you beginReview the requirements before changing anything.

Last reviewed 10 July 2026Owner: Product EducationCurrent guide
On this page
  1. Before you begin
  2. Steps
  3. 1. Open Create agent
  4. 2. Choose Curated or Custom
  5. 3. Name the employee clearly
  6. 4. Decide whether it is a Presenter
  7. 5. Write and review the instructions
  8. 6. Set the personality
  9. 7. Add business knowledge
  10. 8. Select only necessary connected actions
  11. 9. Create and wait for readiness
  12. Expected result
  13. Status meanings
  14. Usage credit impact
  15. Information stored or shared
  16. Limits and permanent actions
  17. Common problems and recovery
  18. Next step

Use this guide when you are ready to build in Agents. You will create a focused AI employee and know when it is ready for private testing.

Before you begin

Prepare:

  • A descriptive employee name and a one-sentence purpose.
  • The audience and result you defined for the job.
  • Current, approved source material.
  • Instructions for tone, boundaries, confirmation, and human handoff.
  • A list of outside actions the employee genuinely needs.

Steps

1. Open Create agent

Open Agents, then choose the add button to open Create agent.

2. Choose Curated or Custom

Choose Curated to begin from a ready-made role grouped by a common business job. Select the category and closest template.

Choose Custom when the job does not fit a template and you need a blank setup.

After changing category or starting mode, review every field again. Confirm that the name, instructions, and selected starting point still describe the same job.

3. Name the employee clearly

Use a name that identifies the job, such as “Website Sales Guide” or “Customer Support First Response.” Avoid generic names that will become hard to distinguish in lists and results.

4. Decide whether it is a Presenter

Turn on Presenter when the employee should guide people through one presentation or video and answer questions about it.

Leave Presenter off when the employee needs a broader collection of websites, documents, notes, audio, video, or images. Presenter employees accept more limited source material, so follow the file guidance shown in the form.

5. Write and review the instructions

Define who the employee is, who it helps, its tasks, approved knowledge, tone, boundaries, clarification rules, human handoff, action confirmations, and handling of personal information.

If the creation page proposes instructions, treat them as a draft. Review every rule before accepting it.

6. Set the personality

Describe how the employee should sound in a short phrase, such as “warm, calm, and reassuring” or “direct, concise, and professional.” Personality should support the instructions, not override them.

7. Add business knowledge

Add a stable public website, supported files, or written content such as approved FAQs, policies, scripts, and product notes. Follow the current type and size guidance displayed in the form, because limits can vary.

Use descriptive source names and remove contradictory versions before uploading.

8. Select only necessary connected actions

If connected services are available, choose only the actions required for this job. For any action that sends a message, books something, changes outside information, or creates a record, include an instruction that requires confirmation first.

9. Create and wait for readiness

Review the setup, then choose Create agent. Wait for preparation to finish before important testing or publishing.

Expected result

The employee appears in Agents with its purpose, instructions, personality, knowledge sources, and any approved actions. Its preparation status tells you whether it can be tested.

Status meanings

Status shownMeaningWhat to do
Pending or ProcessingAivah is preparing the employee or a source.Wait and refresh later.
CompletedThe employee is ready for testing.Test it privately before publishing.
FailedThe employee or a source needs attention.Open the details and retry.

Usage credit impact

No fixed usage-credit charge for creating or preparing an employee is documented here. Private tests and supported activity can use usage credits. Check the balance and notices shown in your workspace.

Information stored or shared

Aivah stores the employee name, purpose, instructions, personality, selected preferences, and added knowledge sources. When a configured connected action is used, the outside service may receive information needed to perform it. Review that service, action, and permission before enabling it.

Limits and permanent actions

Feature availability, source types, file guidance, connected actions, and response choices can vary by account. Some major settings, including the original category, Presenter choice, and connected tools, may not be fully editable later. If the required change is unavailable, create and test a replacement before removing the original.

Common problems and recovery

  • Preparation stays pending: wait for large sources, refresh, then open details to find a source that needs attention.
  • A source fails repeatedly: confirm it opens, remove restrictions, reduce an unusually large file, use a simpler format, remove damaged or duplicate content, and upload a clean replacement.
  • The employee gives conflicting answers: remove contradictory sources and tighten the instructions.
  • The wrong starting role was selected: review every field or create a corrected replacement if the setting cannot be edited.

Next step

Refine knowledge, instructions, and actions, then manage, test, and improve.

Keep going