Core actions

Autopilot carries out real work across the Ema platform on your behalf. Instead of navigating menus and forms, you describe what you want in the chat and Autopilot handles the rest. This section covers every major action, from creating your first AI Employee (AIE) to filing a bug report.

Action	What it covers
Creating an AI Employee	Build a new AIE from scratch or clone an existing one
Editing an AI Employee	Modify workflows and settings in a safe working session
Testing an AI Employee	Chat with an AIE to verify its responses
Managing data and knowledge	Upload files, search knowledge bases, work with dashboards
Generating documents	Produce polished reports and deliverables
Connecting integrations	Link external apps and tools to your AIEs
Organizing AI Employees	Group and arrange AIEs for easy navigation
Asking platform questions	Get answers about Ema capabilities and your account
Reporting bugs	File bug reports directly from the chat

Creating an AI Employee

Every project starts with an AI Employee. Tell Autopilot what you need and it builds the AIE, sets up its workflow, and confirms when it is ready. You can also clone an existing AIE by asking Autopilot to copy it by name.

How to create an AI Employee:

Open the Autopilot chat from any page.
Describe the AI Employee you want — its purpose, the tasks it should handle, and any data it needs.
Autopilot creates the AIE and reports back with a summary of the name, description, and configuration.
To have Autopilot handle everything end to end, say so in your prompt; it will make all design decisions and confirm when complete.

After creation, a version snapshot is saved automatically. You can view the history or roll back at any time.

Example prompts:

Build me an internal knowledge assistant AI Employee that answers employee questions about company policies, SOPs, processes, and documentation. Then, create a sample policy file, upload it, and test that the AI Employee works as expected. Make all design decisions yourself without asking me for input.

Clone my “Customer Support Bot” AI Employee and rename the copy to “Support Bot v2”.

Limits: You must have permission to create AI Employees in your workspace. Autopilot asks for confirmation before finalizing creation.

Editing an AI Employee

Changes happen inside a working session — nothing goes live until you ask Autopilot to deploy. This means you can experiment freely without risk to the live version. If you close the session without deploying, your changes are discarded.

How to edit an AI Employee:

Tell Autopilot which AIE to change and what you want.
Autopilot opens a working session and loads the current workflow.
Make as many changes as you like: rename the AIE, add or remove workflow steps, reconnect steps, enable human approval on a step, set a schedule trigger, assign integration tools to a step, configure a per-step model override with EmaFusion™, manage categorizer options, or enable and disable the AIE.
Ask Autopilot to check the workflow. It validates the configuration and flags errors.
Ask Autopilot to deploy. It will ask you to confirm before pushing changes to production.

You can save a version snapshot at any point and roll back to a previous version whenever you need to.

Example prompts:

Help me analyze and improve an AI Employee to improve its performance. If it is deployed, test it with a few sample queries and analyze their debug trace logs, too.

Add a human-approval step to my “Invoice Processor” so someone on the finance team must sign off on payments over $10,000.

Limits: Load an AIE’s workflow before making structural changes. Deploying always requires confirmation. Only one working session per AIE can be active at a time.

Testing an AI Employee

Building an AIE is only half the work. Autopilot lets you open a live conversation with any AIE, send it messages, and review its answers without leaving the chat.

How to test an AI Employee:

Ask Autopilot to start a conversation with the AIE by name.
Send messages as an end user would. Responses may take a moment for complex workflows.
Review replies and ask follow-ups to probe different scenarios.
List active conversations or delete a test conversation when finished.

For structured evaluation, ask Autopilot to generate a test set and run it automatically.

Example prompts:

Create a 5 question test set for my internal knowledge assistant AI Employee. If the AI Employee doesn’t exist yet, create one first. Then run the test set and report back with the results. Make all design decisions yourself without asking me for input.

Start a conversation with my “IT Helpdesk” AI Employee and ask it: “How do I reset my VPN password?”

Limits: Conversations are asynchronous — complex workflows may need a moment. Deleting a conversation is permanent and requires confirmation.

Managing data and knowledge

AI Employees are only as good as the information they can access. Autopilot makes it easy to upload documents, search knowledge bases, and organize data across AIEs.

Uploading data

