- 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.
2 052 résultats · Compétences · “Sales”
Search approved knowledge — Revenue Operations, Sales
Search approved knowledge for Revenue Operations teams in Sales, delivered by the Q&A Assistant pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a grounded response — Revenue Operations, Sales
Draft a grounded response for Revenue Operations teams in Sales, delivered by the Q&A Assistant pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a review-ready answer — Revenue Operations, Sales
Prepare a review-ready answer for Revenue Operations teams in Sales, delivered by the Q&A Assistant pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft from supplied context — Revenue Operations, Sales
Draft from supplied context for Revenue Operations teams in Sales, delivered by the Drafting & Generation pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Follow configured behavior guidance — Revenue Operations, Sales
Follow configured behavior guidance for Revenue Operations teams in Sales, delivered by the Drafting & Generation pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare copy for revision — Revenue Operations, Sales
Prepare copy for revision for Revenue Operations teams in Sales, delivered by the Drafting & Generation pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize a supplied record — Revenue Operations, Sales
Summarize a supplied record for Revenue Operations teams in Sales, delivered by the Record Review pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess possible risk — Revenue Operations, Sales
Assess possible risk for Revenue Operations teams in Sales, delivered by the Record Review pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Flag items for human review — Revenue Operations, Sales
Flag items for human review for Revenue Operations teams in Sales, delivered by the Record Review pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Run a parameterized read query — Revenue Operations, Sales
Run a parameterized read query for Revenue Operations teams in Sales, delivered by the Data Query & Summary pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize returned records — Revenue Operations, Sales
Summarize returned records for Revenue Operations teams in Sales, delivered by the Data Query & Summary pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a result-set overview — Revenue Operations, Sales
Prepare a result-set overview for Revenue Operations teams in Sales, delivered by the Data Query & Summary pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Check supplied context against policy — Revenue Operations, Sales
Check supplied context against policy for Revenue Operations teams in Sales, delivered by the Compliance Checker pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface potential policy issues — Revenue Operations, Sales
Surface potential policy issues for Revenue Operations teams in Sales, delivered by the Compliance Checker pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend review items — Revenue Operations, Sales
Recommend review items for Revenue Operations teams in Sales, delivered by the Compliance Checker pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied risk context — Revenue Operations, Sales
Assess supplied risk context for Revenue Operations teams in Sales, delivered by the Risk Assessment pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Explain assessment drivers — Revenue Operations, Sales
Explain assessment drivers for Revenue Operations teams in Sales, delivered by the Risk Assessment pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend human review — Revenue Operations, Sales
Recommend human review for Revenue Operations teams in Sales, delivered by the Risk Assessment pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied record data — Revenue Operations, Sales
Query supplied record data for Revenue Operations teams in Sales, delivered by the Reconciliation Brief pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize potential discrepancies — Revenue Operations, Sales
Summarize potential discrepancies for Revenue Operations teams in Sales, delivered by the Reconciliation Brief pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a reconciliation brief — Revenue Operations, Sales
Prepare a reconciliation brief for Revenue Operations teams in Sales, delivered by the Reconciliation Brief pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess a supplied exception — Revenue Operations, Sales
Assess a supplied exception for Revenue Operations teams in Sales, delivered by the Exception Review pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize the assessment — Revenue Operations, Sales
Summarize the assessment for Revenue Operations teams in Sales, delivered by the Exception Review pattern from supplied context. Salesforce and HubSpot are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend follow-up review — Revenue Operations, Sales
Recommend follow-up review for Revenue Operations teams in Sales, delivered by the Exception Review pattern from supplied context. Salesforce and HubSpot 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.