HeyCC
Bot Team workflow

Give every bot one clear job.

HeyCC can configure multiple role-based bots and coordinate their contributions to one project. The dependable pattern gives each bot a narrow responsibility, uses one shared source brief, and requires final human review.

Several HeyCC bots collaborating in a group workflow

Best forProjects that need research, drafting and critical review.

Shared sourceOne objective, non-goals and acceptance checklist.

Final ownerThe user, not the bot group.

Reusable team brief

Project: [name]. Goal: [measurable outcome]. Sources allowed: [list]. Research Bot collects primary-source facts and uncertainties. Writing Bot drafts only from approved facts. Review Bot checks unsupported claims, missing requirements and contradictions. No bot may publish or contact anyone. Return one final package with a change log and unresolved decisions.

Workflow

  1. Write one project objective, non-goals and acceptance checklist.
  2. Assign non-overlapping roles and specify each handoff.
  3. Let the research role produce a source pack before drafting.
  4. Require the review role to point to unsupported or conflicting claims.
  5. Resolve open decisions yourself and approve the final deliverable.

Expected deliverable

A source pack, draft, review notes, final document and unresolved-decision list. More bots do not guarantee better reasoning: they can repeat the same error, increase model cost or create conflicting drafts.

External publishing or communication remains a separate authorized action.

Questions

Is Bot Team fully autonomous?

No. The recommended workflow keeps objectives, permissions and final acceptance with the user.

Do all bots need the same model?

Not necessarily. Available provider and model choices depend on configuration, access and cost.

How is this different from one long chat?

Role boundaries make sources, drafting and review inspectable, but they also add coordination overhead.

Continue

All templatesCustom assistantsModel choiceOfficial downloads