Does Weflow support automatic MEDDIC field extraction?

Yes. Weflow's Conversation Intelligence extracts MEDDIC fields directly from call transcripts and writes them to Salesforce. After each meeting, the AI analyzes what was said, identifies relevant qualification data, and suggests updates to fields like Economic Buyer, Decision Criteria, Metrics, and Next Steps on your Opportunity, Account, Contact, or Lead records.

Admins configure this in the Admin Console under Conversation Intelligence → Field Updates. You create a field update template, select the Salesforce object and fields, then assign an AI prompt to each field. Weflow includes a pre-built library of 250–350+ engineered prompts covering MEDDIC, MEDDPICC, SPICED, BANT, and Challenger, or you can write fully custom prompts up to 2,000 characters each. You can create unlimited templates and assign them to different teams.

After a call, Weflow shows a side-by-side comparison of the current Salesforce field value versus the AI-suggested value. You can review, edit, reject, or approve updates individually or in batch. If you prefer zero manual intervention, you can configure field updates to run automatically in the background.

Supported Salesforce field types include:

• Short text, long text, currency, number, and percent
• Date, date/time, and time
• Picklist and multi-select picklist
• Checkbox, URL, email, phone, and geolocation

Lookup relationship fields are not currently supported. Custom objects work with setup from the Weflow support team.

How does Weflow handle MEDDIC tracking and qualification scoring?

Weflow's Conversation Intelligence extracts MEDDIC qualification fields directly from call transcripts and populates them into Salesforce on Opportunity, Account, Contact, and Lead objects. For example, after a discovery call, Weflow can identify "decision maker: VP Engineering" or "budget confirmed at $50K" and map those values to the corresponding Salesforce fields. You review, edit, or reject each suggested update before anything writes to Salesforce.

The extraction runs on pre-built AI prompt templates. Weflow ships with 250+ prompts covering MEDDIC, MEDDPICC, SPICED, and BANT. Your admin maps specific Salesforce fields to these prompts and assigns different templates to different teams, so your enterprise AE team can run MEDDPICC while your mid-market team runs BANT from the same instance.

At the pipeline level, Weflow supports dedicated MEDDIC tabs per opportunity in Pipeline Intelligence views. You can configure stage-based warnings that fire when a required MEDDIC field is empty, such as flagging any deal in Stage 3 with no Economic Buyer identified.

Weflow's Deal Health Score (0 to 100) layers on 50+ deal signals, including engagement scoring, multi-threading, time-in-stage, and inactivity alerts, to give you a qualification picture that goes beyond methodology fields alone.

For coaching, Weflow auto-generates methodology-specific feedback after each call. Scorecards track rep performance over time, so you can measure whether MEDDIC adoption is improving across your org, not just whether fields are filled in.

What AI-powered deal insights does Weflow provide?

Weflow generates 50+ deal signals by analyzing your Salesforce data and auto-captured activity patterns. At the center is the Deal Health Score, a 0-to-100 rating that auto-calculates based on stage duration, activity frequency, field completeness, and historical win/loss comparisons. Each score includes what's going well, identified risks, and suggested next actions.

The deal signals that feed into this score are specific and measurable:

• Engagement Score (0–100) quantifying buyer and seller activity levels
• Multi-threading count derived from actual captured contacts, not manual entry
• Time-in-Stage tracking days in the current sales stage
• Close Date Pushed counting how many times the close date moved
• Inactivity measuring days since the opportunity last changed
• Amount Changes, Last Activity Date, and Next Meeting Date

Weflow surfaces configurable risk alerts directly in your pipeline views. Examples include "No activity in 14 days," "Close date pushed 3+ times," "Single-threaded: only 1 contact engaged," and "Missing key fields (champion, decision criteria, budget)." Admins can tie warnings to any combination of Salesforce fields, activity data, and deal stage.

For example, if stage is Negotiation and the buying committee field is empty, Weflow triggers a warning automatically.

The Ask AI chat interface lets you query this data in natural language, directly from any pipeline view, analyzing up to 2,000 records at once. You can ask questions like "What's blocking my top deals?" or "Which deals are stalling with a close date this month?" One clarification: deal insights are based on CRM data and activity patterns, not conversation content from calls.

How does Weflow's conversation intelligence work?

Weflow's conversation intelligence records, transcribes, and analyzes sales calls, then pushes structured insights directly into Salesforce. An AI notetaker automatically joins scheduled meetings on Zoom, Google Meet, Microsoft Teams, and WebEx, captures full video including screen sharing, and produces a searchable transcript with auto-language detection across 90+ languages.

After each call, Weflow generates AI summaries using configurable templates you can align to methodologies like MEDDIC, MEDDPICC, SPICED, BANT, or Challenger. Admins build these templates from a library of 250+ engineered prompts or write fully custom prompts. The summary is automatically written back to the Salesforce Event Description field.

The core operational value is automated Salesforce field updates. Weflow extracts structured data from transcripts and suggests updates to Opportunity, Account, Contact, Lead, or custom object fields. You see a side-by-side comparison of the current field value versus the AI suggestion, then approve, edit, or reject individually or in batch. This covers picklist, currency, date, amount, and text fields.

• Populating MEDDIC qualification fields like decision maker and budget from call content
• Updating next steps and close dates based on what was discussed
• Logging competitor mentions to opportunity records automatically
• Generating follow-up emails within 1–2 minutes of the meeting ending

Weflow also provides AI coaching scorecards with per-section ratings and manager overrides, keyword trackers that monitor competitor names or objection patterns across calls, and interaction metrics like talk ratio and question rate. The Ask AI feature lets you query your full recording library and Salesforce data in natural language to find patterns across deals.

Does Weflow automatically summarize meetings and push AI-powered notes to Salesforce?

Yes. After each recorded meeting, Weflow's AI notetaker transcribes the conversation and generates a summary based on configurable templates. That summary is automatically written to the Salesforce Event object's Description field, so Salesforce stays updated without any manual note-taking.

