How does Weflow capture meetings from Zoom, Teams, and Google Meet into Salesforce?

Weflow doesn't require a direct integration with Zoom, Microsoft Teams, or Google Meet. Instead, it reads your calendar through server-side Google Workspace or Microsoft Entra ID app permissions, identifies meetings with external participants, and auto-schedules an AI notetaker to join each qualifying call.

When the meeting starts, the notetaker joins the lobby, waits to be admitted, and records the full video including screen sharing and audio. Depending on your org's security settings, you may need to manually admit the bot, which is common with Zoom. For Zoom, your admin needs to enable local recordings under Account Management > Account Settings > Recordings & Transcripts.

After the call ends, auto-language detection identifies the meeting language (87 to 96+ languages supported) and the recording is transcribed. Weflow then processes the transcript through configured templates to generate AI summaries, field update suggestions, follow-up emails, and coaching scores. Internal participants receive a recap email within roughly one to two minutes of the meeting ending.

Weflow maps each meeting to the correct Account, Opportunity, Contact, or Lead based on participants. Data lands in the following places in Salesforce:

• AI summaries are written to the Event object's Description field
• Full transcripts and recordings are stored on the Weflow_Recording__c custom object, installed via the managed package, with a relationship to Opportunities
• AI field updates can be pushed to any standard or custom Salesforce field, either automatically or after you confirm
• All syncs respect your existing Salesforce validation rules, field dependencies, and role hierarchy

Admins can configure recording rules so external meetings are auto-recorded while internal meetings remain opt-in. You can also prevent recording on any specific call by unscheduling it from the Weflow calendar or removing the notetaker mid-meeting.

Can Weflow automatically capture notes from Zoom calls, Gmail threads, and Slack DMs into Salesforce?

Weflow handles Zoom meetings, Gmail threads, and Slack differently across its two products: Activity Capture and Conversation Intelligence.

Conversation Intelligence records meetings on Zoom, Microsoft Teams, and Google Meet by joining as an AI notetaker participant. After each meeting, it generates AI-powered summaries that automatically write back to the Salesforce Event object's Description field. Full transcripts sync to a custom Weflow Video Recording object installed via the managed package, with a direct relationship to Opportunities.

This covers Zoom video meetings only, not Zoom Phone calls. Zoom Phone integration is on the roadmap but not available today (announced, will be available soon). Most Weflow customers connect their VoIP providers directly to Salesforce for call logging in the meantime.

Activity Capture automatically logs all incoming and outgoing emails from Google Workspace at the server level. No browser extension, plugin, or manual action is required. Emails are stored as native Salesforce EmailMessage or Task objects, preserving From, To, CC, BCC fields, HTML body, and attachments. Weflow can also backfill up to 24 months of historical email data, and internal-only emails are excluded by default.

Weflow does not have a native Slack integration and cannot capture Slack messages into Salesforce. This applies to DMs, channels, and group messages.

Activity Capture and Conversation Intelligence are two separate Weflow products. Activity Capture handles email and calendar sync. Conversation Intelligence handles meeting recording, transcription, and AI summaries. Both write data to native Salesforce objects, so everything is reportable and available to Flows and automations.

Does Weflow store all activities in native Salesforce objects?

Yes. Weflow permanently stores all captured emails, meetings, and contacts in native Salesforce objects.

• Emails are written to the EmailMessage object (used by 75% of customers) or the Task object, preserving From, To, CC, BCC fields, HTML body, and attachments.
• Calendar events are stored in the native Event object, with one parent event per meeting and child events for each attendee.
• New contacts are created as standard Contact records, associated with matching Accounts by domain and linked to Opportunity Contact Roles where applicable.
• Activities can also be logged to Custom Objects and Cases.

Because these are standard Salesforce records, your existing reports, dashboards, Flow automations, sharing rules, and Process Builder logic all apply immediately. Weflow also respects your existing field dependencies, validation rules, permissions, and role hierarchy out of the box.

