Skip to content
NagentNagent
Log inSign upHire your AI Growth Team
NagentNagent
Log inSign up
All documentation

CORA's CRM

Your leads and pipeline in Nagent, how agents read and write them, how email to a lead is written and sent from a rep's own mailbox, and where agent work waits for your approval.

Browse documentation

One pipeline, worked by people and agents on the same record

CORA's CRM is where your leads live in Nagent, and where your sales agents do their work on them. CORA, your CRM teammate, leads the team that works it. A rep and an agent look at the same lead, the same stage and the same email thread. When an agent moves something, the record says so; when it wants to write to a lead, the draft waits for a person first.

You reach it from CRM in the sidebar, which opens Leads. Accounts groups leads by company.

Accounts for Prompt World, with eight companies and the people at each

The CRM team comes with every workspace

Every new workspace gets a team room called CRM team, whatever you pick at sign-up. It is led by CORA, the Customer Outcomes and Relationships Agent, and its charter says the room carries your deals "from first touch to a kept customer".

The lead list also opens inside a room. In the CRM team room and the Sales room, open Team surface and choose the CRM tab: the same list, with the same filters, without leaving the room. Opening a single lead, or another CRM screen, shows Open full page instead. A workspace without the CRM in its sidebar has no CRM tab either.

Leads

The Leads page lists every lead in your workspace, in a list or as a kanban board with one column per pipeline stage. Drag a card to another column to move the lead to that stage.

The Leads list for Prompt World, eight leads with their company, intent and pipeline stage

Filter by:

FilterOptions
IntentHigh, medium or low
StatusAny pipeline stage
SourceWebsite forms, content pages, chatbot, Cal.id bookings, manual or admin, prospecting
OwnerAll owners, My leads, Unassigned
From and ToThe date the lead was created

Four ways to add leads sit above the list:

  1. New lead: type one in.
  2. Quick intake: paste an email or chat thread, and the lead's fields are read out of it for you to check.
  3. Bulk import: upload a spreadsheet or CSV of up to 5,000 contacts, and optionally enrol them in a sequence.
  4. Leads also arrive on their own from your website forms, chatbot and booking links once those are connected.

Bulk import, with a file picker, an optional sequence to enrol into, a source label and tags

Export CSV takes the filtered list away as a file.

Who owns a new lead

A lead you type in with New lead is yours, if you hold a sales or admin role. A lead that arrives from your forms or chatbot is given an owner automatically: the member of your workspace with a sales or admin role who has the fewest open leads. Only people who have joined your workspace are considered. If nobody qualifies, the lead stays unassigned rather than going to anyone outside it, and changing a lead's owner to someone who is not a member of the workspace is refused.

Content attribution

Content attribution, beside Export CSV, opens a breakdown of the leads that came from a content page: an artefact, a blog post or essay, or a comparison page. Choose a window of 30, 90, 180 or 365 days. It shows:

PanelWhat it counts
TotalsLeads from content, High intent, Booked a demo, Won
By kind of pageLeads, bookings and wins for artefacts, blog and essays, and the comparison hub
What sent themThe channel each visitor came from: an AI assistant, search, social, another site or direct
Top pagesEach page with its leads, high-intent leads, bookings, wins and latest lead

It reads the page a lead was captured on, so it fills only for leads that arrived through those pages. A workspace whose leads come from elsewhere sees "No content leads in this window."

The Content attribution view with its 30, 90, 180 and 365 day windows, the four totals, and the By kind of page, What sent them and Top pages tables

The pipeline

Every workspace starts with thirteen stages: New, Contacted, Engaged, Demo Scheduled, Demo Held, Evaluating, POC, Proposal Sent, Negotiation, Verbal Commit, Contract Sent, Won and Lost.

To fit them to how you sell, open Settings, CRM:

  • Pipeline stages: rename and reorder them. Adding or removing stages is not available yet, and each stage keeps its kind: open, won or lost.
  • Lost reasons: rename the reasons offered when a deal is lost.
  • Currency and escalation: your default currency, and the deal value above which a lead escalates to a person.
  • Hot-lead rules: the minimum intent, the ICP bands and the reply window that make a lead show as hot.

Nothing is saved until you press Save changes. Restore defaults returns every setting on the page to the built-in defaults.

CRM settings, with the sending account card above the pipeline stages table

The lead page

Open a lead to see everything about it in one place. The main tabs are Timeline, Emails, Notes, Meetings, Files and Research, with transcripts, proposals, company intelligence and comments under More.

