Quick Start

Build and test your first AI agent — from an empty workspace to a working conversation in the Playground. The whole setup takes 10–15 minutes and requires no code.

In this guide you will:

1. Create an Inbound Agent.
2. Write its instructions.
3. Give it knowledge to answer from.
4. Define which data it collects.
5. Test it in the Playground.

Before you start

• You need a Flametree account. If you don't have one, see Sign up and sign in.
• You need the Tenant Admin role to create agents. If you registered the tenant yourself, you already have it.

Step 1: Create the agent

1. In the left menu, go to AI Agents > Agents.
2. Click Create new agent in the upper-right corner.
3. Select Inbound Agent from the dropdown. This agent type replies to messages your customers send first.
4. In the Create new Inbound Agent window, enter the Agent name and confirm.

Expected result: the agent configuration page opens in Simple mode, with four tabs: Instructions, Knowledge Sources, Channels, and Conversation Results. Fill them in order. This guide covers each tab briefly; for the full field-by-field description, see Simple mode.

Simple vs Advanced mode

Simple mode is enough for this guide. If you later need workflows, tools, or model settings, switch to Advanced mode with the toggle in the upper-right corner. You can switch back and forth at any time.

Save your work

After completing each tab, click Save in the upper-right corner to apply your changes.

Step 2: Write the instructions

The Instructions tab defines how your agent communicates: who it is, how it sounds, and what it must achieve. Fill in:

• Identity & Role — who the agent is and what company it represents.
• Speech Style & Tone — how it should sound.
• Primary Task — what it must accomplish in every conversation.
• Welcome message — the first message customers see.

Each field shows an example you can adapt. Sample content for a fictional events company:

Field	Example
Identity & Role	You are Ted, a helpful AI assistant for EventHub. EventHub organizes online events such as webinars, workshops, and educational sessions. You help people learn about upcoming events and register for them.
Speech Style & Tone	Use a friendly and professional tone. Always introduce yourself. Keep responses short — 1–2 sentences when possible. Always reply in the same language as the customer.
Primary Task	Your main task is to help customers register for events. Guide them through registration, ask for the required details, and confirm. If a question is outside event registration, politely redirect the conversation. In addition to name and email, also ask for the phone and preferred event date.
Welcome message	Hello! I can help you register for our upcoming events. Would you like to see what events are available?

On this tab you can also turn on Allow human handoff and describe Handoff Conditions — when the agent should pass the conversation to a human operator. You can skip this for your first agent.

tip

When writing instructions, refer to the person the agent talks to as human — for example, "Collect the human's contact details." Language models handle this wording consistently. Use client, guest, or another term only if your business requires it.

Step 3: Add knowledge

The Knowledge Sources tab defines what your agent knows. Add at least one source so the agent has facts to work with. The tab contains sub-tabs:

• Core — short, essential facts included with every answer. Checked before any other source.
• FAQs — question–answer pairs for predictable, repeated questions.
• Plain Text — free-form reference text.
• Websites — links to public web pages.
• Files — uploaded documents.
• YouTube — links to public videos; Flametree transcribes them.

For your first agent, fill in Core with the basics, for example:

EventHub hosts short online learning events such as webinars and workshops. Events usually last 60–90 minutes and are held online via Zoom. Each event is limited to 100 participants. Registration requires name and email. Participation is free, but registration is required.

If your tenant already has sources of a given type, you can Connect them; otherwise create a new one directly from the tab. For details on each source type, see Knowledge Sources.

Step 4: Skip channels (for now)

The Channels tab connects your agent to the outside world — WhatsApp, Web-widget, and Telegram in Simple mode. You don't need a channel to test in the Playground, so skip this step for now.

When you are ready to go live, connect and manage channels in Settings > Channels — that page is the source of truth for credentials and channel status — then attach the connected channel on this tab.

Step 5: Define conversation results

The Conversation Results tab defines what data your agent collects during conversations. Use the toggles under Standard Information for common fields, or add your own:

1. Click + Add something else.
2. Choose how the value is captured:
   • Match to options — only values from a predefined list (for example: Service = Loan, Credit card, Mortgage).
   • Any value — any value the customer provides (names, locations, free text).
3. Click Add field.

For the EventHub example, keep the standard name, email, and phone fields, and add a custom Preferred event date field with Any value.

Click Save. Your first agent is configured.

Step 6: Test in the Playground

The Playground panel on the agent page lets you chat with your agent like a customer would.

1. Send a greeting and check the Welcome message and tone.
2. Ask a question your knowledge answers ("How long do events last?").
3. Ask something off-topic and check the agent redirects politely.
4. Go through a registration and provide your name, email, phone, and a date.
5. Open Conversation Results under the Playground area to watch fields fill in live.

Expected result: the agent greets you with your welcome message, answers from your Core knowledge, stays on topic, and the fields you defined fill in as the conversation progresses.

If something is off, adjust the instructions or knowledge, click Save, and test again. Small wording changes in Primary Task and Core often make the biggest difference.

What's next

• Connect a web widget and put the agent on your site.
• Add more knowledge sources for deeper answers.
• Review sessions once real customers start chatting.
• Set up human handoff so operators can take over when needed.