Revenue Grid vs Cirrus Insight (2026)

On the feature grid, Revenue Grid and Cirrus Insight tie. The decision comes down to one case: an account with two open opportunities, a contact on both, and a rep who never opens the sidebar.

In that case, Revenue Grid links the email to an opportunity only when the rep owns it, it's open, and a contact on the email holds a contact role on it. Otherwise the email lands without the deal. Cirrus Insight's Smart Link attaches it to the most recently created or edited record. Neither tool writes contact roles for you.

We meet both tools in mid-market Salesforce evaluations, so Weflow is the third column here. Weflow is the Revenue AI Orchestration platform for sales, customer success, and RevOps teams, and Weflow Activity & Contact Capture is the product you'd put next to these two. We're as plain about where it stops as about where it wins. Below you'll find that scenario walked through rule by rule, the real per-seat costs, what switching involves, and a sandbox script you can run on your own test threads.

Revenue Grid vs Cirrus Insight vs Weflow at a glance

All three tools have a sidebar and a sync. Where they split is mapping, contact creation and data access.

The row that decides most purchases is the third one. The scenario section below walks through it.

Why Revenue Grid and Cirrus Insight look identical on paper

Revenue Grid and Cirrus Insight are both lighter email and activity sync tools. Both started as sidebars where reps file email by hand, and both added background sync later with conservative rules. Both write into native Salesforce objects you own.

So the grid can't separate them. What separates them is how each one decides which record an email belongs to when the rep does nothing.

That matters more than the sidebar does. Where logging depends on a rep clicking in an Outlook add-in or Gmail extension, our data shows only 24 to 52 percent of activity reaches the CRM. You're buying the background behavior.

"…this kind of checkbox item a lot of companies offer, but very few do very well. So, yeah, the devil is really in the detail as always."

— Janis Zech, CEO & Co-founder of Weflow

What happens when one contact sits on two open deals

Every capture tool has to pick one record or fall back. The tools differ in the rule each one runs when the rep never touches the email.

Why Salesforce forces every capture tool to pick one record

Salesforce lets an activity carry one Related To record, either an opportunity or an account. No vendor can change that, so don't blame the tool for the rule itself.

• One Related To record per activity. An email about a renewal and an expansion still lands on one of them, or on the account.
• Contact roles are the signal, and they're usually empty. Opportunity contact roles are the field Salesforce gives you for deciding which deal an email belongs to. In most orgs nobody fills them in.

Put those together and the ambiguous case is the normal case in renewal and expansion motions. The deal looks dead, the account looks busy, and the rep decides the tool doesn't work.

How each tool handles a renewal-plus-expansion email

Here's the setup. An account has an open renewal owned by the account manager and an open expansion owned by the AE. The buyer's contact sits on both. The AE emails the buyer about expansion pricing and never opens the sidebar.

Weflow has its own gap here. If the AE owns both open opportunities, Weflow can't tell them apart automatically. The email stays on the account until the rep picks one in the add-in.

We built it that way on purpose. A silent wrong match is worse than an honest account fallback, because nobody sees the error and every report is built on top of it.

"If there are multiple opportunities, they just don't know where to map it and just randomly assign it to something. This is not acceptable."

— A buyer describing their previous capture tool on a call with us

Weflow Activity & Contact Capture runs at the mail tenant

Weflow captures email through a central app in Microsoft Entra or Google Workspace, so reps install nothing. The mapping rule is stated, and when the evidence runs out, Weflow logs to the account instead of guessing.

How Weflow logs every email without the rep doing anything

Weflow Activity & Contact Capture reads every enrolled mailbox at the tenant, inbound and outbound, on any device. Mail sent from a phone gets the same treatment as mail sent from the desktop.

Writes go through the integration user almost immediately. There are no sync sessions to wait for.

Weflow logs only mail that matches a Salesforce contact, lead or account domain. Internal-only threads never reach Salesforce.

Two gaps to plan around:

