# What you can do over MCP and with the Asistente

> Area by area, what your AI can read and change in watsi over MCP, what the Asistente does inside the app, and which actions ask for a confirmation before reaching a customer.

Source: https://docs.watsi.ai/en/mcp/capabilities

There are two ways for an AI to work in your watsi workspace, and both use the same actions:

- **The MCP server** connects Claude, ChatGPT, Cursor or your own agent to your workspace. When you connect it you choose which permissions (scopes) it gets: most reads come ticked and every write comes unticked, so a connection with no writes can only look things up. How to connect it: [MCP server](/mcp).
- **The Asistente** is the AI that already lives inside watsi. You ask it in the app's chat and it works with your permissions, with no keys or connections. More about it: [watsi Asistente](/insights/assistant).

The tables below are generated from the same actions that both use, so they update on their own when something new ships.

## How each action is confirmed

Nothing writes directly to a customer, someone new or Meta in a single step, although some direct changes trigger the same scheduled follow-ups as in the app (below). Every action is one of these kinds:

| Kind              | Over MCP                                                                                                                                                                   | In the Asistente                                                                                                          |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Read**          | Looks it up and answers. Changes nothing.                                                                                                                                  | The same.                                                                                                                 |
| **Direct change** | Changes something inside watsi (a tag, a note, a draft) in one call.                                                                                                       | The same in most cases; some take a card (below).                                                                         |
| **Two steps**     | The first call does nothing: it answers with a preview and a `confirmToken`. Your AI shows you the preview and, once you confirm, redeems the token with `confirm_action`. | —                                                                                                                         |
| **Approval card** | —                                                                                                                                                                          | The Asistente does not apply the change: it shows you a card with what it will do, and the change happens when you click. |

Anything that writes to a customer, books or cancels an appointment, invites someone or sends something to Meta always takes two steps over MCP and a card in the Asistente. The Asistente also uses a card for changes that take effect at once even though they write to nobody (an agent's configuration, an appointment type's hours) and for some that cannot be undone (removing a calendar block, deleting a command); each row of the tables says which is which. The details of the two steps over the API: [Two-step actions](/guides/two-step-actions).

Some direct changes set off the same things they would in the app: marking whether a customer came to an appointment triggers the same follow-ups (the chat card, the after-sale sequence and, where it is on, the message that offers a no-show a new time), and assigning an advisor notifies them.

## How to read the tables

- **What you can do:** the action, in one line. For two-step actions, what happens once you confirm. When it says "Turned on per workspace", the action appears once that feature is on for your workspace.
- **Over MCP:** the tool's name and how it runs. When it says "Not yet; coming later", the MCP server does not publish it yet (it is not in `tools/list`), even if the Asistente already uses it.
- **In the Asistente:** whether it does it, and whether it asks you to approve it with a card.
- **Scope:** the permission the MCP connection or the API key needs. Writes and some reads are ticked separately; if you did not tick them when you connected, reconnect and tick them. Which ones, and how you get each, is in the scope table on [Authentication](/guides/authentication).

What stays in the watsi app on purpose: payments and billing, roles, owners and API keys, connecting integrations, and deleting contacts, agents or quotes.

