Glossary
The words Falcon uses, in plain language, in alphabetical order.
Each term links to the guide that explains it in full. The API and MCP keep a few older names: a workflow is a pipeline there.
- Agent
- A named assistant that talks to your customers or does work for your team. You shape it in plain words: instructions, skills, knowledge, tools, memory, voice and channels. See Agents.
- Built on
- An agent can build on another agent. On Built on this, a part is fixed when its switch is off (Can't change), or open as Can add to or Can change. See Base agent parts.
- Check
- A test Falcon runs on what people type, such as an identity's details, before it is saved or used. A workflow step can also be a check instead of an agent. See Checks.
- Draft
- The version of an agent or workflow that people are still changing. Customers never meet a draft; you can test it at any time. See Make a version Live.
- Engagement
- What your company counts as someone engaging, such as replying or booking a meeting. Each engagement can start a side chain. See Engagements.
- Identity
- A person or a place an agent acts for, such as Dana in sales or the Downtown store. Identities are records your company keeps; they never sign in and are not users. See Identities.
- Knowledge
- Documents agents can look things up in, such as help articles or policies. Memory is about people; knowledge is about the company and the world. See Add a knowledge base.
- Live
- The version of an agent or workflow that customers meet and that runs for real. Only someone with permission makes a version Live, and you can go back to an earlier one. See Publish and roll back.
- Preprocess
- The workflow tab whose heading is Before the agent. Those steps run on every message before the agent sees it. See Before the agent.
- Side chain
- Extra steps that hang off one step of a workflow and run only when something happens: someone is interested, replies STOP, or the step fails. See Side chains and retries.
- Skill
- A reusable piece of know-how the company writes once. Each skill sits in one skill category, and each agent checks the ones it may use. See Write a skill.
- Spending
- The company's monthly and daily spending limits, on Settings › Spending. A company that has never saved limits already shows the default policy. See Set the company's spending limits.
- Start
- What makes a workflow run: a schedule, an event from a connected app, a conversation arriving, another system calling it, or another workflow failing. A workflow can have more than one start. See How a workflow starts.
- Sub-company
- A company a System admin adds with Add company. It can use the parent company's model keys, its usage is billed to the parent, and it cannot add companies of its own. See Add a sub-company.
- Waiting for you
- Inbox holds questions, decisions and drafts assigned to you, independently of access to the workflow list. You send a draft as it is, edit it first, or decide not to send it. See Waiting for you.
- Workflow
- A series of steps that runs when something happens, such as a new email, a form, a call or a time of day. Each step is an agent or a check. Like agents, workflows have drafts and a Live version. See Start a workflow.