• Deliverability subdomains. Mail sent from a separate deliverability subdomain isn't captured. Outbound sequencer touches stay invisible until the buyer replies to the main domain.
• Personal channels. Personal email accounts, SMS and calls from personal mobiles aren't captured either.

"Most of our team doesn't even know we have Weflow for activity capture. That was a big attraction for me: I didn't need them to set it up or learn anything new."

— Leslie Phillips, Director of Operations, ADVISA

What the Weflow Outlook add-in and Chrome extension let reps do

The add-in is optional. ADVISA runs Weflow fully automated, with no add-in at all.

Most of our customers run hybrid mode. In hybrid mode, the panel lets the rep:

• see the contact, account and open opportunities an email will log to
• re-map the email to a different opportunity, account or custom object
• switch logging off for a thread with one tick
• open Ask Weflow AI

You can also deploy the panel with the suppression control removed. Reps then see the mapping but can't stop it.

How Weflow picks one opportunity when the account has several open

Weflow maps an email by the email address and the Salesforce relationships around it, in a fixed order:

1. It looks up the address in primary and secondary email fields and logs to the contact, lead or custom object that holds it. A contact wins over a lead.
2. If the contact holds a contact role on exactly one open opportunity, that opportunity wins.
3. If the account has exactly one open opportunity, that opportunity wins.
4. If several are open, Weflow weighs the contact role, the opportunity owner, the mailbox owner, the account relationship and the stage. An open opportunity owned by the sender wins.
5. If nothing settles it, the email logs to the account.

Weflow never writes to a closed opportunity. It also doesn't read the email's content. We tested content matching and left it out because it wasn't accurate enough.

The principle behind the fallback is simple: logging to the account is easy to fix, and logging to the wrong deal isn't. If the rep re-maps an email once, every later reply in that thread follows. A new thread resets the choice.

The first message sets the mapping for the whole thread. If it lands wrong, the conversation follows it until someone moves it. Reps and admins can move an already-logged email from the add-in or extension. Weflow never moves logged activity on its own.

With the contact role option on, Weflow writes the opportunity contact role at the moment it logs the email. It leaves the role type blank, because a job title doesn't tell you who's the champion. Every later email from that person then resolves through the role, so mapping gets better the longer the deal runs.

The limits:

• An email lands on one opportunity only.
• No rule picks the opportunity with the nearest close date. Teams running renewals and expansions in parallel split them into separate configurations, filtered on opportunity type or a close-date threshold.
• Two open opportunities with the same owner stay on the account until the rep picks one.

How Weflow creates contacts automatically, and what stops junk records

Weflow creates contacts when the rep sends, from the To and CC lines but not BCC. That's how a buying committee of six shows up in Salesforce instead of one champion.

"I don't want twenty new contacts in there for some prospect I'm just talking to. Only once they're really an account."

— A Sales Ops buyer on a call with us

The guards:

• Existing accounts only. No orphan contacts.
• A cap per event. A 200-person webinar doesn't write 200 contacts.
• A real-time duplicate check. It runs across contacts, leads, custom objects with an email field and secondary email fields.
• Leads are respected. If the address exists as a lead, the activity attaches to the lead. Weflow never creates leads, accounts or opportunities.
• Blocked prefixes. Invoice, billing, no-reply and support addresses are skipped.
• Enrichment is included. It fills name, title, email, phone and LinkedIn where it finds them.

There's no queue where an admin reviews new contacts before they're written. The control sits with the rep, who can clear the tick per email.

Required fields on the Contact page layout block creation silently, because no external tool can see layout requirements through the API. The same goes for a validation rule that requires a field enrichment couldn't fill. Check the Contact layout before go-live.

Which custom objects Weflow can log activity to

Weflow logs activity to any Salesforce object, including Case and custom objects. Case logging can match the right case with a regex pattern on the subject.

You give us the object label and the fields you want shown, and the object appears in the extension for reps to link emails to. Between 20 and 30 percent of our customers log to custom objects.

