Skip to main content

Agent Console

📄️Assign Ticket to Me

Claims the ticket for the calling agent and takes it over from whoever held it — including the AI agent. This is Claim Agent Ticket with `force` always on: the caller becomes the owner (`assignee` and `work.owner`), the first claim ever stamps `work.picked_up_at` / `work.picked_up_by_user_id` and records a customer-visible `picked_up` event, a ticket still at the `received` stage moves to `picked_up`, an `open` ticket moves to `in_progress`, and the ticket leaves the triage queue. Taking a ticket over from the AI agent also records a `released` event (reason `take_over`). A no-op (still 200) if the ticket is already assigned to the caller. The response is the updated ticket.

📄️Hand Back Ticket to AI Agent

A human agent gives the ticket back to the AI agent with an instruction — the AI agent's next input. The AI agent becomes the owner (`assignee`, `work.owner` with `is_bot: true`), its working state starts fresh, and a ticket still at the `received` stage moves to `picked_up`. An internal `handed_back` event records the instruction; if the ticket has a shared reply draft, the draft is kept and travels with the instruction so the AI agent can build on it. The latest hand-back is returned as `work.hand_back`. The instruction is also queued for the AI agent as a `hand_back` instruction (see AI Control → Get AI Control Feed), which it picks up exactly once; `work.pending_instructions` counts it until then.

📄️Open Approval Card

Opens an approval card on a ticket: a proposal a human must decide before the AI agent acts. A ticket has at most one open card — any card still pending or snoozed on the ticket is marked `superseded` (reason `new_card`). The new card gets the next per-ticket `version`. The ticket's owner gets a portal alert (and a push notification on their installed app) when they are a human; otherwise every agent who can decide cards does. No email is sent. Once the card is decided or superseded, its alerts are marked read for everyone. An internal `approval_requested` event is recorded.

📄️Stop AI Agent Run

Ask the AI agent to stop the session it is running on this ticket. The agent ends the session on its next check-in, leaves an internal note saying who stopped it, and confirms with Acknowledge AI Agent Stop, which clears `work.stop_requested_at`. The ticket stays with the AI agent — pause it, take it over or turn the AI off to keep it from starting again. Records an internal `ai_stop_requested` event; a stop already waiting for the agent's confirmation is not requested twice.

📄️Get AI Runner Feed

The calling runner's queue: the agent ticket queue narrowed to the tickets this runner already holds or may claim under the desk's routing rules — tickets assigned to its person (unless that person picked the ticket up themselves), and, when the runner takes unassigned work and is not paused, unassigned tickets. A runner that is turned off sees only the tickets it already holds. Claiming any other ticket returns 409 (see Claim Agent Ticket), so the feed and the claim always agree.

📄️List Agent Ticket Events

Returns the ticket's audit timeline, oldest first. `event` is one of: created, status_changed, priority_changed, type_changed, visibility_changed, group_changed, assigned, unassigned, replied, noted, watcher_added, watcher_removed, linked, unlinked, reopened, rated, tags_changed, tenant_changed, sla_breached, sla_warning, sla_paused, sla_resumed, ai_triaged, snoozed, unsnoozed, merged, split, mentioned, follow_up_changed, notified, rule_applied, message_deleted, picked_up, released, stage_changed, progress_posted, human_requested, requester_linked, approval_requested, approval_decided, handed_back. Each event carries the actor (null for system-generated events, with `actor_label` naming the automation, e.g. `ai` or a rule), the from/to values, and any extra metadata.

📄️List Agent Directory

Lists the support agents another agent can choose from — when assigning a ticket or @mentioning someone in an internal note. By default only active seats held by super-admin users who still exist are returned; pass `include_inactive=1` to also get revoked seats, seats whose user is no longer a super admin, and seats whose user has been deleted from sku.io — all reported with `is_active: false`, since `is_active` here means the seat can actually be assigned work (active AND super admin AND not deleted). Entries are sorted by display name, case-insensitively. No pagination.