Agents.

Agents are AI helpers that work inside your Mosaik workspace. A chat answers a question or does one task with you. A team agent does a task again and again, on a schedule or when something happens in the CRM. An agent reads only what you allow and does only what you allow.

Concepts

• Assistant. The general chat. Ask about your records, pipeline, and connected data. The assistant reads, explains, and drafts.
• Team agent. A saved agent with instructions, tools, triggers, and a record scope. It has a private draft and a deployed version.
• Focus. Each area has its own agents. General agents live in the Assistant. Marketing agents live in Marketing. Inbox agents live in the Inbox. Legal uses the General agents.
• Record scope. Workspace lets the agent read all records. Selected records limits it to the records you tag in the chat that built it.
• Tools. Each tool is a permission, such as reading CRM records, reading Gmail or Google Calendar, creating a note or task, creating a company, contact, or deal, posting a message, or generating an image. A tool that is off cannot be used.
• Triggers. A schedule, a manual run, or a CRM event: a company, contact, or deal is created, a deal changes stage, a deal closes or reopens, or a form or lead is submitted from your website, HubSpot, or a Meta lead form.

Chat with the assistant

1. Open Assistant and select New chat.
2. Ask a question, such as “Which deals close this month and have no meeting booked?”
3. Tag records or connections in the composer to focus the answer.

The assistant groups its reasoning and tool calls into one trace. Open a step to see its input, output, and sources. Share a conversation with a colleague from the chat header.

The Assistant also suggests agents that fit your workspace, based on your connections and data. Select a suggestion to fill the composer. A suggestion never creates or deploys anything by itself.

Build a team agent

1. Open Team agents in the area you want, and start a new agent from a chat.
2. Describe the task. Tag the records and connections it needs. The builder asks questions when it needs a choice, such as a destination channel.
3. The builder saves a private draft. Review its triggers, scope, tools, and exact instructions on the agent page.
4. Change permissions in the Tools section. Record access sits above the tool categories. A disconnected source stays visible with its switches off.
5. Select Run now to test the draft. You can add a short brief. A test uses the draft permissions and can perform approved actions or use credits.
6. Select Deploy agent to make it live for the team. Deploying enables its triggers.

Use Edit agent to change it, Pause agent to stop it, and Activate agent to start it again.

Review runs

Each agent page shows its run history. A run shows its status, its results, generated images, reports, and the record changes it made. A completed run offers the full report and a Markdown download. Marketing labels results Generations. General labels them Results.

Whoever started a run, the creator, and admins can stop a run. Stopping does not undo actions that already completed.

Agents that react to submissions offer Backfill old records. A backfill scans past submissions with saved evidence and starts one run for each eligible submission. It checks for duplicates and uses credits.

General agents

Use General agents for CRM work: a weekly pipeline summary, a note on each new deal, or a new contact for each lead form. They can read CRM records, and Gmail and Google Calendar when you allow them. They can post to the Slack channels you choose.

Marketing agents

Use Marketing agents for content that repeats: weekly posts, a monthly blog, or a campaign review. A marketing agent can save a named design style and an image ratio. Its runs save images, posts, and carousels to Artifacts.

Inbox agents

Use Inbox agents for the shared inbox: a weekly inbox summary, team assignment, or a follow-up sequence. An Inbox agent reads the inbox before it summarises or assigns. It assigns a thread only after you name the thread and owner. It saves a new sequence as paused, and it never sends email from chat.

Record Agent tabs

Every company, contact, deal, finance record, and document has an Agent tab. The chat is filed under that record. Background agents also put proposals there, such as a new deal or a stage change, for you to accept or reject.

Set up

1. Connect the sources your agents need in Settings → Connections.
2. Choose the research model in Settings → General. The default is a low-cost model.
3. Start with one agent, test it with Run now, and deploy it only when the output is right.

Open it in your workspace

Open https://<your-portal>.example.com/<workspace>/chat to start a chat, or https://<your-portal>.example.com/<workspace>/agents to see your team agents.