You can restrict logging on any custom object, or on Opportunity, to conversations the record owner took part in. The setting lives under Admin Console, Activity Capture, Object Management.

How Weflow stores email attachments in Salesforce

Weflow stores attachments when a capture configuration turns them on, and each configuration sets its own size band.

The recommended band skips files under 35 KB, which keeps signature logos out, and files over 5 MB, which keeps circulating decks out. Salesforce applies its own cap of about 25 MB.

Which tools Weflow connects to, and where it stops

• Mail, calendar and meetings: native integrations with Gmail, Google Calendar, Outlook, Zoom, Microsoft Teams and Google Meet.
• Slack, plus calls from the Outreach dialer, which arrive as recordings with Weflow Conversation Intelligence.
• Engagement platforms: Outreach and Salesloft run alongside Weflow through compatibility mode.
• BI tools: Tableau and Looker connect through the API.
• Where it stops: Weflow works with Salesforce only, and it isn't an integration platform. It won't connect to your ERP or finance system.

What Claude and ChatGPT can read through the Weflow MCP connector

Weflow's MCP connector is read-only. An admin switches it on per workspace, and a separate toggle decides whether assistants see full transcripts or only summaries.

It returns playbooks, call summaries, transcripts and forecast calls. It doesn't return captured email content or Salesforce field values. Assistants read those through a Salesforce connector.

On capture alone, the Weflow connector adds little. Its value starts once you record calls. Inside Weflow, Ask Weflow AI reads captured email alongside your Salesforce data.

How to get Weflow data into a warehouse or BI tool

Captured activity sits in native Salesforce objects, so anything you already sync from Salesforce picks it up.

For conversation data, the Weflow REST API bulk-exports transcripts, metadata, scores and signals as JSON or CSV. We have no native Snowflake, Databricks or BigQuery connector, so teams use the API to move data there.

Revenue Grid pairs a sidebar with a 30-minute sync engine

Revenue Grid runs a real server-side Sync Engine next to its Sidebar, and it supports environments few tools touch. Its opportunity linking depends on ownership and existing contact roles, and its defaults are conservative.

How Revenue Grid auto-saves email through its server-side Sync Engine

Revenue Grid's Sync Engine saves every inbound and outbound email with non-blocklisted addresses, whether the Sidebar is open or not. Reps can also tag an email with a Salesforce category or folder, or save it by hand.

Auto-saved email arrives in sync sessions every 30 minutes by default. After a quiet session the gap stretches to 60 minutes, then to 120, until something changes or a user clicks Force sync. Manual saves from the Sidebar write immediately.

If the Sync Engine loses its token, auto-saving stops.

What the Revenue Grid Sidebar does in Outlook and Gmail

The Sidebar runs as an Outlook add-in and as a Chrome extension for Gmail. Reps sign in to Salesforce to use it, even when a service account handles the sync.

Thread auto-saving is useful. Once a rep saves one email from a thread, every past and future email in it is saved with the same records. That includes replies from internal or blocklisted participants.

How Revenue Grid decides whether an email reaches the opportunity

Revenue Grid links an auto-saved email to an opportunity only when all four conditions hold:

• the sender owns the opportunity
• a contact on the email holds a contact role on it
• the opportunity is open
• opportunity linking is switched on in sync settings

Miss one and the email lands without the deal. On a team where CSMs, SEs and managers email the same buyers, that's a lot of activity off the opportunity.

Cloning is a genuine strength. Revenue Grid can link one email to up to ten records, one clone each, and the setting is on by default. With cloning off, re-linking an email moves it instead.

Why Revenue Grid contact creation stays off until you switch it on

Revenue Grid has two creation modes, and both are off by default:

• One creates a contact when the domain matches an account's website and an existing contact's domain. Otherwise it creates a lead.
• The other creates accounts and contacts or leads for every unmatched participant.

