Assistant: giving your operator work
Message your operator like an assistant: it does the work, connects your tools, reads your files, and holds anything outbound for your approval.
Assistant is where you give your operator work. Ask the way you would ask an assistant, and it does the job on your own server while you watch: it reads, researches, drafts, updates your CRM, and shows each step as it goes. It is the first screen you see when you sign in.
What you can ask for
- Answers from your own data. Who called this week, what a lead said last time, what is in your pipeline.
- Drafts. A follow up to your last meeting, a reply to a lead, a message to your team.
- Updates. Notes, tags and tasks in your CRM happen straight away, because they stay inside your business.
- Anything it cannot do yet. It says so, and files a request with our team for you, so you do not have to write it up.
Anything that would reach another person, an email, a text, a team chat message, a change in another service, waits on a card with the exact words. Nothing goes out until you press Approve. You can edit an email on the card before it sends.
Connecting a tool
You do not need a settings screen. Paste the address of the tool, a key, or just its name, and your operator connects it:
- A tool with its own connector. Paste its address. If it needs you to sign in, you get a Sign in button that opens the service's own page.
- A key. If you paste something that looks like a key, the page stops it before it is sent, stores it securely on your server under a name, and the conversation only ever shows the last four characters.
- Any web API. Your operator can read from it straight away. Anything that would change something in that service is shown on a card first, exactly as it will be sent.
Setting up your tools, together
You do not need to know how anything connects. Tell your operator what you use ("I use Gmail and track deals in a spreadsheet") or just ask it to help you get set up. It checks what is already connected, recommends what fits if you have nothing for a job yet, walks you through getting access in a few short steps, collects any key in a secure box, and tests the connection before telling you it works.
- Your own mailbox. Give it the address and it asks for the password in a secure box. Gmail, Google Workspace, Outlook, Yahoo, iCloud, Zoho and Fastmail are recognised, and it explains when the provider needs an app password. Both logins are tested and nothing is sent.
- A live web browser. With a Browserbase account (free to start), your operator opens live pages the way a person would, including sites that block simple lookups. You paste one key; the rest is filled in for you.
- Any other app. By sign-in, by key, or by pasting the link its makers give you.
Teach it once
Show your operator how you like something done ("when I say morning pulse, give me the date, anything waiting for approval, and one line of encouragement") and it saves the steps. Next time you ask, it recognises the request and does it your way. It gets better on its own too: every morning it reviews its recent conversations, learns from anything that went badly, and flags what it still cannot do to the team that builds it.
Ask from anywhere
Every page of your portal has an "Ask" button. Type what you want where you are and the assistant opens with it already underway.
Chats, folders and models
Keep chats in folders, pin the ones you use most, and rename or archive them from each chat's menu, or just ask ("put this in a folder called Sponsors"). New chats name themselves. You can choose the AI model for each chat from the model menu at the top.
Files, screenshots and your voice
Drop a file or a screenshot into the conversation, or use the paperclip. PDFs, Word, Excel, PowerPoint, text and images all work. Tap the microphone to dictate, or choose Talk hands-free to speak, hear back and carry on without touching the keyboard. Where your operator has an approved voice, it can read its replies aloud in that voice.
Who can approve what
Yes. Everyone on your team has their own conversations. The account owner can approve anything; a team member can approve only what they asked for themselves.
Yes. While it is working there is a Stop button. Anything already waiting on a card stays there until you decide.
Talk is a conversation with your operator. Assistant is delegation: each request becomes a piece of work it carries out, with its steps shown and anything outbound held for your approval.
It waits. When your workspace needs a restart, it first lets the task it is working on finish, and anything you send meanwhile waits in line. If a restart cannot wait (a longer job, or the machine rebooting), what it had already written stays in your conversation, it tells you it was restarted, and it picks up where it left off without redoing finished steps.
Was this page helpful?