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

Weflow captures meetings from Zoom, Teams, and Google Meet without requiring a direct integration with any of those platforms. 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 attempts to join about a minute beforehand. If it sits in the lobby and is not admitted, it exits after 10 minutes. Once admitted, it records the full session including audio and screen sharing. After the call ends, auto-language detection identifies the meeting language across 96+ languages 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.

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 in a custom Weflow Video Recording object, installed via the managed package

• 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, and recordings are auto-mapped to the right Salesforce records.

This covers Zoom video meetings only, not Zoom Phone calls. Zoom Phone integration is on the roadmap but not available today. In the meantime, teams that need call logging typically connect their VoIP providers directly to Salesforce.

Activity Capture automatically logs all incoming and outgoing emails from Google Workspace in its fully automated mode, at the server level. No browser extension, plugin, or manual action is required in this configuration. Weflow also offers hybrid and manual modes: the hybrid mode adds an optional Gmail extension so reps can see and adjust how emails are mapped to Salesforce records. 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 or the Task object, depending on your configuration.

• 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 and linked to Opportunity Contact Roles where applicable. Weflow only creates a Contact if a matching Account already exists in Salesforce.

• Activities can also be logged to Custom Objects and Cases.

Because these are standard Salesforce records, your existing reports, dashboards, Flow automations, validation rules, field dependencies, permissions, and role hierarchy all apply immediately.

Unlike EinsteinActivity Capture (EAC), Weflow creates Salesforce-native activity records that you can report on, automate against, and export like any other standard object data. EAC historically stored activity data on AWS and visualized it into Salesforce without writing queryable native records. EAC's Summer '25 "Sync Email as Salesforce Activity" feature began rolling out native EmailMessage storage, but the rollout is incomplete for existing orgs, requires migration via Salesforce Support, and does not address contact auto-creation, mapping accuracy, or scale ceilings.

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 a proprietary database. The only Weflow-specific artifact is a managed package that adds 1 custom object and 3 custom fields to your Salesforce instance, which you can remove at any time.

Does Weflow integrate forecasting with Salesforce opportunity snapshots?

Yes. Weflow integrates forecasting directly with Salesforce opportunity snapshots. Opportunity snapshots track pipeline changes over time and feed the granular pipeline analytics and forecasting views that RevOps leaders and CROs rely on to spot gaps early.

These snapshots feed directly into multiple analytics views:

• A pre-built Waterfall report showing new deals, pulled-in, pulled-out, and closed-out pipeline over time

• 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. Forecast cadence is configurable as weekly, monthly, or quarterly to match how your team runs its revenue motion.

How does Weflow handle sales call recording and transcription?

Weflow handles sales call recording and transcription through an AI notetaker that automatically joins your scheduled external meetings on Zoom, Google Meet, and Microsoft Teams. It records, transcribes, and summarizes meetings, producing a transcript with speaker identification and automatic language detection across 96+ languages 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.

After a meeting ends, 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. The managed package also adds 1 custom object and 3 custom fields to your Salesforce instance, and Weflow can optionally log activities to custom objects and Cases in addition to standard objects.

For emails, your admin can choose whether to log to the EmailMessage object or the Task object in the Weflow admin console. The EmailMessage object preserves From/To/CC/BCC fields, HTML body, and attachments (excluding very small or very large ones). 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. Weflow's real-time API integration automatically respects your Salesforce configuration out of the box, including custom fields, validation rules, field dependencies, permissions, and role hierarchy.

Unlike EinsteinActivity 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's Salesforce integration is deep by design. It's built exclusively for Salesforce users 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 (excluding very small or very large ones), or as Task objects.

• Calendar events store in the native Event object with a parent/child event structure.

• Contacts are auto-created as standard Contact records, mapped to the right Account, and automatically set as 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, for any standard or custom Salesforce field except lookup relationships

• AI meeting summaries synced to the Salesforce Event Description field

• Activity logging to Custom Objects and Cases alongside standard objects

• Support for standard and custom Salesforce fields across all objects

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.

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 syncs emails and meetings to Salesforce automatically through a server-side background service that captures activity from Google Workspace or Microsoft 365 and writes it to native Salesforce objects in real time. No per-user setup is required for the core sync.

Setup starts with a centralized deployment: you install a Google Workspace Marketplace app or a Microsoft Entra ID app, which grants Weflow server-level access to email and calendar data scoped to enrolled users. Weflow will not create a subscription to email or calendar events for a user unless they have been activated in Weflow.

Weflow offers three deployment modes.

• In fully automated mode, the sync runs entirely in the background with no rep action required.

• In hybrid mode, an optional Gmail extension or Outlook Add-In lets reps see the auto-mapping and adjust it directly from their inbox.

• In manual mode, reps choose what gets logged. The optional inbox extensions are not required for the sync to work, but they give reps granular control over mapping when your RevOps team wants it.

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 is open and the Contact is set as a Contact Role, or if it is the only open Opportunity under the parent Account. If multiple open Opportunities exist under the same account, Weflow does not auto-log to an Opportunity. Reps can adjust the mapping manually via the optional Gmail extension or Outlook Add-In.

