FlowGenX AI Teammate · AI that works for you
The AI teammate
that does the work.
In Slack, Teams, Google Chat and Discord. It runs proactive workflows on schedules or app events, asks before it acts, and traces every run.
One teammate · four channels · your apps
What teams hand to it
Real jobs, replayed step by step.
Pick a job. Each one replays a run recorded from the product, in the channel it happened in. The recording itself is one click away.
Talent ops drops two CVs into Slack. Back comes a scored Excel workbook.
Weighted on the criteria the hiring manager set: 8.5 vs 5.4, Proceed vs Hold, with the reasoning per row. The workbook lands in the thread, not in a private tab.
The run
What you get
It shows up, remembers, learns, acts — and stays governed.
Six things a tool never does and a colleague always does. Every one is a shipped capability you configure, not code you write.

Slack
Ethan Carter APP

Microsoft Teams
Ethan Carter APP

Google Chat
Ethan Carter APP

Discord
Ethan Carter APP
One account, one memory, one set of permissions. Connected from one page, in about three minutes each.
Semantic · what is true about your business
Acme renewal owner: Maria Chen · fiscal year starts Feb
Episodic · every run it has made
Mon 08:00 pipeline digest · 14 stalled deals flagged
History · every tool call, in order
salesforce.opportunity.get → knowledge.search → update_quote
Knowledge base · your documents, cited
Drug-Testing-Policy.pdf · HR-Handbook-2026.pdf §4.3
read before every turn
emea-stalled-deal-scan
threat-scanned · savedDistilled from Monday’s run. Tool allowlist: read-only.
salesforce.opportunity.listsheets.read_rangeworkbench.chartFirst run
29
tool calls
With the skill
2
tool calls