Unlike Einstein Activity Capture, Weflow creates Salesforce-native activity records that you can report on, automate against, and export like any other standard object data. Einstein Activity Capture streams activity data without writing queryable records.

There's no data lock-in. If you stop using Weflow, every activity record persists in your Salesforce instance because it lives in standard objects, not custom ones. The only Weflow-specific artifact is a managed package with one custom object and three fields used for event reconciliation and deduplication, which you can remove at any time.

Does Weflow integrate forecasting with Salesforce opportunity snapshots?

Yes. Opportunity snapshots are the foundational data layer for all forecasting and pipeline analytics in Weflow. At regular intervals, Weflow's data engine captures a point-in-time snapshot of every deal in your pipeline, including amount, stage, close date, forecast category, and any custom fields you've configured.

These snapshots feed directly into multiple analytics views:

• Waterfall reports showing deals closed, lost, pushed, pulled in, or changed in amount over the past 3, 6, or 12 months
• Pacing trends that track pipeline development against quota over time
• Pipeline coverage ratios computed by comparing snapshot data across periods
• AI-predicted forecast corridors generated by combining historic snapshots with deal signals like engagement score, multi-threading, time-in-stage, close date push count, and amount changes

The AI prediction sits alongside your human-submitted forecast calls, weighted forecasts, and closed pipeline so you can compare all four in one view and spot gaps early.

Weflow forecasting operates independently from native Salesforce forecasting. All forecast submissions, category assignments, and historical snapshots are stored as native Salesforce records, which means you can use them in Salesforce dashboards, reports, and Flows without exporting anything.

Field updates sync in real time. Snapshot intervals run on a configurable cadence, either weekly or monthly, for analytics purposes.

How does Weflow handle sales call recording and transcription?

Weflow deploys an AI notetaker that automatically joins your scheduled external meetings on Zoom, Google Meet, and Microsoft Teams. It records full video, including screen sharing, produces a real-time transcript with speaker identification, and detects the meeting language automatically. 90+ languages are supported with no manual selection required.

Recordings and transcripts are auto-mapped to the correct Salesforce Account, Opportunity, Contact, and Lead records based on meeting participants. Full transcripts sync to a custom Salesforce object called Weflow Video Recording, linked to Opportunities. AI summaries write directly to the Salesforce Event Description field, making that data available for Salesforce Flows, downstream LLM use, or export to your data warehouse.

Within roughly one to two minutes of a meeting ending, internal participants receive a recap email containing the AI summary, suggested Salesforce field updates, and a draft follow-up email. Post-call processing runs against configurable templates, which you can build from a library of 250+ pre-built prompts or write as custom templates.

• MEDDIC and MEDDPICC
• SPICED, BANT, Challenger, and SPIN
• Custom executive summaries or team-specific formats
• Structured scorecards with per-section ratings for rep coaching

Your transcript library is searchable and organized by account, opportunity, and rep. You can create clips from specific moments and organize them into playlists for enablement. The Ask AI chat interface lets you query across all recorded conversations and Salesforce data in natural language.

Does Weflow store activities in native Salesforce objects like tasks and events?

Yes. Weflow writes all captured emails, meetings, and contacts to native Salesforce objects: EmailMessage, Task, Event, and Contact. No custom objects are used for activity storage.

For emails, your admin can choose whether to log to the EmailMessage object or the Task object in the Weflow admin console. About 75% of Weflow customers use the EmailMessage object, which preserves From/To/CC/BCC fields, HTML body, and attachments. When emails are stored as EmailMessage records, Salesforce also auto-creates a corresponding Task for reporting. Calendar events are stored in the native Event object with one parent event per meeting and child events for each attendee.

Because these are standard Salesforce records, they work with everything you've already built in Salesforce:

• Activity Timeline displays on Contact, Lead, Account, and Opportunity records
• Standard Salesforce reports and dashboards
• Flow and Process Builder automations
• Sharing rules, field-level security, and role hierarchy

