Clone Studio: the complete guide
Everything you need to know to hire, train and run a team of clones in Clone Team Studio and Clone Studio Max.

Clone Studio is where you hire, train and work with your clones: digital teammates that do real work in the same tools you use every day. This guide walks through every major part of it, in the order most teams learn it. Bookmark it. Most "how do I…?" questions are answered somewhere below.
Two editions, one platform
Clone Studio comes in two editions. They have the same capabilities and run on the same platform:
| Clone Team Studio | Clone Studio Max | |
|---|---|---|
| Home | clone.org | clone.me |
| Feel | Chat-first: the fastest way to dive in and work with your clones | The original full studio, with every control on its own page |
| Best for | Teams who want to get going in minutes | People who like to configure everything in detail |
Throughout this guide, articles and videos are tagged Team Studio or Studio Max so you can tell which screens they show. The ideas are the same in both.
What a clone is
A clone is an AI teammate with a name, a face, a voice and a job. It works inside your email, calendar, documents and CRM, and you talk to it the way you'd talk to a colleague: in chat, on the phone, by text, by email, in Slack or Teams, or in a meeting.
Clones aren't chatbots that only answer questions. They do work: draft and send emails, book meetings, update records, research a market, write a report, make an image or a video, build a small app. And they do it as a member of your team, with the context of your business.
Roles and skills
Two words matter more than any others in Clone Studio.
Roles: the job
Every clone is hired into a role: sales development rep, support specialist, executive assistant, marketing manager, finance analyst and many more. A role comes with:
- Instructions and prompts tuned for the job
- Role knowledge: the know-how of doing that job well
- Default skills: the capabilities that role normally needs
The role is what makes a clone good at the work from day one.
Skills: the capabilities
Skills are what a clone can do: send email, read a calendar, update a CRM, search the web, create an image, write a research report, make a video, build software. A clone in a role uses its skills to get its job done.
Skills are turned on per clone. Two clones can share the same connected Google account but have different skills enabled. That's on purpose: your executive assistant may send email on your behalf, while your research analyst only reads it.
Some skills come with their own interface, such as a review page or an approval step, because the work is bigger than a chat reply. See Automated Video: skills with their own UI.
Spotlights on two of the most-used skills:
- Image Operator: create and edit images by describing them.
- Research Report: designed, cited research reports and slide decks.
Hiring clones
The Marketplace
The fastest way to get a great clone is the Marketplace. Browse by department, search for a role, read the clone's bio and skill list, and deploy it in one click. Want a whole department? Use Add all. (Video: Hire your first clone)
Building from scratch
You can also create a clone from scratch from the Clone Team page. You'll write its instructions yourself and choose its skills. Start from the Marketplace unless you have a very specific job in mind.
Your first team
A strong starting team is one right hand (a chief of staff or executive assistant) plus a few specialists for the work that takes most of your week. Paid plans include unlimited clones (the 30-day Free Trial includes 3 active clones), so it's worth trying several.
Onboarding mode
A newly hired clone starts in onboarding mode (in Team Studio you'll see a yellow dot). It asks you about you, your business, your tools and how you like work done. Answer, then tell it when it's set up enough. Specific answers here save a lot of corrections later.
Talking to your clone: Chat
Chat is where most work starts.
- Ask in plain English. "Find every customer who hasn't replied in two weeks and draft a friendly check-in for each" is a perfectly good instruction.
- Start a new thread for a new topic with + New. It starts a new conversation; it doesn't create a clone.
- Attach files with the paperclip, dictate with the microphone, or talk live with the waveform.
- Start with drafts. Until you trust your clone with a type of task, ask it to draft rather than send. Give specific feedback ("shorter", "warmer", "always include the order number"). This is how it learns your style.
(Video: Give your clone its first task)
The Execution Log
Next to Chat is the Execution Log: a receipt of every skill your clone ran, with what it sent and what came back. When you want to know "did it really send that?", the log is the answer. It's also the first place to look when something didn't work.
Archive, Chats and tasks, Projects
- Archive holds everything your clone has produced: files, media, meeting transcripts.
- Chats and tasks lists every conversation and every scheduled run.
- Projects are folders that keep related chats together.
Knowledge: long-term memory
A chat thread is short-term. Knowledge is long-term: documents and facts your clone searches automatically whenever they're relevant. If your clone gives generic answers or forgets things, Knowledge is the fix.
Knowledge levels
Knowledge comes in levels that flow downward:
- System: shared by all clones on the platform
- Organization: everything in your company
- Department: one team
- Role: everyone in a role
- Personal: one clone
Upload a document once at the right level and every clone below it can use it.
What to upload first
- A brand voice and style guide
- Your product or service sheet
- A customer FAQ
- Your escalation policy (when a clone should hand off to a person)
- How you like meeting notes written
Fill-in templates for each of these are in the Knowledge templates library.
Runtime access
Organization knowledge only reaches your clones while they work if Runtime access is turned on. If you uploaded something and your clones can't see it, check this first.
(Video: Knowledge, your clone's brain)
Connections: signing in for you
A connection is how your clone signs in to Google, Microsoft, Salesforce and other services on your behalf. You connect an account once (from your personal settings, or by asking your clone to set one up), and then enable skills that use it on each clone.
- A skill with 0 connections is fine if it doesn't touch your accounts.
- If a connection says waiting for admin approval, your IT team needs to approve the app.
(Video: Connect your accounts and turn on skills)
Integrations: reaching your clone anywhere
Integrations are the channels where you and others reach your clone. It's the same clone, with the same knowledge and skills, everywhere.
- Phone calls and texts. Give your clone its own phone number and call or text it.
- Email. Every clone can have its own email address. Access Control decides who may email it; Organization Only keeps outsiders out.
- Slack and Microsoft Teams. Add your clone and message or @mention it like a colleague.
- Meetings. Paste a meeting link or let your clone join from your calendar. Choose whether it greets people, and whether recaps go to all attendees or only to you. Transcripts are saved in Archive.
- Embeddable links. Put your clone on a website as a chat or voice widget, the way Graham Chambers appears on this site.
- The power switch. Pause your clone on every channel at once.
(Video: Reach your clone anywhere)
Schedule: routines that run themselves
A scheduled task is the same prompt you'd type in Chat, run on a timer: hourly, daily, weekly or on a custom repeat. Create one from Schedule → + New, or simply ask:
"Every weekday at 7 AM, send me an outline of my day from my calendar, with prep notes for each external meeting."
Get the prompt right in Chat first, then schedule it. Keep credit use down by narrowing what each run reads ("the last 24 hours", "only unread"). Check what a run did in Chats and tasks and its Execution Log.
(Video: Put your clone on a schedule) · Ready-made routines: Skill and schedule instructions
Events: waking a clone from your other systems
Events let your other systems wake a clone up. You create an event source (a secure address your system sends data to) and link it to a clone with a handler: a short instruction for what the clone should do when an event arrives. When the event lands, the clone runs as itself, with its own knowledge and skills.
Common uses:
- A new form submission arrives → the clone qualifies the lead and drafts a reply.
- A support email arrives → the clone researches it and opens a case.
- Your CRM marks a deal as won → the clone sends the welcome pack.
Working as a team of clones
Clones can work together. A chief-of-staff clone can coordinate the others, and specialists can hand work to each other. Start simple: give each clone a clear role, and ask your right-hand clone to route requests to the specialist that owns them.
Staying in control
- Drafts first, sending later.
- The Execution Log for every action.
- Access Control on email, and meeting settings for what your clone says and sends.
- Skills per clone, so each clone only has the capabilities its role needs.
- The power switch to pause a clone on every channel.
When something isn't working
- Check the Execution Log for the message in question.
- Check the clone has the right skill enabled and a connection.
- For knowledge problems, check the file is indexed and Runtime access is on.
- Ask your clone: "Why didn't that work?" Clones are good at explaining their own runs.
- Still stuck? Ask your clone to open a Clone Support case, or open one here. See How to open a support case.
Where to go next
- Getting started learning path: seven short videos, in order
- Use case library: complete, ready-to-run setups by department
- Starter prompts: your first dozen things to ask
- Community: questions, ideas and show-and-tell from other Clone users
Was this helpful?
Thanks. That helps us make this better.