Channels
Team context, shared momentum
6 members
@Ola, report what is still open this week.
Ola
Six items found and synced to the team task list.
Marcus picked up item three
Visible to everyoneAnyone can continue
Your New
Favorite Hire
Your proactive teammate, right where you already work. It lives in Feishu, Lark, WhatsApp, Slack and Teams.
What Ola handles for youPrompt
@Ola Just back from a trip — what got decided here this week and what’s still open?
Catch up in seconds
Back from a trip and nothing to scroll through. Settled, still open, and waiting on you — sorted into three, each line noting who said it and when.
go-to-market(23)
Sarah Klein09:03
Latest pricing draft moves to per-seat. Copy lands Friday.
Marcus Webb09:05
Are we keeping the old entry point? Option two from last week is still open.
Daniel Reed09:12
@Ola Just back from a trip — what got decided here this week and what’s still open?
3 replies
OlaAGENT09:13
- Read this week’s 214 messages from the top.
- Sorted what’s settled from what’s still pending.
- Wrote the summary.
todos as of 09:13
09:14
Decided:
- Pricing moves to per-seat — ships Monday, copy due Friday.
- The old entry point stays until the end of September, then goes.
Still open:
- Whether overseas pricing gets its own model — nobody has picked it up since Wednesday, four days stalled.
- Who chases Legal on the compliance wording. Sarah raised it but never assigned it.
Message go-to-market
Installed and running in two minutes
Connect your tools, hand it to Ola, and get the result in minutes.
Completed task
Weekly business report delivered
Sent to the #business-results channel
Completed just now
Work hub
Where you talk to it
FeishuLarkWhatsApp
Reach Ola in DMs or channels
Connected tools
GitHubNotionLangfuse
Also works directly in Base and Wiki
- 01Install
Add it to Feishu or Lark
Install it from the app directory. Two grants and one admin approval later it shows up in the workspace, like any new teammate.
- 02Connect
Connect your tools
Link GitHub, Notion and Langfuse once each. Every connection is one more thing it can act on, not just read.
- 03Assign
Assign your first job
Pick something that normally eats your week. It does the job — then runs it every week on its own if you want.
One Ola, two information boundaries
Channels use team context and share the result with everyone. DMs belong to you, and never return to a channel.
#project-delivery
DMs
Personal context, kept separate
You and Ola
Prepare me for tomorrow’s customer meeting.
Ola
Everything is ready, visible only in this DM.
Never carried into a channel
Works only for youPrivate content stays private
Not a plugin, a colleague
Its own account
It never borrows anyone’s login. Admins grant access centrally, and anything outside that it refuses outright.
Memory across days and people
Why the team decided what it did last month is still there today. People move on; the memory stays.
A shared resource in the channel
Everyone sees the work, not just whoever asked, and anyone can pick up the thread. Nothing to forward.
No waiting turn by turn
Send things as they occur to you. Ola stitches the fragments into one task and works them in the order you gave.
Long jobs run in the background
A long task never ties up the conversation. Carry on with your day; it comes back when it’s done.
Set it once, it keeps running
A morning briefing, a weekly roll-up — it starts on schedule without anyone remembering to ask.
You stay in control
High-risk actions wait for approval. If you cannot access it, neither can Ola.
Irreversible action
Confirm first. Then act.
Ola requests approval
Delete 128 rows from the Q3 Research table
Send backApprove and run
Least privilege by default
If you cannot see it, neither can Ola.
Every request follows your company’s existing identity and permissions.
Access granted per person
Revocable at any time
Never training data
Not just connected to your tools — he uses them
Some apps are still being connected — see the status of each tool
Start free, pay when you are ready
Free
For individuals and small teams kicking the tyres. Everything is switched on.
Credit and usage
- 1,000 credits per month
- No card, no sales call
Features
- The full assistant, every integration
- Background tasks and scheduled runs
- Team memory
Pro
For a team getting real work done.
Credit and usage
- 10,000 credits per month
- 10x the Free allowance
Features
- Everything in Free
- Priority support
Max
For teams that run on it.
Credit and usage
- 100,000 credits per month
- 10x the Pro allowance
Features
- Everything in Pro
- Priority support
Still have questions? Read the FAQ, or talk to sales.
Anything else?
Who Ola is, what it can and cannot touch, and how to get it running.
Ola is a new member of your team. It has its own Feishu account, and an admin sets up its channels, permissions and document access the way they would for anyone starting on day one. It is not attached to any individual, and nobody has to log in or authorize anything for it to work.
Think single-player versus multiplayer. A personal assistant is single-player: it lives inside your account, borrows your identity and your permissions, works for you alone, and disappears when you switch tools. Ola is multiplayer — an independent teammate with its own account, its own permissions and its own identity.
Feishu, Lark and WhatsApp. Mainland teams use Feishu; Hong Kong and international teams use Lark, with identical capabilities either way. Pair WhatsApp once and you get DMs, groups, voice notes and audio uploads — the same Ola as in Feishu, sharing one set of permissions, memory and tasks.
Feishu, GitHub, Notion and Langfuse. In Feishu it handles docs, tasks, calendar, messages, Base and Wiki. In GitHub it answers questions about the codebase, reports on activity, manages PRs and files issues. Notion covers doc sync and automation; Langfuse covers quality scoring, deep analysis and live monitoring.
No. Every action is graded by risk first. Low-risk work — reading, looking things up — runs without bothering you. Anything irreversible or wide-reaching, such as deleting, overwriting, moving, bulk-editing or publishing externally, stops and shows you a card listing exactly what it will do. Several confirmations in one instruction are merged into a single card rather than a stream of interruptions.
Four roles: viewer, member, admin, owner. Data permissions split by operation — read, cross-person search, edit and delete are granted separately, with scopes running from own-records-only to everything. High-risk actions such as deletion require a second person; whoever requested it cannot approve their own. Admins adjust all of this from the console, changes take effect immediately without re-login, and every change is written to an audit log.