Weflow also supports logging activities to Custom Objects and Cases, in addition to standard objects. Your CSM can configure custom object logging in the admin console. No field mapping is required, since Weflow automatically detects your Salesforce schema, including custom fields, validation rules, and field dependencies.

Unlike Einstein Activity Capture, Weflow writes permanently to the Salesforce database, creating fully queryable records. If you stop using Weflow, every activity record stays in your Salesforce instance with no data lock-in and no cleanup required.

How deep is Weflow's Salesforce integration?

Weflow is built exclusively for Salesforce with real-time, bi-directional API integration. It automatically detects your existing Salesforce schema, including standard and custom fields, custom objects, field dependencies, validation rules, permissions, and role hierarchy. No field mapping is required.

All captured data writes permanently to native Salesforce objects. Emails store as EmailMessage records, preserving From/To/CC/BCC, HTML body, and attachments, or as Task objects. Calendar events store in the native Event object with parent/child event structure. Contacts are created as standard Contact records, associated with matching Accounts by domain and linked to Opportunity Contact Roles where applicable.

The integration covers several layers beyond basic data sync:

• Real-time email-to-record matching against Contact, Lead, and Custom Object records, traversing relationships from Contact to Account to Opportunity
• Inline and bulk editing of any editable Salesforce field, with validation rule errors surfaced directly in Weflow's interface
• AI-driven field updates that push methodology data (MEDDPICC, SPICED, BANT) to Opportunity, Account, Contact, and Lead objects
• AI meeting summaries synced to the Salesforce Event Description field
• Activity logging to Custom Objects and Cases alongside standard objects
• Support for all Salesforce field types, including multi-picklist, currency, and date fields

Installation requires a managed package that adds one custom object and three custom fields. You can optionally configure a dedicated Salesforce API-only integration user with a specific permission set. Weflow works with Salesforce Platform licenses.

Every record Weflow creates is queryable, reportable, exportable, and available in Salesforce Flows. If you stop using Weflow, all data stays in your Salesforce instance with no lock-in.

How does Weflow sync emails and meetings to Salesforce automatically?

Weflow runs as a server-side background service that captures emails and meetings from Google Workspace or Microsoft 365 and writes them to native Salesforce objects in real time. No browser extension, no email plugin, and no manual action from your reps is required. You install a central app via the Google Workspace Marketplace or Microsoft Entra ID, which grants Weflow server-level access to email and calendar data for enrolled users. From there, Weflow receives a notification for every email sent or received and every calendar event created, modified, or deleted.

For each captured activity, Weflow performs a real-time lookup against Salesforce using the email address as a unique identifier. The mapping algorithm matches against Contact, Lead, and Custom Object records, supports multiple email fields per record, and traverses relationships from Contact to Account to Opportunity. Weflow logs to an Opportunity only if it's open and the Contact is a Contact Role, or if there's a single open Opportunity under the parent Account. When multiple open Opportunities exist, your rep selects the correct one manually.

Emails are stored as EmailMessage objects, preserving From, To, CC, BCC, HTML body, and attachments, or as Tasks. Calendar events are stored in the native Salesforce Event object with parent and child events per attendee, including attendee status: accepted, declined, or tentative.

• Email sync is one-directional (email provider to Salesforce); calendar sync is bi-directional
• Internal-only emails, where all participants are from your domain, are automatically excluded
• Meeting reschedules, cancellations, and recurring events are tracked
• Compatibility mode detects existing tracking from Outreach, Salesloft, Apollo, and Gong Engage to prevent duplicate activity records

Because Weflow writes to standard Salesforce objects, every synced activity is immediately available in reports, Flows, and automations.

Does Weflow work with Zoom, Microsoft Teams, and Google Meet?

Yes. Weflow's AI notetaker fully supports Zoom, Microsoft Teams, and Google Meet. It automatically joins your scheduled meetings with external participants, records the full video including screen sharing, and produces a searchable transcript. No separate authentication with Zoom, Teams, or Google Meet is required.

How the notetaker behaves varies by platform:

