Squawk Co-pilot

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.

​

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. 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, purchase or 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 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 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