## Conversations and inbox

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| Find conversations by status, assignee, stage, dates or unanswered, with the total. | `find_conversations` · read | Yes | `conversations:read` |
| Read a conversation: its messages and the AI summary. | `get_conversation` · read | Yes | `conversations:read` |
| Search for text inside messages. | `search_messages` · read | Yes | `conversations:read` |
| Set or clear one of your workspace's statuses on a chat. | `conversation_set_status` · direct change | Yes, with an approval card | `conversations:write` |
| Assign a conversation to a member, by name, email or id. | `conversation_assign` · direct change | Yes | `conversations:write` |
| Leave a conversation with no owner, with an optional reason. | `conversation_unassign` · direct change | Yes | `conversations:write` |
| Mark a conversation as resolved. | `conversation_resolve` · direct change | Yes | `conversations:write` |
| Reopen a resolved, cancelled or escalated conversation. | `conversation_reopen` · direct change | Yes | `conversations:write` |
| Escalate a conversation to the team, with a reason. | `conversation_escalate` · direct change | Yes | `conversations:write` |
| Pause the AI agent on one conversation for a while, or resume it. | `conversation_set_agent` · direct change | Yes | `conversations:write` |
| Turn the AI agent on or off in one conversation, until someone changes it. | `conversation_set_agent_enabled` · direct change | Yes, with an approval card | `conversations:write` |
| Choose which agent answers a conversation's customer. | `conversation_set_active_agent` · direct change | Yes, with an approval card | `conversations:write` |
| Mark a conversation as read or unread. | `conversation_mark_read` · direct change | Yes | `conversations:write` |
| Add or remove the members who observe a conversation's contact. | `conversation_set_observers` · direct change | Yes | `conversations:write` |
| See a conversation's internal notes, which only the team sees. | `conversation_list_notes` · read | Yes | `conversations:read` |
| Add an internal note to a conversation. | `conversation_add_note` · direct change | Yes | `conversations:write` |
| Change the text of an internal note. | `conversation_edit_note` · direct change | Yes | `conversations:write` |
| Delete an internal note (needs the `note:delete` permission). | `conversation_delete_note` · direct change | Yes | `conversations:write` |
| See your quick replies and the quick actions you hid. | `list_quick_replies` · read | Yes | `conversations:read` |
| Save a quick reply for your chat composer. | `quick_reply_create` · direct change | Yes | `conversations:write` |
| Hide a quick action from your composer, or show it again. | `quick_reply_set_hidden` · direct change | Yes | `conversations:write` |
| Create a custom status for the workspace's conversations. | `chat_status_create` · direct change | Yes | `conversations:write` |
| Rename a custom status or change its emoji. | `chat_status_update` · direct change | Yes | `conversations:write` |
| Change the order of the conversation statuses. | `chat_status_reorder` · direct change | Yes | `conversations:write` |
| Block or unblock a contact: the agent stops answering them. | `contact_set_blocked` · direct change | Yes | `conversations:write` |
| Reply to a customer in their conversation, inside the 24-hour window. | `conversation_reply` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `messages:write` |
| Send an approved WhatsApp template in a conversation. | `conversation_send_template` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `messages:write` |
| React to a customer's message with an emoji, or remove the reaction. | `conversation_react` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `messages:write` |
| Forward a message into other conversations. | `conversation_forward` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `messages:write` |
| Open a WhatsApp conversation with a number or a contact, with a template. | `start_conversation` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `broadcast:write` |

## Contacts and CRM

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| Find contacts by name, phone or email, most recent first. | `list_contacts` · read | Yes | `contacts:read` |
| Create a contact, or update the one that already has that phone or email. | `create_contact` · direct change | Yes | `contacts:write` |
| Add a tag to a contact. (Turned on per workspace). | `crm_tag_customer` · direct change | Yes | `crm:write` |
| Remove a tag from a contact. (Turned on per workspace). | `crm_untag_customer` · direct change | Yes | `crm:write` |
| Add a note to a contact. (Turned on per workspace). | `crm_create_note` · direct change | Yes | `crm:write` |
| Create a follow-up task for a contact. (Turned on per workspace). | `crm_create_task` · direct change | Yes | `crm:write` |
| Move a conversation to another funnel stage. (Turned on per workspace). | `crm_update_funnel_stage` · direct change | Yes | `crm:write` |
| Edit a contact: name, phone, email, relationship, lead quality and status, and observers. (Turned on per workspace). | `contact_update` · direct change | Yes | `contacts:write` |
| Set or remove a contact's advisor; the new advisor is notified. | `contact_assign_advisor` · direct change | Yes, with an approval card | `contacts:write` |
| Edit the text of a note on a contact's profile. (Turned on per workspace). | `crm_edit_note` · direct change | Yes | `crm:write` |
| Edit, complete, reopen or reassign one of your follow-up tasks. (Turned on per workspace). | `crm_update_task` · direct change | Yes | `crm:write` |
| See the channels and lead sources a contact is known by. | `contact_list_channels` · read | Yes | `contacts:read` |
| Attach a channel or lead source to a contact; a channel that belongs to another contact is refused. (Turned on per workspace). | `contact_add_channel` · direct change | Yes | `contacts:write` |
| Remove a channel that was added to a contact by hand. | `contact_remove_channel` · direct change | Yes, with an approval card | `contacts:write` |
| See the possible duplicate contacts waiting for review. | `pending_merge_list` · read | Yes | `contacts:read` |
| Reject a possible duplicate so the two contacts stay separate. | `pending_merge_reject` · direct change | Yes, with an approval card | `contacts:write` |
| See the leads from your forms, with their phone, email and answers. | `list_leads` · read | Yes | `leads:read` |
| Fetch from Meta the leads that had not arrived yet, once a minute. | `refresh_leads` · read | Yes | `leads:read` |
| Tag, or move to a funnel stage, every contact that matches a filter, in one go. | Not as such: over MCP you make the same change one record at a time, with the tools in this area. | Yes, with an approval card | — |

