FLAE

English

Tiếng Việt

English

Tiếng Việt

Appearance

FLAE overview ​

What it is ​

FLAE runs parts of a company's operations with Agents: LLM workers that answer customers, look things up and act in the Apps you connect (Zalo, Facebook, Haravan, Gmail). People stay in charge: they build the Agents, approve what needs approval and take over when an Agent hands work to them.

The left menu of a Workspace has:

PartPages
TopChat (the FLAE Assistant, and the Workspace's home page), Runs
InboxAgent Inbox, Contact Center
BuildAgents, Tools, Skills, Workforces, Automations, Knowledge
SettingsIntegrations, Workspace

Key concepts ​

How FLAE is organised: Organization → Workspaces → members. Your company is one Organization. It holds one Workspace per business area, and each Workspace has its own members, Apps, Agents and data. What you can do in a Workspace depends on your role there.

Glossary

  • Organization — your company in FLAE; you create it when you sign up, and it holds your Workspaces. See Organization.
  • Workspace — one business area of the Organization, such as Customer Operations, with its own Agents, Tools, Apps, Contacts and members. See Workspace settings.
  • Member roles — Organization roles (Owner, Admin, Member) and Workspace roles (Admin, Builder, Operator, Viewer) decide who builds, who operates and who changes settings; Organization Owners and Admins act as Admins in every Workspace. See Workspace settings and Organization.
  • Agent — an LLM worker that reads a request, decides what to do, calls Tools and hands over to a person when a rule says so or when it is not sure; chat Agents answer messages and voice Agents take calls. See Agents.
  • Tool — a fixed, reusable action that Agents and Workforces call, built from steps such as App actions, LLM steps, Branch and Loop, that does the same thing every time. See Tools.
  • Skill — know-how written once (a refund process, a brand voice) that every Agent having it opens when a request matches. See Skills.
  • Knowledge Base — a set of documents your Agents search and quote; Public ones are read in customer conversations, Internal ones only in Workforce steps without a conversation. See Knowledge.
  • Workforce — a team of Agents, Tools and logic on a canvas, for work that needs several Agents, fixed steps, or a person's approval between steps. See Workforce.
  • Automation — puts Agents and Workforces to work on their own: a Message Automation lets an Agent answer a Facebook Page on Messenger, an App event Automation runs a Workforce when an App sends an event. See Automations.
  • Run — the record of Agent work for one conversation, Automation run, call or test, with its turns and steps; runs are listed on Runs and kept for 30 days. See Runs.
  • App — an outside service connected to a Workspace on the Integrations page; today Gmail, Facebook, Haravan and Zalo. See Apps and Workspace settings.
  • Action — one thing an App can do, such as Haravan "Get order" or Zalo "Send text message"; a Tool step runs an action, and each App's page lists its actions' inputs and outputs. See Apps.
  • Event — something an App reports to FLAE, such as a new Haravan order or a Zalo message received; today Haravan and Zalo send events, and an App event Automation can start a Workforce on one. See Automations.
  • Contact — the record of one customer, a Person or an Organisation, with phone, email, channel identities, facts and a brief; Agents read it through {{contact.*}} variables. See Contact Center.
  • Conversation — a customer's messages to one Page on one day and the replies; today conversations come from Messenger and show in the Contact Center. See Contact Center.
  • Approval — a request for a person to allow a Tool call before it runs, answered in the Agent Inbox; an Agent's Tool approval goes to whoever started the run, a Workforce approval to the connection's Approver. See Agent Inbox.
  • Report — a note from an Agent about results or progress in the Agent Inbox; it needs no answer and does not hold the run. See Agent Inbox.
  • Trace — FLAE has no separate trace page: the step-by-step record of an Agent's work (each LLM call, Tool call, Knowledge search and wait for a person) is a run's Timeline on the Runs page. See Runs.
  • Eval — a test suite that scores an Agent or Tool; not working yet: an Agent's Evals tab is a preview that saves nothing, and Tools have none. See Agents.
  • LLM — the language model an Agent, an LLM step or an LLM Condition runs on; you pick it per Agent, where each model shows its price. See Agents.
  • Credits — FLAE's unit for model prices, 1 credit = $0.01; plans and balances are not live yet, so the Credits shown in the left menu and on your profile are sample numbers. See Account and billing.
  • FLAE Assistant — the assistant in Chat that explains FLAE, answers questions about your Workspace and data, and builds draft Tools, Skills, Agents and Workforces. See Chat with the Assistant.

How it works ​

  1. Connect Apps. A Workspace Admin connects Gmail, Facebook, Haravan or Zalo on Settings → Integrations. Tools and Automations act through these accounts.
  2. Build. Make Tools from App actions, write Skills, add Knowledge Bases, then build an Agent that uses them. For work with several Agents or fixed steps, place them on a Workforce.
  3. Test and publish. Agents, Tools, Skills and Workforces are edited as a draft and used only once published. Everything that runs uses the published version.
  4. Put to work. An Automation starts the work: an Agent answers a Facebook Page on Messenger, or a Workforce runs when an App event arrives.
  5. Operate. Agents ask for approval, ask questions, hand over and report in the Agent Inbox; customer conversations and Contacts live in the Contact Center; Runs shows what each Agent did, step by step.

The FLAE Assistant in Chat can do much of step 2 for you as drafts, which you then publish.

Common tasks ​

Limits and rules ​

  • Building (Agents, Tools, Skills, Workforces) needs the Workspace role Admin or Builder. Automations, connected Apps and Workspace settings need Admin. Organization Owners and Admins can do all of it in every Workspace.
  • Pausing an Agent does not stop it: channels, Automations and Workforces that use it keep running its published version. To stop them, turn off the Automation or remove the Agent from the Workforce.
  • A Tool that writes data and that FLAE recommends approving starts on Ask first on an Agent; only a person can switch it to Auto, in the Agent builder.
  • The Assistant builds drafts. It publishes only Tools; you publish Skills, Agents and Workforces yourself.
  • Credits are not live: no plan, balance or limit applies to your work today.
  • Inviting people to a Workspace and changing roles are not available in the app yet.
  • Nothing can be changed in an archived Workspace.