How to Capture Outreach Dialer Calls and Meeting Recordings Together in Weflow

You can keep Outreach for sequencing and dialing while bringing its recorded outbound calls into the same Weflow coaching workflow as scheduled meetings. Weflow imports the recording Outreach creates after the call. It doesn’t place or live-record the Outreach call.

The practical test is to follow one phone call and one video meeting through that workflow. You should see usable coaching feedback and the intended Salesforce updates, without adding another upload task for reps or inflating activity counts.

Weflow is the Revenue AI Orchestration platform for sales, customer success, and RevOps teams. Built for Salesforce teams, Weflow Conversation Intelligence processes Outreach recordings alongside meetings from Zoom, Google Meet, Microsoft Teams, and WebEx.

What do you need before connecting Outreach to Weflow?

Start with a small test using your existing meeting-recording workflow and an Outreach account that creates outbound call recordings. You’re testing the coaching process and Salesforce outputs, not just whether audio arrives.

• Weflow access: Sign in through your Salesforce account and have Weflow Conversation Intelligence available for the test.
• Source recordings: Use an Outreach-recorded outbound conversation and a recorded video meeting with a comparable purpose, such as discovery.
• Approved recording policy: Cover outbound recording and subsequent analysis under your company’s consent and privacy procedures. Importing audio doesn’t replace those procedures.
• Salesforce destinations: Identify the contacts, accounts, opportunities, and fields you expect the test conversations to update.
• Configuration ownership: Name the person who maintains scorecards, prompts, and field mappings. The manager owns whether the coaching output is useful; your RevOps or Salesforce admin owns the configuration.

Choose conversations where the rep had a fair opportunity to demonstrate the skill you want to coach. Comparing a brief appointment-setting call with a full discovery meeting tells you more about the conversation length than the rep.

1. Set Salesforce logging ownership before connecting Outreach

Give each activity source one designated Salesforce writer before you add conversation analysis. A second recording system shouldn’t turn one customer interaction into two reported activities.

We separate three things here: the source recording, the Salesforce activity, and the structured information extracted from the conversation. They serve different purposes and need separate checks.

Assign one Salesforce activity writer per conversation source

Keep Outreach responsible for the outbound activities your team already logs through Outreach. Assign inbox and calendar capture separately, then let Weflow process the recordings and generate the configured outputs.

For a team using both Weflow Conversation Intelligence and Weflow Activity & Contact Capture, the ownership plan can look like this:

This table defines the intended result. Use the actual Salesforce records to judge whether your running configuration produces it.

A Weflow recording record isn’t a duplicate meeting activity. For scheduled meetings, Salesforce stores the Event and the recording as separate records. Your activity report should count the meeting, not count the recording as another meeting.

Exclude Outreach-tracked emails from Weflow Activity and Contact Capture

If you also use Weflow Activity & Contact Capture, compatibility mode identifies Outreach-tracked emails through tracking links in the message body. A branded tracking domain needs its own exclusion pattern.

1. Find the custom tracking domain in Outreach’s admin configuration.
2. Add that domain to the exclusion patterns in your Weflow capture configuration. For example, a team using track.example.com needs an exclusion that recognizes that domain.
3. Send an Outreach email containing a tracked link, then inspect the resulting Salesforce activity.
4. Send a separate one-off email from the rep’s inbox. Make sure your exclusion hasn’t removed the inbox activity you wanted Weflow to capture.

Weflow’s Outreach tracking-domain exclusions prevent overlapping email logging. They aren’t a universal deduplication rule for calls and meetings, so test those sources separately.

2. Connect Outreach through Weflow’s Setup and Integrations

Connect your Outreach account from Weflow’s Setup and Integrations page. Once connected, Weflow pulls Outreach calls into its recording workflow for transcription, summaries, and coaching.

1. Open Setup and Integrations in Weflow.
2. Find the Outreach integration and connect your Outreach account.
3. Make an approved outbound test call through that account, with Outreach recording the conversation.
4. Open the imported call in Weflow to inspect the result.

Use the account that will place the test call. Connecting your own Outreach account and testing a colleague’s call would introduce another variable before you’ve established the basic workflow.

Reps continue dialing in Outreach. Weflow imports the resulting recordings without a separate upload step for each call.

3. Check an Outreach recording alongside a video meeting

An imported Outreach recording contains the called person’s name, audio, speaker separation, a transcript, a summary, and coaching output. It arrives as an outbound call and contains no video.

Open your Outreach discovery call and a Zoom discovery meeting in Weflow’s Recordings library. Keep this pair for the coaching and Salesforce tests that follow.

1. Identify each conversation. Match the Outreach entry to the person called. Match the Zoom recording to the scheduled meeting and participants.
2. Play a section you recognize. Listen for both sides of the conversation and compare the audio with the transcript.
3. Inspect speaker separation. Make sure the transcript distinguishes the rep’s statements from the customer’s answers.
4. Read the summary against the conversation. Look for the customer’s stated problem and agreed next steps, rather than accepting plausible wording.

Weflow processes Outreach calls through the same recording workflow used for AI summaries, field updates, scorecards, search, and Ask Weflow AI. That gives you a shared review process without changing where reps make their calls.

4. Review Outreach calls and meetings with Weflow scorecards

Use the same coaching criteria for phone and video conversations with a comparable purpose. Weflow scorecards provide configurable ratings and feedback, so you can review the behavior rather than treating the channel as a proxy for quality.

