# Autopilot handover and error handling

Route an Autopilot conversation to a task or human help when the agent hands over, times out or encounters an error.

*Release 3.3 · admin, operator, visitor*

**Settings › AI › Features** · **Settings › AI › Functions** · **Settings › Bots › Virtual Assistant › Tasks**

## What it is

Autopilot can hand a conversation to a Virtual Assistant task or human route. **Chat Control Expiry Task** and **Error Task** provide recovery when the bot does not respond in time or encounters an unexpected error. The selected task determines what the visitor sees next.

## Who uses it and why

Administrators choose the recovery routes. Bot trainers maintain the receiving tasks. Operators take over conversations that need human help, while visitors continue through the configured route.

## Where to find it

Edit **Autopilot** under **Settings › AI › Features**. Intentional handoff uses a **Virtual Assistant Task** function under **Settings › AI › Functions**. Maintain the receiving task in **Settings › Bots › Virtual Assistant › Tasks** with the **Bot Trainer** role.

## How it works

There are three main routes:

- An AI function starts a selected task when the agent decides that task is appropriate. Any required data fields must already be populated.
- If the visitor is waiting and the bot response wait exceeds **Chat Control Expiry (secs)**, INSIDE starts **Chat Control Expiry Task**. Without a selected task, it attempts human assignment or uses the queue.
- An unexpected Autopilot error starts **Error Task**. Without a selected task, the conversation goes to the human queue.

In supported AI execution, a successful workflow handoff stops further generation, skips remaining function calls and discards pending AI output. A rejected handoff that does not transfer control can allow the agent to continue responding.

## Configure it

Prepare the receiving tasks first. Use the **Settings** role with the **AI** permission, or the **Developer** role, to select expiry and error tasks on the Autopilot feature.

The ordinary **Chat Control Expiry (secs)** control starts at 30 seconds and offers 5 to 60 seconds. Choose a wait suitable for the work your agent performs. Ask Powerfront to review expiry alongside longer-running AI configurations.

For intentional handoff, configure a **Virtual Assistant Task** function, select its **Task** and add it to the Autopilot feature's **Functions**. Ensure the agent can collect any prerequisite information.

### Settings

| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Chat Control Expiry (secs) | Settings › AI › Features | website | 30 seconds in the new-feature editor | Settings role, Developer role | Sets the response wait before bot control expires while the visitor is waiting. |
| Chat Control Expiry Task | Settings › AI › Features | website | Not set; use human assignment or the queue | Settings role, Developer role | Starts the selected Virtual Assistant task when bot control expires. |
| Error Task | Settings › AI › Features | website | Not set; use the human queue | Settings role, Developer role | Starts the selected Virtual Assistant task when Autopilot encounters an unexpected error. |
| Task | Settings › AI › Functions | website | Not set: choose a task for the function to invoke | Settings role, Developer role | Selects the Virtual Assistant task invoked by a Virtual Assistant Task function. |

### Permissions

| Permission | Lets you |
|---|---|
| Settings | Configure AI features and functions when the AI Settings permission is allowed. |
| AI | Allows AI configuration under Settings Permissions. |
| Developer | Configure AI handoff functions and feature recovery options. |
| Bot Trainer | Maintain Virtual Assistant tasks used for handoff and recovery. |

## Limits and good to know

- Expiry is a response wait safeguard, not a fixed limit on the whole conversation.
- A task handoff does not necessarily mean immediate human assignment. The task controls the next steps.
- Human availability and normal routing still apply. A queued conversation may need to wait.
- A missing required field prevents the task function from handing over.
- **Virtual Assistant Task** functions are supported for **Autopilot** and **Voice Autopilot**, not every AI feature type.

## Depends on and works with

### This feature uses

- **Requires** [Autopilot for live chat](AI-003.md): These expiry and error options apply to conversation Autopilot.
- **Configured in** [Roles and permissions](ADM-008.md): AI configuration permissions control who can change the recovery options.
- **Configured in** [AI feature settings and change history](AI-001.md): Recovery options are saved in the Autopilot feature.
- **Configured in** [AI functions and required inputs](AI-016.md): A Virtual Assistant Task function enables an intentional AI handoff.
- **Configured in** [AI updates to customer and conversation data](AI-019.md): Required data must be populated before a configured task function can run.
- **Configured in** [Virtual Assistant task setup](ENG-009.md): The selected tasks define what happens after an expiry, error or intentional handoff.
- **Works better with** [Virtual Assistant task pauses and handover](ENG-015.md): The selected task can continue the workflow or hand over to human routing.
- **Related** [Chat queue](CHAT-005.md): Recovery can send a conversation to the human queue when no task or immediate assignment is available.
- **Related** [Virtual Assistant tasks started by Autopilot](ENG-027.md): Intentional task handoff stops further AI output once control has transferred.

### Used by

- **Configures** [Autopilot for live chat](AI-003.md): Expiry and error tasks control recovery and handoff.
- **Enhances** [Autonomous AI performance reports](REP-024.md): Handoffs and recovery affect escalation outcomes.

## FAQ and troubleshooting

### Why did the chat go to the queue?

Autopilot may have failed or expired without a selected recovery task. Check **Error Task**, **Chat Control Expiry Task** and human availability.

### Why did the AI continue after trying to hand over?

The handoff may have been rejected. Check the selected task and any required data fields. Only a successful transfer stops that AI run.

### Does expiry end the visitor's conversation?

It routes the conversation to the selected task or human handling. The receiving route determines any later closure.

### Why did a handoff not send a final AI answer?

Successful workflow handoff suppresses pending AI output so the receiving route can continue the conversation.