Setting up with your AI chief of staff
How your AI chief of staff sets up your whole workspace in a conversation, saving each detail itself with Undo, leaving only tool sign-ins to you, with voice and video (Beta), check-ins, hand-overs, and how to switch to the set-up screens.
Browse documentation
Two ways to set up
When you sign up, the set-up chat opens by itself, with the lead of the first team you chose, while your teams activate. It can run the whole set-up with you in conversation.
On a first visit to Home, the welcome card offers the same two ways in. Set up your workspace opens the conversation with your AI chief of staff. I'll set it up myself takes you to the set-up screens. Both save to the same settings, and you can switch at any time: the conversation has a link to the screens, and every next-step card has a Do it with my team button.
The conversation is at Set up your workspace. It is marked Beta. N, the head of your AI growth org, runs it with your lead, and the heading names them both, for example N, with MIRA, your AI Marketing Chief of Staff. Under it sit Turn voice on and I'll set it up myself, and a line counts how far set-up has got. When you have more than one lead, The huddle beside the chat shows them all: press another lead to open its chat, and a lead that left you a note says Left you a note. Suggested questions sit above the message box: pressing one sends it straight away, as if you had typed it. Anything else goes in the box, which reads Message N, and you can attach a file to it.

Talk to your lead (Beta)
You can talk instead of typing. Turn voice on sits under the chat's heading, beside the Beta tag.
Voice
Press Turn voice on and allow the microphone when the browser asks. Your lead then speaks its replies and listens: talk, or type as usual. What you say is sent when you stop, as if you had typed it, and talking over the lead stops its voice. While it hears you, the line under the buttons says Hearing you.
- Mute stops the voice and the listening, and typing works as usual. Unmute turns them back on.
- Spoken language appears once voice is on. Choose English or Detect automatically. It starts on English, and this browser remembers what you chose.
- If you opened the chat from Set up your workspace on Home, voice starts on that same press.
If voice cannot start, the line under the buttons says why, and the chat stays typed: the microphone was not allowed, the browser cannot do voice, voice is not set up on this workspace yet, or its budget has run out.
Video
Press Video to see your lead's face say its replies. A video lasts up to 15 minutes; the line under it says so, and when it ends you press Video again to keep going. End video closes it. Video shows the lead speaking; to talk to it as well, turn voice on.
If your lead has no face yet, the chat stays voice and text. Video can also be busy, or at your workspace's limit for live video, and the page says so.
Who guides you
Each team has a lead, and each lead guides its own team:
| Team | Lead |
|---|---|
| Sales | SERA |
| Marketing | MIRA |
| Content | CREA |
The lead of the first team you picked also guides the set-up of the workspace as a whole: the brand name, who you sell to, inviting people and the rest. If your first team has none of these leads, MIRA guides you. If you picked leads one by one instead of whole teams, the first lead you picked guides you, and its work is charged to its own budget.
The set-up guides your lead follows
Before your lead starts on an area, it reads that area's set-up guide: the questions to ask in order, the fact each one needs, and which steps your workspace has already done. It asks one question per reply, skips what is done, and does each step the moment it has the fact. It never asks you to press, click or open anything to set something up. The one thing that stays yours is signing in to a tool.
There are twenty-one guides:
| Guide | What it covers |
|---|---|
| Workspace basics | What the business is for, what it sells and to whom, the name its work is signed with, and the one number it is run against |
| Website and knowledge | The site the team reads, and everything else every agent should know about the business |
| Buyers and offerings | Who you sell to, the targeting agents prospect from, and what you sell |
| Brand | The brand book every agent writes from: tagline, mission, voice, colours, fonts and the mark |
| Sending | The address mail is sent from, and the domain that proves it |
| Connect tools | Every tool the team works in, signed in once, and the account or property each one uses |
| Invite people | The people who work in the workspace with the agents, each with the right role |
| Autonomy and budgets | How much agents may do on their own, and what each lead may spend in a month |
| Plan and billing | Choosing a plan. Payment details are always typed on the payment page, never in the conversation |
| Room set-up | One team room from its install to its first run: who sits in it, what it is for, its goals and what it runs |
| CRM room | Which CRM, the pipeline stages, when a deal is stalled, and existing leads |
| A team of your own | A team you design: what it is for, which agents sit in it, and its charter |
| Agent basics | The five steps that make any agent ready: its voice, switched on, its tools, its reporting line and when it runs |
| NORA set-up | NORA and VANI before the first prospect: who to look for, how many a week, where, and this period's targets |
| DRIS set-up | Domains, Search Console and Analytics, competitors, pages to watch, its daily cap and its objective |
| NIA set-up | NIA's ad accounts, connected and chosen |
| HOOK set-up | HOOK's brand pack and ad data: the offer, the voice, the words never to use, each claim and its proof |
| Echo set-up | What Echo listens for, the monthly cap on paid reads, and the facts it may state |
| MOXA set-up | MOXA's social channels. Nagent's team adds MOXA itself; see MOXA |
| Content set-up | The Content team and publishing to the site |
| Studio set-up | What RUPA and Alpha render from: the brand book, the mark and references |
Some steps are not your lead's to do. Where a step needs a page, or a role you do not hold, your lead says plainly who does it and carries on. You can also leave a step: the chat notes it as Left for now and does not ask again.
What your lead saves, and what it asks you first
Your lead starts with what you want to achieve, in your own words, and saves it as soon as you say it. The card reads What you want to achieve, and the entry sits in your Knowledge Hub under "What this business wants to achieve", where every agent reads about the business. Your objective orders the rest of the set-up: the guides that fit it come first, and the facts that matter to it are asked before the others.
Then it asks about your business, one question at a time: what you sell, to whom, and what you want from the next three months, unless your site or your profile already says. It works out what the workspace needs from your answers and from what it read from your site, your profile and your brand, then sets the baseline: the one number the workspace is run against and, for DRIS, today's visibility as its starting point.
When a team or lead your workspace could add fits your objective, your lead may suggest it: one at a time, with one sentence on why it fits. It is added only after you say yes. If you say no, your lead notes that and never suggests it again.
Your lead sets the workspace up for you. Once it knows a detail from what you said, what you attached or what the workspace already holds, it saves it straight away, with your own permissions, as if you had saved it on its own screen. Each change shows as a card in the conversation, marked Saved, with Undo where it can be undone. If your role cannot make that change, nothing is saved and your lead says so. If a save did not work, the card reads Not saved and offers Save to try again.
| Your lead saves | Undo |
|---|---|
| The brand name | Yes, back to the previous name |
| Who you sell to | Yes, back to the previous description |
| Confirming a drafted offering | Yes, back to draft |
| The address your team sends from | Yes, back to the previous address |
| The picture of your business | No, though you can change any answer later |
| The number the workspace is run against | No, a new one replaces it |
| The charter of each room it sits in | Yes, back to the previous charter |
| An entry in your Knowledge Hub | Yes, it comes back out |
| DRIS's starting point | No, it stays as the baseline |
The charter, the Knowledge Hub entry and DRIS's starting point are agent actions, so they follow your agent settings: if one needs a person's approval, it waits in your Inbox and your lead tells you so. Adding to the Knowledge Hub spends a little of your lead's budget.
The same goes for the rest of the set-up. Your lead does it in the conversation, without asking you to press anything:
| Your lead also saves | Undo |
|---|---|
| How much agents may do on their own: Standard or Strict, while none is chosen | Yes, back to Standard |
| Adding a team, or a single team lead | No, a team cannot be removed from here once it is seated |
| Inviting a teammate | No, the email has gone; you can remove the person later |
| A lead's spend cap | Yes, back to the previous cap |
| An agent's level, when an Organisation admin asks for it | Yes, back to the previous level |
| Running a team's first job | No, it spends from your budget, and what it makes waits for your review |
| Running that job every week | Yes, Undo stops it |
| Asking a person at Nagent | No, the message has gone |
A first job starts on its own and shows Running your first job while it works; when it is done, Open what it made takes you to the result.
For a spend cap, your lead suggests your plan's monthly allowance split across your leads, then saves what you agree to.
Your website, read from the chat
Give your lead your site's address, or one sentence on what you sell if you have no site. A card, Your website, starts reading the site at once, with nothing to press: up to 25 pages go into your Knowledge Hub, and your brand is drawn from them after. If pages could not be indexed for search, your lead says plainly how many were read, how many were indexed and how many failed. It does not invent a fix, and when the reason is on Nagent's side it offers to send it to a person at Nagent.
Once the read is done, a card headed Here is what I learned about you reads back what the site gave: what you sell and to whom, your industry and size, the area you target, and your brand's colours and voice. It has no button. Say yes, or tell your lead the one line to change, and it saves the rest where it belongs.
With the site read and a Content or Marketing team seated, your lead also drafts Three social posts from your site without being asked. They are drafted once for the whole workspace and wait for one review in that team's room. Nothing is published.
Attaching a file
The message box has an Attach a file button. One file goes with a message, up to 25 MB. Your lead is told the file's name, kind and size, never its contents, and saves it through the page that owns it: a document for the Knowledge Hub, a brand guideline, your mark (an image under 500 KB), a spreadsheet of existing leads to import, or a document about what you sell. It asks when it is not clear which. Ad results for HOOK still go on HOOK's own upload page.
Connecting a tool from the conversation
Signing in to your tools is the one step that stays yours. Your lead starts the connection, and the card it leaves has a Sign in to connect button that takes you to the tool's own sign-in. When you come back, the conversation checks the connection with the tool and the card says Connected only once the tool has confirmed it. It checks when the card is drawn, when you come back to the tab, and every few seconds for up to ten minutes. Undo disconnects it again.
What a lead never does
- Approve, reject or decide any work for anyone. Work that needs a decision waits for a person in the Inbox.
- Change an agent's level unless an Organisation admin asks for it, or suggest raising one. Even then, what needs a person's approval is unchanged.
- Spend past your workspace's budget.
- Take payment details in the conversation. They are always typed on the payment page.
Watching your lead work
While your lead works, the conversation shows each step as it happens, such as reading your site or saving your brand, with done or did not work against each. Its reply then arrives word by word. If the connection drops while a turn runs, the page reads the conversation again rather than sending your message twice, because the turn kept running.
Under your lead's name, a line such as Set-up 3 of 17 shows how far the set-up has come, with the time since your workspace was made beside it. It counts every lead's set-up items across the whole workspace, not only the lead you are talking to.
One small run between steps
Between steps, your lead may offer one real run, in one sentence, after the step it has just finished:
| After | The offer |
|---|---|
| Your website is saved | CREA drafts a first post from your site, in your brand voice |
| Your website is saved | DRIS checks your home page against search and AI answers, and brings back the first fix worth making |
| Your buyers are saved | NORA finds up to ten leads that match your buyers, and drafts the first email to the best one |
| Search Console is connected in the chat | Your top searches, from Search Console |
Say yes and it runs at once. A team's job spends from your workspace's budget, and what it makes waits for your review in the team's room, as the team's first job does. Say no and the offer is noted and never made again. The first offer comes once your website is saved, and each next one after two more saved steps.
Check-ins
Once you have written to your lead, it may leave you a short note at a day, two days, three days, a week and a month, about the one thing that would help most next, such as connecting a tool or inviting someone to approve with you. It only writes when there is something left to do, never more than once for each of those moments, and never when you open a page. The next-step card tells you when a note is waiting.
Handing over to another team
Your leads work as one team. When you ask for work another lead's team does, your lead brings that lead in at once, carrying your request in your own words, and says so as a teammate: "CREA runs content, I'm bringing CREA in." The new lead's conversation opens with an introduction card: the arriving lead's face and one line on what it will do for your business, and a line from the leaving lead on what it saved. The new lead then starts on your request straight away.
When a lead's part of the set-up is complete, it says so, lists what it saved and what was left and why, and hands you to the lead with open steps that best fits your objective. That lead names the step it starts with. You can also open any other lead yourself from the huddle at the top of the page.
When the set-up is done, a card headed Your set-up is done sums it up: what was saved, what you left for now, what only a page or another role can do, what runs next on the schedules already stored, and when the first results land, in UTC. If nothing is on a schedule, it says so and your lead offers to put a workflow on one.
What it costs
Each answer is a model call and spends from your lead's budget in this workspace. If that budget is reached, the lead says so plainly and answers again when it resets or when an admin raises it. Check-ins spend nothing.
Voice spends from the same budget, for hearing you and for speaking. Video checks that the lead's budget can cover a whole 15 minutes before it opens, then charges only for the time it ran.