Copilot

Un assistant branché sur ton workspace, qui retient et reprend la conversation partout.

Ask your workspace a question or request an action. The copilot reads your real data with its tools, acts with your approval, and remembers from one conversation to the next.

What it does for you

The copilot lives in the back-office top bar and full-screen at /copilot. It makes nothing up: before answering, it calls tools that fetch your real data, contacts, invoices, bookings, content, campaigns. The question never leaves your workspace, and the model never picks the workspace: the scope is set server-side by your account and your permissions.

It can answer in read mode and act in write mode, but every change goes through your approval, shown right in the chat. It can never delete data. Only one action is approved by default: remembering a durable fact you give it.

Two separate memories keep continuity. Persistent memory holds facts about you and your business and reinjects them into every conversation. Threads are saved in the same store the Kernel uses, so you open the copilot on mobile and pick up where you left off on desktop.

How it works

Wired to your data

The copilot has a broad toolbox covering most of the product's modules. It uses it to read your real data before answering. When it cannot find something, it says so instead of guessing.

Contacts and CRM, Booking, Workbench
Studio, Pages, Emails, Forms, SEO and AI visibility
Counsel quotes, invoices, contracts
Ads, Products, Program, Webinars, Voice

Copilot

Questions

Six contacts have gone quiet for ten days. The warmest is Camille: she opened your quote twice yesterday.

Sources CRMCounsel

Click a question to see the answer and the sources it used.

Approve before it acts

Reading is free. A write action stops on an approval prompt shown in the chat: you accept or decline. Destructive actions are never offered, the copilot cannot delete records.

Persistent memory

When you state a durable, useful fact, target day rate, preferred tone, ICP, constraint, the copilot remembers it for future conversations. A stable key like "tjm" updates the fact instead of stacking a new one. Known facts are handed to it at the top of context, so it does not ask again.

Saved threads, cross-device

Every exchange is written to the shared conversation tables. The copilot reopens your last thread when the page loads and rebuilds the active thread from the start to the latest message. The back-office can branch a thread into versions, mobile writes a linear chain, both render the same conversation.

Long-conversation summary

On a thread that grows, older turns are summarized into a short, self-contained text while the most recent exchanges stay shown as is. The summary keeps facts, decisions and open tasks, and goes back into context on every new message.

The daily briefing

Ask "give me a briefing" or "what should I do today" and the copilot ranks your priority actions by urgency: sent invoices to chase, hot contacts to reach, bookings to prepare, open tasks. Each line is linked to the tool to act right away.

Connected to

agents Chaque échange du copilote passe par la même mécanique de run et retombe dans le flux Activitécrm Le copilote lit tes contacts et remonte les plus chauds dans le point du jourmembers-app Le copilote mobile partage le même stock de fils, tu reprends la conversation du bureauworkbench Il liste tes tâches ouvertes et peut enchaîner dessus depuis le point du jour

Copilot

What it does for you

How it works

Wired to your data

Approve before it acts

Persistent memory

Saved threads, cross-device

Long-conversation summary

The daily briefing

Connected to

Try Copilot in Freelance OS.