Run your business from chat: a practical guide to chat-first operations

Chat-first operations means the chat app on your phone becomes the place where you give instructions, review drafts and make decisions, while AI agents do the work inside your existing systems. You don’t log into five tools to move a job forward; you send a voice note from the car, approve three reminders between appointments and read one report in the morning. Your email, accounting file and CRM stay the systems of record. Chat becomes the front door.

For owner-operators and small teams this is usually a better fit than another dashboard, because the bottleneck in a small business is rarely software — it is the owner’s attention, which is spread across sites, clients and a phone. This guide covers why chat works, how to set it up, the house rules that keep it safe, and the risks to manage. It is the hub of our chat operations series, with deeper articles linked throughout.

Why chat beats another dashboard for owner-operators

Dashboards assume you will sit down and go to them. Owner-operators mostly don’t. They are on a roof, in a session with a client, at an inspection or driving between jobs. Chat meets them where they already are, and it has properties that suit delegation particularly well:

• No new app to learn. Your team already knows how to use it, and so do you.
• Asynchronous by default. You send an instruction now; the agent replies when the work is ready. Nobody needs to be online at the same time.
• Rich inputs. A voice note, a photo of a meter, a scanned invoice or a 40-second walk-through video carries more context than a typed form.
• The thread is the record. Request, plan, drafts, approvals and outcome sit in order in one place you can scroll back through.
• Notifications you already manage. You decide which threads buzz and which wait.

That doesn’t make dashboards useless. Bulk work — reviewing 200 transactions, laying out a roster, reading a financial report — is still better on a big screen in the proper tool. Our position is simple: chat for instructions, approvals and exceptions; specialist systems for records and bulk review. An agent that can move between the two is what makes that split work.

A chat-first working day, hour by hour

Here is an illustrative day for a property manager running a small rent roll, working with an operations agent from her phone. The times and tasks are representative, not a report of a specific customer.

Nothing on that list required opening a laptop. Equally, nothing went to a tenant or contractor without her OK.

Choosing the chat app

The four common choices are Telegram, WhatsApp, Slack and Discord, and they suit different businesses. Telegram has strong bot support and topic threads inside groups. WhatsApp is where many Australian customers and tradies already are, but has stricter rules on business automation. Slack suits teams that already work at desks. Discord suits communities and technical teams. We compare them on groups, bots, files, privacy and cost in Telegram vs WhatsApp vs Slack vs Discord.

If you have already decided, the set-up guides go deeper: setting up a Telegram AI assistant covers topics, bots, privacy mode and file limits, and using WhatsApp with an AI assistant covers the Business app versus the Business Platform, and the line between internal and customer-facing use. Cortex works in all four; the channels page lists what each supports.

How to run your business from your phone: eight set-up steps

1. Pick one channel for internal work. Running instructions across three apps fragments the record. You can add others later.
2. Keep business and personal separate. Use a business account or workspace, not the family group chat. It protects privacy and makes hand-over possible if you hire someone.
3. Create one thread per area of work — for example Rentals, Accounts, Sales — rather than one endless conversation. Topics or channels make this easy.
4. Connect systems narrowly. Give the agent the inbox, folders and CRM views the first tasks need, and no more.
5. Write your house rules (below) and pin them where the agent and your team can see them.
6. Set approval rules: what always needs your OK, and who else can give it.
7. Set one report time for the daily summary, and turn off per-task notifications.
8. Start with a low-stakes task such as research or draft replies, and widen from there.

House rules for running a business from chat

Chat is informal, which is its strength and its risk. A short set of written rules, agreed once, prevents most problems. Here is a starting set; adjust it to your business.

Rule 3 and rule 4 matter more than they look. The OAIC recommends, as best practice, not entering personal information — particularly sensitive information — into publicly available generative AI tools, and doing due diligence on commercial AI products. See its guidance on commercially available AI products. Our security series covers the Privacy Act and AI in Australia in more depth.

Approvals from your phone

Approvals are where chat-first operations either work or fall over. A good approval request on a phone shows the exact message, who it goes to, why the agent thinks it is right and anything unusual — all on one screen, answerable with “OK” or an edit. A bad one says “approve 7 items?” with a link to somewhere else.

Two habits make mobile approvals sustainable. Batch non-urgent approvals into two or three windows a day, and keep real-time requests for things that are genuinely time-sensitive. And never approve something you haven’t read just to clear the notification; that is how a gate becomes theatre. The full design, including undo windows, is in approval gates for AI agents.

Making agent replies readable on a small screen

Agents left to their own devices write as if you were reading at a desk. On a phone, long replies get skimmed and tables break. Tell the agent how to write for you, once, and add it to the house rules:

• Answer first. The first line says the result or the question: “Done — 4 of 5 booked, one needs you.”
• Six lines or fewer in the message itself. Anything longer goes in an attached document or a linked record.
• One decision per message when it needs your input, so a single reply can’t be misread.
• Names and amounts, not IDs. “Sam Lee, A$880, 21 days overdue” beats “INV-2231”.
• Links back to the record — the CRM contact, the folder, the draft — for when you do want the detail.

It sounds fussy. In practice it is the difference between reading the agent’s messages and muting them.

Voice notes, photos and videos as instructions

The biggest practical advantage of chat over forms is that you can instruct the way you think: out loud, with a photo. Cortex accepts voice notes, photos, documents and phone videos as instructions. Tony Lorenzo at Elite Partners Real Estate, for example, says his agent turns his phone walk-through videos into NSW ingoing condition reports.

Voice notes work best with a little structure — say who it’s about, what you want and by when — and the agent should reply with a short written brief and any questions before acting. We give a script and examples from site visits and driving in turning voice notes into tasks.

Bringing your team into the same chat

Once more than one person is involved, the questions change: who can instruct the agent, who can approve, which threads staff can see, and how you stop someone pasting a client’s details into the wrong group. A group chat with people and agents can genuinely replace a lot of status meetings, but it needs roles and etiquette. We cover permissions, secrets and when to split threads in AI agents in group chats.

Behind the chat, the orchestrator keeps track of who owns each piece of a larger request and reports progress back in the thread; see Fulcrum Sessions.

Risks of chat-first operations, and how to manage them

On platform rules: messaging apps do change their terms. WhatsApp’s terms of service, for example, prohibit bulk messaging and auto-messaging and non-personal use unless authorised, and Meta’s WhatsApp Business Solution terms barred general-purpose AI assistant providers from the platform from 15 January 2026 while still allowing businesses to use AI to serve their own customers, as reported by TechCrunch. That is one reason we recommend chat as the front door and never as the only copy of your records.

When chat-first isn’t the right fit

• Your work is mostly at a desk with large screens and heavy spreadsheets. Chat is still useful for exceptions, but your main workspace is elsewhere.
• You need high-volume customer messaging. Hundreds of customer conversations a day need a proper contact-centre or messaging platform, with chat as the internal side only.
• Your team strongly prefers email and works fixed hours at desks. Forcing a chat app on them will fail; let the agent report by email instead.
• Your regulator or contracts require records in a specific system. Chat can feed that system; it shouldn’t replace it.

If none of those apply and your day is spent away from a desk, chat-first is worth trying with one area of the business. The channels page shows how Cortex works in each app, and you can book a walkthrough from there.