5,814 agents prêts à l'emploi et 15,654 compétences de bibliothèque couvrant 24 secteurs et 12 métiers par secteur — installables depuis le catalogue, connectés à vos systèmes et exécutés à travers la même chaîne de contrôles en échec fermé que tout le reste sur Cortex.
21,511 modèles de bibliothèque dans la matrice du catalogue
Des suites conçues à la main pour les tâches que les entreprises automatisent en premier — chaque collection est livrée gouvernée, politiques et audit inclus.
Recherchez parmi 21,500+ compétences et agents gouvernés, ou filtrez par secteur et par type : chaque résultat s'installe depuis le catalogue et franchit les mêmes points de contrôle.
864 résultats · Customer Support
Check supplied context against policy for Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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 Voice of Customer Analyst 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.
Les agents de la bibliothèque ne sont pas des scripts — ce sont des identités gouvernées. En installer un l'enregistre avec un propriétaire, un budget, des modèles et des actions autorisés, et une place dans le registre d'audit.
Filtrez par secteur et par rôle ; chaque élément indique les systèmes auxquels il se connecte et les compétences qu'il invoque.
Connecteurs, serveurs MCP et imports OpenAPI — cadrés par des listes d'autorisation et le DLP au niveau de la passerelle.
Identité, budget, garde-fous, registre, Control Tower, exécution, garde-fou de sortie — puis un reçu signé dans le Trust Ledger. Sur toutes les formules.
Le générateur visuel de compétences livre de nouvelles compétences sans code — ou dites-nous ce qui manque et nous vous orienterons vers le modèle gouverné le plus proche.