Weflow's AI notetaker joins your scheduled meetings with external participants on Zoom, Microsoft Teams, or Google Meet. It records the full video, including screen sharing, and produces a searchable transcript with auto-language detection across 96+ languages. The summary is generated within 1 to 2 minutes of the meeting ending.

All internal participants receive a recap email containing the summary, a draft follow-up email, and suggested Salesforce field updates with a link to the full recording.

Admins control what the summary looks like through a template system with a library of 250 to 350+ pre-built prompts, plus fully custom prompts up to 2,000 characters per block. Templates can be aligned to specific methodologies and assigned per team:

• MEDDIC and MEDDPICC
• SPICED, BANT, Challenger, and SPIN
• Short executive summaries or multiple summary variants per meeting
• Custom templates for any use case

Weflow also extracts structured data from the transcript and suggests updates to Salesforce fields. You can configure those field updates to require manual approval or run automatically in the background, giving you full control over what gets written to Salesforce. Recordings are auto-mapped to the correct Account, Opportunity, Contact, and Lead records based on meeting participants.

How does Weflow's AI-powered forecasting work?

Weflow's AI forecast prediction combines historic opportunity snapshots with 50+ deal signals to generate a forecast corridor for your pipeline. These signals include engagement score (scored 0 to 100 based on buyer and seller activity), multi-threading depth, time-in-stage, close date push count, inactivity periods, amount changes, and last activity date. The model also factors in historical win rates by stage, average deal cycle length, seasonal patterns, and your org's historical forecast accuracy.

• Engagement score (0–100, based on buyer and seller activity)
• Multi-threading depth
• Time-in-stage
• Close date push count
• Inactivity periods
• Amount changes
• Last activity date

The AI projection sits alongside your human-submitted forecast calls and weighted forecasts as an objective, data-driven reference point. For example, if your reps submitted $2.4M in Commit but historical patterns project $2.1M based on current pipeline, Weflow surfaces that gap directly in the forecast roll-up. This gives CROs and sales managers a concrete reference point instead of relying solely on rep judgment.

Weflow's forecasting does not analyze call recordings or email content to inform projections. It draws from three data layers: Salesforce CRM data, activity data captured by Weflow Activity Capture, and conversation-derived field updates from Weflow Conversation Intelligence. When you pair forecasting with Activity Capture, you get the full set of deal signals that feed the prediction engine. Without that activity data layer, the AI loses access to those 50+ signals, which directly impacts prediction quality.

All forecast data, including submissions, category assignments, and historical snapshots, is stored as Salesforce records. Weflow also tracks forecast accuracy over time, comparing forecasted vs. actual outcomes and identifying systematic over- or under-forecasting patterns by rep, team, or segment.

How accurate is Weflow's AI forecasting?

Accuracy depends on your Salesforce data quality. Weflow's AI projections are built on historical opportunity snapshots, win rates by stage, average deal cycle length, and seasonal patterns. The model also reads more than 50 deal signals, including engagement score (0–100), multi-threading depth, time-in-stage, close date push count, inactivity flags, and amount changes.

Rather than a single number, Weflow generates a forecast corridor, giving you a realistic range to compare against what reps submit. One concrete example: Aleph, a Weflow customer in advertising services, achieved 95% forecast accuracy. Your results will vary based on how complete your Salesforce data is. The AI projection is only as good as the pipeline data, activity history, and stage conversion patterns it can read from your org.

Accuracy improves when you pair forecasting with Weflow Activity Capture and Weflow Conversation Intelligence. Activity Capture fills in engagement signals such as emails, meetings, and contact roles that feed deal health scoring. Conversation Intelligence auto-populates fields like MEDDIC criteria from call data. This creates a data-quality flywheel where better inputs drive tighter projections over time.

Weflow tracks forecast accuracy over time, logging every forecast call and manager adjustment so you can spot systematic over- or under-forecasting by rep, team, or segment. The AI projection sits alongside human-submitted calls and weighted forecasts as an objective counterpoint, answering one question: are we being realistic? Weflow imports historical data during setup and is operational within two weeks.

Does Weflow offer pipeline inspection features like deal health scores and risk warnings?

Yes. Weflow includes an auto-calculated Deal Health Score (0 to 100) and configurable risk warnings that surface directly in your pipeline views.

The Deal Health Score analyzes Salesforce data patterns including stage duration, activity frequency, field completeness, and historical win/loss comparisons. Each score breaks down what's going well, what's at risk, and what actions to take next. You can use it as a single metric to prioritize which deals need attention during your weekly review.

Weflow generates 50+ deal signals that feed into risk detection. These include:

• Engagement Score (0 to 100 based on buyer and seller activity)
• Multi-threading count (number of prospects involved in an opportunity)
• Close Date Pushed (how many times the close date moved)
• Time-in-Stage (days in current stage)
• Inactivity (days since the opportunity last changed)
• Next Meeting Date and Last Activity Date

Admins configure warnings based on any combination of Salesforce fields, activity data, and Weflow signals. For example, you can trigger a warning when a deal is single-threaded, has no next meeting scheduled, has been inactive for 14 days, or is missing required fields like champion or decision criteria at a specific stage.

Warnings appear in pipeline views and in a pre-built Deals at Risk view, and can also trigger email alerts. This means you spot stalled deals, missing stakeholders, and slipping close dates before your forecast call, not during it.

Can Weflow generate pipeline coverage reports and forecast accuracy dashboards?

Yes. Weflow includes pre-built Pipeline Coverage and forecast accuracy views out of the box, with no need to build custom Salesforce reports or maintain Tableau dashboards.

The Pipeline Coverage view compares open opportunities across stages against quota, calculates coverage ratios automatically, and updates in real time. Admins set quotas at the org, team, and individual level. Weflow surfaces coverage gaps by comparing forecast calls, open pipeline, weighted forecasts, and AI predictions against those quotas.

Unlike Salesforce native forecasting and spreadsheets, Weflow tracks every forecast call and manager adjustment over time, then compares forecasted vs. actual outcomes. You get a full history of changes so you can measure how accurate your team's calls were at any point in the quarter.

The analytics suite includes several other pre-built reports:

