Supporting Documents & Deal Context

A great RFP answer shouldn’t just be factually correct - it should sound like it was written for the specific buyer, in the specific deal. SiftHub doesn't just generate answers using your knowledge sources. It can also read additional context to shape how those answers are written, and to bring specifics about this deal into them.

This context comes from two places, Supporting Documents and Connected Sources, and both are available only within Projects. Supporting Documents is on by default. Deal Context is off until you turn it on.

Where this is available

Supporting Documents and Deal Context are Project-only features. They are not available in standalone autofill. If you open Autofill Settings outside of a Project, you’ll be prompted to create a Project first.

Supporting Documents

Any files that you attach in the Project's "Supporting Documents" will be considered as context when autofilling. This setting is on by default for every Primary document in a Project.

What they contain: anything that helps SiftHub understand who the buyer is, how your company should sound, or what’s expected in the response. Common examples:

• Your brand and tone guidelines
• The prospect’s submission instructions
• A discovery brief or deal summary
• The buyer’s “About Us” page or company background
• Industry or compliance context the prospect has shared
• Call transcripts and deal notes

How to add them: attach in the Project creation form, or add later from the Project Documents tab.

Transactions: each Supporting Document consumes 3 additional transactions to process that are over and above the autofill transactions per answer.

Refresh: context updates automatically whenever a Supporting Document is added or removed from the Project.

Deal Context from Connected Sources

Deal Context is pulled automatically from your connected CRM and call recording tools, so you don't attach anything manually. It is off by default, so turn it on for a deal that is already well documented in your CRM or your call recordings.

Requirement: at least one of CRM or call recording must be connected. If neither is connected, the Deal Context toggle is disabled, and you’ll be guided to connect a CRM.

How matching works: enter the Account and Deal name in the Project form. SiftHub uses this to search your connected sources for a matching record.

• If a confident match is found, that record’s context (deal stage, stakeholders, call transcripts, objections raised, and similar signals) is used to shape your answers.
• If no confident match is found, Deal Context is silently skipped — no error is shown, and your autofill run proceeds normally without it.

Transactions: Deal Context can consume up to 50 transactions per use, depending on the complexity of the deal and the number of connected sources and calls considered.

How Supporting Documents and Deal Context Are Used

Supporting Documents are context, not a source. They shape the framing, tone, and emphasis of an answer. SiftHub does not cite them, and does not pull facts or figures from them. Factual content still comes from your connected knowledge sources. Supporting Documents only influence how that content is written and what it emphasizes.

Deal Context goes further. When Deal Context is turned on, SiftHub can use facts about the deal directly in the answer, not just to set the tone. Those facts can come from a matching deal record (such as a CRM opportunity or call transcript) and from the Supporting Documents attached to the project.

Examples: How Context Shapes an Answer

The examples below show the same question answered with and without context, so you can see exactly what changes.

Example 1 — Deal Context

Question: “What integrations does your platform support?”

Without context: SiftHub integrates with a broad range of tools across your workflow. Supported integrations include Salesforce, HubSpot, Google Drive, SharePoint, Slack, Microsoft Teams, Jira, and Zendesk. We are continuously expanding our integration library.

With context: SiftHub’s Salesforce integration offers full two-way sync — automatically pushing completed RFP data into your CRM and pulling deal context to personalise answers. We also integrate with Google Drive, SharePoint, and Slack.

What shaped it: a discovery call where the prospect said, “Our whole team lives in Salesforce — two-way CRM sync is non-negotiable for us.” SiftHub picked this up from the connected call recording and led with the integration that matters most to this buyer.

Example 2 — Brand Guidelines

Question: “How do you ensure data security?”

Without context: At SiftHub, we are deeply committed to ensuring the highest standards of data security. Our robust platform employs industry-leading encryption and access controls. Our dedicated security team works tirelessly to safeguard your information at all times.

With context: SOC 2 Type II certified. ISO 27001 compliant. Data encrypted at rest (AES-256) and in transit (TLS 1.3). Access controls: RBAC, SSO, and MFA. Audit logs available on request.

What shaped it: the brand guidelines document attached to the project stated, “Remove filler phrases. No ‘deeply committed’ or ‘robust security.’ State certifications and facts directly.” SiftHub applied that tone rule across the answer.

Example 3 — Prospect Details

Question: "How do you ensure our data remains private?"

Without context: No, SiftHub does not use customer data to train or fine-tune models. Content is retrieved at query time, used to generate the response, and remains inside the customer tenancy.

With context: No, SiftHub does not use customer data to train or fine-tune models. There is no mixing of customer content across tenants, and all content remains isolated within your tenancy. Content is retrieved at query time and used solely to generate your response.

What shaped it: The prospect's security requirements document, attached as a Supporting Document, stated, "Vendor must guarantee strict data isolation between customers with no cross-tenant data leakage." SiftHub surfaced the tenant isolation and no cross-tenant mixing guarantee to directly address the prospect's primary concern, rather than stopping at the standard no-training statement.

Supported Document Types

Supporting Documents support the following file types:

• PDFs
• Word documents (.docx)
• Spreadsheets (.xlsx, .csv)

Support for Google Drive / SharePoint file links is coming soon.

Turning Supporting Documents and Deal Context On or Off

Supporting Documents is on by default, while Deal Context is off by default. Both are available as toggles in Autofill Settings within a Project. The toggles are set per primary document, from Settings on that document.

Proposal documents are the exception. SiftHub writes a proposal from the project's supporting documents, so that context is always used and cannot be turned off for a proposal.

Turning a toggle off excludes that context type from all subsequent autofill runs for that document until it's turned back on.