Emails are permanently stored in native Salesforce objects as Tasks or EmailMessages, including logged attachments (with size-based exclusions). Calendar events are stored in the native Salesforce Event object, with one parent Event per meeting and child Events created by Salesforce for each attendee.

• Internal-only emails, where all participants are from your domain, are automatically excluded

• Domain, email body, and custom exclusion rules are configurable in the admin console

• Compatibility mode detects existing tracking from sequencing tools like Outreach, Salesloft, Apollo, and Clay to prevent duplicate activity records

Because Weflow writes to standard Salesforce objects, every synced activity is immediately available in reports, Flows, and automations. If you ever stop using Weflow, the data persists in Salesforce as native records.

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

Yes. Weflow's AI notetaker supports Zoom, Microsoft Teams, and Google Meet. It automatically joins your scheduled meetings with external participants, records, transcribes, and summarizes them. No separate per-user authentication with each conferencing platform is required beyond your existing Google Workspace or Microsoft Entra ID connection.

The notetaker attempts to join about a minute before the call starts. If it isn't admitted, it waits in the lobby and exits after 10 minutes. This applies across all three supported platforms.

Weflow handles recording consent through a general consent flow that works across platforms:

• Pre-meeting notification: External participants can receive an email before the meeting starts, giving them the option to opt in or opt out of recording.

• In-meeting notification: A chat message is sent during the call as an additional opt-out mechanism.

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. The product is highly configurable, so admins can tailor recording behavior to fit your team's workflows.

You can prevent recording by not admitting the notetaker. It will exit the lobby automatically after 10 minutes. External participants can also opt out via the pre-meeting email or the in-meeting chat notification.

Two limitations worth noting: Weflow records video meetings only. Phone and VoIP calls are not yet supported, though Zoom Phone support is on the roadmap. Aircall is a native Weflow integration, but native telephony transcription is not yet available for any VoIP provider.

All conversation data captured through the notetaker is stored in Salesforce as native objects, not in a separate Weflow database. Transcripts, AI summaries, and AI field updates (including MEDDIC, SPICED, and custom methodology fields) write directly to the Salesforce records tied to the meeting. If you stop using Weflow, the data stays in Salesforce.

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 recording is on the roadmap but not available today. For teams that need to log calls from a VoIP or telephony provider, the most common approach is connecting that provider directly to Salesforce.

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 handles sales call recording and transcription through an AI notetaker that automatically joins your scheduled external meetings on Zoom, Google Meet, and Microsoft Teams. It records, transcribes, and summarizes meetings automatically. 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 96+ languages with no manual selection needed. Recordings are auto-mapped to the correct Account, Opportunity, Contact, and Lead records in Salesforce based on meeting participants. You can cut clips, build playlists for enablement, and track keyword or topic mentions across your full call library.

Full transcripts can sync to a custom Salesforce object (Weflow Video Recording), and AI summaries sync to the Salesforce Event Description field, making them reportable and available to Flows.

After each meeting, Weflow generates an AI summary, an AI follow-up email draft, and suggested Salesforce field updates pulled directly from the transcript. For field updates, Weflow compares current Salesforce field values against what was discussed and shows a side-by-side diff, with columns for current and new values across fields like Next Steps, Metrics, Economic Buyer, and Decision Criteria. This works across MEDDIC, MEDDPICC, SPICED, BANT, and custom methodologies, using 250+ pre-built prompts.

A mobile app for recording in-person field sales meetings is available on Android and iOS.

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

• Native telephony and VoIP recording are not available today; Zoom Phone support is on the roadmap

• A botless local desktop recording option (no bot in the meeting) is on the roadmap

You can prevent recording on any call by not admitting the notetaker. If left in the lobby, it exits automatically after 10 minutes. Weflow also supports pre-meeting opt-in or opt-out notifications for external participants via email, and an in-meeting chat notification, giving you a consent flow that satisfies GDPR requirements.

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 and reportable, and they work with standard Salesforce reporting, dashboards, Flows, APIs, and SOQL from day one.

Because Weflow data lives in native Salesforce objects, you can build Flows and automations that reference it just like any other Salesforce activity data. You can also build standard Salesforce reports on captured activities, since all captured activities are available in standard reports and dashboards from day one.

Unlike EinsteinActivity Capture, Weflow permanently writes activity data to the Salesforce database as queryable records. Historically, EAC stored activity on AWS and visualized it into Salesforce without making it queryable, so it wasn't usable in Flows, reports, or dashboards. EAC's Summer '25 changes began writing emails as native EmailMessage objects, but the rollout is incomplete for existing orgs, and even when fully rolled out, the changes don't address contact auto-creation, mapping accuracy, or Activity Metrics scale ceilings. This reporting gap is one of the most common reasons RevOps teams switch from EAC to Weflow.

Email open tracking, including last open date and open count, is stored as native Salesforce fields via Weflow's managed package. These fields are 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 respects your existing Salesforce setup out of the box, inheriting standard and custom fields, dependencies, validation rules, and permissions automatically. Activity mapping is automated by default, with optional rep-level adjustment available via the Outlook Add-In or Gmail extension. 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. Ask Weflow AI follows the same rules. It only returns data the user can already access in Salesforce. You can't query deals or accounts that fall outside your permission scope.