• Pacing tracks pipeline development against monthly, quarterly, or annual goals with an AI projection overlay and optimal pace line
• Waterfall shows start pipeline, new opportunities, amount changes, moved in/out of period, won/lost, and end pipeline
• Team Benchmarks breaks down attainment, open opportunities, and opportunities created by rep and team
• Deals at Risk flags opportunities that need attention before your next forecast call

All views support quick, custom, and preset filters and can be configured per team. These are included in the Deal Intelligence and Forecasting product at $39 per user per month. Advanced pipeline analytics including pipeline velocity, stage conversion rates, and sales cycle length are on the roadmap for 2026 (coming 2026).

Can Weflow automatically update Salesforce opportunity fields like next steps and close date from meeting notes?

Yes. Weflow's Conversation Intelligence extracts structured data from meeting transcripts and suggests updates to Salesforce opportunity fields, including Next Steps, Close Date, MEDDPICC qualification fields, and any other field on the Opportunity object.

Admins create field update templates in the Admin Console by mapping specific Salesforce fields to AI prompts. After a meeting ends, Weflow analyzes the conversation within one to two minutes and shows a side-by-side comparison of the current Salesforce field value versus the AI-suggested new value. For example, a Next Steps field showing "Schedule a call" might be updated to "Send documentation and get intro to VP of Procurement" based on what was discussed.

You can review, edit, reject, or approve each suggested update individually or in batch. Admins can also configure per-field granularity, setting some fields like Next Steps to require manual review while others update automatically in the background.

Supported field types include:

• Date and date/time, for Close Date updates
• Picklist and multi-select picklist, for stage, forecast category, or methodology fields
• Currency and number, for Amount or custom scoring fields
• Short text and long text, for Next Steps, MEDDPICC criteria, or notes

Salesforce validation rules, field dependencies, and permissions are respected automatically with no additional configuration. This feature is available starting with the Conversation Intelligence plan at $39 per user per month.

How accurate is Weflow's transcription?

Does Weflow offer AI-powered sales coaching and performance insights?

Yes. Weflow's Conversation Intelligence product includes AI-powered coaching and performance insights as core capabilities, priced at $39 per user per month standalone.

AI coaching auto-generates methodology-aligned feedback after every recorded meeting. Weflow ships with pre-built templates for MEDDIC, MEDDPICC, Challenger, and other frameworks, plus a library of hundreds of prompts you can customize. Coaching can be delivered as open-text qualitative feedback or as structured scorecards with 1–5 ratings per section and an overall meeting score. Managers can review AI-generated scores and apply overrides where needed.

Templates can be conditionally applied based on Salesforce field values, so a discovery coaching template only fires when the opportunity is in the Discovery stage. You can assign multiple templates per call and configure them by team in the Admin Console. After each meeting, Weflow sends a summary email with coaching feedback available in the Coaching tab.

Performance insights come through pre-built dashboards covering the following metrics:

• Interaction metrics: talk ratio, longest monologue, longest customer story, interactivity score, patience, and question rate
• Activity metrics: meeting volume, meeting duration, time spent in meetings, email volume, and recorded meetings count
• Responsiveness metrics: email response time, share of emails responded to within 24/48/72 hours, open rate, and reply rate
• Leaderboards comparing individual reps against team averages and benchmarks

Scorecard ratings are tracked over time so managers can measure rep improvement across users, scorecards, and timeframes, then drill into the related activities. Managers see full team data, while individual reps see only their own metrics compared to team averages. One limitation to note: when multiple internal sellers attend the same meeting, scorecards are per-meeting, not per-participant.

How does Weflow's forecasting compare to Gong and Salesforce Einstein?

The core difference is what data each platform uses to generate forecasts. Weflow builds projections from CRM pipeline data, historical win rates, stage conversion patterns, and activity levels. Gong Forecast layers in conversation signals like buyer engagement and stakeholder involvement from recorded calls. Salesforce Collaborative Forecasts offers basic roll-ups but lacks AI projections, trending, and pipeline coverage analysis.

Gong's conversation-signal approach is genuinely valuable. It can flag that a deal's close probability should drop because buyer engagement fell off on recent calls, even when CRM data still looks healthy. That said, Gong Forecast requires full Gong adoption across all calls to deliver accurate projections. If not every call is recorded, those conversation-based signals have gaps.

Unlike Gong, Weflow stores forecast submissions, categories, and snapshots directly in Salesforce, so your forecast data appears in native Salesforce reports and dashboards alongside opportunity data. Weflow gives you three forecast methods: bottom-up, dynamic-weighted, and AI prediction factoring in seasonality. The structured weekly submission workflow tracks how forecasts evolved over the quarter and identifies systematic over- or under-forecasting by rep.

Unlike Salesforce Collaborative Forecasts, Weflow lets you forecast on any custom or standard field, stores field changes automatically without enabling field history tracking, and generates Waterfall, Pacing, and Deal Flow reports out of the box.

On cost, Weflow runs $49/user/month ($29,400/year for 50 users). Gong requires the Foundation platform (approximately $1,600/user/year) plus the Forecast add-on ($200–$700/user/year), totaling $130K–$200K+ annually for 50 users.

View a detailed comparison: Weflow vs Gong.

Learn more about the detailed differences between Weflow and Salesforce Einstein.

What features are included in Weflow's activity capture module?

Weflow Activity Capture is a server-side sync solution that automatically logs emails, calendar events, meetings, and contacts from Google Workspace or Microsoft 365 into Salesforce as native records. No rep action is required. The system runs in the background and captures 99.9% of email activity without relying on rep behavior.

The module covers four core areas:

• Email Capture: Logs all inbound and outbound emails as EmailMessage or Task objects, preserving From, To, CC, BCC fields, HTML body, and attachments. Internal emails are excluded via domain filtering, and calendar confirmation emails are automatically filtered out.
• Calendar and Meeting Capture: Syncs calendar events as Salesforce Events with one-directional or bi-directional sync. Captures attendee names, account relationships, opportunity associations, and RSVP status. Supports recurring events, reschedules, cancellations, and meetings booked through Calendly or Chili Piper.
• Contact Capture: Auto-creates or updates Contact records with name, email, title, and company when new external contacts appear in email threads or calendar invites. Admins can restrict creation to existing accounts, set exclusion rules (for example, skip emails containing "invoices" or meetings with 8+ participants), and assign Opportunity Contact Roles automatically.
• Activity Matching: Associates every captured activity with the correct Account, Contact, Lead, and Opportunity using email domain matching, participant matching, and configurable rules. When multiple open opportunities exist on one account, you select the correct one from the Gmail or Outlook extension, and Weflow remembers that selection for the entire thread.

Every captured record is a standard Salesforce Task or Event. That means it appears in Activity Timeline, works in reports, triggers Flows and Process Builder automations, and respects your sharing rules and validation rules.

If you ever uninstall Weflow, all captured data stays in your Salesforce org permanently.

What's the difference between Weflow's activity capture and conversation intelligence modules?

Activity Capture and Conversation Intelligence are two separate Weflow modules that cover different data sources and write to different Salesforce objects. Activity Capture syncs emails, calendar events, and contacts from Google Workspace or Microsoft 365 into Salesforce as native records. Conversation Intelligence records and transcribes sales calls on Zoom, Google Meet, and Microsoft Teams, then pushes structured insights and field updates into Salesforce.

Activity Capture runs as a server-side background service with no browser extension or user action required. It includes email open tracking, auto contact creation, activity matching, and up to 24 months of historical backfill. Everything it writes lands on standard Salesforce objects (Task, Event, EmailMessage, Contact), so your reports, dashboards, Flows, and automation rules work immediately.

Conversation Intelligence goes beyond recording and transcription. After each call, it generates AI summaries covering action items, objections, competitor mentions, and next steps, then automatically updates Salesforce fields based on configurable extraction rules. Fields updated include MEDDIC/SPICED qualification criteria, close dates, and custom fields.

It also provides coaching metrics, including talk-to-listen ratios, question frequency, and longest monologues. The searchable transcript library is organized by account, opportunity, and rep, with support for 96+ languages and 250+ pre-built AI prompts.

The two modules don't overlap: Activity Capture does not record calls, and Conversation Intelligence does not capture email or calendar data. Pricing for each module is:

• Activity Capture: $19/user/month
• Conversation Intelligence: $39/user/month
• Both modules bundled: $49/user/month

Is Weflow a good activity capture solution for mid-market teams?

Yes. Weflow is built for mid-market B2B teams, with a target company size of 100 to 10,000 employees and a sweet spot of 30 to 300 users across sales, CS, and other customer-facing teams. RevOps leaders and Salesforce Admins at B2B companies with 50 to 500 employees are the primary audience.

Weflow runs as a server-side background service with no browser extension, no email plugin, and no action required from reps. Setup takes 20 to 45 minutes with a Salesforce Admin and a Google Workspace or Microsoft 365 Admin. Reps don't install anything or change their workflow, which means zero change management.

Weflow is not a sales engagement platform. It doesn't send sequences or outbound emails. It captures all inbound and outbound emails, calendar events, meetings, and contacts, then writes them to Salesforce as native Task, Event, and Contact records. Those records appear in Activity Timeline, work in standard Salesforce reports, trigger Flows and Process Builder automations, and respect your sharing rules.

Unlike Outreach, Salesloft, or Apollo, Weflow has a compatibility mode that avoids duplicate logging if you already use one of those platforms.

Pricing is $19/user/month with no platform fees and no implementation fees, with a minimum of 10 users. Volume discounts are available for larger teams. Every plan includes:

• White-glove onboarding
• Pre-built activity analytics dashboards
• 24-month historical backfill from Google Workspace or Microsoft 365
• No implementation fees

For a 50-person team, that's $11,400/year. For 100 users, $22,800/year.

Does Weflow automatically update Salesforce fields after calls and meetings?

Yes, but with an important distinction: by default, Weflow suggests field updates after each recorded meeting and lets you review them before anything is written to Salesforce. After a call or meeting, Weflow's Conversation Intelligence analyzes the transcript, identifies relevant fields based on admin-configured templates, and presents a side-by-side comparison of the current Salesforce value versus the AI-suggested value. You can approve, edit, or reject each suggestion individually or in batch.

If your team prefers zero-touch updates, an automatic background mode is available as a configuration flag. In this mode, field updates are pushed to Salesforce without manual confirmation. Most Weflow customers stick with the review-and-approve workflow to maintain data integrity, but the option exists for teams that prioritize speed over manual oversight.

Field update templates are fully configurable by admins and support a wide range of Salesforce field types:

• Text, picklist, and multi-picklist (AI selects from your existing picklist values rather than generating free text)
• Currency, date, amount/number, and boolean fields
• Any standard object (Account, Contact, Opportunity, Lead) and any custom object
• Methodology fields like MEDDIC or SPICED stages

Lookup relationship fields are the one exception and aren't supported for AI updates. You can create unlimited templates and assign them to different teams, so your AEs and CSMs each get relevant suggestions.

AI meeting summaries are also written automatically to the Salesforce Event object's Description field after every recorded meeting, with no user action required.

Does Weflow automatically create contacts in Salesforce?

Yes. Weflow detects email addresses and calendar attendees that don't yet exist in Salesforce and creates them as standard Contact objects. It runs as a server-side background service, so contacts appear in Salesforce without reps doing anything manually. The feature is part of Weflow Activity Capture, priced at $19 per user per month.

When Weflow creates a contact, it matches the email domain to an existing Account record and associates the contact automatically. It also sets Opportunity Contact Roles where applicable, which solves one of the most common data quality gaps in Salesforce: empty Contact Roles that break stakeholder mapping and deal health scoring. Contact data is enriched with first name, last name, title, phone, and email from Google Workspace contact cards via the Contacts API when available.

Auto-creation isn't enabled by default. You turn it on in the Weflow admin console, where you can also choose between fully automated background creation or manual opt-in through the Gmail or Outlook extension.