• Zoom: The notetaker sits in the meeting lobby and must be admitted by the host. Your Zoom admin needs to enable local recordings via Account Management > Account Settings > Recordings & Transcripts.
• Microsoft Teams: Participants receive a pre-meeting email where they can opt in or opt out of recording. An in-call chat message gives them an additional way to remove the notetaker.
• Google Meet: The notetaker joins as a participant with no recording permission needed. By default, it must be manually admitted into the call. Same-org notetakers may auto-join depending on your organization's settings.

Weflow reads your calendar via Google Workspace or Microsoft Entra ID to identify external meetings and auto-schedule the notetaker. Your reps don't need to configure anything. Admins can set recording rules so external meetings are auto-recorded while internal meetings stay opt-in.

You can prevent recording by not admitting the notetaker, unscheduling specific meetings from the Weflow calendar, or removing the notetaker mid-call.

Two limitations to note: Google Meet livestreams and breakout rooms are not currently supported, and Weflow records video meetings only. Phone calls via Zoom Phone, Dialpad, or Aircall are not yet supported, though Zoom Phone support is on the roadmap (announced, will be available soon).

Can Weflow automatically capture notes from Zoom calls, Gmail threads, and Slack DMs into Salesforce?

Weflow covers Zoom meetings and Gmail threads, but not Slack DMs.

For Gmail, Weflow Activity Capture automatically logs all inbound and outbound emails at the server level in Google Workspace. No user action is required. Every email is written to native Salesforce objects (EmailMessage or Task), matched to the correct Account, Contact, Lead, and Opportunity based on participant email addresses.

The following email fields are preserved: From, To, CC/BCC, HTML body, and attachments.

For Zoom meetings, Weflow Conversation Intelligence joins your call as an AI notetaker and records, transcribes, and generates AI summaries. The AI summary is automatically written to the Salesforce Event object's Description field. The full transcript syncs to a custom Weflow Video Recording object installed via the managed package. This also works on Microsoft Teams and Google Meet.

Weflow captures video meetings, not Zoom Phone calls. Zoom Phone integration is on the roadmap but not available today (announced, will be available soon). Most Weflow customers connect their VoIP provider directly to Salesforce for call logging.

For Slack, Weflow has no integration and does not capture Slack DMs or any messaging platform data.

These capabilities span two separate Weflow products. Weflow Activity Capture handles email and calendar sync. Weflow Conversation Intelligence handles meeting recording, transcription, and AI-generated summaries with structured field updates back to Salesforce.

How does Weflow handle sales call recording and transcription?

Weflow deploys an AI notetaker that automatically joins your scheduled external meetings on Zoom, Google Meet, and Microsoft Teams. It records full video (including screen sharing), captures audio, and produces a real-time transcript with speaker identification and timestamp-linked segments. Weflow detects your calendar via server-side Google Workspace or Microsoft Entra ID permissions, so no manual scheduling is required.

Transcription includes auto-language detection across 87+ languages with no manual selection. Your transcript library is searchable and organized by account, opportunity, and rep. Full transcripts sync to a custom Salesforce object (Weflow Video Recording) installed via the managed package, with a direct relationship to Opportunities. Recordings are auto-mapped to the correct Account, Opportunity, Contact, and Lead records based on meeting participants.

After each meeting, internal participants receive a recap email within one to two minutes containing an AI summary, a follow-up email draft, and suggested Salesforce field updates. Weflow compares current Salesforce field values against what was discussed and shows a side-by-side diff. Summaries are written to the Salesforce Event Description field, making them reportable and available to Flows.

There are a few current limitations to be aware of:

• The notetaker joins as a visible meeting participant and waits in the lobby until admitted

• Phone calls, Zoom Phone, and SMS are not recorded today

• A stealth desktop recording option (no visible bot) is on the roadmap for Q2 2026

• A mobile app for recording in-person field sales meetings has also been announced

You can prevent recording on any call by not admitting the notetaker, unscheduling a specific meeting, or removing the notetaker mid-call.