## Calendar and appointments

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| See appointment confirmation, attendance and no-show rates. | `appointment_stats` · read | Yes | `scheduling:read` + `workspace:read` |
| See the upcoming calendar appointments. | `list_appointments` · read | Yes | `scheduling:read` |
| Set team members' working hours for scheduling. | `set_member_schedules` · direct change | Yes, with an approval card | `scheduling:write` |
| Book an appointment; the customer is notified. | `book_appointment` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `scheduling:write` |
| Move an appointment to another time; the customer is notified. | `reschedule_appointment` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `scheduling:write` |
| Cancel an appointment; the customer is notified. | `cancel_appointment` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `scheduling:write` |
| Correct an appointment's email, notes or name; setting an email re-sends the invitation to it. | `update_appointment` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `scheduling:write` |
| See calendar blocks: when an advisor, an appointment type or the workspace cannot be booked. | `list_calendar_blocks` · read | Yes | `scheduling:read` |
| Block calendar time, one-off or recurring; nobody is notified. | `create_calendar_block` · direct change | Yes, with an approval card | `scheduling:write` |
| Change or pause a calendar block. | `update_calendar_block` · direct change | Yes, with an approval card | `scheduling:write` |
| Remove a calendar block so its time can be booked again. | `delete_calendar_block` · direct change | Yes, with an approval card | `scheduling:write` |
| See the appointment types: duration, whether active, and booking page. | `list_appointment_types` · read | Yes | `scheduling:read` |
| See an appointment type's team, breaks and weekly hours. | `get_appointment_type_schedule` · read | Yes | `scheduling:read` |
| Add a person to an appointment type's team. | `add_appointment_type_member` · direct change | Yes, with an approval card | `scheduling:write` |
| Remove a person from an appointment type's team. | `remove_appointment_type_member` · direct change | Yes, with an approval card | `scheduling:write` |
| Add a weekly break to an appointment type. | `create_appointment_type_break` · direct change | Yes, with an approval card | `scheduling:write` |
| Change or pause an appointment type's break. | `update_appointment_type_break` · direct change | Yes, with an approval card | `scheduling:write` |
| Remove an appointment type's break. | `delete_appointment_type_break` · direct change | Yes, with an approval card | `scheduling:write` |
| Replace an appointment type's weekly hours. | `set_appointment_type_weekly_rules` · direct change | Yes, with an approval card | `scheduling:write` |
| Create an appointment type: duration, notice, confirmation and agent. | `create_appointment_type` · direct change | Yes, with an approval card | `scheduling:write` |
| Change an appointment type, or stop offering it. | `update_appointment_type` · direct change | Yes, with an approval card | `scheduling:write` |
| See the rooms, offices or units appointments are booked in. | `list_spaces` · read | Yes | `scheduling:read` |
| Create a space appointments can be booked in. | `create_space` · direct change | Yes, with an approval card | `scheduling:write` |
| Change a space, or the advisors its chats go to. | `update_space` · direct change | Yes, with an approval card | `scheduling:write` |
| See when a space cannot be booked. | `list_space_blocks` · read | Yes | `scheduling:read` |
| Block a space for one appointment type or for all. | `create_space_block` · direct change | Yes, with an approval card | `scheduling:write` |
| Change a space block. | `update_space_block` · direct change | Yes, with an approval card | `scheduling:write` |
| Remove a space block so it can be booked again. | `delete_space_block` · direct change | Yes, with an approval card | `scheduling:write` |
| Mark whether the customer came to an appointment that has ended; it triggers the same follow-ups as in the app. | `mark_appointment_attendance` · direct change | Yes | `scheduling:write` |
| Record whether an appointment that has ended led to a sale. | `mark_appointment_sale` · direct change | Yes | `scheduling:write` |
| Accept a pending booking request; the customer is notified. | `accept_appointment_request` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `scheduling:write` |
| Decline a booking request with a reason; the customer is notified. | `decline_appointment_request` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `scheduling:write` |