Attach files by clicking the “Attach files” button, dragging and dropping into the chat (a blue border appears), or pasting an image directly. Each file can be up to 20 MB. Uploaded files show as a chip with the name, size, and a remove button. Tell Autopilot which AIE the data belongs to and it handles the rest.

Searching and organizing data

Ask Autopilot to list data sources for an AIE (results are paginated).
Search within a knowledge base by keyword.
Copy a data source or replicate it to another AIE.
Delete a data source (permanent — Autopilot asks for confirmation).

Dashboards

You can upload dashboard data and trigger workflows from individual rows. Ask Autopilot to view rows, trigger a workflow for a specific row, or refresh the data — useful for batch processing or monitoring structured datasets.

Example prompts:

Upload the Q4 sales report to my “Revenue Analyst” AI Employee and search it for mentions of APAC.

Show me all data sources attached to my “Policy Assistant” AI Employee.

Limits: 20 MB per file. Deleting data is irreversible. Paginated results require you to request the next page.

Generating documents

When you need a polished deliverable — a report, summary, or structured analysis — Autopilot generates it in the background so you can keep working while it runs.

How to generate a document:

Tell Autopilot what document you need, including the AIE, data, or format to use.
Autopilot starts generation and notifies you when it begins.
When the document is ready, Autopilot delivers it in the chat.

Generation time depends on complexity and data volume. If something goes wrong, Autopilot reports the error and suggests next steps.

Example prompts:

Generate a summary report of all support tickets handled by my “Support Triage” AI Employee this week.

Create a document comparing the performance of my three sales assistant AI Employees over the last quarter.

Limits: Generation is asynchronous; complex requests take longer. Output quality depends on the underlying data and AIE configuration — keep your knowledge base current.

Connecting integrations

Ema connects to over 100 apps and tools so your AI Employees can pull data from or take actions in external systems.

How to connect an integration:

Ask Autopilot what integrations are available to see the full list.
Choose an integration and ask Autopilot to set it up. It walks you through credentials and permissions.
Once connected, assign the integration’s tools to individual workflow steps when editing an AIE.

Example prompts:

What apps and tools can I connect to Ema? Show me the full list of integrations available and how to set them up.

Connect my Salesforce account so my “Lead Qualifier” AI Employee can pull in new leads automatically.

Limits: Each integration requires its own credentials. Not all integrations support every action — ask Autopilot about specific capabilities. Removing an integration that active AIEs depend on may cause workflow errors.

Organizing AI Employees

Groups act as folders that let you categorize AIEs by team, function, project, or any scheme that fits your organization.

How to organize AI Employees into groups:

Ask Autopilot to create a group with a name.
Move an AI Employee into the group by specifying both the AIE and group names.
Reorganize by moving AIEs between groups, renaming groups, or deleting groups you no longer need.

Ask Autopilot to list all groups or list AI Employees with filters like status or type to find what you need quickly.

Example prompts:

Create a group called “Sales Team” and move my “Lead Qualifier” and “Demo Scheduler” AI Employees into it.

List all my AI Employees that are currently active.

Limits: Deleting a group is permanent and requires confirmation. AIEs inside a deleted group become ungrouped — they are not deleted.

Asking platform questions

Not sure what Ema can do or how a feature works? Autopilot doubles as a platform guide. Type your question directly — no special syntax needed.

Example prompts:

Give me an overview of Ema’s platform capabilities and what I can do as a user. How can you help me through my journey?

What is the difference between a scheduled trigger and a manual trigger for an AI Employee?

Limits: Autopilot answers based on current platform capabilities. For billing, account limits, or enterprise agreements, it may direct you to Ema support.

Reporting bugs

If something is not working as expected, you can file a bug report directly from Autopilot without leaving the platform.

How to file a bug report:

Describe the issue in the chat. Include what you were doing, what you expected, and what happened instead.
Autopilot files the report and confirms submission.

Example prompt:

I found a bug: when I upload a CSV to my “Data Analyst” AI Employee, the upload spinner never stops and the file does not appear. I tried three times with different files.

Limits: Provide as much detail as possible — vague reports are harder to act on. Reports go to Ema’s internal tracking; you will not receive a ticket number in the chat, but all submissions are reviewed.