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.