Custom AI assistants and personal bots on your phone
HeyCC lets you create role-based personal bots with their own name, appearance and purpose. Research, writing, planning or another repeatable job can have a focused assistant instead of sharing one undifferentiated conversation.

Verified customization boundary
- Give a bot a name, choose its appearance and shape its role.
- Create multiple bots when different jobs need different instructions or working styles.
- Bring several roles into GroupBot when a discussion benefits from more than one perspective.
- Keep the selected model, tool permissions and final review under user control.
What makes a useful custom AI assistant
A useful bot has a narrow responsibility, a clear audience and an output the user can check. “Help with everything” gives the model little guidance. “Turn product notes into a launch brief, list missing evidence and never invent metrics” gives the assistant a repeatable job and a visible quality bar.
How to define a personal bot in HeyCC
- Name the job in one sentence: research, planning, writing, review or another focused responsibility.
- State what inputs the bot may use and what it should ask for when information is missing.
- Define the expected output, including format, level of detail and facts that require sources.
- Choose a supported model configuration appropriate for the task.
- Test with non-sensitive material, correct the instructions and review every important result.
Group AI chat: personal bot versus GroupBot
A personal bot is the focused place for its own instructions, conversation and tool-enabled work. GroupBot brings several roles into one discussion so the user can compare suggestions, mention a specific bot and ask another perspective to check what may be missing.
GroupBot is coordination, not a promise of a fully autonomous agent team. The current App Store description says that when a task needs tools, the user continues in that bot's individual conversation.
Work and personal bots
Separate work and personal bots can make responsibilities and instructions easier to understand. That organizational separation is useful, but it is not automatically a privacy or security boundary. Review what information each bot receives, which model endpoint processes it and what permissions are available.
Models, tools and approval
A bot's identity is separate from the model service that processes its requests. Tool access and consequential actions are another layer again. Changing a name, avatar or role does not grant expertise, add a tool, bypass an operating-system permission or remove the need for user review.
Limits and user control
- Output quality depends on the instructions, selected model service and supplied information.
- A custom role does not guarantee expertise, factual accuracy or consistent judgment.
- Multiple perspectives can repeat the same error; independent checking still matters.
- Use low-risk test material before giving a bot sensitive content or consequential work.
Custom AI assistant FAQ
Can I create multiple custom AI assistants in HeyCC?
Yes. HeyCC supports multiple role-based bots so research, writing, planning or other work does not have to live in one undifferentiated assistant.
What can I customize about a HeyCC bot?
The current App Store description says users can give a bot a name, choose its appearance and shape its role through conversation or settings.
What is GroupBot in HeyCC?
GroupBot brings several bot roles into one discussion so the user can compare perspectives and mention a bot when its contribution is needed. Tasks requiring tools continue in that bot's individual conversation.
Are custom bots fully autonomous?
No. A custom role does not guarantee expertise, accuracy or unsupervised execution. The model, available tools, permissions and final review remain important.
Do separate work and personal bots create a security boundary?
No. Separate roles help organize work, but a bot name is not a security boundary. Review data flow, provider configuration, permissions and what information each bot receives.