• Restrict creation to contacts whose domain matches an existing Account only, preventing orphan records
• Apply string-based exclusion rules to skip addresses containing patterns like "invoices" or "noreply"
• Set max participant thresholds to avoid creating contacts from webinars or large meetings, such as those with more than 8 attendees
• Enable or disable automatic Opportunity Contact Role assignment

Weflow respects your Salesforce permission structure. If your org requires a parent Account for contact creation, Weflow won't create the record until one exists. If the Account is created later, Weflow re-associates the contact automatically.

How does Weflow improve CRM data quality and completeness?

Most Salesforce data quality problems trace back to one root cause: reps don't log their work. Weflow fixes this with server-side activity capture that runs in the background with no browser extension, no email plugin, and no rep action required. The result is 99.9% of emails and meetings reaching Salesforce automatically, stored permanently in standard objects (EmailMessage, Task, Event) where you can report on them, use them in Flows, and feed them into automations.

Weflow also fills the gaps that break stakeholder mapping and deal health scoring. When a contact appears in an email thread or calendar event but doesn't exist in Salesforce, Weflow auto-creates the Contact record, associates it with the matching Account, and populates Opportunity Contact Roles. Contact data is enriched with first name, last name, title, phone number, and email pulled from Google Workspace contact cards.

Weflow's mapping algorithm uses email addresses as unique identifiers and traverses relationships across Contacts, Leads, Accounts, Opportunities, and custom objects to log activities to the correct records. When multiple open opportunities exist on the same account, you can select the right one from the Gmail Extension or Outlook Add-In, and Weflow remembers that selection for the full thread.

• Up to 24 months of historical activity backfill from Google Workspace or Microsoft 365
• Full respect for your existing validation rules, field dependencies, permissions, and role hierarchy
• Compatibility mode to prevent duplication when tools like Outreach, Salesloft, or Gong Engage are also syncing
• All data persists in native Salesforce objects if you stop using Weflow, with no lock-in

How does Weflow's CRM data quality compare to Einstein Activity Capture?

The core difference is architectural. Einstein Activity Capture (EAC) streams activity data into Salesforce but does not write it to the database. That means EAC activities can't appear in Salesforce reports, can't trigger Flows, and can't feed automations. Weflow writes every captured email, meeting, and contact as a native Salesforce record (EmailMessage, Task, Event, Contact), so your data is immediately queryable, reportable, and available to any downstream process you've built.

Unlike EAC, Weflow gives you control and coverage across several dimensions that directly affect data quality.

• Auto-creation of Contact records and Opportunity Contact Roles when new external contacts appear in email threads or calendar invites
• Relationship-graph mapping across Contacts, Leads, Accounts, Opportunities, Custom Objects, and Cases, with manual override via Gmail and Outlook extensions
• Email open tracking stored in custom Salesforce fields (last open date, open count) usable in Flows
• Historical backfill of up to 24 months from Google Workspace or Microsoft 365
• Support for multiple contact relations per email or event, a known EAC limitation
• Custom exclusion rules by domain, email body content, or any Salesforce field condition

EAC is fully automated with no user controls for mapping adjustments. When auto-relating fails, and practitioners report it frequently does, there's no recourse. EAC also requires individual user OAuth connections that break when passwords change.

Unlike EAC, Weflow uses central admin enrollment via Google Workspace Marketplace or Microsoft Entra ID, so connections don't depend on individual reps.

EAC is included in certain Salesforce editions and may work if you have zero reporting or automation requirements. If your RevOps team needs activity counts by account over 30/60/180-day windows, or your CRO wants data they can build reports on, Weflow is the more practical path. If you stop using Weflow, all captured data stays in Salesforce permanently.

View a detailed comparison: Weflow vs Einstein Activity Capture.

How does Weflow's automatic CRM data capture work?

Weflow runs as a server-side background service that captures emails, meetings, and contacts from Google Workspace or Microsoft 365 and writes them to native Salesforce objects. There's no browser extension, no email plugin, and no manual action required from your reps. You install a central application via the Google Workspace Marketplace or Microsoft 365 Entra ID, which grants Weflow server-level access to email and calendar data for enrolled users.

Once connected, Weflow receives a real-time notification for every email sent or received and every calendar event created, modified, or deleted. For each activity, it performs a lookup against Salesforce using the email address as a unique identifier, matching against Contact, Lead, and Custom Object records. It then traverses relationships from Contact to Account to Opportunity, logging activities to open Opportunities where a Contact Role exists or where only one open Opportunity sits under the parent Account.

Weflow stores emails as EmailMessage objects, preserving From, To, CC, BCC, HTML body, and attachments, or as Task objects, depending on your configuration. Calendar events are stored in the native Salesforce Event object with parent-child relationships per attendee, including RSVP status updates, reschedules, and cancellations. Internal-only emails and meeting status notifications are automatically filtered out.

Weflow also detects contacts that don't yet exist in Salesforce and can auto-create them with enriched data like name, title, and phone number. Admins control this with exclusion rules, such as blocking creation for meetings with more than 8 participants or restricting auto-creation to contacts matching existing Account domains. Everything writes to standard Salesforce objects in real time, so your reports, Flows, and automations work immediately.

How does Weflow prevent data decay in Salesforce over time?

Data decay in Salesforce happens for three reasons: reps don't log activities, contacts go missing, and deal fields go stale. Weflow addresses each of these at the source.

Weflow Activity Capture runs server-side through Google Workspace or Microsoft Entra ID, syncing 99.9% of emails, meetings, and contacts to Salesforce without any rep action. Central admin enrollment means no per-user OAuth connections that break when passwords change, so capture runs continuously with zero adoption gaps. All activities write permanently to native Salesforce objects (Task, Event, EmailMessage, Contact), making them available in reports, Flows, and downstream automations.

In addition to activity logging, Weflow addresses the most common data quality gaps:

