Skip to main content
The AI SDR is the sales-side AI chat that lives on every CRM page. It reads your pipeline, drafts emails, updates deals, enrolls contacts into sequences, builds tasks, runs spam checks, and schedules its own follow-up reminders — all from natural-language instructions. It’s scoped to your account, to your user (for “mine-only” queries), and to whatever page you’re on (it knows which contact / deal / sequence you’re looking at without you pasting IDs).
If you’ve used the AI in the website builder or the email marketing agent: same idea, different domain. The AI SDR ships with CRM-specific tools, not page-editing tools.

​
Where to find it

Click the AI SDR launcher in the bottom-right of any CRM page:

​
What it can do

Pipeline + records

List, search, create, update, close, reopen, and delete contacts, companies, deals, and tags. Set custom field values. Bulk-update up to 500 records at once.

Outbound email

Draft, spam-check, and send 1:1 emails from your connected inbox. Or schedule a batch. Never sends without your explicit approval (see below).

Sequences

Build and edit cadences, enroll contacts (single or bulk), unenroll, pause / resume, check analytics, A/B compare two cadences.

Calendar

Create, update, delete meetings on your connected Google / Outlook calendar.

Intelligence

Score leads, flag at-risk deals, compute weighted forecast, rep win-leaderboard, surface stale contacts / duplicates / missing fields.

Follow-up reminders

Schedules itself to ping you later — “remind me in 2 days to check if Acme replied”. See AI SDR Reminders.
For the data-hygiene tools (crm_contacts_duplicates, crm_contacts_stale, crm_contacts_missing_field), the AI SDR will list candidates and propose an action; it only runs destructive cleanup (like merge) after you approve.

​
Approval-gated actions

Anything that writes to another system or can’t be undone stages an approval card instead of running immediately. When the AI SDR decides to do one of these, the chat renders a yellow card with:
  • A one-line summary of what’s about to happen (e.g., “Close deal ‘Acme Q2 expansion’ as won for $48,000”)
  • The exact payload (who / what / when)
  • Two buttons: Approve (runs it) or Cancel (does nothing and writes an audit row)
These actions go through the approval card:
CategoryExamples
Email sendsSend a one-off email, schedule a batch of sequence sends
Calendar writesCreate / update / delete meetings on your OAuth calendar
Destructive CRM opsDelete a contact, tag, custom field, or sequence. Merge two contacts. Close or reopen a deal
Sequence enrollmentEnroll / unenroll a contact (since this kicks off real email sends)
Draft-only operations (reading, listing, scoring, drafting copy, building a sequence) never gate — you see them run inline.

​
Why it works this way

Two reasons:
  1. Trust — destructive or outbound actions deserve a human confirming before they’re visible to someone else. A misrouted bulk unenroll on 80 contacts is hard to undo; an approval card makes it impossible.
  2. Audit — every approval card writes an audit row on both Approve and Cancel, keyed by the pending-token and the rep’s user id. You can see “who approved what, when” in Settings → Audit Log.

​
Reading the card

A typical approval card looks like: 
⚠ Send email to jane@acme.com
  From: you@yourdomain.com
  Subject: Quick question on your H1 plans
  Body (preview): Hi Jane — saw your post on...
  [Approve]  [Cancel]
The body preview is the actual rendered email, with merge vars already substituted and the unsubscribe footer shown if applicable. If you see {{first_name}} in the preview, that variable is missing on the contact — fix the data or the AI SDR’s prompt before approving.

​
Bulk approval

For batch operations (e.g., “enroll these 42 contacts”), the approval card shows the count, a sample of rows, and the break-down of any skips or failures before it runs. You approve the batch as a unit — not per-row.

​
Non-obvious behaviors

  • Page context is implicit. If you open a contact detail page and type “start a 3-step sequence with them”, the AI SDR resolves “them” from the URL. No need to name them.
  • “Mine-only” by default for some queries. “Show me stale contacts” → defaults to your owned contacts. Ask “across the whole account” to broaden.
  • No outbound without an OAuth inbox. If your Gmail / Outlook isn’t connected, email drafts work but sends fail the approval card pre-check. Connect under Connect Gmail or Connect Outlook.
  • Custom fields are available as merge vars. If you’ve defined a custom field renewal_date, you can reference {{renewal_date}} in any drafted email and the AI SDR will merge it per-contact at send time.
  • Cross-agent delegation. The AI SDR can hand off to the marketing agent (for a newsletter) or the content agent (for a blog draft) when the request is off-domain. You’ll see a “Delegating to …” step in the chat.

​
Things it won’t do

  • Send from an email address you don’t own. Only connected OAuth inboxes in your account.
  • Skip the approval card for outbound or destructive ops — there’s no “run without asking” mode. By design.
  • Make up a field. If you ask “set their renewal_date to next March”, it’ll first check the custom-field catalog. If renewal_date doesn’t exist, it’ll offer to create the field (which itself is a write, so gated).
  • Auto-suppress based on a reply tone. Reply = exit the active sequence (if exit_on_reply is on). Adding the contact to the global suppression list is a separate explicit step.

​
Common asks

Give me the 10 highest-scoring contacts I own that I haven't
emailed in the last 14 days, and draft a warm follow-up for each.

What deals of mine are at risk this week? For each, tell me why
and draft a next-step message to the primary contact.

Find duplicate contacts on the account where the email matches,
ignoring case. Show me the pairs — don't merge yet.

Enroll Jane Smith in the "Post-demo follow-up" sequence, starting
Monday morning, and remind me in 4 business days to check if she
replied.

Spam-check this subject + body and rewrite to score under 20.