Credits and good habits: get more from every credit
What uses credits in Clone Studio, what uses more or fewer, and simple habits that save credits and improve quality.

Clone Studio is usage-based. This guide explains what credits are, which kinds of work use more or fewer of them, and a few habits that keep your usage down while making your clone's work better.
What credits are
Every skill run uses credits. How many depends on what systems and models it uses and how much work it does. Your plan includes a monthly credit allowance.
You can:
- See your usage in billing.
- See how many credits each skill call used, so you know what's driving your usage.
- Buy more credits if you run low, or pause until the next cycle.
You're always in control.
What uses more credits
- Searching a very large inbox and pulling attachments from thousands of emails
- Long, complex reports run against years of history
- Video generation, especially long videos
- Research reports and large coding builds
What uses fewer credits
- Normal chat with your clone
- Searching a knowledge base
- Short, focused scheduled tasks
Habits that save credits
1. Use a SharePoint or OneDrive folder for documents
Instead of asking your clone to find and extract attachments from an inbox, put the documents in a folder and have your clone read the folder. This uses far fewer credits.
2. Keep reports to short windows
Ask for the last 24 hours or the last 7 days, not the entire history.
3. Start small
Test a new scheduled task on a small scope before turning it on for everything. See Put your clone on a schedule for how to set one up.
4. Put long-term information in Knowledge
Documents indexed once are cheaper than re-explaining or re-searching every time. Learn more in Knowledge: your clone's brain.
5. Review scheduled tasks monthly
Turn off anything nobody reads.
6. Check the execution log
The execution log shows which skills ran, so you can spot unnecessary work.
Good habits for quality
- Start with drafts for anything that goes to a resident or customer, and give feedback so your clone learns your style.
- Tell your clone what you want in plain English. Be specific about audience, tone and length.
- Fix the source, not just the answer. If your clone can't answer something, improve the document it should have used, rather than only correcting the answer.
- Keep one current version of each document, so your clone isn't working from outdated copies.
Getting help
Ask your clone first. If it can't solve the issue, it can open a support case for you (see How to open a support case, and what happens next). You can also email your onboarding contact, and watch the Clone Support channel on YouTube.
For more ideas on what to do with your clone, browse use cases.
Common questions
Where can I see how many credits I've used? In billing. You can also see how many credits each skill call used.
What happens if I run low on credits? You can buy additional credits or pause until the next cycle.
Does chatting with my clone use a lot of credits? No. Normal chat and knowledge base searches are among the lightest things your clone does.
What's the quickest way to cut usage? Shorten report windows, move documents out of your inbox and into a folder or Knowledge, and turn off scheduled tasks nobody reads.
Related
Was this helpful?
Thanks. That helps us make this better.


