- Getting started
 - Best practices
 - Data privacy
 - Autopilot chat
 - Generating automations
 - Generating tests
- Generating tests
 - Quality-check requirements
 - Generate tests for requirement
 - Import manual test cases
 - Find obsolete tests
 - Generate tests for SAP transactions
 - Generate coded automations
 - Generate coded API automation
 - Refactor coded automations
 - Generate low-code automations
 - Generate synthetic test data
 - Generate test reports
 - Search Test Manager project
 
 - Autopilot for Everyone
- About Autopilot for Everyone
 - Autopilot for Everyone feature comparison
 - User types
 - Data sources
 - Toolset automations
 - Localization
 - Prerequisites
 - Autopilot widget
 - The Autopilot for Everyone tenant card
 - Prerequisites for installation
 - Enabling Anthropic models
 - Installing Autopilot for Everyone
 - Updating Autopilot for Everyone
 - Uninstalling Autopilot for Everyone
 - Configuring Autopilot for Everyone
 - Disabling the Autopilot welcome screen in Assistant
 - Configuring an LLM for Autopilot for Everyone
 
- Deploying toolset automations
 - Prompt-to-response flow
 - Launching Autopilot for Everyone
 - Autopilot settings for business users
 - Using a specialized Autopilot
 - Using a starting prompt
 - Uploading and analyzing files
 - Running automations
 - Interacting with Autopilot answers
 - Using suggested prompts
 - Starting a new chat
 - Chat history
 - Providing general feedback
 
- Clipboard AI Enterprise version
 - Troubleshooting
 
 

Autopilot user guide
There is a predefined interaction flow that Autopilot follows to answer each query:
Once Autopilot receives the prompt, it analyzes its intent, along with any images or files, and determines which (if any) actions it should perform to answer your query.
A pre-response action is an automation or a data source query that Autopilot runs in the background before responding to the query. This helps collect any information or context needed to provide a relevant answer.
If Autopilot decides it should use pre-response actions to help answer your request, it can perform up to six pre-response actions automatically.
A non-pre-response action is an automation which is not configured as a pre-response. If Autopilot decides to use a non-pre-response action, it recommends and sets up the automation to the user by inferring argument values from the conversation context. You can then validate the argument values and execute the automation. Only one non-pre-response action can be recommended at a time.
Any relevant citations, such as those sourced from actions, appear under the previously generated response.