Free-mail domains never trigger creation. Revenue Grid doesn't create contact roles automatically. An admin can add the Opportunity Contact Role object to the Sidebar's Create menu so reps can add roles by hand.

Which custom objects Revenue Grid can save activity to

Revenue Grid saves emails and calendar items to custom objects that have Allow Activities enabled in Salesforce. If the setting is off, the Sidebar tells the rep the email can't be saved to that object type.

How Revenue Grid saves attachments, and what support has to enable

Revenue Grid saves attachments as Content documents or Attachment records, filtered by an admin allow-list of file extensions. Manual saves are capped at 25 MB.

Support enables the rest on request: minimum and maximum auto-save sizes, blocked extensions, forcing the Attachment object, and saving files attached to meetings.

Which mail, CRM and meeting systems Revenue Grid connects to

Environment breadth is where Revenue Grid earns its place:

• Mail: Microsoft 365 through Graph or EWS, Microsoft Exchange on-premises, and Google Workspace.
• Salesforce clouds: Sales, Service, Health, Financial Services and Experience Cloud.
• Other CRMs: Siebel, Oracle Sales Cloud, SAP Hybris Cloud, Workbooks and Creatio.
• Meetings: a Microsoft Teams notetaker and Zoom recordings, in the Ultimate tier.
• Paid extras: third-party API integrations, such as Teams and Slack, sit in a paid customization package.

What AI assistants can reach through the Revenue Grid MCP server

Revenue Grid launched an MCP server on 13 July 2026 for ChatGPT, Claude, Copilot and custom agents. It covers relationship history, engagement trends, revenue signals and AI insights.

Customers connect it manually. It has no public documentation, tool list or pricing tier yet. The Claude plugin requires Pipeline Assistant, Meetings Assistant or AI Mentor.

How to get Revenue Grid activity data out without a public API

Revenue Grid has no public API for captured activity. Its only API is the Salesforce Scheduler Adapter's calendar endpoints.

Captured emails and meetings live in Salesforce as Tasks, EmailMessages and Events, so you reach them through Salesforce's API.

Cirrus Insight puts the rep in charge of filing

Cirrus Insight treats rep-directed filing as a feature, not a gap. Its argument is that capturing everything produces a CRM nobody trusts. Its background sync logs only people Salesforce already knows, and it attaches by recency.

How Cirrus Insight Email Sync logs email when a contact exists

Cirrus Insight's Email Sync ($5 per user per month) runs without the sidebar open. It logs an email only when an existing Salesforce contact or lead is on the To, CC or From line.

Admins set the rules. A replies-only mode syncs later messages only on threads a rep already filed.

The minimum cycle is 15 minutes. Fast Sync brings it to 5 minutes for another $5 per user per month, at the cost of more Salesforce API requests.

What the Cirrus Insight sidebar lets reps file and create

• Quick File logs the email to the contact or lead in one click.
• Custom File relates it to the person plus one more record, such as an opportunity or case, and lets the rep pick attachments.
• Multi-file logs several selected emails at once.
• Record creation: reps create and edit contacts, leads, accounts, opportunities, cases, tasks, events and custom object records from Gmail or Outlook.
• Licensing: one license covers both inboxes and their mobile apps. Every user needs the API Enabled permission.

How Cirrus Insight Smart Link picks the most recently touched record

Smart Link relates each synced email to the most recently created or edited record of one object type you choose, such as opportunity or case. On an account with a renewal and an expansion open, the email lands on whichever was touched last, not the deal the conversation is about.

Thread-Based Smart Link keeps a thread on the record a rep chose, with conditions:

• The rep has to file the first email by hand.
• It needs the Save Email IDs setting and the Pro plan or higher.
• It's fully supported only with Enhanced Email.
• On Tasks it's in beta and needs two custom text fields of at least 180 characters on Activities.
• Cirrus recommends blocking draft filing, because a changed message ID breaks the thread link.

Why Cirrus Insight Email Sync never creates contacts