A lead page for a Marketing Director at a fictional retailer, with the stage bar, the contact card and a drafted first email waiting for Approve and send

The lead's score shows its ICP fit as Strong fit, Medium fit, Weak fit or Out of ICP, with Rescore to compute it again. The Meetings tab schedules an upcoming meeting or logs one that has happened; see Meetings.

From Demo Held onwards, two more cards sit in the right-hand column. Deal Room creates and shares the private page the buyer opens, and Contract is where order forms will be drafted once DEXA, which is coming soon, arrives. See order forms and contracts.

Each lead also carries Data subject rights: export everything held on the person, or erase them. Erasure cannot be undone and keeps only the audit record that it happened.

Who writes the email

Two AI teammates write email to leads, and both join every Sales team. You will see them on the org chart with a Beta chip.

TeammateWrites toFrom
LIPI, CRM Email WriterPeople your workspace has already spoken toThe lead's record and conversation
VANI, Outbound Email WriterProspects who have never repliedNORA's research dossier

Both write only from your own material: their prompt, which you can edit in the Agent Workbench, your Knowledge Hub, your brand voice and your products and services. Every product or outcome a draft names must come from your list of offerings. A draft signs off as the lead's owner, or as your company's team when the lead has none.

If your workspace has no offerings and no knowledge yet, you still get a draft, but it makes no product claim and the lead page says: "Drafted on your brand name only. Add Offerings or knowledge and the next draft will use them."

Our logic: an email that names a product you do not sell is worse than no email. Grounding the writers in your material alone is what lets you trust a draft enough to approve it.

Opt-outs are honoured on both sides of the CRM. A sequence email to a lead carries an Unsubscribe link that marks the lead unsubscribed and ends their active enrolments, and no sequence, nurture follow-up or sales agent email goes to a lead marked that way. A prospect who opted out of NORA's outbound email arrives in the CRM already marked unsubscribed, and the sequencer checks the workspace's suppression list before every send. No agent can clear either mark. See unsubscribe and suppression.

Sending from your own mailbox

By default, email to leads leaves from your workspace's sending address. A rep can instead send from their own Gmail or Outlook mailbox, so the lead hears from a person and replies land in that person's inbox. This is in Beta.

  1. Open Settings, CRM and find Your sending account.
  2. Read Before you connect. The connection can read mail only from addresses already in your CRM, your workspace admin can see and revoke it, and it stays with the workspace if you leave.
  3. Choose Connect Gmail or Connect Outlook and approve the request with your mail provider.
  4. Reload the page. The card reads "Connected and sending."

Once connected:

  • Approved agent follow-ups to a lead go out from the mailbox of the person who owns that lead. A lead with no owner, or an owner with no mailbox, uses the workspace address. Sequence emails, and an email you write and send by hand from the lead page, still leave from the workspace address.
  • Replies from your leads are pulled onto the lead's timeline, so reply detection and stage movement keep working. Nothing else in the mailbox is read or stored.
  • Each rep has one sending mailbox. Connecting a different one makes it the sender; the old one stops sending but keeps collecting replies to threads that left it.
  • If a mailbox reaches its daily sending limit, further email that day goes from the workspace address and starts a fresh thread rather than switching addresses inside a live one.
  • Password resets, invitations and digests never leave a rep's mailbox.

Disconnect returns that rep's email to the workspace address.

What agents read and write

AgentReadsWrites
NORA, in the Sales roomEach open lead's stage, owner, value and last activity. Never notesNothing, from the room
LIPI and VANIThe lead, your knowledge and offeringsDrafts only

DEXA (deal execution) and RIVA (revenue operations) are coming soon. Neither will be able to change a deal's amount, stage or owner: those three are what pipeline health is measured on, and an agent that could move them could improve its own report.

Where Nagent has set up CORA's CRM agents for your workspace, a further group works the records: outreach (follow-ups, nudges, post-demo recaps, break-up emails), enrichment, scoring, meeting booking and data health. They start at L3, where every email and every booking waits for approval, while scoring, enrichment and stage changes go ahead and are logged. See autonomy and governance.

Where agent work waits for you

  • Approval queue: every next-best action an agent has drafted across the pipeline, sorted by urgency and risk. Approve sends the drafted email straight away; Edit opens the lead to change it; Dismiss hides it for seven days.
  • Reply triage: inbound replies, sorted by priority, with a jump to the lead to answer.
  • Actions: every agent action that is waiting for approval, across all agents.

The Approval queue with four drafted next actions for Prompt World leads, each with Approve and send, Edit and Dismiss

Where to go next