Maestro AI & Account Brain
By Conversa Labs
By Conversa Labs
What Maestro is, voice onboarding, generative copilot (propose→confirm→execute), departments, risk, insights and per-module tools.
What is Maestro AI and the Account Brain
Overview Maestro AI is the artificial intelligence layer of ConversaLabs. It works as a copilot for your team: it suggests replies, drafts messages, runs actions across your modules (CRM, Calendar, Catalog and more) and helps you operate the account faster — always under your confirmation. The Account Brain (Maestro Brain) is your company's knowledge and context base inside the platform. Think of it as a "second brain" or digital twin: it gathers documents, objectives, concepts and relationships from your business into a searchable, traceable model. From that knowledge, Maestro produces answers that cite their source, organizes departments and generates analysis and insights. The relationship between the two is simple: the Brain is the source of truth (what your company is and knows) and Maestro AI is what uses that knowledge to act. The richer the Brain, the better Maestro's suggestions and actions. Prerequisites - A ConversaLabs account with Maestro enabled for your plan/account. - The Account Brain is an optional capability — it may depend on specific enablement for your account. If you can't find it, contact an administrator. - Administrator permission to configure, provision and adjust autonomy. - For voice/dictation features, an up-to-date browser with microphone permission. Step by step 1. Open the Account Brain area from the platform navigation. 2. Run the assisted onboarding (by voice or text) so Maestro understands your business and provisions the basics — see the voice onboarding article. 3. Feed the knowledge corpus with documents, objectives and operational information. 4. Use the generative copilot in conversations to suggest replies and propose actions. 5. Configure departments, autonomy, and review insights and risk analysis. Settings & options - Maestro per channel/inbox: you can control where Maestro acts. - Per-module tools: you enable which actions Maestro may propose/execute (CRM, Calendar, Catalog, etc.). - Autonomy: each department can run at an autonomy level (for example, read-only or with human approval) — nothing destructive happens without confirmation. - Knowledge (corpus): the sources the Brain indexes to answer with source references. Use cases - Speed up support replies with suggestions grounded in company knowledge. - Create CRM deals, schedule appointments and build orders straight from the conversation. - Centralize manuals, policies and objectives so the whole operation answers consistently. - Track risks and opportunities with automatically generated insights. Tips, limits & best practices - Start with onboarding and the corpus: Maestro is only as good as the knowledge it receives. - Keep knowledge up to date — stale information produces outdated suggestions. - Start with conservative autonomy (with approval) and increase as trust grows. - Maestro proposes; the team confirms. Use this to keep quality high. Troubleshooting - I don't see Maestro/the Brain: it may not be enabled for your account or profile — contact an administrator. - Suggestions feel generic: enrich the knowledge corpus and redo onboarding. - Nothing executes: confirm the module tools are enabled and that you have permission. See also - Voice onboarding and assisted setup - Generative copilot: propose, confirm and execute - Departments, risk analysis and insights - Maestro tools per module
Voice onboarding and assisted setup
Overview Voice onboarding is the Maestro Brain assistant that configures your account from a conversation. You describe your business — speaking or typing — and Maestro proposes an initial structure (such as departments and basic settings). You review everything and, once you confirm, the structure is provisioned. The flow always has three moments: briefing (you describe the business), review (you see the proposal) and apply (you confirm and Maestro provisions). Nothing is created without your review. Prerequisites - An account with Maestro enabled and the Account Brain available. - Administrator permission to apply the provisioning. - For voice dictation: an up-to-date browser with microphone permission. If voice isn't available, you can still complete the entire onboarding by text. Step by step 1. Open the Account Brain area and start the assisted setup (onboarding). 2. In the briefing, describe your business: what you do, how you serve customers, which areas/departments exist and what your goals are. You can dictate by voice or type. 3. Let the conversation flow: the assistant asks questions to understand the operation better. 4. Move to the review: Maestro shows the proposal (for example, suggested departments and initial settings). 5. Adjust what you want and click Apply to provision the structure in your account. 6. After applying, keep connecting channels, feeding knowledge and enabling modules. Settings & options - Voice input (dictation): speak instead of typing; handy to describe the business quickly. - Text input: a full alternative if voice isn't available. - Review before apply: the proposal is always presented for your confirmation. - Non-destructive provisioning: Maestro complements what's missing without overwriting what already exists — hand-made agents and settings are preserved. Use cases - Quickly set up a new account with a basic department structure. - Standardize the opening of new operations with a few guided questions. - Reuse the assistant to review and complete the structure of an account already in use. Tips, limits & best practices - The clearer your business description, the better the suggestions. - Speak in short, objective sentences when dictating; review the transcribed text before continuing. - Always review before applying — you can adjust everything later. - Onboarding is a starting point: dive deeper into each module in the categories of this Help Center. Troubleshooting - The assistant won't open: confirm Maestro is enabled and that you have administrator permission. - Voice/dictation doesn't work: check the microphone permission in your browser; use text input as an alternative. - Apply provisioned nothing: review the proposal, check error messages in the assistant and try again. If the account already has agents/structure, Maestro only complements what's missing. See also - What is Maestro AI and the Account Brain - Generative copilot: propose, confirm and execute - Departments, risk analysis and insights
Generative copilot: propose, confirm and execute
Overview The generative copilot is Maestro working alongside you in the conversation. Instead of only suggesting free text, it presents action cards: a message draft ready to send, or an action in a module (create a CRM deal, schedule an appointment, build a Catalog order). The principle is always the same: propose → confirm → execute. Maestro proposes the action, you review and confirm, and only then is it executed. This keeps you in control: nothing happens without your approval. Prerequisites - An account with Maestro enabled. - The per-module tools you want to use (CRM, Calendar, Catalog) must be enabled — see the per-module tools article. - Permission to act on the corresponding module (for example, create deals or schedule). Step by step 1. Open a conversation and trigger the Maestro copilot (the "ask Maestro" area). 2. Ask for what you need in natural language — for example, "reply confirming the time" or "create a deal for this contact". 3. Maestro proposes one or more cards: - Message draft: you can copy it or send it to the reply editor. - Module action: a CRM, Calendar or Catalog card with the suggested data. 4. Review the card content and adjust whatever is needed. 5. Confirm to execute the action (send the message or create the record). 6. Track the result in the card itself (in progress, done or error). Settings & options - Message drafts: always available; they help you write replies quickly. - CRM/Calendar/Catalog actions: appear according to the tools enabled for the account. - Automatic link to the conversation: actions created by the copilot are already associated with the current conversation (the deal/appointment is born linked to the right contact). - Reply editor: drafts can go straight into the reply field, respecting the channel type (plain or rich text). Use cases - Reply faster with a draft consistent with the conversation history. - Turn a conversation into a CRM deal without leaving the screen. - Schedule an appointment from the customer's request. - Build an order with Catalog items during the conversation. Tips, limits & best practices - Be specific in your request: the clearer the goal, the better the proposal. - Always review before confirming — the copilot suggests, but the decision is yours. - Only actions whose tools are enabled appear; if one is missing, enable it in Maestro's settings. - Use drafts as a base and personalize the tone for your customer. Troubleshooting - No action cards appear: confirm the module tools are enabled. - The action doesn't execute: check your permission on the module and whether there's an error message in the card. - The draft doesn't go to the reply: make sure the conversation/channel is selected and try again. See also - What is Maestro AI and the Account Brain - Maestro tools per module - Departments, risk analysis and insights
Departments, risk analysis and insights
Overview The Account Brain organizes Maestro's work into departments — operational areas such as support, sales, risk, finance and knowledge. Each department runs periodic routines over the account's conversations and data and produces two main outputs: risk analysis (signals of problems or attention) and insights (opportunities and recommendations). Each department has an autonomy level. At conservative levels, it only observes and suggests (read-only). At levels with human approval, it proposes actions that wait for your confirmation before any execution. Nothing destructive or final happens automatically without that approval. Prerequisites - An account with Maestro and the Account Brain enabled. - Administrator permission to create/adjust departments and autonomy. - Recommended: complete the onboarding (which already provisions the basic departments) and feed the knowledge corpus for richer analysis. Step by step 1. Open the Account Brain and go to the Departments area. 2. Review the provisioned departments (or create/enable the ones that make sense). 3. Set the autonomy level of each one (for example, read-only or with approval). 4. Let the routines run: Maestro processes conversations periodically. 5. Follow the risk analysis and the insights feed generated by the departments. 6. When there are proposals that require approval, review and confirm (or decline) each one. Settings & options - Departments: areas such as support, sales, risk, finance and knowledge. - Autonomy per department: from the most conservative (observes and suggests) to the most autonomous (executes what was approved). Start conservative and evolve. - Human approval (HITL): proposals wait for your decision before being executed. - Insights and risk: panels that consolidate what Maestro found, with source references when applicable. Use cases - Identify at-risk conversations (dissatisfaction, delays, churn) before they become problems. - Discover sales opportunities and next-action recommendations. - Distribute intelligence across areas, with the right level of automation for each one. - Standardize the operation with routines that run on their own and report what matters. Tips, limits & best practices - Start with conservative autonomy (read-only or with approval) and increase as trust grows. - The richer the knowledge corpus, the more accurate the risks and insights. - Departments may appear empty at first — they populate after the routines run. - Periodically review pending proposals so the queue doesn't pile up. Troubleshooting - Empty departments: confirm they are enabled and wait for the routines; check whether onboarding/ provisioning was applied. - No insights/risk: enrich the knowledge and confirm there are enough conversations to analyze. - Proposals don't execute: at approval levels, they depend on your confirmation — review the pending items. See also - What is Maestro AI and the Account Brain - Voice onboarding and assisted setup - Maestro tools per module
Maestro tools per module and how to enable them
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 1. Open the Maestro / Account Brain configuration area. 2. Find the list of tools per module (CRM, Calendar, Catalog, messages and others). 3. Enable the tools your team should use and disable the ones that don't apply. 4. If you want, define where Maestro acts (per channel/inbox). 5. 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. - Calendar tools: propose and create appointments from the conversation. - Catalog tools: build orders and suggest items during the conversation. - 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. See also - What is Maestro AI and the Account Brain - Generative copilot: propose, confirm and execute - Departments, risk analysis and insights