Update to CRM Connector

"---\nname: plan-an-ai-agent\ndescription: Answer questions about CRM Connector AI Agents before anything is set up. Use it when a person asks whether ChatGPT can work with the customers, deals, invoices or quotes in their own CRM or accounting system, what an AI agent can do in a particular system, which systems have an AI agent, or what the difference between AI Analyst and AI Agent is.\n---\n\n# Explore what an AI agent can do\n\nThis belongs to part 1 of the plugin, **AI Agents inside one system**. An AI agent works with the records of one of the person's own systems, right here in the chat: it reads their customers, deals, invoices and quotes, and when they allow it, it changes records and keeps automations running in that system. None of these questions needs a CRM Connector account. Answer from the tools, then offer the next step.\n\n## What AI Agents is\n\n- \"Can ChatGPT work with my CRM?\", \"Can you update my deals for me?\", \"Can you read my invoices?\"\n- Call `get_ai_agent_options` without a system. It explains AI Agents and names the systems that have an AI agent.\n- Explain the two packages in plain words:\n  - **AI Analyst** reads: it searches and reads records, counts and adds them up, and finds the same customer in the person's other connected systems.\n  - **AI Agent** also changes records when the person asks: fields, stages, notes, tasks, activities, line items and links. Every change is shown first and only written after a yes; risky ones the person approves in CRM Connector. It can also keep automations running: fixed rules inside that system, approved once.\n- Say what it never does and what waits for the customer: it never deletes a record, it records a payment only where the system allows it and after the customer approves it, and it does not sync between two systems. Syncing between two systems is an integration, part 2 of the plugin.\n- Do not call `search_records` or other record tools for this: they work on an agent that is already set up.\n\n## What an agent can do in one system\n\n- \"What can an AI agent do in my CRM?\", \"Can it move deals between stages?\", \"Can it add tasks?\"\n- Call `get_ai_agent_options` with the system. It lists per record type whether the agent can read it and change it, the actions it can take there, what it cannot do yet, and what its automations can use.\n- Answer only from that list. When something the person wants is not in it, say so plainly and offer to request it with `send_request`.\n\n## Several accounts\n\n- One AI agent works in one account of a system: one GoHighLevel sub-account, one HubSpot portal, one QuickBooks Online company. Someone with several accounts, such as an agency with many sub-accounts, sets up one agent per account, each with its own place.\n- In the chat they then name the account they mean, and the assistant can answer across accounts one agent at a time.\n\n## Ideas to try\n\n- When the person is unsure what to use it for, give a few examples that fit what the tool returned for their system, such as:\n  - \"Which deals did not move in the last two weeks?\"\n  - \"Add a follow-up task to every open quote older than a week.\"\n  - \"Whenever a deal is won, add a kick-off task due in two days.\" (an automation, see the `automate-workflows` skill)\n- If the tool answer carries automation ideas for that system, pass those on.\n\n## Next step\n\n- **Set it up right here**: when `plan_ai_agent` says the system is already connected to their account (an installed app's sub-accounts, or a system they signed in to), the agent can be saved in the chat instead of through the link. Call `set_up_ai_agent` without `confirm` and show its review: per account what is saved, the package, what it may do per record type and the actions. Only after their yes call it again with the same arguments and `confirm` true, and share the link to each saved agent. Nothing is bought in the chat: an agent without an unused place is saved and waits to be switched on in CRM Connector, and it can be tried first: up to 100 records read and 25 changes.\n- **Plan it**: ask what the agent should read and what it may change, then call `plan_ai_agent` and share the link it returns. It opens the setup in CRM Connector filled in, where the person signs in to their system. The plan is saved under AI Agents; nothing works until they finish it. With AI Agent, the plan also names two or three automations that fit and switches on the actions they need.\n- **Back from the setup**: the setup page sends the person back here and asks them to say \"done\" (or ask them to, once the setup is saved). Then call `get_ai_agent_options` with the system to check that the agent is saved.\n- **Test it**: before the agent is switched on, it can be tried here in the chat before it is switched on: it reads up to 100 records of that system with every read tool, filters, counting, reports and lists included, and makes up to 25 changes the person agrees to. Offer a first question that shows its value, such as their open deals by stage or five newest contacts, then a small change. Sending messages, recording payments and voiding wait until it is switched on. Answers say how much of the test is left.\n- **A first automation**: offer one of the automations the plan named. `propose_automation` writes it right away, also before the agent is switched on; the person's yes approves it with `set_automation_status`, and it starts the moment the agent is switched on (see the `automate-workflows` skill).\n- **Switch it on**: when the person wants the agent to work for real, share the Switch it on link the tool answer gives. One step there switches on every agent that waits.\n- **No key or token**: when a tool answer names an app that connects the system without a key or token, offer that way in.\n- **Already set up**: when the person has an agent, continue with the `manage-business-records` skill.\n- **Another system**: when their system has no AI agent yet, offer `send_request` with kind `ai_access`, the system, `read` or `read_write`, and in the details what the agent should do there. Show what will be sent and send it only after the person confirms.\n\n## Rules\n\n- Only describe what the tools return. Never name a system as having an AI agent unless a tool answer names it.\n- Keep AI Agents and integrations apart, and ask which one the person needs when it is not clear.\n- Do not discuss prices, fees, plans, trials or discounts.\n- Never ask for passwords, API keys or tokens. Systems are connected inside the CRM Connector app, never in the conversation.\n"