Overview
Maestro AI is the artificial intelligence layer of Conversa Labs. 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 Conversa Labs 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.
- Per-account AI keys (optional): under Integrations you connect provider keys (OpenAI, Anthropic, Google, Groq, xAI, DeepSeek, OpenRouter, Cohere, ElevenLabs) used by this account's agents — the Cohere key also keeps the knowledge base indexing as a fallback.
- Tavily key (optional): it sits on the same screen but is not a chat provider — no model ever runs on it and it never appears in the robot's model chain. It is the key that unlocks the web search and page reading tools.
Step by step
- Open the Account Brain area from the platform navigation.
- Run the assisted onboarding (by voice or text) so Maestro understands your business and provisions the basics — see the voice onboarding article.
- Feed the knowledge corpus with documents, objectives and operational information.
- Use the generative copilot in conversations to suggest replies and propose actions.
- 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.
- Language: by default the robot speaks the account's language — see the section below.
Which language the robot replies in
The account's language is the baseline. It is the language set in Settings → Account — the same one that drives the dashboard — and the robot writes in it by default, with nothing for you to configure.
Two things change that:
- The contact writes in another language. If someone clearly writes in Spanish to an account set to Portuguese, the robot answers in Spanish and keeps following the contact for as long as they use that language. This is automatic and needs no setting.
- You pin a language on the robot. In the robot's form, the Language field defaults to Automatic (account language). Pick a specific language and it applies to that robot, even if the account uses a different one.
So the order is: the language picked on the robot → the account's language → the contact can override it by what they write. The same language drives the other surfaces: audio transcription, image and document reading, the conversation summary, copilot suggestions and voice calls.
Every language the platform supports is available (not just Portuguese, English and Spanish).
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.