> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squawkvoice.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Squawk Co-pilot

> Build agents, link knowledge, and configure actions in plain English with the in-platform AI assistant

Squawk Co-pilot is the AI assistant built into Studio — you'll see it labeled **Build with AI** in the app. Describe what you want in plain English and the Co-pilot does the building for you: it creates and configures AI agents, links knowledge, sets up actions and flows, and answers questions about the platform along the way.

<Note>
  Squawk Co-pilot is now **generally available** to all Studio users — no beta enrollment or plan add-on required.
</Note>

## Open the Co-pilot

Two ways, from anywhere in Studio:

* Click the **sparkles button** in the top bar.
* Press **`Cmd/Ctrl + I`** to toggle the panel.

The Co-pilot opens as a resizable panel on the right side of the screen, so you can keep working while you chat. Use **New Chat** to start fresh, or **History** to reopen a previous conversation — sessions are saved per workspace.

## What it can do

Ask for an outcome, not a procedure — "Design a renewals agent for our SaaS product", "Link our product FAQs", "Add an order-lookup step to this flow". The Co-pilot asks follow-up questions where it needs detail; once your request contains everything it needs, it gets to work.

| Area                         | What the Co-pilot can do                                                                                                                                                                                                         |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **AI Agents**                | Create new agents from a plain-English description — name, greeting, and guidelines drafted for you — and update existing ones, including dispositions and advanced settings (languages, transcription hints, timezone, voices). |
| **Knowledge**                | Create knowledge bases, crawl a website into one, add FAQs, and link knowledge to an agent. Attach documents directly in the chat with the paperclip — they're uploaded and indexed as part of the conversation.                 |
| **Actions & Flows**          | Create and update pre-call, during-call, and post-call actions. It edits during-call flows node by node — adding, updating, and removing steps and branches — and the flow editor refreshes in real time as it works.            |
| **Variables & Transformers** | Create agent variables and build or update [Data Transformers](/build/data-transformers).                                                                                                                                        |
| **Integrations**             | List available Connected-App integrations and their actions, enable them for an agent, and run a live test request against an action to verify it works.                                                                         |
| **Analytics**                | Answer questions about call volume, outcomes, and dispositions from your call analytics.                                                                                                                                         |
| **Navigation**               | Opens the relevant page automatically after it creates something — a new agent's design page, a new knowledge base — and surfaces links (such as the Connected Apps connect dialog) when a task needs finishing by hand.         |

When you're on an agent's design page or inside a flow editor, the Co-pilot picks up that context automatically — "add a compliance disclaimer to the greeting" just works, without restating which agent you mean.

### Building an agent end to end

For a from-scratch agent, the Co-pilot works through four stages, confirming direction with you at each step:

1. **Mission & persona** — it drafts the agent's name, greeting, and guidelines from your description of the business goal.
2. **Knowledge** — it connects or creates the knowledge the agent should answer from.
3. **Workflow automations** — pre-call, during-call, and post-call actions for the tasks the agent must perform.
4. **Handoff** — dispositions and escalation behavior for the moments a human should take over.

### What it won't do

The Co-pilot's write access covers the build surface listed above. It does not create or launch [outbound campaigns](/campaigns/overview), purchase or manage [phone numbers](/manage/phone-numbers), or make billing changes — it will point you to the right page for those instead.

## How changes are applied

* The Co-pilot typically describes what it's about to do and asks follow-up questions when details are missing — but if your message already contains everything it needs, it proceeds immediately, and each executed step appears in the chat as it runs. There is no separate approval dialog or undo, so be specific about exactly what you want before sending large requests.
* Screens affected by a change refresh automatically — you can watch a flow update in the editor while the Co-pilot builds it.
* Everything it changes is recorded in [Audit Logs](/manage/audit-logs) under your user as the actor, with the request source labeled **Squawk Copilot**, so you can always tell which changes came from the assistant.
* It only touches workspaces and resources your user can already access, and credential fields (auth tokens, passwords, API-key fields) are redacted from the conversation and its saved history. As a general habit, avoid pasting raw secrets into the chat — connect credentials through [Auth Profiles](/manage/auth-profiles) instead.

## Tips

* **One goal per chat.** Long conversations eventually trim older context; start a **New Chat** when you switch topics so the Co-pilot stays sharp.
* **Big asks are fine — expect stages.** Very large requests are handled in stages across a few turns rather than one giant step. The Co-pilot usually summarizes how far it got — if it stops early, just ask it to continue.
* **Attach source material.** Dropping a product sheet or policy document into the chat is usually faster than describing its contents.

## Related assistants

Two smaller AI helpers share the Co-pilot lineage on specific screens:

* **Guidelines Assistant** — on the agent's voice & guidelines editor, drafts and refines the agent's instructions in place.
* **Generate Action with AI** — inside during-call actions, scaffolds an action from a description.

## Where to go next

<Columns cols={2}>
  <Card title="AI Agents" icon="robot" href="/build/ai-agents">
    What the Co-pilot is building for you — agents, guidelines, and settings.
  </Card>

  <Card title="Actions" icon="bolt" href="/build/ai-agents/during-call-actions">
    The flows and actions the Co-pilot can create and edit.
  </Card>
</Columns>