• Automatic contact creation for people found in email threads or calendar events who don't yet exist in Salesforce, with Opportunity Contact Role population
• 24-month historical backfill from Google Workspace or Microsoft 365 to restore incomplete activity baselines
• AI-generated field updates from Conversation Intelligence that push methodology fields (MEDDPICC, SPICED, BANT) to Opportunity, Account, Contact, and Lead objects after recorded meetings
• An editable deal grid where reps update close dates, amounts, stages, and qualification fields without switching to Salesforce
• Configurable warnings, such as "single threaded," "no next meetings scheduled," or "inactive for 14 days," that enforce process compliance in real time

Weflow's deal signals, including engagement score, multi-threading count, and last activity date, depend on complete underlying data. The tight coupling between activity capture and pipeline intelligence ensures those signals reflect reality rather than whatever reps remembered to log.

How does Weflow handle Salesforce activity logging?

Weflow Activity Capture is a server-side background service that automatically logs emails, meetings, and contacts from Google Workspace or Microsoft 365 into native Salesforce objects. No browser extension, email plugin, or manual action is required from reps. Activities sync in real time as they occur.

Emails (both incoming and outgoing) are stored as EmailMessage or Task objects in Salesforce, preserving From, To, CC, BCC fields, HTML body, and attachments. Internal-only communications are excluded by default, and meeting status emails like calendar confirmations are filtered out automatically. Calendar events sync to the native Salesforce Event object with support for one-directional or bi-directional sync, recurring events, reschedules, and cancellations.

Weflow's mapping algorithm uses email addresses as unique identifiers, matching them against the following Salesforce objects:

• Contacts
• Leads
• Custom Objects
• Cases
• Accounts
• Opportunities

The algorithm considers whether an Opportunity is open, whether the contact is a Contact Role, and whether it's the only open opportunity under the parent Account. When multiple open opportunities exist for the same account, reps can select the correct one via the Gmail Extension or Outlook Add-In, and Weflow remembers that selection for the entire thread.

All captured data is written permanently to standard Salesforce objects, so it's queryable, reportable, exportable, and available in Flows and automations. If you stop using Weflow, your data stays in Salesforce with no lock-in.

Weflow can also auto-create contacts that appear in email threads or calendar events but don't yet exist in Salesforce, either as a fully automated background process or as a manual opt-in from your inbox.

How does Weflow map activities to opportunities and prevent incorrect attribution?

Weflow uses a relationship-graph-based mapping algorithm that starts with email addresses as unique identifiers. It matches each address against Contacts, Leads, and custom objects in Salesforce, then traverses the relationships to parent Accounts and Opportunities. This goes beyond standard Opportunity Contact Roles.

For Opportunity-level logging, Weflow applies two conditions. It logs to an Opportunity only if the Opportunity is open and the Contact is set as a Contact Role, or if there is exactly one open Opportunity under the parent Account. If multiple open Opportunities exist for the same Account and the algorithm cannot determine the right one, Weflow deliberately does not auto-map. This prevents activities from landing on the wrong deal and breaking pipeline analytics or deal velocity metrics.

When multiple Opportunities are in play, you can select the correct one via the Gmail Extension or Outlook Add-In. Weflow remembers that selection at the thread level, so every future email in that conversation maps to the same Opportunity without further input. If something does get logged incorrectly, you can unlog the activity and re-log it to a different record directly from your inbox.

Admins get additional controls to tighten attribution:

• Condition-based logging rules using any Salesforce field (e.g., "if Account Type = Partner, do not log")
• Object-level toggles to enable or disable logging to Opportunities, Leads, Custom Objects, or Cases
• Team-specific configurations so AEs, CSMs, and SDRs can have different mapping behaviors
• Compatibility mode that checks for tracking patterns from tools like Outreach, Salesloft, or Gong Engage before logging, avoiding duplicates

Weflow also filters out noise automatically. Internal-only emails are excluded by default, and calendar confirmation messages like "Meeting accepted" are never logged as activities.

What reporting and analytics does Weflow offer?

Weflow offers reporting and analytics across four areas: pipeline intelligence, deal intelligence, activity analytics, and forecasting. All of it is built on your Salesforce data, so the numbers match your Salesforce reports with no discrepancies between systems.

Pipeline Intelligence includes five pre-built dashboards: Waterfall (start pipeline, new opps, amount changes, push count, won/lost, and end pipeline), Pipeline Pacing (pipeline development against goals with overlay for prediction, hard commit, and other forecast categories), Pipeline Coverage (open opps across stages vs. quota), Pipeline Generation (new pipeline creation), and Team Benchmarks (attainment, open opps, opps created). Every view supports filters by rep, team, record type, and any Salesforce field.

Deal Intelligence generates 50+ signals per deal, including Close Date Pushed, Engagement Score (0 to 100), Multi-threading, Time-in-Stage, and Inactivity. A Deal Health Score auto-calculates from 0 to 100 with risks and suggested actions. You can configure warnings like "Single threaded" or "No next meetings scheduled" using any combination of Salesforce fields, activity data, and Weflow signals.

Activity Analytics tracks meeting volume, email volume, open rate, reply rate, and responsiveness metrics like average time to respond and share of emails answered within 24, 48, and 72 hours. Reps see their own metrics against team averages; managers get full team visibility.

Forecasting includes AI-predicted forecast corridors, automated roll-ups across your Salesforce role hierarchy, and forecast accuracy tracking with change history on every call and adjustment. Weflow also supports multiple independent forecasts (new logo, expansion, renewal) mapped to different Salesforce fields.

Unlike Einstein Activity Capture, Weflow writes all captured data to native Salesforce objects (Task, Event, EmailMessage). This means you can report on it with standard Salesforce dashboards, Flows, and automations, and export to data warehouses for analysis in BI tools.

Explore Weflow's detailed comparison with Einstein Activity Capture.

What pipeline visibility and deal inspection features does Weflow offer?

Weflow Pipeline Intelligence is built for RevOps leaders, sales managers, and CROs who need to spot deal risk and track pipeline changes without leaving Salesforce data behind.

