Your CRM, inside your AI
Connect Orkasa to Claude or your assistant and ask about your deals the way you would ask a colleague. It does not answer from memory: it reads your real data, right now.
ver_expedienteReading the file · 5/5- ✓Operation
- ✓Property
- ✓Viewings
- ✓Documents
- ✓Messages
Ask the buyer for their file
Without a file, no offer the seller takes seriously
The same question you would ask a partner. What comes back is not a table row — it is the file, with the next move inside it.
What you can ask it
Five questions, each answered in one go. No stitching the file together across screens.
“How is the Herrera deal going?”
The whole file: her operations and what stage they are in, the property, viewings, offers, documents and the latest messages.
“What do I have today?”
The next moves the Copilot recommends, in order: what depends on you first, and within that, the most overdue.
“What do I have in Chapinero under 600 million?”
Your portfolio filtered by area, type, price, bedrooms — for sale or for rent.
“Who am I seeing tomorrow?”
Your viewing schedule, with the client and the property for each one.
“Do you have Marta’s phone number?”
Search by name, phone, email, address or neighbourhood.
And what it can do
Four actions, and the list is short on purpose: only what a sentence is enough to really mean.
- Create a clientWith their contact and their buy or rent operation opened.
- Book a viewingConfirmed in your country’s time, not ours.
- Move an operation forwardOne step at a time, with the same locks as the Pipeline.
- Record an offerLogs the amount and conditions. It does not accept it for you.
And above all, what it does not do
If a stage is missing documents, the operation does not move — not here, not anywhere. The assistant does not force the lock: it tells you exactly what is missing, and stops there. Publishing a listing, generating a mandate or sending something for signature do not go through here either: those carry your name on a document, and they start with your eyes on the screen.
What it sees, and what it does not
- You choose the permissionsBefore anything connects, you see the exact list of what it asks for — “See your leads”, “Book viewings” — and you approve only that.
- It sees what you see, no moreIf in Orkasa you only see your own assigned clients, your assistant will not see the rest of the office either.
- One click cuts it offSettings › Connections lists the assistants with access, who authorized them and when. One button disconnects them.
- It never leaves your agencyEvery query is stamped with your agency. Another agency’s data does not exist for your connector.
How to connect it
No keys to generate, nothing to install. Three steps, once.
- 1Copy the addressIt is in Orkasa, under Settings › Connections, on the “Claude · ChatGPT” card.
- 2Paste it into your assistantIn its settings, where you add a custom connector.
- 3AuthorizeYou come back to Orkasa, review the permissions and accept. Done.
One detail we would rather tell you up front: adding a custom connector is a paid-plan feature in Claude. On the free version, the option does not appear.
Shall we try it on your data?
In a demo we connect it live and you ask it about one of your own deals. It is the shortest way to see whether it helps.
Technical, and want the protocol detail? The connector documentation