## Quotes and contracts

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| Find quotes by status, contact, unit, development or advisor. (Turned on per workspace). | `list_quotes` · read | Yes | `quotes:read` |
| See one quote: totals, payment calendar, unit, status and customer link. (Turned on per workspace). | `get_quote` · read | Yes | `quotes:read` |
| See the units available to quote, with development and price. (Turned on per workspace). | `list_quotable_properties` · read | Yes | `quotes:read` |
| See the sales schemes and their rules, payment methods and what is missing. (Turned on per workspace). | `get_quoting_setup` · read | Yes | `quotes:read` |
| Create a draft quote for a unit, held to its scheme's rules. (Turned on per workspace). | `create_quote_draft` · direct change | Yes | `quotes:write` |
| Change a draft: contact, scheme, discount, validity or note. (Turned on per workspace). | `update_quote_draft` · direct change | Yes | `quotes:write` |
| Cancel a draft or sent quote. (Turned on per workspace). | `set_quote_status` · direct change | Yes | `quotes:write` |
| Copy a quote into a new draft of yours, as "Duplicate" does. (Turned on per workspace). | `duplicate_quote` · direct change | Yes | `quotes:write` |
| Get a 15-minute link to a quote's PDF. (Turned on per workspace). | `get_quote_pdf_link` · read | Yes | `quotes:read` |
| See the contract templates and the variables each one asks for. (Turned on per workspace). | `list_contract_templates` · read | Yes | `quotes:read` |
| See the contract of one of your quotes: status, template, values and what is missing. (Turned on per workspace). | `get_quote_contract` · read | Yes | `quotes:read` |
| Create the draft contract of one of your sent quotes. (Turned on per workspace). | `create_quote_contract` · direct change | Yes | `quotes:write` |
| Choose a draft contract's template and fill in its variables. (Turned on per workspace). | `update_quote_contract` · direct change | Yes | `quotes:write` |
| Send the customer the contract for their quote. (Turned on per workspace). | `prepare_quote_contract_send` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `quote_sends:write` |
| Create a sales scheme: payment plan, discount cap, price floor and taxes. (Turned on per workspace). | `create_quote_scheme` · direct change | Yes, with an approval card | `quotes:write` |
| Change a sales scheme; new quotes use the change. (Turned on per workspace). | `update_quote_scheme` · direct change | Yes, with an approval card | `quotes:write` |
| Change a payment method's label or whether it is offered. (Turned on per workspace). | `update_quote_payment_method` · direct change | Yes, with an approval card | `quotes:write` |
| Change a unit's price or status: the agent quotes it from its next reply, and marking it available releases the reservation. (Turned on per workspace). | `prepare_inventory_unit_update` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `quotes:write` |
| Send a quote to the customer. (Turned on per workspace). | `send_quote` · two steps: a preview, then `confirm_quote_send` | Yes, with an approval card | `quote_sends:write` |

