Start
Quickstart
This guide turns rough backup notes into a client update draft. The notes are included in what you send, so you will know which facts the agent received and can check that it did not invent anything important.
You will create and use two things:
- Scout, an agent that writes short service updates.
- A session, which is the saved record of your conversation with Scout. Each request and reply is one turn.
Nothing here connects to a backup system, contacts a client, or runs on a schedule. Scout answers you, and only you, until you decide otherwise.
Before you start
You need:
- a Mobius account;
- permission to create agents in your organization; and
- at least one model available in the agent form. A model is the AI, such as Claude or GPT, that writes the response.
A turn may use paid model services, so make sure you are allowed to use your organization's model access. If the model menu is empty, ask your Mobius organization administrator to check that access before continuing.
Northwind IT and Ridgeline Dental are fictional companies used throughout this guide. Replace them with your own names when you adapt the example.
1. Create Scout
-
Click Open app in the docs header, or open the app directly. Sign in if asked.
-
In the sidebar, open Build, then click Agents.
-
Click Create agent.
-
Set Agent name to
Scout. -
Set Agent description to
Turns service notes into clear client updates. -
In Agent instructions, enter:
You write short updates for clients of Northwind IT. Use only the facts in the request. Do not guess at causes, dates, people, or work that was not mentioned. State the current result first, then explain what happened. End with any action the client needs to take. If no action is needed, say so. Keep the update under 120 words. -
Leave the model on its available default.
-
Click Create agent.
Mobius opens Scout's page and shows the message Scout is ready. If you miss the message, seeing Scout's page is enough to confirm it was created. The agent's instructions are the standing rules Mobius sends with every assignment Scout receives. The next section gives it one specific assignment.
2. Ask Scout for a draft
Warning: A turn may use billable model or tool services even if it fails.
-
In the sidebar, click New chat. This is the conversation surface.
-
Beside the message box, open the agent menu and choose Scout.
-
Type this assignment and send it:
Write a client update from these notes: - Ridgeline Dental's overnight backup reported a failure at 2:14 AM. - The automatic retry started at 2:29 AM. - The retry completed successfully at 2:47 AM. - The latest backup is complete. No client action is needed. Do not say that anyone was notified. Do not add a cause for the first failure. -
Wait for Scout's reply. The turn is
runningwhile the model works, and a short stay inqueuedmeans the work is waiting to start. If nothing has arrived after the ten-minute turn limit, reload the page and read the final status and error.
The wording will vary because an AI model wrote it. Check the facts instead. The result should name Ridgeline Dental, say that the backup failed at 2:14 AM, the automatic retry ran from 2:29 AM to 2:47 AM, the latest backup is complete, and the client does not need to act. The current result should come first. The draft should be under 120 words and should not name a cause for the first failure or claim that someone was notified.
If the turn fails, its error stays in the transcript. If the error names a setting you cannot change, such as model access, copy it for your Mobius organization administrator. For any other error, read the message and correct what it names before sending again.
3. Change one fact and ask again
Now make a change with an obvious result. In the same conversation, send:
Same notes, with one change: Northwind will review the backup logs today, and
the client still does not need to act. Rewrite the update.The second reply should say that Northwind will review the logs today and that the client does not need to act. It must still satisfy the first reply's fact checks.
Scroll up. The first request and reply are still there, unchanged. A session keeps every turn in order, so you can compare what you asked with what came back. Later turns can also use what was already said, which is why the second request could say "same notes" instead of repeating them.
4. Find the conversation again
- In the sidebar, click History.
- Open the conversation with Scout.
This is the same session, with both turns and Scout's tool activity, and it is where you return when you need to answer what an agent was asked and what it did.
What you just learned
The model produced the response. Scout supplied the standing writing rules. Your message supplied this assignment and its backup facts. The session kept the facts, activity, result, and final status of each turn.
Most Mobius work follows the same sequence:
- start with facts you can check;
- ask for the smallest useful version by hand;
- inspect the turn;
- change one thing; and
- put it on a schedule only after the result is dependable.
Next
- See how the main Mobius objects fit together.
- Connect an integration when an agent needs live input or must change another system.
- Triage inbound tickets with a human review before a reply is sent.
- Ask for a routine when the same request should repeat on a schedule.
- Set time and spending limits before an agent works without supervision.