Does Weflow's activity capture work with Salesforce Flows and native reports?

Yes. Weflow writes every captured email and meeting to standard Salesforce objects: Task, Event, and EmailMessage. Because these are native Salesforce records, they're fully queryable, reportable, and available as triggers in Flows, Process Builder, and Apex triggers.

You can build Salesforce Flows that reference Weflow-captured data to populate a "last meeting date" field on an Account, count total touchpoints per Opportunity, or alert a manager when no activity has been logged on a deal in 14 days. You can also build standard Salesforce reports showing metrics like emails sent per opportunity stage or meetings per closed-won deal.

Unlike Einstein Activity Capture, Weflow permanently writes activity data to the Salesforce database as queryable records. EAC streams data into Salesforce without storing it as queryable records, which means EAC data can't be used in Flows, reports, or dashboards. This is one of the most common reasons RevOps teams switch from EAC to Weflow.

Email open tracking fields, specifically last open date and total open count, are stored as custom fields on the EmailMessage or Task object via a separate managed package. These fields are also Flow-compatible, so you can trigger automations based on whether a prospect opened an email. If you ever uninstall Weflow, all captured activity data stays in Salesforce with no lock-in, since it lives in native objects your org already uses.

Does Weflow respect Salesforce permissions and sharing rules when capturing activities?

Yes. Weflow respects your Salesforce permissions, sharing rules, and role hierarchy out of the box, with no custom configuration required. Because Weflow stores captured activities as native Salesforce objects (Task, Event, EmailMessage, Contact), every record inherits the same sharing and permission behaviors as any record created manually in Salesforce.

Weflow connects via real-time, bi-directional API integration and works within your existing Salesforce governance. That includes:

• Permission sets and field-level security
• Role hierarchy and sharing rules
• Validation rules and required fields
• Record types, field dependencies, and custom objects

Weflow doesn't bypass your data model. It reads your Salesforce schema automatically, so no field mapping is needed. If a user lacks write access to a specific object or field, Weflow won't override that restriction.

The same applies to conversation intelligence: you only see recordings you already have access to based on permissions defined in Salesforce and Weflow.

Because activity data lives in native Salesforce objects, it appears in Activity Timeline, works with standard Salesforce reports, and triggers Process Builder and Flow automations. The data stays in your org even if you uninstall Weflow.

Admins can also create multiple activity capture configurations and assign them to different user profiles or teams for granular control over what gets captured and where.

Does Weflow offer historical sync to backfill past emails and meetings?

Yes. Weflow can backfill up to 24 months of past emails and calendar events from Google Workspace or Microsoft 365 into Salesforce. This is useful if you're switching from Einstein Activity Capture, Groove, or manual logging where historical activity data is incomplete or missing.

Unlike Einstein Activity Capture, Weflow offers historical backfill as a capability, letting you populate Salesforce with past activity data for reporting, trend analysis, and deal context from day one.

• 3 months of historical sync is included at no extra cost with your Activity Capture license
• Extended backfill up to 24 months is available as an add-on, with pricing through your CSM or sales contact
• The process typically completes within 72 hours, depending on volume and time range
• Backfill is batched to respect Salesforce API limits, where each record requires 3–5 API calls, so large volumes are spread across days or weeks to avoid disrupting daily operations
• Existing activities in Salesforce are not deleted or modified during the backfill

To initiate a historical sync, contact your Customer Success Manager or email support@getweflow.com with the relevant email addresses and target date range. Weflow is also working on a self-service option for shorter time ranges up to 180 days (announced, will be available soon). Anything beyond that will still require a managed process due to Google, Microsoft, and Salesforce API rate limits.

Does Weflow's conversation intelligence integrate natively with Salesforce?

Yes. Weflow's conversation intelligence is built for Salesforce as its primary destination, not as a separate analytics platform with a sync layer added on top. Every output from a recorded call lands in native Salesforce objects in real time via a bi-directional, API-based integration.

