Product · chat & messengers
The money questions get asked in the chat anyway.
Somebody asks what is left in the budget in a group chat, and the answer arrives hours later from whoever opened the app. Connect the space to that chat and the answer is already there, from the same ledger, only for the people who are allowed to see it.
A group or a channel, bound to one space
An owner or admin mints a code and pastes it in the Telegram group or the Slack channel. The chat then carries that space's invoices, card events, budget warnings, automation results, goals and approval requests, and a Monday summary that stays quiet on a quiet week.
Ask in words, not commands
Name it in a group, reply to something it said, or just write in the DM. Commands still exist and still answer instantly without spending an AI message, so the fast way to see balances is still the fast way.
Its memory is the thread, and nothing else
In Slack it reads the thread it is answering in. In Telegram it reads the message being replied to. Nothing is kept on Orla's side, so what it remembers is exactly what the people in that chat can already see.
Buttons that check before they act
Approve or reject a payment, freeze a card from a fraud alert. Permissions are checked when the button is pressed rather than when it was drawn, so a button that has gone stale refuses instead of acting on an old assumption.
The client gets their own chat
Bind a chat to one contact and it receives that client's invoices, payment confirmations and overdue reminders, with a Pay button. Nothing else from the space reaches it, the client needs no Orla account, and a client chat never talks to the AI.
Send the receipt as a photo
Photograph it and send. A receipt comes back as a draft expense with a Save button and nothing is written until it is pressed. Anything else is filed into the space's Documents under the type it recognised, with a button in case the guess was wrong.
A screen inside Slack
The Home tab shows balances, open invoices and the last few transactions for the space you are on, plus two real forms: add an expense, or raise and send an invoice. A viewer sees the numbers without the buttons.
Everyone else in the room gets silence.
Commands and questions answer members of the connected space only. Not a polite refusal with a number in it: nothing at all.
- Where
- Telegram groups and private chats, Slack channels and DMs
- Space kinds
- Family, group and business, never a personal space
- Plan
- Space and client chats are on paid plans; personal chats and DMs are on every plan
- Connect code
- Single use, expires in 15 minutes, only works for whoever minted it
- Who is answered
- Members of that space, viewers may read but not ask the AI
- What lands there
- Payments, cards, budgets, groups and splits, chosen by checkbox
- Files
- Photos and PDFs, read as a receipt or filed as a document
- AI cost
- One Copilot message, on the same allowance as the web chat
Does the bot read the rest of our group chat?
No. In a group it answers when it is named or when someone replies to one of its messages, and it sees nothing else that goes on in the room.
Can someone outside the space get numbers out of it?
No. Commands and questions answer members of the connected space only; anybody else gets silence rather than a refusal that leaks the shape of an answer.
Can a client press Pay from their own Slack workspace?
Yes. External Slack Connect members can press the buttons in a client channel, though they cannot type commands.
What happens to a button after someone loses the permission?
It refuses. Permissions are re-checked at the moment the button is pressed, not when the message was posted.
Put Orla in the chat you already use.
One code, one channel, the same ledger.