Email Sync doesn't create contacts or leads. A new stakeholder reaches Salesforce only when a rep clicks Add Contact or Add Lead in the sidebar.

Cirrus makes that step quick. It pre-fills the account, plus title, phone and company from the signature. A Strict account match setting fills the account only when every contact on that domain sits under one account.

A domain fallback relates the email to the account when no contact exists. It still creates no contact. People on recorded calls become records through CRM Updates, a separate $15 line.

Which custom objects Cirrus Insight can file email to

Custom objects related to Account or Contact appear in the sidebar automatically, as long as the user's profile can see them. Email Sync can relate emails to any custom object with an Email field. Either way, the object has to allow activities in Salesforce.

How Cirrus Insight attachment sync works as a support-enabled beta

Automatic Attachment Sync is a beta that support switches on. It takes Word, Excel, images and plain text up to 25 MB, and skips CSV, PowerPoint, archives and attached emails.

There's no deduplication or versioning. Without the beta, attachments arrive only when a rep files them.

Which tools Cirrus Insight connects to through Zapier and webhooks

• CRM: Salesforce is the only CRM.
• Inbox and meetings: Gmail, Outlook and Microsoft Teams.
• Scheduling: Zoom, Teams and Google Calendar links for meetings booked through Cirrus scheduling, plus a HubSpot scheduler embed.
• Zapier connects Cirrus to other tools.
• Webhooks fire only on Smart Scheduler bookings and configuration changes, not on synced emails or recorded meetings.

Cirrus Insight offers no MCP connector for AI assistants

Cirrus Insight has no MCP server or connector for Claude or ChatGPT. An assistant reaches Cirrus data through the preview API or through Salesforce, where Cirrus writes what it captures.

How to get Cirrus Insight data out through its preview API

Cirrus has a preview REST API covering scheduling, meeting transcripts, CRM accounts, contacts and deals, Buyer Signals and Email Blasts. Rate limits are 300 reads, 60 availability queries and 20 writes per minute, with 50,000 requests a day. Cirrus labels the endpoints as likely to change before general availability.

Captured activity reaches a warehouse through Salesforce, the same way it does with Weflow.

What Revenue Grid, Cirrus Insight and Weflow cost per seat

The three tools use three different pricing models. List price alone misleads, because extras and terms change the real number.

How each vendor prices an activity capture seat

Weflow publishes $19 per seat for Weflow Activity & Contact Capture. Revenue Grid's capture tier is $30 per seat, sold through a quote. Cirrus Insight sells each line separately.

Here's what list prices come to at 40 seats for a year:

• Weflow: $9,120
• Revenue Grid: $14,400, before the implementation fee
• Cirrus Insight: $12,960, or $15,360 with Fast Sync

What costs extra beyond the list price

Weflow:

• We charge no implementation or platform fees.
• Enrichment, Ask Weflow AI Pro and Agent Builder Free come in the seat.
• Historical backfill of up to 24 months is an add-on.
• Call recording lives in Weflow Conversation Intelligence ($39), or in the Revenue AI Foundation bundle ($49) together with capture.

Revenue Grid:

• A one-time implementation and onboarding fee.
• History older than six days, extra folders and pre-activation calendar items are a custom service that may carry a fee.
• Salesforce-to-calendar Instant Sync is a paid add-on.
• A fully admin-authorized rollout needs a separate paid Salesforce license for the service account.
• Meeting recording and forecasting start at Ultimate, $149 per user per month.

Cirrus Insight:

• Fast Sync is $5 per user per month and Task Sync is $2.50.
• Historical email backfill is a service scoped on request.
• Recording calls takes Meeting Capture at $39, plus CRM Updates at $15 to write call content into Salesforce.

Minimum seats, term length and mid-term seat changes

• Weflow: a 10-user minimum and 12-month terms. Seats added mid-term are charged pro rata to the end of the term. You can't reduce seats mid-term, but you can reassign a seat when someone leaves.
• Revenue Grid: every plan runs on a yearly commitment, and plan changes go through support.
• Cirrus Insight: you choose the term and billing frequency in the configurator and set a headcount per line.

