---
template: "page.peb"
title: "Using Salesforce CPQ Context in Sales Document Workflows"
displayName: "Using Salesforce CPQ Context in Sales Document Workflows"
description: "How Salesforce CPQ context can support proposal, quote explainer, and sales document generation without replacing CPQ."
category: "resources"
contentType: "article"
audience: "end-user"
tags: "articles,salesforce-cpq,sales-documents,quote-explainers"
section: "resources"
seoTitle: "Using Salesforce CPQ Context in Sales Document Workflows"
seoDescription: "Use Salesforce CPQ context to support proposal, quote explainer, and sales document generation without replacing CPQ."
---

# Using Salesforce CPQ Context in Sales Document Workflows

Salesforce CPQ data can provide useful source context for customer-ready sales documents. iDialogue should be
positioned around the document workflow that happens around quoting: proposals, quote explainers, SOW drafts,
and sales packets.

This article is intentionally scoped. iDialogue should not be positioned as a quote system, pricing engine,
billing system, tax system, invoicing system, ERP, legal review system, or revenue recognition system.

## Practical options

1. Keep using Salesforce CPQ as the system that owns quote structure, pricing rules, approvals, and commercial
   calculation.
2. Use iDialogue to help explain quote context, generate customer-ready supporting documents, and package
   reviewed output for sharing.
3. If a team is simplifying its CPQ footprint, use iDialogue only for the document and review workflow around the
   Salesforce data model that remains.

## Good document use cases

- Quote explainer drafts.
- Proposal drafts grounded in Opportunity, Quote, and Product context.
- SOW draft starters for review.
- Customer-ready sales packets that summarize approved commercial context.

## Related pages

- [Guided Quote Support](/solutions/guided-quote-assistance/index.html)
- [Proposals and Sales Documents](/solutions/proposals-sales-documents/index.html)
- [AI Document Generation](/product/document-content-processing.html)