Integrations / Salesforce
Explain what the opportunity record can't.
Your Salesforce opportunity says Proposal, closing at month end. Dealscale reads that context and sets it beside what buyers actually said, so the team can see whether the record and the evidence agree.
Book a demo (opens in a new tab)
What Dealscale reads
Opportunity context such as stage, close date, amount, owner and related contacts. The connection is read-only — Dealscale doesn't write back to Salesforce.
The workflow
- Opportunity context comes in from Salesforce.
- Conversation evidence from recordings and transcripts is linked to the same opportunity.
- Reasoning highlights where they disagree — for example, a close date that hasn't moved while a finance approval is still only reported.
- Your team decides what to update in Salesforce and what to ask the buyer next.
Worked example (fictional)
| Salesforce shows | Conversations show | What it means |
|---|---|---|
| Stage: Proposal | Champion says finance is “fine” | Finance approval is reported, not confirmed |
| Close: end of month | Legal reviewer not yet named | Contract timeline is unresolved |
| Primary contact: champion | IT joined the last call | The buying group is larger than the record |
Who it helps
- Sales managers preparing forecast reviews
- Account executives planning the next conversation
- RevOps reconciling record and reality
Evaluation criteria
- Is the CRM connection read-only, or does it write?
- Does each insight link to its source?
- Are confirmed, inferred and unresolved distinguished?
Mapping and freshness in your Salesforce environment
Bring an opportunity with your actual stage labels, custom fields and buying-group structure to the walkthrough. Confirm which source records and related contacts are available in the proposed configuration, how they map to one opportunity and what happens when records are missing, duplicated or changed. Ask when context was last refreshed and whether an earlier field value remains inspectable beside newer conversation evidence. Do not assume every organization's custom mapping is identical.
- Record
Proposal; close date at month end
Stage-to-category mapping describes the CRM configuration. - Conversation
Champion reports finance support
Keep the report distinct from finance confirmation. - Dependency
Security waits for completed documentation
Seller delivery does not prove buyer acceptance. - Review
Manager decides category and next conversation
Evidence explains the judgment; it does not automate it.
Source ownership and local edits
Salesforce remains the source of record for imported opportunity fields. A manual edit to a Salesforce-mapped field in Dealscale can be overwritten by the next Salesforce refresh. Make durable corrections in Salesforce, then verify that the refreshed context reflects them. A local edit is not a Salesforce update. Keep buyer evidence and its source separate from the imported stage, amount and close date, so a refresh does not turn a reported approval into a completed one.
| Field or context | Ownership decision | Pilot check |
|---|---|---|
| Stage and forecast category | Use your actual Salesforce labels and mappings | Compare one mapped record with the source; do not treat a category as buyer approval |
| Amount, currency and close date | Salesforce is authoritative for imported fields | Change a permitted source field, refresh and reconcile currency, date and value |
| Owner and related contacts | Verify opportunity association and permitted access | Test a reassignment and a similarly named contact on another opportunity |
| Manual edit to a mapped field | Temporary local value; refresh may replace it | Record a local edit, refresh, and confirm the source value wins |
| Conversation claim | Attributed to speaker, date and source | Keep a finance report distinct from a direct budget decision |
Agree the implementation contract before importing context
RevOps and the opportunity owner should agree a short field dictionary: source object and field, business meaning, destination display, currency, time zone, blank-value behavior and responsible correction owner. Include only fields needed for the review. Compare an actual permitted opportunity with its linked conversation before expanding the sample. A wrong association can make fluent reasoning misleading even when each individual source is accurate.
Check source timestamps separately: when a buyer made a statement, when Salesforce changed, and when the imported context was refreshed are different moments. Ask the team to demonstrate available freshness information rather than assuming a refresh interval. When a source is inaccessible, identify the missing context and withhold conclusions that depend on it. Test with the roles your pilot will use; a demonstration by an administrator does not establish ordinary-user access.
Security and access questions for your review
- Which records can each role access, and how is that access enforced?
- What data is retained, where, for how long and how can it be deleted?
- Which connections read context, and which actions could change a system?
- What recording consent and data-handling documentation can our reviewers inspect?
- What happens when a connection is revoked or a source is unavailable?
A 30-day pilot decision
- Days 1–5: agree consented opportunities, permitted sources, mappings and two accountable reviewers. Record the current preparation workflow; this is a pilot design, not a measured baseline.
- Days 6–15: inspect source attribution, reported-versus-confirmed approvals and waiting dependencies on the same opportunities.
- Days 16–25: introduce a known scope change and a contradictory conversation. Check freshness and whether proposed next actions retain uncertainty.
- Days 26–30: review unsupported claims, editing effort and useful confirmations. Decide whether the workflow meets your criteria with IT and revenue leaders; do not extrapolate a guaranteed revenue outcome.
Salesforce documents stage-to-forecast-category mappings. Your own configuration matters. A mapped category is not independent buyer approval evidence; use the forecasting with buyer evidence guide alongside it.