5,000+tools it can callyoursAPIs · MCP · workflows- Mon 08:00routine
Pipeline digest
reports back in #revops · Slack
Weekdays 09:00routineClickUp status digest
reports back in #general · Discord
On eventwatcherDiscount request lands in the CRM
reports back in asks the AE manager
On webhookwatcherConnector auth expiring
reports back in re-authorises, tells the owner
Set up by saying “I want a routine” in any channel.
- knowledge.searchreadsAutosalesforce.opportunity.getreadsAutoupdate_quotewritesAskslack.post_messagewritesAskPII and secrets maskedPause, every channel
Slack
Ethan Carter APP
Microsoft Teams
Ethan Carter APP
Google Chat
Ethan Carter APP
Discord
Ethan Carter APP
Human in the loop
Approve once. Always allow for team. Deny.
Every tool is on or off, Auto or Ask first. It asks before it acts, right in the thread.
Native in every channel
Buttons in Slack and Discord, reaction chips in Google Chat, a card or typed answer in Teams. The same three choices everywhere.
Park and resume
Answer now or in three hours. The run keeps its context and resumes exactly where it stopped, no re-prompting, no lost work.
Ask mode
When on, it asks before every action, not just sensitive ones. “Always allow for team” flips a tool to Auto for everyone. Try the button →
Ethan Carter app 11:40 AM
I’ll update the Acme quote to the approved 12% discount.
Before I do this, I need your okay:
update_quote · Salesforce · writes
⏸ parked · waiting 00:00 · or reply approve · always · deny
Pulse
It notices before you ask.
Turn on proactive mode and it listens to the apps it works in, sorts every event, and keeps the loops nobody else is tracking: meetings to prepare for, replies owed, follow-ups, escalations.
Listening
The apps and events it watches.
Duties
What it does about them: meeting prep, briefs, escalations, your own rules.
Notifications
How it reaches you: DM, team channel, inbox or email.
Freedom
How much it may do on its own: Observe, Assist or Autonomous.
You decide how far it goes alone.
Set it for the Teammate, then per duty. Start in Assist and raise it once the drafts look right.
Observe
Watches and tells you. Never drafts or changes anything in your apps.
Assist
Does the research and prepares drafts. Anything it would send or change waits for your okay.
Autonomous
Makes the changes the work needs.
Still asks before deleting, paying, sharing or changing permissions.
Voice and phone
Talk to it. Or have it make the call.
The transcript lands back in the thread, and the work it took on keeps going after you hang up.
Web voice chat
One button in FlowGenX Chat. The call joins the conversation you have open.
From any channel
Slack and Discord get a Join button. Teams and Google Chat get a personal link.
By phone
Call your Teammate, or have it call someone for you.
In meetings
It listens in on a Google Meet and files the action items.
1 · The brief
- Goal
- Confirm the Tuesday 2 pm demo
- May share
- Agenda and attendees
- Must not
- Agree to pricing
- Find out
- Who else will join
2 · Nothing is dialed until you approve
3 · On the call
Ethan: Hi Priya, this is Ethan, the AI teammate at Acme, calling for Dana about Tuesday’s demo.
It speaks as an AI teammate, never as a person, and only uses the apps and knowledge the brief allows.
4 · Back in the thread
Goal met: Tuesday 2 pm confirmed, and their controller joins too. Summary, full transcript and next step attached.
Hands and memory
5,000+ tools. Including yours. And it remembers how it used them.
Connected apps, imported APIs, MCP servers, and your own workflows and agents: one tool surface, one set of controls. Every tool is on or off, Auto or Ask first, masked and traced the same way. A good run is distilled into a skill: an invoice status query went from 29 tool calls to 2.
Connected apps
Every endpoint of your apps — Salesforce, HubSpot, Jira, Gmail, Snowflake, Xero, QuickBooks, Zendesk and more — called by name.
Imported APIs
Import any OpenAPI or Postman spec and its endpoints become tools in seconds. One spec in, 77 endpoints the Teammate can call.
MCP servers
Your own MCP servers, inherited from the account’s connections and governed like every other tool.
Four memory surfaces
Semantic (what is true), episodic (what happened), history (every call, in order) and your knowledge base, cited. Read before every turn.
Specialist agents
Two ways to build a specialist.
Describe the job in plain words, or design the steps as a workflow. Your Teammate brings in either one, the same way it uses any tool.
Declarative agent
Configured in natural language. For business users, analysts and domain experts.
- Built with
- A job description, instructions, knowledge and tools
- Who sets the steps
- The model plans the steps and picks the tools
- Predictability
- Varies with the model’s reasoning
- People in the loop
- Through approval tools or a delegated workflow
- State and recovery
- Conversation and task context; tool-level retries
- What you can inspect
- Reasoning summaries and tool-call logs
- Best for
- Research, analysis, recommendations, ad hoc work
Workflow agent
Built in the workflow builder. For developers, architects and power users.
- Built with
- FlowGenX Companion or the drag-and-drop workflow canvas
- Who sets the steps
- The workflow; models decide inside individual steps
- Predictability
- Follows the orchestration you defined
- People in the loop
- Approval, review and escalation steps on the canvas
- State and recovery
- Checkpoints, history, retries, exception and compensation paths
- What you can inspect
- Node-level traces, status, errors and timings
- Best for
- Multi-step operations, approvals, system updates
Teammate investigates. Workflow enforces. A person decides.
On one deal, a declarative Deal Strategist works out the approach. A workflow agent then generates the proposal, waits for the VP of Sales to approve, and updates the CRM. The thinking varies with each deal. The steps never do.
The film
Five minutes. Every second is the real product.
Seven jobs recorded live in Slack, Discord, Teams and Google Chat: hiring, sales charts, routines, a customer report, live store data and company policy.
Governance
Autonomous, but never unaccounted for.
The controls an enterprise expects of a human teammate, scope, approvals, an audit trail and an off switch, apply to the Teammate.
Every run, on the record.
Every chat, routine, Pulse event, task and meeting is a run you can open: where it came from, what triggered it and how it ended. When someone asks why it did that, this is the answer.
- Filter by channel, status or trigger
- Turns, tools and tokens for every run
- Failed turns flagged where they happened
- Replay any run step by step, or follow a live one
- Success rate and p95 duration over 24 h, 7 d or 30 d
| Run | Status | Turns | Tools | Flow |
|---|---|---|---|---|
Find every stalled deal in EMEA Slack · #sales-emea | Completed | 3 | 8 | Flow |
Pulse: invoice.created Pulse · QuickBooks | Completed | 1 | 15 | Flow |
Pulse: Daily brief Pulse · Daily brief | Completed | 1 | 6 | Flow |
Attended weekly ops review Meeting · Google Meet | Completed | 1 | 0 | Flow |
Overdue invoice digest Routine · Weekdays 08:00 1 failed turn | Failed | 2 | 11 | Flow |
End-to-end trace of every run
Every tool call, decision and approval logged in order and attributed to the Teammate. Open any run, replay it step by step, compare versions.
Scope inherited, never expanded
It acts only through the apps, MCP servers and credentials of the account that owns it. Unequip a skill and its tool routes disappear.
Auto or Ask, per tool
Tools that act ask in the thread: approve once, always allow for team, or deny. Parked asks resume when answered.
Credentials used, never read
A stored credential is invoked without the secret ever reaching the model. Channel tokens stay encrypted, decrypted per call.
PII and secrets masked
Masking rules for email, card numbers, SSNs, IP addresses and secrets apply to tool results, cards and answers — not just a warning.
Bounded runs
Loop guardrails warn, block and halt on repeated failures. A watchdog bounds every call; bursts are queued, never dropped.
Channel security, fail-closed
Every inbound message is signature-verified; unknown senders, other bots and duplicates are dropped before anything runs.
Pause, one switch
Pause quiets every channel at once on the next message — no cache to wait out, no redeploy. Resume brings them all back together.
SOC 2-ready: controls implemented and operating. Memory is account-scoped; the knowledge base is read-only; your models, your keys. Execution in your cloud or ours.
Ready-made
One Teammate per role.
Nine ready-made roles arrive configured with identity, skills, starter routines and apps. Edit any of them before you publish, or start from scratch. Start with one.
Finance & Bookkeeping
Receipt follow-up, invoice reminders and close-pack preparation.
Customer Support Lead
Ticket prioritization, grounded reply drafts and knowledge gaps.
Sales & CRM Operations
Deal briefs, enrichment, follow-ups and forecast support.
Data Analyst
Metric analysis, queries, anomalies and recurring reports.
Executive Assistant
Meeting briefs, calendar coordination, inbox and action follow-up.
Technical Product Manager
Requirements, sprint visibility and stakeholder updates.
Recruiter & HR Partner
Candidate shortlists, interview coordination and follow-up.
Social Media Manager
Content plans, approved publishing and engagement reviews.
SEO Specialist
Search audits, content briefs and ranking updates.
Not the same thing
Not an assistant. Not a script. Not a single-task agent.
Nine things an enterprise needs from an AI teammate, and which category delivers them.
| What an enterprise needs | AI assistant | Scripts & RPA | Single-task agent | FlowGenX AI Teammate |
|---|---|---|---|---|
| Present in your channels as a named teammate | ||||
| Remembers across runs, threads and surfaces | ||||
| Learns its own job into reusable skills | ||||
| Acts across 5,000+ tools in your apps, plus your own APIs | ||||
| Works unattended on schedules and events | ||||
| Asks in the thread, parks and resumes when answered | ||||
| Takes work by email, meeting, phone, photo and voice, not just chat | ||||
| Bounded runs: approvals, masking, trace, pause switch | ||||
| Promotes a proven routine into a governed workflow |
✓ delivers · – partial or bolt-on · ✕ absent
Getting started
A working teammate in about fifteen minutes.
Included in the 30-day trial. Prerequisites: a FlowGenX Chat account and at least one connected app. Then six steps.
Open Teammate Studio
From the left rail in FlowGenX Chat. A draft Teammate is created for you, and Flo, the in-app guide, can fill in any page for you to review.
Pick a ready-made Teammate, or give it an identity
Nine personas arrive configured with identity, skills, starter routines and apps. Or set a name, title, traits and a job description.
Connect a channel
Slack, Microsoft Teams, Google Chat or Discord, from one page. Event triggers are set for you.
Equip skills, set Auto or Ask
Apply the role recommendations; every tool on or off, Auto or Ask first. Start in Ask mode.
Switch it on
One switch publishes the persona. It takes effect on the next message.
Give it real work
@mention it in the channel: a policy question with a citation, then a tool action. Open the trace.
Runs where your data lives
SaaS
FlowGenX-hosted
Fastest to start. Connect your systems and a channel from one page, configure the role, switch it on.
Hybrid
Managed control plane, execution in your network
Sensitive tool calls and data stay inside your network; orchestration and studio stay managed.
Private runtime
Execution plane inside your VPC
The full execution plane runs in your cloud account for regulated workloads. The control plane stays managed.
Deploy the teammate.
Keep the authority.
Name the role, the three systems it reaches and the person who approves. Fifteen minutes to switch one on; a four-week pilot in Ask mode with the trace open.