Every feature

Type your email address and enter the code Studio sends you. There is no password to remember or leak.

Add an authenticator app or a passkey as another way to sign in, with backup codes for when you lose a device.

An administrator can let people sign in with their Google or Microsoft work account. Email codes stay available as a way back in.

The administrator named when the workspace was created signs in once to claim it. Everyone else joins by invitation.

People join a company's Studio only when someone with the right role invites them. The invitation says which role they get.

Keep your name and photo current, choose which notices you get, and pick light or dark.

Add a mobile number to your profile and confirm it with a code sent by text.

Someone with a company email address can ask to join, and an administrator says yes or no.

See every agent you can open, grouped by category, with whether each is a draft, Live or waiting for approval.

Start from a blank agent or a starter for a common job, then change anything you like.

Tell the agent who it is, what it is for and how to behave, in plain words, with a preview of what it will be told.

A skill is a reusable piece of know-how, with a note on when to use it. Write one once and share it across agents.

Give agents your help articles, policies and documents to answer from. Studio keeps its copy up to date.

Tools let an agent do things, such as look something up, save a file or send a message. You choose which tools each agent may use.

Turn your own web endpoint or a remote MCP server into a tool your agents can call.

Tools for sending texts, WhatsApp, Slack, Telegram and email, with company rules for each.

Choose what an agent remembers about the people it talks to, and send what it learns to your own systems.

Give an agent named values, such as an opening time or a booking link, that its instructions can use.

Pick which AI model an agent uses from the models your company allows.

Choose whether an agent is off on calls, only listens and takes notes, or listens and talks.

Choose where people can reach an agent: a chat widget on your website, a link, texts and RCS, WhatsApp, Slack, Telegram or email.

When an agent is unsure, it asks a person instead of guessing, and tells them only what they need to answer.

Choose the identity an agent speaks as by default, such as a person on your team or one of your places.

Talk to the draft before anyone else does, look inside each reply, and save good conversations as test cases.

Nothing reaches customers until someone with permission makes a version Live. Studio checks the agent is ready first.

Every published version is kept, so you can see what changed between two of them.

Decide who can see, edit or publish each agent, and invite collaborators to one agent only.

Let other agents build on this one, so a change here reaches them too, and see what a change would affect.

See what an agent has been doing. The words of a conversation stay hidden until someone with permission chooses to show them.

Pause an agent, copy it, hand it to someone else, archive it or take its content with you.

Rules for how long a conversation lasts and when a new one begins.

Write a short script as a tool, with its own settings and secrets, and let agents call it.

Mark a reply good or bad and ask Studio to suggest a change to the instructions.

Reach people through notifications on their phone, as another channel.

Keep the company's people and places in one list, each with its own page and a short code you can use to refer to it.

Keep identities of your own, for agents you build for yourself.

Decide once which details every identity has. Name, company, communication style, background and voice are built in; you can hide them or add your own.

Studio checks what is typed into an identity's fields, such as whether a name looks like a name, before it is saved.

Give a person or place its hours, so workflows know when it is open.

Each identity an agent acts as can have its own email address, phone number, voice address, link and website chat widget.

Messages can come from the company's shared RCS sender, or an identity can have its own.

Connect an identity's own mailbox and calendar, so an agent can send as them and check when they are free.

Add photos of a person or place, with a note on when an agent should use each one.

Bring in many identities at once from a file. Studio shows every row before anything is saved.

Set the layout and logo placement for email your agents send, once for the whole company.

Connect an identity's Outlook mailbox and Microsoft calendar, as with Gmail.

See every way a customer has reached you, which agent and identity answered, and when.

Let an agent draw a picture of an identity from its reference images, labelled as made by AI.

See the company's workflows, and read a short guide to how a workflow runs.

Add, move and remove steps on a canvas, with the chosen step's settings beside it.

Start a workflow on a schedule, when an app sends an event, when a conversation arrives, or when another system calls it.