What switching and piloting involve in each tool

Setup effort, history and pilot hygiene differ more than the feature lists suggest. You'll own all of it.

Which integration user and Salesforce license each tool needs

Connecting mailboxes centrally versus one rep at a time

Per-user connections break silently. A rep ignores a re-authentication prompt, the sync stops, nothing errors, and weeks later an account looks like nobody touched it.

Cirrus lists the causes in its own docs: password resets, MFA prompts, token expiry and conditional access changes. Revenue Grid rates per-user authorization lower in scalability and higher in user-side error risk.

All three tools offer a central connection. Only Weflow runs capture with no rep authentication path at all. United Fintech went live with Weflow in under an hour, rolled out centrally through OAuth.

How much email history comes across when you switch

• Weflow: historical backfill of up to 24 months is an add-on. Emails sent before an account existed in Salesforce log automatically once someone creates the account, with no re-sync.
• Revenue Grid: on activation it saves the previous six days of Inbox and Sent. Older email, other folders and pre-activation calendar items are a custom service.
• Cirrus Insight: email backfill is a scoped service. Calendar Sync reaches back at most seven days on its own.

How to pilot two capture tools without duplicate activity

Two capture tools on one inbox compete for the same emails, so plan the bake-off:

1. Disable one tool before you test the other, or run Weflow in compatibility mode. Compatibility mode holds Weflow's sync back by about ten seconds so the other tool logs first, then matches on the record ID so the email isn't written twice.
2. Add tracking patterns for any sequencer whose bulk sends should never reach Salesforce.
3. In Revenue Grid, add and set the InternetMessageId field before testing. Auto-saved emails only deduplicate on message ID once it's in place.
4. In Cirrus Insight, keep calendar subject lines consistent. Calendar Sync links events only when subject, start and end time all match, and may create duplicates otherwise.
5. Count activity per test thread in Salesforce before you compare tools.

Which tool fits your Salesforce team

Choose Weflow Activity & Contact Capture if

• You run 10 or more Salesforce seats and can commit to a 12-month term.
• You want capture that needs no rep install, no rep login and no rep action.
• Your accounts carry several open opportunities, and you want a stated mapping rule with an account fallback and one correction per thread.
• You want contacts and contact roles created as reps work, with guards against junk records.
• You want a published seat price with no implementation fee.

Choose Revenue Grid if

• You run Exchange on-premises, or a CRM other than Salesforce, such as Siebel or Oracle Sales Cloud.
• You need two-way calendar sync between Salesforce and the calendar.
• You want one email cloned onto several records, up to ten.
• Your security review asks for ISO 27001 and ISO 27701 alongside SOC 2 Type 2.

Choose Cirrus Insight if

• You have fewer than 10 users.
• You want reps to decide what gets filed, and treat manual filing as the default.
• You want to buy by user group, such as calendar sync for everyone and the sidebar only for reps.
• You want scheduling, lead routing and email engagement from the same vendor.

How to test all three tools in your Salesforce sandbox

Test the ambiguous case with clean data, and measure your own override rate. No vendor publishes one, Weflow included.

1. Give each test company a unique domain. Free-mail domains in the Website field tie every sender to several accounts and measure your test data instead of the tool.
2. Create one account with two open opportunities, a renewal and an expansion, and one contact shared by both.
3. Give the contact a role on each opportunity, run the test, then remove the roles and run it again.
4. Send from the opportunity owner's mailbox without opening the sidebar.
5. Time how long the email takes to land in Salesforce.
6. Note which record it lands on: the right deal, the wrong deal or the account.
7. Make one rep own both opportunities and send again.
8. CC a new stakeholder and check whether a contact appears, and on which account.
9. Check whether an opportunity contact role was written for that stakeholder.
10. Correct the mapping once, have the buyer reply, and check where the reply lands.
11. Move a logged email to a different record and check both timelines.
12. List the required fields on your Contact page layout and validation rules, and check whether contact creation went through.
13. Build one activity report and compare what Task and EmailMessage logging give you.
14. Watch API usage in Setup over a full day of test sends.
15. In the pilot, count overrides per rep per week.