The core interface is an editable deal grid with a spreadsheet-like layout. You can update stage, amount, close date, next steps, and custom fields inline, and every edit syncs bi-directionally to Salesforce in real time. You can switch between table and Kanban views, add or remove columns, and build custom views using any combination of Salesforce fields and Weflow deal signals. Views can be saved, shared, and assigned to specific teams.

Weflow generates 50+ deal signals and a Deal Health Score (0 to 100) that flags what's going well, active risks, and suggested actions. Signals include Close Date Pushed count, Engagement Score, Multi-threading depth, Time-in-Stage, and Inactivity days. Admins configure warnings based on any mix of Salesforce fields, activity data, and Weflow signals.

• Single-threaded: only one contact engaged on the opportunity
• No next meeting scheduled
• Inactive for 14+ days (configurable threshold)
• Close date pushed 3+ times
• Missing key fields like champion, decision criteria, or budget at a given stage

Warnings surface directly in your pipeline views, and deal alerts can trigger email notifications. Weflow includes pre-built dashboards: Waterfall (start-to-end pipeline movement), Pipeline Pacing (development against goals), Coverage (open pipeline vs. quota by stage), Generation (new pipeline creation), and Team Benchmarks (attainment, open and created opportunities).

Pipeline Change Tracking uses opportunity snapshots to show exactly what changed since your last review: new deals, stage advances, slipped deals, and removed deals.

Does Weflow flag stale opportunities and enforce close date hygiene?

Yes. Weflow flags stale opportunities and enforces close date hygiene through deal signals, configurable warnings, and AI deal scoring, all based on what's in your Salesforce data.

Weflow Pipeline Intelligence generates 50+ deal signals, and several target staleness and close date discipline directly. The Close Date Pushed signal tracks how many times the close date was moved on each opportunity. The Inactivity signal measures the number of days since anything changed on a deal. Time-in-Stage shows how long an opportunity has sat in its current stage. These signals surface in your pipeline views so you can spot problems before your next forecast call, not during it.

Weflow also provides configurable risk alerts that admins can build from any combination of Salesforce fields, activity data, and Weflow signals:

• Close date pushed 3+ times on an opportunity
• No activity in 14 days (threshold is configurable)
• Below average activity for the current deal stage
• Missing key fields like champion, decision criteria, or budget at a given stage
• Single-threaded deals with only one contact engaged
• No next meeting scheduled

Warnings enforce your sales process without requiring reps to remember checklists, and they can trigger email alerts for follow-up. The Waterfall view includes a dedicated "Close date in past" category so you can quickly isolate overdue opportunities.

Weflow's AI Deal Scoring layers on top of all this, analyzing stage duration, activity frequency, field completeness, and close date slip patterns to generate a 0-to-100 deal health score with specific risk callouts and suggested actions.

Does Weflow provide deal-level signals like single-threading and inactivity?

Yes. Weflow surfaces both single-threading and inactivity as named deal signals, along with 50+ other signals calculated from your Salesforce data, activity patterns, and conversation data.

The single-threading signal flags deals where only one contact is engaged. The inactivity signal tracks the number of days since an opportunity last changed, with a default threshold of 14 days that your admin can configure. Multi-threading counts are derived from actual captured contacts, not manual entry, so the data reflects real engagement rather than what reps remember to log.

In addition to those two signals, Weflow's signal engine covers a broad set of deal health indicators:

• Close Date Pushed: number of times the close date was moved
• Engagement Score: 0 to 100, based on buyer and seller activities
• Time-in-Stage: days in current stage
• Amount Changes
• Last Activity Date and Next Meeting Date
• Contact insights showing whether the right stakeholders are engaged
• Deal Health Score: 0 to 100, with risks, strengths, and suggested actions

Admins configure warnings based on any combination of Salesforce fields, activity data, and Weflow signals. For example, you can trigger a warning when a deal reaches a specific stage but the buying committee field is still empty. These warnings surface directly in your pipeline views and can also trigger email alerts so managers catch risk without waiting for the weekly call.

Deal signals and configurable warnings are part of the Deal Intelligence and Forecasting product at $39 per user per month, billed annually.

What forecasting capabilities does Weflow offer?

Weflow Forecasting & Analytics is a Salesforce-native module with three distinct forecasting methods: bottom-up submissions (deal-by-deal or aggregate), dynamic-weighted forecasting, and an AI prediction corridor. The AI prediction corridor factors in historic opportunity snapshots, seasonality, and deal signals including engagement score, multi-threading depth, time-in-stage, close date push count, and amount changes.

Forecast calls roll up automatically across your Salesforce role hierarchy, so managers and leaders see aggregated numbers without spreadsheet consolidation. Admins configure submission cadences with defined time periods, frequency, overwrite logic, and permissions. Automatic email reminders prompt reps to submit on schedule. Weflow tracks week-on-week and month-on-month changes to every forecast call and manager adjustment, then compares forecasted vs. actual outcomes to measure accuracy over time.

You can run multiple independent forecasts, each mapped to different Salesforce currency or number fields, with its own cadence and roll-up logic. Common configurations include new logo, expansion, and renewal forecasts. Quotas are set at org, team, and individual levels, with annual entry, auto-monthly distribution, and per-month overrides for ramp schedules. Coverage ratios update in real time.

Pre-built analytics views give you pipeline visibility without building reports from scratch:

• Waterfall: tracks start pipeline through new opportunities, amount changes, moved in/out, won/lost, to end pipeline
• Pacing: pipeline development over time against monthly, quarterly, and annual goals
• Pipeline Coverage and Pipeline Generation tracking
• Team Benchmarks and Deals at Risk

From any forecast view, you can drill into the underlying deals, each surfacing 50+ signals, activity insights, and contact insights. Setup takes minutes using standard or custom Salesforce forecast categories. Weflow stores field changes automatically without requiring Salesforce field history tracking to be enabled.

Does Weflow track slippage and forecast adjustments week over week?

Yes. Weflow tracks both forecast adjustments and deal slippage on a weekly or monthly cadence, depending on your configuration. Every forecast call and manager adjustment is stored as a snapshot, with full track change history showing exactly when a number changed, who changed it, and by how much. This eliminates the "he said / she said" dynamic that derails most forecast reviews.

