Skip to content
SquadOS SquadOS Docs

First Complete Agent

This guide takes you from an initial goal to a tested agent and, when needed, an agent connected to an inbox. It assumes an account that can create agents; visible menu items may vary with your role and the features enabled for the organization.

1. Define the goal

Section titled “1. Define the goal”

Start with something focused:

  • answer frequent questions;
  • guide customers through a process;
  • help the internal team with procedures;
  • collect information before handing off to a human.

Small flows are much easier to test — you can expand later.

2. Create the agent

Section titled “2. Create the agent”

Open My Agents and click New Agent. In the New Agent dialog:

  1. enter the Agent name;
  2. choose an Initial category when the field is required for your access;
  3. click Create Agent.

SquadOS opens the new agent’s editor. On desktop screens, AgentMaker opens automatically to help build the first prompt.

3. Write and save the prompt

Section titled “3. Write and save the prompt”

The editor starts in Prompt. Choose how you want to work:

  • chat with AgentMaker, review its proposals, and apply only the ones that fit;
  • click Edit Prompt to write or adjust the instructions manually.

Include the agent’s role, intended audience, responsibilities, limits, and when it should hand off or ask for more information. Save before testing. If changes are pending, the test panel uses the saved version and offers Save and test.

4. Choose the model

Section titled “4. Choose the model”

Open Model. The section may show Cheapest, Best value, and Best performance shortcuts, followed by the Suggested and Other models (not suggested for this agent) groups.

Recommendations are calculated from the catalog available to the organization and the capabilities required by the current configuration, such as tool use, image input, and context size. The recommended model can therefore change and should not be selected from a fixed name in this guide.

Compare capability and credit cost, select the model that fits your use case, and save. For a simple first flow, Best value is a reasonable starting point; validate the result with the questions in step 6.

5. Add knowledge and tools if needed

Section titled “5. Add knowledge and tools if needed”

The editor separates these settings:

  • In Knowledge, select the Knowledge bases the agent may search on demand. You can also select Context blocks, which are sent in full on every reply, and configure AutoLearn when a base is selected.
  • In Tools, click Add Tool to connect available Native Tools, Organization Tools, Other Tools, or MCP Servers. Users with permission can also create an HTTP / API Tool or connect an MCP Server.

Do not look for Search Knowledge Base in the tool picker: that capability is managed by the Knowledge section when you select a base.

6. Test inside the editor

Section titled “6. Test inside the editor”

In the header, click Test Agent. Testing opens in an integrated editor panel and keeps earlier conversations available for you to resume. The button is disabled when the agent is inactive.

Test at least:

  • a common question the agent should answer;
  • a difficult or ambiguous question;
  • an out-of-scope request;
  • an action using knowledge or a tool, if those capabilities are configured.

Correct the prompt or configuration, save, and repeat until the behavior is consistent.

7. Connect an inbox if needed

Section titled “7. Connect an inbox if needed”

Testing in the editor completes the agent creation journey. To receive messages from an external channel, open Inboxes and click Connect inbox.

Choose an available channel, complete its setup, and select the agent as the destination under Who handles this inbox? The wizard then opens Service hours; you can save a schedule or choose Set up later.

Channels may include WhatsApp, WhatsApp Official, compatible providers, Instagram Direct, Instagram Comments, Telegram, Public page, Widget, and API. Availability depends on the features enabled for the organization.

For a controlled validation, start with a Public page shared only with the team. Before exposing any channel to the public, run the Publishing Checklist. The complete flow is in Inboxes.

Next steps

Section titled “Next steps”
  • Explore the Native Tools to understand what the agent can already do without external integrations.
  • Configure Users and Roles if other people in the company will also administer or use SquadOS.