- Getting started
- Best practices
- Data privacy
- Autopilot chat
- About Autopilot chat
- User interface
- Interacting with Autopilot chat - recommendations
- User scenarios for the 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
- 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
The Autopilot chat is designed to help you build, edit, and troubleshoot automations through a conversational experience. To get the most out of it, follow these recommendation to craft prompts, respond to suggestions, or manage your interactions:
Writing clear and specific prompts
Type your request in the chat input field. The more specific you are, the better Autopilot can understand and respond to your needs:
- Example: "Build a workflow that reads emails from Outlook, saves attachments, and logs the filenames in Excel."
- Too vague: "Help with email."
You can also reference existing elements from your project, for example "Update the UploadFiles sequence to include error handling."
Engaging with follow-ups and proposed solutions
Autopilot may guide you through the task by:
- Asking follow-up questions to clarify intent.
- Suggesting a step-by-step solution for you to accept or reject.
- Offering multiple options for how to complete a task.
Providing feedback on the responses
Each response from Autopilot includes:
- Thumbs Up / Thumbs Down votes—Use these to rate how helpful the response was.
- Copy—Copy the response to paste it into your workflow or documentation.
Feedback helps improve results over time, and copying allows quick reuse of code, descriptions, or suggestions.
Managing chat history
Autopilot chat saves your conversations for up to 30 days, allowing you to revisit and continue past sessions.
- Use the Chat History panel to browse or search previous conversations.
- Select a chat to pick up where you left off, as Autopilot retains full context.
- Delete chats you no longer need by selecting the conversation and choosing Delete. option.
Starting a new chat
If you want to switch to a different task, select New Chat in the Autopilot header. This starts a clean session and ensures that previous context does not interfere with your new request.