The CRM app is the customer-facing slice of Apragya AI: who you sell to, what stage each deal is at, what conversations happened, what's next. It ships with a pre-built pipeline, contact + company directories, an activity timeline, a templated email engine, and AI agents already wired to the events that matter.
What's inside
- Pipeline - your deal stages (configurable, default 6), Kanban + table views, per-stage automation
- Contacts and Companies - linked to deals; custom-fields supported via TenantAppConfig
- Activities - calls, emails, tasks, meetings - rolled up onto contact + deal records
- Calendar - per-user + per-team views, shared with Activities
- Email Templates - tenant-authored, mergeable variables, attachable to any record
- Drip Campaigns - multi-step sequences, configurable per pipeline stage, with deliverability metrics
Bundled AI agents
- Lead Qualifier - scores inbound leads by ICP fit + intent signals; fires on lead.created
- Email Drafter - generates first-draft replies from prior thread context; manual trigger
- Activity Summarizer - rolls up the last 14 days of activity into a deal-status note
- Drip Campaign Composer - drafts the next email in a sequence based on the recipient's engagement
Every CRM record action writes a triggered-entity event (lead.created, deal.stage_changed, contact.updated, …) - bound agents fire automatically. If you build a custom agent, drop it on any of these events via the Automations tab and the rest of the wiring is done.
Configure on day one
- Pipeline stages - rename, reorder, add/remove. Each stage can have its own SLA and required fields
- Custom fields on contacts/companies/deals - JSONB overflow means no schema change required
- RBAC v3 - per-role view scopes (Mine / Team / All); used in 80% of tenants to fence sales reps to their own deals
- Email templates and drip sequences - load from the marketplace templates or author your own
Common workflows
Inbound lead lands -> Lead Qualifier scores -> if ICP fit -> auto-assign to the right rep based on territory rules -> rep gets a notification + the first-draft email already in the activity timeline. Whole loop takes about 4 seconds from form-fill to assigned, with the rep's first reply pre-staged.