These pages describe typical business agents and how to assemble them with betool's building blocks: an input channel, one or more agents, integrations and actions.
These are recipes, not shipped templates. None of these agents is published in the template catalog: you build them in the visual editor from the nodes, tools and integrations mentioned — all available on the platform.
The "Chief of Staff" principle
The recommended design stance for these agents: they own the information and follow-up layer; you decide. They read your data, summarize, alert, prepare the trade-offs and draft documents. It is up to you to wire human approval before any action that commits spend or sends something sensitive.
Read-only first, action under approval second: you keep control and gain altitude.
The recipes
- CFO IA — financial cockpit: weekly briefing, alerts on follow-ups to make.
- COO IA — head of execution: tracks an action register and follows up on whatever is stalling.
- CTO IA — technical output review of the team.
- Product Manager IA — automated competitive intelligence.
- Personal assistant — voice assistant: calendar, mail, prepaid appointment booking.
How to assemble them
- Create a model in your organization (Models menu).
- Connect your integrations (Stripe, GitHub, Google… in BYO).
- Write the agent's role and mission for your context (thresholds, tone, priorities).
- Schedule the trigger (see Schedule).
The template catalog
The Templates menu lets you install an already-built model into your organization: a standalone copy, from which secrets are always excluded and for which connector accounts must be supplied at installation. The catalog only contains what organizations have contributed to it — yours, and those the platform operator has made visible to everyone. The feature is enabled organization by organization by the platform operator; otherwise, the screen says so.
An installed model is never frozen: anything it does, you can change in the visual editor.