🧭 Table of Contents

• Overview
• Logic at a glance
• Decision flow (incoming vs outgoing)
• User mapping requirements
• Verify the behavior (steps)
• Edge notes & clarifications
• FAQs
• Related articles

🧠 Overview

The integration automates deal and activity tracking based on phone calls, so your team has a complete view of deal progress without manual data entry.

🔝 Back to top ⬆️

🧩 Logic at a glance

🔝 Back to top ⬆️

🧬 Decision flow (incoming vs outgoing)

Incoming call → Open deal exists?
• Yes → Log as activity under that deal.
• No → Create new deal → Log call as first activity.

Outgoing call (made via MyOperator) → Open deal found?
• Yes → Log as activity under the existing open deal.
• No → Not specified in this document. (See FAQs for guidance.)

🔝 Back to top ⬆️

👥 User mapping requirements

• Matching email IDs in both Pipedrive and MyOperator are required for correct user-to-deal linkage.
• If users are added or updated in either system, raise a sync request to MyOperator tech support to keep mappings accurate.
  

🔝 Back to top ⬆️

🧪 Verify the behavior (steps)

1. Test incoming with open deal: Call from a number tied to a contact that already has an open deal in Pipedrive → Expect: call activity under that deal.
2. Test incoming with no open deal: Call from a number with no open deal → Expect: new deal created + call logged as first activity.
3. Test outgoing: Place an outgoing call via MyOperator to a contact with an open deal → Expect: call activity under that open deal.
4. If results differ: Confirm matching email IDs for the user(s) and, if recently changed, request a user sync with tech support.

✅ Goal: “Every call interaction is captured,” giving a complete view of deal progress. Use the checks above to confirm.

🔝 Back to top ⬆️

🧯 Edge notes & clarifications

• Outgoing when no open deal: The behavior is not specified in this PDF; outcomes may depend on your organization’s process or settings.
• User changes: After adding/updating users in either system, email matching must remain identical and a sync request should be raised to tech support to ensure correct linking.
  

🔝 Back to top ⬆️

❓ FAQs

Q1. What happens on an incoming call if the contact doesn’t have an open deal?
A. A new deal is automatically created, and the call is logged as the first activity.

Q2. How are outgoing calls logged?
A. For outgoing calls made via MyOperator, the call is logged as an activity under the existing open deal (if found).

Q3. Why are matching emails required?
A. The integration relies on matching email IDs across Pipedrive and MyOperator for accurate user mapping.

Q4. We added/updated users and logs look wrong—what now?
A. Raise a sync request to MyOperator tech support so user mappings are refreshed.

Q5. Does the integration capture every call?
A. The PDF states the integration ensures every call interaction is captured, enabling a complete view of deal progress.

🔝 Back to top ⬆️

🔗 Related articles

• Requirements for Pipedrive ↔ MyOperator integration (plan, token, service number, emails, sync) — Guru card.
• Missed OBD call behavior (retries, re-queue, windows) — useful for sales ops workflows — Guru card.
  

🔝 Back to top ⬆️

🏷️ Keywords

Pipedrive integration logic, MyOperator call logging, incoming call new deal, outgoing call activity, open deal mapping, first activity, matching email IDs, user sync request, sales activity automation, complete view of deal progress