Overview
Tools are the actions Maestro can propose and execute in each module of the platform. For example: write a message draft, create a CRM deal, schedule an appointment in the Calendar, or build a Catalog order. You control which tools are enabled β so Maestro only offers the actions that make sense for your operation.
Enabling a tool has two effects: it starts to appear as an action card in the generative copilot and becomes available to departments with their configured autonomy. Disabled tools simply aren't proposed.
Prerequisites
- An account with Maestro enabled.
- Administrator permission to change the tools and autonomy configuration.
- The corresponding module must be active in the account (for example, for CRM tools, CRM must be enabled).
Step by step
- Open the Maestro / Account Brain configuration area.
- Find the list of tools per module (CRM, Calendar, Catalog, messages and others).
- Enable the tools your team should use and disable the ones that don't apply.
- If you want, define where Maestro acts (per channel/inbox).
- Save the changes and test in the copilot: ask for an action and check that the corresponding card appears.
Settings & options
- Message tools: drafts and reply suggestions (usually always useful).
- CRM tools: create/update deals and records related to the contact.
- Company tools: see who works at each company, 360Β° overview, link the contact to a company and record relationships between people and companies.
- Calendar tools: propose and create appointments from the conversation.
- Catalog tools: build orders and suggest items during the conversation.
- Order (Commerce) tools: read the contact's purchase history and record manual sales in the orders registry.
- Campaign tools: follow status and delivery metrics, list recipients and operate the campaign (pause, resume, cancel, retry failures).
- Flow tools: start a published flow on the conversation, inspect sessions and unstick/cancel runs.
- Sales tools: seller portfolio, leaderboard, goals, unified revenue, commission simulator and order attribution/portfolio transfer (with human approval).
- Engagement tools: the lead score (cold/warm/hot) and the event timeline.
- Ads tools: the conversation's ad context (CTWA), leads, spend KPIs and CAPI conversions (actions that spend budget require human approval).
- Web search tools: search the public internet (
web_search) and read a page's text by URL (web_fetch). They sit under the Knowledge base category in the grid β they are knowledge from outside the account, unlike the knowledge base tools, which read your own material. They are read-only, send the contact nothing and depend on a Tavily key; without the key Maestro just carries on with what it already knows. - Scope per channel/inbox: control which inboxes Maestro may act in.
- Autonomy (per department): defines whether tools only suggest or execute after approval β see the departments article.
Use cases
- Release only message drafts for a team still getting to know Maestro.
- Enable CRM and Calendar tools for a sales team that creates deals and schedules meetings.
- Restrict Maestro to specific channels while you validate the results.
Tips, limits & best practices
- Enable the essentials first: start with a few tools and expand as adoption grows.
- Avoid enabling an excessive number of tools at once β there is a technical limit on tools per agent. If you hit the limit, disable the ones you don't use to free up space.
- Pair tools with the right autonomy: powerful tools should start with human approval.
- Review the list periodically to reflect the modules actually in use.
Troubleshooting
- An action doesn't appear in the copilot: confirm the tool is enabled and the module is active.
- I can't save the configuration / limit error: you may have exceeded the maximum number of tools β disable some and try again.
- Maestro doesn't act on a channel: check the scope per channel/inbox.
- The action appears but doesn't execute: check your permission on the module and the autonomy level.