After each meeting, Weflow pushes structured data to specific places in your Salesforce org:

• AI summaries written to the Event object's Description field
• Full transcripts stored in a custom object called Weflow Video Recording, linked to Opportunities via the managed package
• AI field updates pushed to any standard or custom object and field type (text, picklist, multi-picklist, currency, date, number, boolean), except lookup relationship fields
• Extracted MEDDIC/SPICED criteria, next steps, close dates, and competitor mentions populated automatically based on configurable extraction rules

The integration respects your existing Salesforce validation rules, field dependencies, permissions, and role hierarchy with no additional configuration. Recordings are auto-mapped to the correct Account, Opportunity, Contact, or Lead based on meeting participants. All conversation data stored in Salesforce is queryable, reportable, and available for Flows and automations.

Unlike Gong, Weflow makes the Salesforce field update the output itself, rather than treating its own dashboards as the primary destination for insights and requiring reps to manually update Salesforce afterward. You can configure updates to run automatically in the background or present a side-by-side comparison of current vs. AI-suggested values for review before writing.

Setup requires installing a managed package (one custom object, three custom fields), connecting your video platform (Zoom, Google Meet, or Microsoft Teams), and configuring field mapping. Most teams are operational within two weeks.

Does Weflow integrate forecasting with Salesforce opportunity snapshots?

Yes. Opportunity snapshots are the foundational data layer behind Weflow's forecasting and pipeline analytics suite. Weflow's data engine captures point-in-time snapshots of every deal at regular intervals, recording amount, stage, close date, forecast category, and custom fields, including formula fields like Gross Margin.

The AI prediction engine combines historical snapshot data with deal signals like engagement score, multi-threading, time-in-stage, close date push count, inactivity, and amount changes to generate a forecast corridor. That AI-predicted corridor sits alongside human-submitted forecast calls, weighted forecasts, and closed pipeline so you can compare machine prediction against rep judgment.

Snapshot data also powers a full set of pipeline analytics:

• Waterfall view showing start pipeline, new opportunities added, amount increases and decreases, deals moved in or out of period, won, lost, and end pipeline
• Pacing view tracking pipeline development over time against goals with prediction and commit overlays
• Pipeline coverage and generation reports computed from snapshot deltas across time periods
• Deals at Risk and Team Benchmarks for inspecting the specific opportunities driving any pipeline change

Weflow forecasting operates independently from native Salesforce forecasting. All forecast data, including submissions, category assignments, and historical snapshots, is stored as native Salesforce records. That means you can use it in Salesforce dashboards, reports, and Flows alongside your opportunity data.

Weflow stores field changes automatically without requiring you to enable Salesforce field history tracking, and supports both standard and custom forecast categories.

How difficult is the setup process for integrations with Weflow?

The technical integration takes 30 to 45 minutes. Most onboarding time is spent on business logic, not technical setup. You'll need a Salesforce admin and a Google Workspace or Microsoft 365 admin to complete the process.

• Install the Salesforce managed package (about 3 minutes)
• Install the Google Workspace Marketplace App or Microsoft Entra ID App
• Optionally configure an integration user

Weflow automatically detects your Salesforce schema, including custom fields, custom objects, field dependencies, validation rules, and permissions, so there's no field mapping required. The managed package installs one custom object with three custom fields.

Activity capture runs server-side in the background, meaning reps don't need to install anything, authenticate individually, or change their workflow. Most organizations deploy activity capture with zero change management on the rep side.

Full platform onboarding, including configuration of pipeline views, warnings, templates, and team rollout, targets one to three weeks. The technical integration is a small fraction of that. Every customer gets white-glove onboarding at no extra cost, with step-by-step video walkthroughs, free admin support for integration user setup, and a self-service admin console for any configuration changes after go-live. There are no implementation fees.

If you want to test before committing, a 14-day free trial includes the same white-glove implementation support, a mid-trial check-in, and a 30-minute results review.

Are there limitations on data sync frequency or scope?