1. Inspect scorecard applicability. Review which scorecard and conditions apply to each test recording, including any deal-stage conditions.
2. Compare the same dimension. Start with customer qualification or objection handling instead of comparing only the overall scores.
3. Read the evidence. Use the transcript and relevant audio to understand the feedback. A score tells you where to look; the conversation explains what happened.
4. Choose one behavior to coach. Give the rep a specific action to practice on the next comparable call.

For example, focus both discovery reviews on decision process:

That’s a useful coaching theme across channels: the rep uncovers a need but leaves the approval path incomplete. Keep the feedback at that level.

Weflow supports methodology scoring at the individual-call, opportunity, and long-term rep level. Once your test passes, use the broader view to distinguish a repeated skill gap from one conversation where the topic never came up.

You can also add both recordings to one Ask Weflow AI question. Ask which decision-process questions the rep left unanswered, then review the supporting conversation before using the answer in coaching.

5. Verify Salesforce field updates before expanding Outreach coverage

Expand only after both recording types produce the intended Salesforce outputs. A transcript in Weflow doesn’t prove that the summary reached its destination or that the activity belongs to the right opportunity.

1. Record the starting state. Note the current values in your selected Salesforce fields and the existing activity count for each test conversation.
2. Review the generated content. Compare the AI output with the transcript before judging the Salesforce write.
3. Trace each output to its destination. For the Outreach call, follow the extracted next step to the intended Opportunity field. For the Zoom meeting, inspect the configured Event summary and Opportunity field separately.
4. Inspect associations independently. Open the recording’s linked records and the activity’s related record. They answer different questions.
5. Count activities again. Compare the result with your logging-ownership plan and investigate unexpected Tasks or Events.
6. Test each intended destination. Include Account and Opportunity destinations if your configuration uses both. One successful write doesn’t establish that every destination works.

For scheduled meetings, changing a recording’s links inside Weflow doesn’t move the Salesforce Event. Correct the meeting mapping through the Outlook or Chrome add-in when both records need to move.

Before you add more reps, your acceptance checklist should include:

• The configured summaries and field values reach the intended Salesforce records.
• Recording links and activity associations reflect the correct customer and deal.
• Activity counts match the agreed ownership plan.
• The manager can access the audio, transcript, and coaching results they need.
• Your admin has tested recording access with the intended user roles, including access to transcript and summary data in Salesforce.
• A named owner maintains prompts, scorecards, and field mappings.

We put this test before rollout because failed AI summary and field-update writes can’t be replayed. The content remains in the Weflow recording object, but recovering a missed Salesforce update requires someone to copy it across manually.

See how Weflow captures activity, updates Salesforce fields from calls, and rolls up your forecast. Book a 30-minute demo.

Troubleshoot Outreach imports and Salesforce writes

Find the failing stage before changing configuration: source recording, Weflow processing, or Salesforce write. A missing call and a missing opportunity update need different fixes.

Trace a missing Outreach recording

Start in Outreach and establish whether the original recording exists. Weflow can’t recover a conversation that Outreach never recorded.

1. Find the call in Outreach and open its recording.
2. Match the rep’s Outreach account to the account connected through Weflow’s Setup and Integrations page.
3. Look for the corresponding outbound recording in Weflow using the called person and call details.
4. If the source recording exists but the Weflow entry is missing, gather the details needed to trace that specific import.

For escalation, include:

• The Outreach account and rep involved.
• The call date, time, time zone, and person called.
• The source recording reference and whether its audio plays in Outreach.
• Whether other calls from the same connected account appear in Weflow.

Recover a missing Salesforce summary or field update

Recover the existing content manually, then repair the configuration for future writes. Treat those as separate jobs.

1. Open the Weflow recording object and locate the summary or extracted content.
2. Review the content and copy the missing update to the intended Salesforce destination.
3. Have your admin inspect the field mapping, integration-user access, validation rules, and relevant record types.
4. Run a fresh recorded conversation through the corrected configuration and inspect every intended write.

For meeting logging and updates, the integration user needs access to the Event and Task objects, including the fields and record types Weflow writes. If your Event object has several record types, set a default in Weflow.

In Salesforce orgs with Private organization-wide defaults, Weflow’s integration user requires Modify All Records on Account, Opportunity, and Contact. Read, Edit, and View All alone don’t provide the access needed for subsequent updates to records the user doesn’t own.

Trace duplicate Salesforce activities to their logging source

Identify the overlapping writers before changing exclusions. The record type and creation details help you distinguish a duplicate activity from a separate recording record.

Retest with a new interaction from the affected source. Use the same ownership plan to evaluate the result, then address the existing duplicate records separately.

Weflow and Outreach integration FAQ

Weflow Conversation Intelligence handles the imported recordings. Weflow Activity & Contact Capture is a separate product for email, calendar, and contact capture.

Which Weflow product do I need for Outreach recordings?

You need Weflow Conversation Intelligence for recording analysis, summaries, scorecards, and AI field updates. Weflow Activity & Contact Capture alone doesn’t include call recording.

• Weflow Conversation Intelligence: $39 per user per month, billed annually.
• Revenue AI Foundation: $49 per user per month, billed annually, combining Weflow Activity & Contact Capture with Weflow Conversation Intelligence.

Weflow’s plans have a 10-user minimum. Choose Revenue AI Foundation when you also need inbox and calendar capture alongside conversation analysis.

Do reps need to upload Outreach recordings to Weflow?

No. Once the Outreach account is connected, Weflow pulls the recordings into its processing workflow. Outreach still needs to create the source recording.

Does Weflow provide live coaching during Outreach calls?

No. Weflow provides post-call analysis, not a live assistant or real-time battlecards. You review the processed transcript, summary, scorecard, and field updates after the conversation.