Different jobs deserve different rules.
HeyCC can create custom bots with different names, instructions and responsibilities. A work bot and a personal bot can make recurring tasks easier to route, but a different bot name alone is not a security boundary.
Work botPrimary sources, formal output and explicit publication approval.
Personal botShort planning help and confirmation before system changes.
Actual boundaryConfiguration, permissions, connected tools and provider data flow.
Two reusable instruction sets
Work bot
Help with product operations. Prefer primary sources, show assumptions, use concise business writing, and never send or publish anything without explicit approval.
Personal bot
Help with personal planning. Keep answers short, ask before creating calendar events or reminders, and never infer high-stakes conclusions from incomplete information.
Workflow
- List recurring jobs and remove overlapping responsibilities.
- Give each bot a clear role, output format and permission rule.
- Add only the minimum context needed for that role.
- Test both bots with the same ambiguous request and compare behavior.
- Review connected tools and model-provider settings periodically.
Expected deliverable
Two distinct bot configurations plus a short routing guide: which requests go where, what context is allowed and which actions require review. “Work” and “life” are example configurations, not fixed built-in security modes.
Data may be sent to a selected model provider when needed for a request.
Questions
Are the two bots automatically isolated from every data source?
No. Distinct instructions help organization, but actual access depends on configuration and connected tools.
Can each bot use a different model?
The audited source supports provider configuration and model selection; availability and cost depend on the provider account.
Can either bot take external action without review?
Permission behavior depends on configured rules. Publishing, messaging and other commitments require explicit authorization.