## Tickets

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| See the support tickets you can see, most urgent first. (Turned on per workspace). | `list_tickets` · read | Yes | `tickets:read` |
| See one ticket: its fields, contact, who attends it and its history. (Turned on per workspace). | `get_ticket` · read | Yes | `tickets:read` |
| See the ticket types and the fields each one asks for. (Turned on per workspace). | `list_ticket_types` · read | Yes | `tickets:read` |
| Open a ticket for a contact, by type. (Turned on per workspace). | `create_ticket` · direct change | Yes | `tickets:write` |
| Start attending a ticket. (Turned on per workspace). | `claim_ticket` · direct change | Yes | `tickets:write` |
| Leave a team comment on a ticket. (Turned on per workspace). | `add_ticket_note` · direct change | Yes | `tickets:write` |
| Change the status, priority or owner of a ticket; resolving it notifies the customer. (Turned on per workspace). | `prepare_ticket_update` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `tickets:write` |
| Add a ticket type, with the fields and resolution reasons it asks for. (Turned on per workspace). | `create_ticket_type` · direct change | Yes, with an approval card | `tickets:write` |
| Change a ticket type's fields, owner, SLA or whether it is active. (Turned on per workspace). | `update_ticket_type` · direct change | Yes, with an approval card | `tickets:write` |

## Campaigns and templates

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| Send an approved template to a group of contacts. | `prepare_template_broadcast` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `broadcast:write` |
| Stop a broadcast; what was already delivered stays sent. | `cancel_template_broadcast` · direct change | Yes | `broadcast:write` |
| See how a bulk send went: accepted, delivered, read and blocked by Meta. | `broadcast_status` · read | Yes | `analytics:read` |
| See the WhatsApp campaigns with their status and numbers. | `list_campaigns` · read | Yes | `campaigns:read` |
| See one campaign: template, sending number, schedule, send window, numbers and estimated cost. | `get_campaign` · read | Yes | `campaigns:read` |
| See who a campaign went to and what happened to each message. | `list_campaign_recipients` · read | Yes | `campaigns:read` |
| Save a campaign draft: template, sending number and audience rule; it sends nothing. | `create_campaign_draft` · direct change | Yes | `broadcast:write` |
| Edit a campaign draft; it sends nothing. | `update_campaign_draft` · direct change | Yes | `broadcast:write` |
| Pause a running campaign; it is resumed from the app. | `pause_campaign` · direct change | Yes, with an approval card | `broadcast:write` |
| See the WhatsApp templates and their approval status. | `find_message_templates` · read | Yes | `templates:read` |
| Submit a WhatsApp template for Meta to review. | `prepare_message_template_submission` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `templates:write` |

## Comment automations

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| See the automations that answer Instagram and Facebook comments. | `list_comment_automations` · read | Yes | `integrations:read` |
| See what each automation did with each comment. | `list_comment_automation_activity` · read | Yes | `integrations:read` |
| Create a comment automation, always as a draft. | `create_comment_automation` · direct change | Yes | `automations:write` |
| Edit a draft or paused automation. | `update_comment_automation` · direct change | Yes | `automations:write` |
| Pause an active automation. | `pause_comment_automation` · direct change | Yes | `automations:write` |
| Copy an automation as a new draft. | `duplicate_comment_automation` · direct change | Yes | `automations:write` |
| Turn a comment automation on: from then on it answers public comments. | `prepare_comment_automation_activation` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `automations:write` |

