- 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
Search approved onboarding knowledge — Technical Support, Customer Support
Search approved onboarding knowledge for Technical Support teams in Customer Support, delivered by the Onboarding Guide 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 step-by-step guidance — Technical Support, Customer Support
Draft step-by-step guidance for Technical Support teams in Customer Support, delivered by the Onboarding Guide 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 review checklist — Technical Support, Customer Support
Prepare a review checklist for Technical Support teams in Customer Support, delivered by the Onboarding Guide 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 feedback — Technical Support, Customer Support
Summarize supplied feedback for Technical Support teams in Customer Support, delivered by the Feedback 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.
Surface recurring points — Technical Support, Customer Support
Surface recurring points for Technical Support teams in Customer Support, delivered by the Feedback 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 follow-up questions — Technical Support, Customer Support
Prepare follow-up questions for Technical Support teams in Customer Support, delivered by the Feedback 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.
Search approved knowledge — Technical Support, Customer Support
Search approved knowledge for Technical Support teams in Customer Support, delivered by the Research & Discovery 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 findings — Technical Support, Customer Support
Summarize supplied findings for Technical Support teams in Customer Support, delivered by the Research & Discovery 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 research brief — Technical Support, Customer Support
Draft a research brief for Technical Support teams in Customer Support, delivered by the Research & Discovery 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.
Search approved process knowledge — Technical Support, Customer Support
Search approved process knowledge for Technical Support teams in Customer Support, delivered by the Process Guidance 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 process context — Technical Support, Customer Support
Summarize supplied process context for Technical Support teams in Customer Support, delivered by the Process Guidance 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 next-step guidance — Technical Support, Customer Support
Draft next-step guidance for Technical Support teams in Customer Support, delivered by the Process Guidance 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 request context — Support Team Lead, Customer Support
Summarize supplied request context for Support Team Lead teams in Customer Support, delivered by the Intake Review & Triage 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 urgency and risk — Support Team Lead, Customer Support
Assess urgency and risk for Support Team Lead teams in Customer Support, delivered by the Intake Review & Triage 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 review priority — Support Team Lead, Customer Support
Recommend a review priority for Support Team Lead teams in Customer Support, delivered by the Intake Review & Triage 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.
Condense supplied content — Support Team Lead, Customer Support
Condense supplied content for Support Team Lead teams in Customer Support, delivered by the Document Summarizer 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 key points — Support Team Lead, Customer Support
Surface key points for Support Team Lead teams in Customer Support, delivered by the Document Summarizer 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.
Produce a concise brief — Support Team Lead, Customer Support
Produce a concise brief for Support Team Lead teams in Customer Support, delivered by the Document Summarizer 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.
Search approved knowledge — Support Team Lead, Customer Support
Search approved knowledge for Support Team Lead teams in Customer Support, delivered by the Q&A Assistant 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 grounded response — Support Team Lead, Customer Support
Draft a grounded response for Support Team Lead teams in Customer Support, delivered by the Q&A Assistant 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 review-ready answer — Support Team Lead, Customer Support
Prepare a review-ready answer for Support Team Lead teams in Customer Support, delivered by the Q&A Assistant 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 from supplied context — Support Team Lead, Customer Support
Draft from supplied context for Support Team Lead teams in Customer Support, delivered by the Drafting & Generation 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.
Follow configured behavior guidance — Support Team Lead, Customer Support
Follow configured behavior guidance for Support Team Lead teams in Customer Support, delivered by the Drafting & Generation 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 copy for revision — Support Team Lead, Customer Support
Prepare copy for revision for Support Team Lead teams in Customer Support, delivered by the Drafting & Generation 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.