Because activity data lives in native Salesforce objects, it works with standard Salesforce reports, automations, and Flows. 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 Activity Capture, Groove, or manual logging where historical activity data is incomplete or missing.

Unlike Einstein Activity Capture, which has no automatic backfill and limits historical data migration to approximately 180 days, Weflow offers historical sync as a dedicated capability. This lets you populate Salesforce with past activity data for reporting, trend analysis, and deal context from day one.

• Historical sync-back of up to 24 months is an add-on for the Activity & Contact Capture standalone product and the Revenue AI Foundation bundle

• It is included at no extra cost in the Revenue AI Business and Revenue AI Enterprise bundles

• Backfill includes deduplication against sequencing tools like Outreach, Salesloft, and Apollo to avoid duplicate activity records in Salesforce

• For some customers, Weflow can sync back up to three years of historical activity data. There is typically an additional cost associated with this extended range.

One important distinction: historical activity data (emails and meetings) can be recovered through backfill. Conversation data from past calls cannot. If your team isn't recording calls yet, that data is gone permanently, which is why getting conversation intelligence in place quickly matters.

To initiate a historical sync, contact your Customer Success Manager or email [email protected] with the relevant email addresses and target date range.

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 Salesforce object and field, 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. Technical implementation typically takes about an hour, with full guided onboarding taking 2 to 4 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 creates point-in-time snapshots of your Salesforce opportunities to track pipeline changes over time, giving RevOps leaders and CROs a reliable record of how deals have moved across any period.

The AI prediction engine combines historical snapshot data with deal signals including engagement score, multi-threading, time-in-stage, close date push count, inactivity, and amount changes to generate a forecast projection. That AI-predicted projection sits alongside human-submitted forecast calls and weighted forecasts, so you can compare machine prediction against rep judgment in a single view. Specifically, Weflow shows AI Projection, Team Forecast, and Weighted Forecast side by side against pipeline, commit, and closed pipeline.

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 pipeline generation reports, alongside opportunity snapshots that track pipeline changes 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 tracks pipeline changes with opportunity snapshots and field history tracking, and supports multiple forecast methodologies with configurable forecast categories. Pipeline analytics, forecasting, and opportunity snapshots are available on the Revenue AI Enterprise bundle at $79 per user per month.

How difficult is the setup process for integrations with Weflow?

The Weflow integration setup is straightforward. Most teams complete the technical setup in 20 to 45 minutes. The majority of onboarding time is spent on business logic and configuration, 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 (adds one custom object and three custom fields to your org)

• 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 manual field mapping required.

Activity capture is deployed centrally via the Google Workspace App or Microsoft Entra ID App, which means reps don't need to authenticate individually for sync. In fully automated mode, capture runs in the background with no rep-side action required. If you choose hybrid or manual mode, reps can optionally install a Gmail extension or Outlook add-in to view and adjust activity mapping directly from their inbox. Centralized deployment minimizes rep-side change management, particularly in fully automated configurations.

Full platform onboarding, including configuration of pipeline views, warnings, templates, and team rollout, typically takes 2 to 4 weeks, with some rollouts completing in 1 to 2 weeks depending on scope. The technical integration is a small fraction of that timeline. Guided onboarding is included with no implementation fees. All plans include access to a self-service admin console for configuration changes after go-live, pre-recorded onboarding materials, and support for integration user setup.

If you want to test before committing, a 14-day free trial includes the same guided setup support, a mid-trial check-in, and a 30-minute session to review your results.

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 Deal Intelligence and Forecasting also sync in real time via a bidirectional Salesforce API integration.

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.

• Weflow creates one parent event per meeting, and Salesforce creates child events for each attendee. This keeps activity counts clean for reporting and coaching dashboards.

For historical backfill, Weflow can sync past activity data up to 24 months. This is included in Revenue AI Business and Revenue AI Enterpriseplans, and available as a paid add-on for Activity and Contact Capture standalone and Revenue AI Foundation. For some customers, Weflow can sync back up to 3 years of historical emails and meetings, typically with an associated cost. Note that conversation data cannot be recovered retroactively. Only activity data is available for backfill, which is one reason there's value in getting recording in place as early as possible.

Pipeline analytics use opportunity snapshots to track pipeline changes over time, giving RevOps leaders a reliable view of how pipeline is developing week over week.

On the attachment side, Weflow can log attachments while excluding small or large ones, with configurable size thresholds, giving admins control over Salesforce data storage consumption.

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. If you also use a sequencing tool like Outreach, Salesloft, or Clay, Weflow detects when those tools have already logged an email or meeting and skips it, so you avoid double-logging in Salesforce.

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 is typically $120 to $200/user/month plus a $5,000 base platform fee. 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.

The extension lets you search, create, and update any Salesforce record from anywhere in your browser. You can look up an opportunity, edit a field, or create a new record without switching tabs or opening Salesforce directly.

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

• Track email opens and last open date, stored as native Salesforce fields

• 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.