## Agents, knowledge and files

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| See the workspace's AI agents. | `list_agents` · read | Yes | `agents:read` |
| See an agent's full configuration. | `get_agent_config` · read | Yes | `agents:read` |
| Create an AI agent. | `create_agent` · direct change | Yes, with an approval card | `agents:write` |
| Change an agent's configuration. | `update_agent_config` · direct change | Yes, with an approval card | `agents:write` |
| Set how conversations are assigned to the team. | `set_assignment_policy` · direct change | Yes, with an approval card | `agents:write` |
| Add a document to an agent's knowledge base. | `add_agent_knowledge` · direct change | Yes, with an approval card | `knowledge:write` |
| Remove a document from an agent's knowledge base. | `delete_agent_knowledge` · direct change | Yes, with an approval card | `knowledge:write` |
| Add a public web page to an agent's knowledge base. | `crawl_agent_website` · direct change | Yes, with an approval card | `knowledge:write` |
| Process an agent's knowledge documents again. | `retrain_agent_knowledge` · direct change | Yes | `knowledge:write` |
| Add questions and answers to an agent's knowledge base. | `import_agent_qa_pairs` · direct change | Yes, with an approval card | `knowledge:write` |
| See an agent's learned answers, suggested and saved. | `list_learned_answers` · read | Yes | `agents:read` |
| Find the saved learned answer closest to a suggestion. | `find_similar_learned_answer` · read | Yes | `agents:read` |
| Dismiss a suggested learned answer. | `dismiss_learned_answer` · direct change | Yes | `knowledge:write` |
| Save a suggested learned answer for the agent to use. | `save_learned_answer` · direct change | Yes, with an approval card | `knowledge:write` |
| Teach an agent a question and its answer. | `create_learned_answer` · direct change | Yes, with an approval card | `knowledge:write` |
| Correct a saved learned answer. | `edit_learned_answer` · direct change | Yes, with an approval card | `knowledge:write` |
| Delete a saved learned answer. | `delete_learned_answer` · direct change | Yes, with an approval card | `knowledge:write` |
| See an agent's saved versions and which one each channel serves. | `list_agent_versions` · read | Yes | `agents:read` |
| Rename a saved version of an agent. | `rename_agent_version` · direct change | Yes | `agents:write` |
| Bring an agent's draft back to a saved version. | `restore_agent_version` · direct change | Yes, with an approval card | `agents:write` |
| Publish a saved version on a channel the agent is already on. | `publish_agent_version` · direct change | Yes, with an approval card | `agents:write` |
| Try an agent with a message and see what it would answer, without writing to anyone. | `test_agent` · direct change | Yes | `agents:write` |
| Generate a property's frequently asked questions, published on its public page. | `generate_product_faqs` · direct change | Yes, with an approval card | `agents:write` |
| Choose which Google Ads conversion a funnel stage reports, or stop it reporting. | `set_stage_google_ads_conversion` · direct change | Yes, with an approval card | `agents:write` |
| See the files in the resource library. | `resources_list` · read | Yes | `resources:read` |
| See the details of one file in the resource library. | `resources_get` · read | Yes | `resources:read` |
| Get a short-lived link to upload a file. | `attachment_create_upload` · direct change | Not needed: in its chat you attach the file directly. | `agents:write` |
| Attach an uploaded file to Resources, a property or the knowledge base. | `attachment_finalize` · direct change | Yes, with an approval card | `agents:write` |
| Download a public https:// link and attach it in one step. | `attachment_import_url` · direct change | Yes, with an approval card | `agents:write` |

## Video calls

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| Find past video calls by what was said, contact, date, advisor or outcome. | `search_meetings` · read | Yes | `meetings:read` |
| See one video call: contact, advisor, duration, status and who spoke. | `get_meeting` · read | Yes | `meetings:read` |
| Read the AI summary of a video call: key points and next steps. | `get_meeting_summary` · read | Yes | `meetings:read` |
| Read the transcript of a video call. | `get_meeting_transcript` · read | Yes | `meetings:read` |
| See coming appointments and whether the assistant will join each. | `list_upcoming_meetings` · read | Yes | `meetings:read` |
| See which appointments the assistant joins across the workspace. | `get_meeting_assistant_settings` · read | Yes | `meetings:read` |
| Turn the video-call assistant on or off for one appointment. | `set_meeting_assistant` · direct change | Yes, with an approval card | `meetings:write` |
| Set which appointments the video-call assistant joins. | `update_meeting_assistant_settings` · direct change | Yes, with an approval card | `meetings:write` |

## Phone calls

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| See the agent's phone-calling configuration. | `voice_calling_config` · read | Yes | `agents:read` |
| See recent calls, inbound and outbound. | `list_voice_calls` · read | Yes | `agents:read` |
| Check, step by step, why the workspace can or cannot receive calls. | `diagnose_phone_calling` · read | Yes | `agents:read` |
| Change the phone-calling configuration. | `update_voice_calling_config` · direct change | Yes, with an approval card | `agents:write` |
| See the voices the phone agent can use and which one it uses today. | `list_voice_catalog` · read | Yes | `agents:read` |
| Ask watsi for a phone number for your workspace. | `prepare_phone_number_request` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `agents:write` |

