5,814 agentes preconstruidos y 15,654 habilidades de biblioteca en 24 sectores y 12 roles por sector, instalables desde el catálogo, conectados a tus sistemas y ejecutados a través de la misma cadena de puertas de fallo cerrado que todo lo demás en Cortex.
21,511 plantillas de biblioteca en la matriz del catálogo
Suites creadas a mano para los trabajos que las empresas automatizan primero — cada colección se entrega gobernada, con políticas y auditoría incorporadas.
Busca entre 21,500+ habilidades y agentes gobernados, o filtra por sector y tipo: cada resultado se instala desde el catálogo y pasa por las mismas puertas.
864 resultados · Customer Support
Check supplied context against policy for Technical Support teams in Customer Support, delivered by the Compliance Checker pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface potential policy issues for Technical Support teams in Customer Support, delivered by the Compliance Checker pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend review items for Technical Support teams in Customer Support, delivered by the Compliance Checker pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied risk context for Technical Support teams in Customer Support, delivered by the Risk Assessment pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Explain assessment drivers for Technical Support teams in Customer Support, delivered by the Risk Assessment pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend human review for Technical Support teams in Customer Support, delivered by the Risk Assessment pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied record data for Technical Support teams in Customer Support, delivered by the Reconciliation Brief pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize potential discrepancies for Technical Support teams in Customer Support, delivered by the Reconciliation Brief pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a reconciliation brief for Technical Support teams in Customer Support, delivered by the Reconciliation Brief pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess a supplied exception for Technical Support teams in Customer Support, delivered by the Exception Review pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize the assessment for Technical Support teams in Customer Support, delivered by the Exception Review pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend follow-up review for Technical Support teams in Customer Support, delivered by the Exception Review pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Run an on-demand read query for Technical Support teams in Customer Support, delivered by the On-demand Reporting & Insights pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize query results for Technical Support teams in Customer Support, delivered by the On-demand Reporting & Insights pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Highlight supplied exceptions for Technical Support teams in Customer Support, delivered by the On-demand Reporting & Insights pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied context for Technical Support teams in Customer Support, delivered by the Decision Support pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a recommended response for Technical Support teams in Customer Support, delivered by the Decision Support pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare rationale for review for Technical Support teams in Customer Support, delivered by the Decision Support pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied work for Technical Support teams in Customer Support, delivered by the Routing Advisor pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess priority and risk for Technical Support teams in Customer Support, delivered by the Routing Advisor pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend a routing decision for Technical Support teams in Customer Support, delivered by the Routing Advisor pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied historical data for Technical Support teams in Customer Support, delivered by the Trend Briefing pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize observed trends for Technical Support teams in Customer Support, delivered by the Trend Briefing pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare questions for forecast review for Technical Support teams in Customer Support, delivered by the Trend Briefing pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Los agentes de la biblioteca no son scripts: son identidades gobernadas. Instalar uno lo registra con un propietario, un presupuesto, modelos y acciones permitidos y un lugar en el registro de auditoría.
Filtra por tu industria y tu rol; cada elemento indica los sistemas a los que se conecta y las habilidades que invoca.
Conectores, servidores MCP e importaciones OpenAPI — acotados por listas de permitidos y DLP en el gateway.
Identidad, presupuesto, guardrails, registro, Control Tower, ejecución, guarda de salida — y luego un recibo firmado en el Trust Ledger. En todos los planes.
El constructor visual de habilidades permite lanzar nuevas habilidades sin código — o dinos qué te falta y te señalaremos el patrón gobernado más cercano.