Skip to content

Hello, How can we help?

Back to FAQ

Best practices for AI Employees

Last updated: 7 May 2026


What this does

Use this guide to introduce AI Employees with clear scope, review expectations, and entitlement control.

Current access and functionality

  • Verified against the current impact-web, impact-client, and impact-marketplace code on 2026-05-07.
  • AI Employee creation and management are handled in impact-web.
  • Management requires workspace owner or admin access and the AI Advanced entitlement.
  • AI Employee capacity is controlled by subscription or entitlement limits.
  • Staff may interact with AI Employees through permitted workflows but do not manage setup unless granted admin access.

When to use AI Employees

  • Use them for bounded support roles with repeatable context.
  • Use them where outputs can be reviewed by a human owner.
  • Use them to reduce drafting, summarising, routing, or support workload.
  • Avoid using them as the sole owner of ambiguous or sensitive decisions.

Setup practices

  1. Define the AI Employee’s purpose in one sentence.
  2. Assign a human owner responsible for review and correction.
  3. Limit workspace or team scope to where the AI Employee is needed.
  4. Use clear names so staff can distinguish AI Employees from human members.
  5. Review capacity and entitlement before adding more AI Employees.
  6. Revisit configuration after process or subscription changes.

Review practices

  • Check early outputs more often after setup.
  • Keep humans responsible for approvals, sensitive messages, and exceptions.
  • Document what the AI Employee should not handle.
  • Remove or adjust AI Employees that no longer have a clear purpose.

Common issues

  • Issue: AI Employee creation is blocked. Fix: Check AI Advanced entitlement and available capacity.
  • Issue: Staff misunderstand what the AI Employee does. Fix: Rename it and clarify its scope in the workflow.
  • Issue: Output quality varies. Fix: Narrow the scope and add human review checkpoints.