## Reports

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| See the headline analytics: volume, AI response rate and trends. | `workspace_overview` · read | Yes | `analytics:read` |
| See each agent's conversation and response metrics. | `agent_performance_overview` · read | Yes | `analytics:read` |
| See handoffs to a person: rate, timing, by topic, stage and agent. | `escalation_breakdown` · read | Yes | `analytics:read` |
| See how contacts answered one profiling field. | `profiling_report` · read | Yes | `analytics:read` |
| See where leads came from (ads, links, sources). | `lead_attribution` · read | Yes | `analytics:read` |
| See what people write to you about, by topic, over a date range. | `conversations_report` · read | Yes | `analytics:read` |
| See the conversion funnel for a period: conversations, profiled contacts, appointments and attendance, with the drop-off at each step. | `funnel_conversion` · read | Yes | `analytics:read` |
| See the ads pipeline for a period, from Meta impression to sale. | `ads_pipeline_funnel` · read | Yes | `analytics:read` |
| See the appointments the agent could not book, and why (e.g. no appointment types). | `appointment_booking_failures` · read | Yes | `analytics:read` |
| See the spend, clicks and results of each Meta ad, and the prospects it brought. | `meta_ads_performance` · read | Yes | `analytics:read` |
| See the views, reach and engagement of the Instagram and Facebook posts. | `content_performance` · read | Yes | `analytics:read` |
| See who follows the Instagram account and the best times to post. | `content_audience` · read | Yes | `analytics:read` |
| See the conversations burning their response time right now. | `advisor_at_risk_conversations` · read | Yes | `analytics:read` |
| Download the conversations, the posts or the Meta ads as CSV, through a 15-minute link. | `prepare_analytics_export` · read | Yes | `analytics:read` |

## Workspace and team

| What you can do | Over MCP | In the Asistente | Scope |
| --- | --- | --- | --- |
| See the workspace's Google Ads conversions and which stages report each one. | `list_google_ads_conversion_actions` · read | Yes | `integrations:read` |
| See the team members and pending invitations. | `list_workspace_members` · read | Yes | `workspace:read` |
| Invite someone to your workspace by email. | `prepare_member_invite` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `members:write` |
| See the plan, subscription status, credits and seats. | `workspace_billing_status` · read | Yes | `billing:read` |
| See credit usage over a period, by day. | `workspace_credit_usage` · read | Yes | `billing:read` |
| See past payments (credit packs and invoices). | `workspace_payment_history` · read | Yes | `billing:read` |
| See the workspace's name, time zone and active integrations. | `workspace_settings` · read | Yes | `workspace:read` |
| See the connected channels and integrations. | `list_integrations` · read | Yes | `integrations:read` |
| See the workspace's notifications and your own preferences. | `notification_settings` · read | Yes | `workspace:read` |
| See which step of the initial setup the workspace is on. | `activation_progress` · read | Yes | `workspace:read` |
| Change which notifications admins and members get, by email and push. | `update_notification_matrix` · direct change | Yes, with an approval card | `notifications:write` |
| See your ⌘K menu commands and what each one can replay. | `list_operator_commands` · read | Yes | `workspace:read` |
| Save a ⌘K menu command for yourself. | `create_operator_command` · direct change | Yes | `commands:write` |
| Rename, rebind or re-record one of your commands. | `update_operator_command` · direct change | Yes | `commands:write` |
| Change the workspace time zone; the slots offered to your customers move to the new one. | `prepare_set_workspace_timezone` · two steps: a preview, then `confirm_action` | Yes, with an approval card | `workspace:write` |
| Cancel a pending invitation; nobody is emailed. | `revoke_member_invite` · direct change | Yes, with an approval card | `members:write` |
| Get a link to upload the workspace's new logo. | `prepare_company_logo_upload` · direct change | No: you upload it in the app. | `workspace:write` |
| Make the uploaded image the workspace's logo. | `set_company_logo` · direct change | No: you upload it in the app. | `workspace:write` |
| Delete one of your commands. | `delete_operator_command` · direct change | Yes, with an approval card | `commands:write` |
| Remove a member from the workspace. | Not offered over MCP. | Yes, with an approval card | — |
