- Revenus de retraite et stratégie de décaissement
- Fiscalité : Roth/RRSP, récolte de pertes, évolutions réglementaires
- Succession, assurance et planification transfrontalière
- Outils du conseiller : préparation des rendez-vous, pré-contrôle de conformité
21 500+ compétences et agents. Tous gouvernés.
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
Partez d'une collection sélectionnée.
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.
- Service, ventes et customer success
- Service desk IT, RH et finance ops
- Réception juridique, achats et opérations terrain
- Risque et conformité
- Tri de la boîte de réception et rédaction d'e-mails
- Préparation de réunions, notes et suivi
- Planification intelligente et briefing quotidien
- Orchestration d'assistant de direction
- Sinistres intelligents, actuariat et AML
- Audit, GRC et reporting ESG
- ITAM / ITSM et opérations de sécurité
- Ateliers data et analytics
Trouvez la compétence dont votre équipe a besoin.
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
Summarize a supplied record — Support Team Lead, Customer Support
Summarize a supplied record for Support Team Lead teams in Customer Support, delivered by the Record 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.
Assess possible risk — Support Team Lead, Customer Support
Assess possible risk for Support Team Lead teams in Customer Support, delivered by the Record 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.
Flag items for human review — Support Team Lead, Customer Support
Flag items for human review for Support Team Lead teams in Customer Support, delivered by the Record 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 a parameterized read query — Support Team Lead, Customer Support
Run a parameterized read query for Support Team Lead teams in Customer Support, delivered by the Data Query & Summary 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 returned records — Support Team Lead, Customer Support
Summarize returned records for Support Team Lead teams in Customer Support, delivered by the Data Query & Summary 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 result-set overview — Support Team Lead, Customer Support
Prepare a result-set overview for Support Team Lead teams in Customer Support, delivered by the Data Query & Summary 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.
Check supplied context against policy — Support Team Lead, Customer Support
Check supplied context against policy for Support Team Lead 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 — Support Team Lead, Customer Support
Surface potential policy issues for Support Team Lead 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 — Support Team Lead, Customer Support
Recommend review items for Support Team Lead 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 — Support Team Lead, Customer Support
Assess supplied risk context for Support Team Lead 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 — Support Team Lead, Customer Support
Explain assessment drivers for Support Team Lead 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 — Support Team Lead, Customer Support
Recommend human review for Support Team Lead 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 — Support Team Lead, Customer Support
Query supplied record data for Support Team Lead 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 — Support Team Lead, Customer Support
Summarize potential discrepancies for Support Team Lead 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 — Support Team Lead, Customer Support
Prepare a reconciliation brief for Support Team Lead 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 — Support Team Lead, Customer Support
Assess a supplied exception for Support Team Lead 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 — Support Team Lead, Customer Support
Summarize the assessment for Support Team Lead 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 — Support Team Lead, Customer Support
Recommend follow-up review for Support Team Lead 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 — Support Team Lead, Customer Support
Run an on-demand read query for Support Team Lead 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 — Support Team Lead, Customer Support
Summarize query results for Support Team Lead 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 — Support Team Lead, Customer Support
Highlight supplied exceptions for Support Team Lead 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 — Support Team Lead, Customer Support
Assess supplied context for Support Team Lead 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 — Support Team Lead, Customer Support
Draft a recommended response for Support Team Lead 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 — Support Team Lead, Customer Support
Prepare rationale for review for Support Team Lead 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.
L'installation est la partie facile. La gouvernance vient avec.
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.
Choisissez dans le catalogue
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.
Reliez-le à votre stack
Connecteurs, serveurs MCP et imports OpenAPI — cadrés par des listes d'autorisation et le DLP au niveau de la passerelle.
Chaque exécution passe les verrous
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.
Vous ne trouvez pas la compétence qu'il vous faut ?
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.