Weflow syncs activity data in real time as emails and meetings occur. Field updates and deal changes in Forecasting and Pipeline Intelligence also sync in real time. Pipeline analytics use snapshot-based intervals, configurable to weekly or monthly depending on your setup.

There are several scope limitations to know about:

• Weflow captures emails, meetings, and contacts from Google Workspace or Microsoft 365 only. Phone calls, SMS, and VoIP activity are not captured.
• Internal-only communications, where all recipients are from internal domains, are excluded by default.
• If multiple open Opportunities exist under the same Account, Weflow won't auto-log to an Opportunity. You select the correct one via the Gmail or Outlook extension.
• Recurring event modifications across all occurrences or "this and following" are not fully supported today. Single-occurrence updates, creation, and deletion work as expected.

For historical backfill, Weflow includes 3 months of back-syncing emails and meetings at no extra cost. Beyond that, you can sync up to 3 years of historical emails as a paid add-on. Each back-synced record requires 3 to 5 Salesforce API calls, so large backfills are batched over several days or weeks to stay within API and Google/Microsoft rate limits.

Weflow caches variables and groups status-update calls using Salesforce's composite APIs, so daily API consumption stays low. If your reps send 100 to 200 emails per day, you won't hit API limits. If you plan to log thousands of emails per user per day, contact the Customer Success team. You can also configure attachment size exclusions (below 35 KB or above 10,000 KB) to manage Salesforce data storage.

How does Weflow work if you already record calls?

Most teams recording calls fall into one of two setups: keep your current recorder and add Weflow for activity capture, or replace your recorder with Weflow Conversation Intelligence. Both work.

If you're using Gong today, many organizations run Gong for call recording alongside Weflow for activity capture, since they solve different problems. Weflow's compatibility mode checks for existing activity records before syncing to Salesforce, so you won't get duplicate logs when running multiple tools. Some teams disable their sales engagement platform's Salesforce sync entirely and let Weflow handle all activity capture from the Google or Microsoft email server.

If you want to consolidate, Weflow Conversation Intelligence records meetings on Zoom, Microsoft Teams, and Google Meet and covers transcription, AI summaries, coaching, and follow-up emails. Unlike Gong, Weflow writes every output directly to native Salesforce objects, so conversation summaries and field updates land in Salesforce automatically without reps manually updating records after reviewing insights.

Gong treats its own platform as the destination for conversation data. Weflow treats Salesforce as the destination.

For teams migrating off Gong, Weflow imports your entire Gong recording library via Gong's API at no additional cost. The price difference is significant: Weflow Conversation Intelligence is $39/user/month standalone, while Gong typically lands around $250/user/month with platform fees. Weflow can also be purchased as a standalone product without requiring any other Weflow module, and technical setup takes 30 to 45 minutes.

Does Weflow offer a Chrome extension?

Yes. Weflow offers a Chrome extension included with all products: Activity Capture, Conversation Intelligence, and Deal Intelligence & Forecasting. You can install it from the Chrome Web Store by searching "Weflow," clicking "Add to Chrome," and signing in with your Salesforce account.

The extension replaces your Chrome new tab with a workspace that gives you direct access to Notes, Pipeline, Tasks, Search, new record creation, and shortcuts. You can search and update any Salesforce record from anywhere in the browser using CMD+J on macOS or ALT+J on Windows.

The extension also integrates with Gmail and Google Calendar to give you visibility into what Weflow's activity capture is logging and where. From your inbox, you can:

• Adjust activity mapping manually when auto-association needs correction
• Create contacts and update Salesforce fields without leaving Gmail
• Insert email open tracking pixels, which requires the extension since it can't run server-side
• View deal context, past activities, and related opportunities while composing emails

The extension is fully optional for both pipeline management and activity capture. Activity capture runs as a server-side background service, so your data syncs to Salesforce whether or not you install the extension. The extension adds transparency into what's happening and lets you intervene when needed. Admins can configure extension behavior through the Admin Console's Chrome Extension settings.