The CRM ships with eight atomic agents in v1 — not twelve, and not one. Each agent has a single job and shares state with the others through the CRM database, never by direct invocation. The architecture is deliberately boring: lots of small agents earning trust independently beats one omniscient one.
| Agent key | What it does |
|---|---|
| aica-to-activity | Converts an AICA call payload into an Activity, linking to Account / Contact / Opportunity where possible. |
| summarise-call | Generates a structured summary of a call activity from its transcript. |
| email-draft | Drafts a reply email grounded in the activity thread and the opportunity context. |
| prep-call | Produces a pre-call brief: where the deal sits, what's been said, what to ask next. |
| icp-regen | Regenerates the ICP signal weights from won/lost outcomes. |
| deal-risk-flagger | Flags opportunities at risk of slipping based on activity cadence, MEDDPICC gaps, and stage age. |
| enrich-account | Fills firmographic gaps on an account from public signals. |
| detect-competitor-mention | Scans recent activities for competitor mentions and tags the opportunity. |
Module dependencies
Some agents need other modules subscribed. aica-to-activity requires AICA; if your tenant isn’t subscribed, the agent shows as skipped_missing_subscription in the runs log and the related CRM features stay greyed-out with a “Subscribe to AICA” upsell.
How agents are triggered
Most agents are triggered by webhooks (AICA, WhatsApp, Gmail) or by scheduled cadences (ICP regen, deal-risk flagging). You can also trigger them manually from the agents admin page for a single record — useful when you’re debugging or back-filling.