The last number is the one that sizes your rollout. Weight it by how many of your accounts carry more than one open opportunity.

Walk through the product yourself, no call required.

Revenue Grid vs Cirrus Insight FAQs

How often do reps have to override the opportunity mapping?

No vendor publishes an override rate, and we don't either. The rate depends on how many of your accounts carry several open opportunities and how well your contact roles are maintained. Measure it per rep per week in the pilot.

"Do you know on average how often that happens? … then we can see how much manual task we can expect."

— A buyer evaluating automated mapping on a call with us

Does each tool log email as a Task or an EmailMessage?

• Weflow: logs to EmailMessage or Task, chosen per configuration. About nine in ten of our customers choose EmailMessage.
• Revenue Grid: saves completed Tasks, or EmailMessage records with Enhanced Email on.
• Cirrus Insight: writes Tasks of type Email, or EmailMessage with Enhanced Email. Its thread memory is fully supported only on Enhanced Email.

The trade-off is reporting. A single activity report spans Tasks and Events but not EmailMessage. EmailMessage keeps From, To, Cc and thread structure, at roughly seven times the storage of a Task.

Can one email log to two opportunities at once?

• Revenue Grid clones an email onto up to ten records, one clone per record.
• Cirrus Insight gives each email one Related To record under Salesforce's rules.
• Weflow logs an email to one opportunity. Weflow recordings, a custom object, can link to several records, which helps when one call covers a renewal and an expansion.

How much Salesforce API load does each tool add?

• Revenue Grid documents about 14 calls to auto-save one email with an attachment and 3 to 6 per meeting, plus up to about 1,500 a day to keep sync running. Near its threshold it backs off to sessions every 2.5, 4.5, 6.5 hours and longer.
• Cirrus Insight makes more API requests the shorter you set the sync cycle.
• Weflow caches some Salesforce data to keep API calls low.

How do I keep internal, executive and confidential mail out of Salesforce?

Weflow gives you four layers:

• It excludes internal-only threads before any write.
• You can exclude supplier and free-mail domains.
• You can put leadership on manual mode.
• Custom rules block logging against any record by its field values, such as a confidential flag.

Revenue Grid auto-saves every email with non-blocklisted addresses. Once a rep saves one email in a thread, its thread auto-saving includes internal and blocklisted replies.

Cirrus Insight's admin-only blocked lists support wildcards such as noreply*. Calendar Sync can skip private events.

How do I limit which mailboxes each tool can read?

For Weflow, set Assignment required to Yes on the Weflow Entra app. Without it, assigning a group doesn't restrict anything.

To test it, add someone outside the group to a capture configuration and save. If the restriction holds, a warning icon appears next to that user.

Cirrus Insight limits its Microsoft Graph app to a security group. Revenue Grid scopes access through user profiles.

What happens to new stakeholders at a prospect not yet in Salesforce?

• Weflow creates no contact when no account matches the domain, and nobody gets told. Once someone creates the account, the earlier emails log to it automatically. Reps can also create the contact from the extension.
• Revenue Grid can create accounts and contacts or leads for every unmatched participant, if you switch that mode on.
• Cirrus Insight doesn't log the email to that person. A rep can add the contact from the sidebar and create a new account there.

Do Revenue Grid or Cirrus Insight connect directly to Snowflake?

Cirrus Insight has no direct Snowflake connection. Like Weflow, it writes activity natively into Salesforce, and activity reaches Snowflake from there.

Revenue Grid has no public activity API, so its captured activity also reaches a warehouse through Salesforce's API. Weflow adds a REST API for moving conversation data into Snowflake, Databricks or BigQuery, with no native connector.