The Forecast Trending view gives you a historical timeline of how forecasts evolved across the quarter, comparing what was forecast at week 1 vs. week 4 vs. week 8. It also surfaces systematic over- or under-forecasting patterns by rep, team, or segment, so you can calibrate future calls based on actual behavior.

For slippage, Weflow captures opportunity snapshots at regular intervals and runs pipeline change analytics across them. The Waterfall view breaks your pipeline into specific categories:

• Start pipeline and end pipeline totals
• New opportunities added to the period
• Amount increases and decreases on existing deals
• Deals moved in or out of the period (pushed close dates)
• Won and lost outcomes

You can drill into any change and inspect the specific deals driving it. Weflow also tracks deal-level signals like how many times a close date was pushed and when amounts changed.

Unlike Salesforce's native forecasting tool, Weflow supports week-over-week change tracking and pipeline development analytics in a single view. IDnow, for example, reduced deal slippage by 24% after adopting Weflow.

Are Weflow features like call scoring, coaching, and pipeline health analysis automated or manual?

All three are automated by default, with optional manual review where it matters.

Call scoring and coaching: After each meeting, Weflow's AI notetaker records, transcribes, and summarizes the conversation, then auto-generates coaching feedback using pre-built methodology templates covering MEDDIC, MEDDPICC, Challenger, and others. Each call receives an AI-generated rating based on customizable templates. Managers can review and adjust those ratings in the Coaching tab, and Scorecard Insights lets you track ratings across reps, scorecards, and time periods.

AI field updates push methodology fields like MEDDPICC and BANT directly to Opportunity, Account, Contact, and Lead objects in Salesforce without manual entry.

Deal health analysis: Weflow's AI Deal Scoring auto-calculates a Deal Health Score from 0 to 100 by analyzing stage duration, activity frequency, field completeness, and historical comparisons. It generates 50+ deal signals automatically, including Engagement Score (0 to 100), multi-threading counts, time-in-stage, close date changes, and inactivity flags.

Specific risk alerts surface without any manual setup:

• No activity in 14 days
• Close date pushed 3+ times
• Missing key fields for the current stage
• Single-threaded: only one contact engaged

Pipeline analytics: Pre-built dashboards for Waterfall, Pipeline Pacing, Coverage, Generation, Team Benchmarks, and Deals at Risk compute automatically from Salesforce data plus Weflow signals. Weflow creates opportunity snapshots automatically to track pipeline changes over time, replacing manual spreadsheet work.

Admins can configure warning conditions tied to any combination of Salesforce fields, activity data, and Weflow signals. Those warnings surface automatically in pipeline views and can trigger email alerts. The core intelligence runs without manual effort, but you keep full control over thresholds and review workflows.

Does Weflow support MEDDIC tracking and compliance monitoring?

Yes. Weflow supports MEDDIC, MEDDPICC, SPICED, BANT, Challenger, and SPIN across three product layers: Conversation Intelligence, Deal Intelligence, and Salesforce field automation.

On the conversation side, Weflow includes 250–350+ pre-built prompts aligned to each methodology. After every recorded meeting, AI summaries are generated using configurable MEDDIC templates, and AI field updates extract structured data from transcripts to populate your MEDDIC fields on any standard or custom Salesforce object. You can assign different summary and field update templates per team.

Field updates support the following field types:

• Text
• Picklist and multi-picklist
• Currency
• Date
• Number
• Boolean

Updates can run automatically in the background or in a manual confirmation mode where reps review suggestions before pushing to Salesforce.

For coaching, Weflow provides structured scorecards with per-section ratings and an overall meeting score, tracked over time in a dedicated Insights view. Coaching templates can be conditionally applied based on opportunity stage or other Salesforce field values, so discovery calls get different MEDDIC coaching than late-stage negotiation calls.

In Deal Intelligence, a MEDDIC panel inside the deal inspection view lets you track fields like Metrics, Economic Buyer, Decision Criteria, and Decision Process. Configurable deal warnings use a condition builder to flag compliance gaps, such as missing MEDDIC fields at specific stages.

Weflow also publishes a dedicated MEDDIC implementation guide covering Salesforce custom field setup, note templates with correlated Salesforce fields, panel templates for the Opportunity object, and pipeline view templates. The Weflow team uses MEDDIC internally and offers hands-on help setting it up in your org.

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.

Can Weflow capture emails from both Outlook and Gmail simultaneously?

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 replace Salesforce Einstein Activity Capture completely?

Yes. Weflow is designed to fully replace Einstein Activity Capture. You should turn off EAC when adopting Weflow to avoid duplicate activities.

The core difference is architectural. EAC streams activity data into Salesforce but does not store it as queryable records, so you can't use that data in Salesforce reports, dashboards, or Flows. Weflow writes permanently to native Salesforce objects (Task, Event, EmailMessage), making every captured email and meeting immediately available for reporting, automations, and downstream Flows.

Unlike EAC, Weflow gives RevOps and Business Systems teams capabilities that go beyond basic activity sync:

• Activity logging to Custom Objects and Cases
• Auto contact creation with Opportunity Contact Role assignment
• Multiple contact relations per email or event
• Email open tracking with Salesforce fields for last open date and open count
• Historical backfill from Google Workspace or Microsoft 365 going back up to 24 months
• Advanced mapping with manual override controls via Gmail and Outlook extensions
• Custom exclusion rules and per-team configurations

Unlike EAC, Weflow lets you build Flows that trigger on captured activity data, such as populating a last activity date field, counting touchpoints on an Account, or alerting when an account goes inactive. If you stop using Weflow, all data stays in your Salesforce org with no lock-in.

EAC is included with certain Salesforce editions at no extra cost and may work if you have no reporting or automation needs. If your CRO or RevOps team needs activity data they can query and act on, Weflow is the more practical choice.

Review the full comparison of Weflow and Salesforce Einstein Activity Capture.

Can Weflow handle multiple Salesforce production instances?

Does Weflow work with both Salesforce Lightning and Classic?

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.