Skip to main content
Doris periodically scans your CRM data against recent sales conversations and proposes field-level updates — so your pipeline stays accurate without manual data entry.

​
How it works

CRM Pulse runs automatically in the background. It compares what’s been discussed in your meetings against what’s currently in your CRM, and surfaces discrepancies as proposed updates.
  1. Scan — Doris reviews your active deals, pulling recent call summaries and current CRM field values
  2. Compare — For each deal, Doris checks whether conversation evidence suggests a field is stale, missing, or incorrect
  3. Propose — Updates are staged with a clear diff showing the current value and the proposed change, along with the reasoning
  4. Review — You approve or skip each update individually, or use bulk actions to move through them quickly
CRM Pulse results appear in your Outbox as a dedicated thread, complete with an email notification when new updates are ready.

​
The CRM Pulse Card

When Doris finds updates to propose, they appear as an interactive card in your Outbox thread:

CRM Provider Logo

The card header shows your connected CRM (HubSpot, Salesforce, or Zendesk) so you know exactly where changes will be applied.

Field-Level Diffs

Each proposed update shows the field name, the current value (greyed out with strikethrough), and the new value (highlighted in green) with an arrow between them.

Evidence-Based Reasoning

Every update includes a one-line reason explaining what conversation evidence supports the change.

Approve or Skip

Review each update individually with Approve and Skip buttons, or use the bulk action bar to approve or skip all updates at once.
Updates are grouped by entity type — Deals, Contacts, and Companies — with collapsible sections so you can focus on what matters most.

​
What CRM Pulse looks for

CRM Pulse prioritizes updates by impact:
PriorityCategoryExamples
HighMissing critical fieldsDeal amount, close date, or stage not set
MediumStale dataClose date has passed, stage doesn’t match recent conversation signals
LowEnrichmentContact title or company details mentioned in calls but not in CRM
CRM Pulse checks your previous scan results to avoid re-proposing updates you’ve already skipped. If you skip an update, it won’t come back unless new evidence emerges.

​
Applying Updates

When you approve an update, Doris writes the change directly to your CRM through the connected integration. The update status changes in real-time:
  • Pending — Awaiting your review
  • Applying — Being written to your CRM
  • Applied — Successfully updated in your CRM
  • Skipped — You chose to skip this update
  • Failed — The CRM write failed (you can retry)

​
Email Notifications

When CRM Pulse completes a scan and finds updates, you receive an email summary with:
  • How many deals were scanned
  • How many updates are proposed
  • A direct link to the Outbox thread to review and apply them
CRM Pulse requires an active CRM connection (HubSpot, Salesforce, or Zendesk Sell). Connect your CRM from Settings to get started.

​
Budget & Safety

CRM Pulse runs within your team’s AI usage budget. If the budget limit is reached mid-scan, Doris saves any updates already found and notifies you. Scans are also protected against duplicate runs — if a scan is already in progress for your account, a new one won’t start until the first completes.