Hang extra steps off a step for when someone is interested, replies STOP, or the step fails.

A step that checks whether a person or place is open now, and sends the workflow one way or the other.

A first step that greets the person, looks them up in past conversations, and hands them to the right agent, such as sales or service.

Say what counts as someone engaging, such as replying or booking, so each can start a side chain.

Drafts that need a person before they are sent, from every workflow, in one place.

Give any outside system its own address to call, and map what it sends into a workflow or an agent.

See each time a workflow ran, and step in when one needs it.

Make a workflow Live, go back to an earlier version, or archive it.

Tell your own systems when a workflow does something, by sending them a signed message.

If two agents or identities wrote to someone and they reply, choose whether the reply goes to the latest, to both, or is read to decide.

Share new conversations between identities in turn, such as sales reps who are available, and keep returning people with the same one.

Pick which identity an agent acts as on each step, so the same agent can appear three times as three people.

Label outgoing messages with a topic, so opting out of marketing never stops order updates, and route replies by keyword.

A step that scores or checks the work of earlier steps, and workflows that only evaluate.

Repeat a set of steps, such as a follow-up every few days, until someone replies or a limit is reached.

Remind people who haven't answered, and pass work through more than one review before it goes out.

Connect business apps such as a CRM, payments or email with a browser sign-in, using Falcon's sign-in or your own.

Connections that belong to you, such as your own mailbox, and what may use them.

Send your agents' email from your own domain, through SendGrid, or through any mailbox that offers SMTP and IMAP.

Connect your Twilio account to send and receive texts with your own numbers.

Give an identity its own phone number for incoming calls, and let calls outside hours go to an AI voicemail that takes a message.

Connect an Amazon S3 bucket so agents can save, read and list files, and share files by link.

Let a system send events to Studio, so a workflow can start when something happens there.

Set which domains the company's links and addresses use.

Install the GitHub app for your organisation and choose which repositories agents may work in.

Describe your own REST API once and turn its endpoints into tools.

Keys that let your own systems send messages through your agents' channels.

The company's name, logo, colours and images, previewed before you apply them.

See everyone in the company, invite someone new, and make a person inactive when they leave.

Upload a list of people with their roles and send all the invitations together.

A role is a set of things a person may do. Use the built-in roles or make your own.

Decide how people sign in, whether a second step is required, and how long sessions last.

Let people sign in through the company's own Microsoft tenant or identity provider.

One place for the checks Studio runs on what people type, such as identity details, with a way to try each one.

The groups agents are sorted into on the Agents page. Every company starts with a set.

Choose which AI models agents may use, and set daily and monthly spend limits, so a runaway loop can't run up a bill.

Use your own key for a model provider, such as OpenRouter or xAI, so that spend is on your account.

Use OpenAI directly, any OpenAI-compatible service, or your company's own Amazon Bedrock.

See the company's plan, keep payment methods, and download invoices.

A record of who changed what, and when, across the company.

Answer people's requests to see or delete their data, and export what the company has written.

Run your agents in Falcon's AWS account, or in your company's own.

How much each agent is used, across the company or for one agent.

How often each workflow ran, and how often it finished, failed or waited for a person.

What the company spent on models and services, by agent, workflow and day.

Download a report as a file, or have it sent on a schedule.

Choose, for each agent, how much detail Studio keeps about its work.

Open the panel on any page, ask a question in your own words, and get an answer about that page.

Describe an agent or a workflow in your own words, answer a few questions, and Studio drafts it for you.

Connect an AI assistant to Studio over MCP and sign in as yourself.

When an assistant asks to do something risky, such as publish or send, it waits until you approve it in Studio.

Administrators decide whether people may connect assistants, and what those assistants may do.

The same operations as MCP, over HTTP, each described with when to use it and who may call it.

Show parts of Studio inside your own app, so your users can shape their agents there.