---
template: "marketing.peb"
title: "Product - Salesforce Context Builder"
displayName: "Salesforce Context Builder"
description: "Assemble account, opportunity, quote, product, and supporting Salesforce context before generating sales documents."
category: "product"
contentType: "overview"
audience: "end-user"
tags: "product,data-context,builder,crm,salesforce,sales-documents"
section: "product"
seoTitle: "Salesforce Context Builder for Sales Documents"
seoDescription: "Collect the Salesforce account, opportunity, quote, product, and supporting context needed to generate reliable sales documents."
---

## Salesforce Context Builder

Salesforce Context Builder defines what record data should be gathered before a sales document is drafted.
It gives document workflows the account, contact, opportunity, quote, product, activity, and supporting context
needed to create useful output.

<!--
DCD tab and record.
Diagram similar to Jostens parallel retrieval.
Quote Approval Agent response: given the past history of this client, their usage patterns indicate xxx

-->

## Core capabilities

- Pull related Salesforce records into a single document workflow context.
- Define required and optional fields for each proposal, quote explainer, SOW, or account summary workflow.
- Identify missing inputs before generation so reps can fill the gaps.
- Reuse context definitions across similar sales document workflows.
- Extend context with approved external sources only when the workflow requires it.

## Typical outcomes

- Better drafts because the workflow starts with the right Salesforce context.
- Less manual data gathering before proposal, SOW, quote, or handoff creation.
- More consistent document output across reps and territories.
- Clearer separation between trusted CRM fields, user-provided inputs, and optional external context.

## Operational model

- Context definitions specify which objects, relationships, and fields are needed for each document type.
- Retrieval runs under Salesforce permissions and workflow-specific controls.
- Missing or low-confidence values can be flagged for human input instead of silently appearing in a customer document.

## Related capabilities

- [Document & Content Processing](/product/document-content-processing.html)
- [Knowledge and Retrieval](/product/knowledge-retrieval.html)
- [Orchestration and Workflows](/product/orchestration-workflows.html)
