Keep your Deal Room content current automatically after every call. When you have a Gong call with a buyer, Spekit reviews the content in that buyer's Deal Room and flags anything the conversation made out of date, then offers you a one-click suggestion to accept or reject. There is nothing to trigger manually, and nothing changes until you approve it. This guide covers how it works, what you need, how to review suggestions, and what is in scope.
ℹ️ How it fits together: Dynamic Deal Content connects three things you may already use. A Gong call is linked to a buyer through the Salesforce opportunity tied to the Deal Room, and Spekit uses the call to keep that Deal Room's content current. If any one of those links is missing, suggestions will not appear (see requirements below).
1. What it does
Deal Room content is accurate the day a rep builds it, and drifts with every call after. A stakeholder changes, pricing shifts, a timeline moves. Dynamic Deal Content keeps that content current at the individual deal level: after a call, Spekit finds the facts the conversation made stale, flags the affected content, and offers a suggested update, with you in control of every change.
| What you get | Detail |
|---|---|
| Automatic detection | Tied to a real Gong call, not a generic AI rewrite. A background pass runs on its own, with no button to press. |
| Side-by-side review | The current content and the suggested patch appear together, with the call detail shown as the reason for the change. |
| You stay in control | Every suggestion is a proposal you accept or reject. Nothing changes until you approve it. |
| Deal-scoped edits | Accepted edits land on that Deal Room's own copy, so your team's master template is never touched. |
2. What you need
⚠️ Requires Gong and Salesforce Revenue Insights. To use Dynamic Deal Content, your account must be connected to both Gong and Salesforce CRM Revenue Insights, and the Deal Room must be associated with a Salesforce Account or Opportunity. If you have Gong and Deal Rooms but not Revenue Insights, or the Deal Room is not linked to an opportunity, suggestions will not appear.
| Requirement | Why |
|---|---|
| Gong connected | The call insights come from Gong. See Setting up the Gong Integration. |
| Salesforce Revenue Insights connected | Links the call to the right account and opportunity. See Setting up Salesforce for Revenue Insights. |
| Deal Room linked to an opportunity | This is what connects the call to the Deal Room. See Connect a Deal Room to a Salesforce Opportunity. |
| Deal Room has content | Suggestions only run when the Deal Room already holds at least one eligible Spek. |
3. How it works
You do not start this. It runs on its own after a qualifying call.
- A call happens. A Gong call moves the deal: 80 licenses becomes 150, a new stakeholder appears, a date slips, a discount gets floated.
- Spekit checks the room. Because the call is linked to the Deal Room through the shared Salesforce opportunity, a background pass compares the call's summary and key points against the existing Speks.
- You are notified. Both the deal owner and collaborators get an email notification, and a banner appears in the Deal Room, for example "New suggestions from your call, 4 suggested updates across 2 items."
- Affected items are flagged. In the Deal Room content list, each Spek with suggestions shows a small count badge.
4. How to review suggestions
Open a flagged Spek to review its suggestions.
- Open the flagged content, or click Review suggested updates from the banner.
- In the AI Content Builder panel, each suggested change appears as its own card with a before-and-after view: the current text and the proposed replacement, with the call detail shown as the reason.
- For each card, accept or reject the change. Read the reason before you accept, since you should only accept content you agree with.
- You can Accept all to take every suggestion on that Spek at once.
- Click Save after reviewing each Spek. Accepted edits update the Deal Room's copy on the spot.
ℹ️ What if I do nothing? Nothing changes. The flag simply stays until you accept or reject it. It does not clear itself.
💡 Pro tip: If the banner count and the panel count ever disagree, trust the panel count. It reflects exactly what is ready to review on that Spek.
5. Manage your suggestion notifications
By default, Spekit notifies you when a call surfaces suggested updates, by both email and in-app. These are personal settings that do not affect other collaborators, and you can turn them off.
- Open the Deal Room and click Deal Room settings (the gear icon).
- Go to the Notifications tab.
- Find Suggested content updates ("A call surfaces updates to content in this Deal Room").
- Toggle Email and In-app on or off, then click Save changes.
💡 Pro tip: Leave at least one notification on. The suggestion flag does not clear itself, so a notification is what tells you a call created updates worth reviewing before your next buyer touchpoint.
6. What is in scope
Dynamic Deal Content currently works on a specific set of content. Knowing the scope prevents surprises about where suggestions do and do not appear.
| In scope | Not in scope (for now) |
|---|---|
| Deal Room-native Speks: customized copies of Source Speks, or Speks you create in the Deal Room | Files such as Google Slides, PowerPoint, Google Docs, and PDFs |
| Replace and append edits | Free-form editing before you accept |
| Binary accept or reject | Source Speks that live only in Topics |
ℹ️ Only Speks in the Deal Room get suggestions. Suggestions run on Speks that live in the Deal Room: ones you created there, or customizable copies of Source Speks you added to the room. They do not trigger on a Source Spek that lives only in a Topic, so to get suggestions on that content, add a customizable copy of it into your Deal Room. Suggestions never touch your team's master template, only the Deal Room's own copy.
7. Best practices
| Best practice | Why it matters |
|---|---|
| Check your Deal Rooms after every call | Make it a post-call habit. Any time a Gong call logs against a deal that has a Deal Room, check for suggestions before your next buyer touchpoint. The flag does not clear itself. |
| Read the reason before you accept | Every suggestion shows the call detail that triggered it. Read that line first, and accept only if the change is right. Remember to click Save after reviewing each Spek. |
| Report what misses | If a suggestion overwrites a manual edit you made on purpose, or gets the call wrong, reject or dismiss it. That feedback improves the suggestions over time. |
| Use customizable copies in your Deal Room | Suggestions only run on Deal Room-native Speks. Add a customizable copy rather than relying on a Source Spek from a Topic. |
8. Example use cases
Mutual action plan timeline slip. A rep builds a mutual action plan with the buyer's milestones and dates. The security review runs three weeks long, the buyer says so on a call, and go-live moves. Spekit flags every Spek referencing the old date, shows the new one beside it, and cites the call as the reason. The buyer never catches a dead date in a doc you sent them.
Executive summary, new economic buyer. A rep writes an exec summary around the champion's business case. Two calls later the champion moves teams and a VP of Ops shows up with different priorities. Spekit flags the stakeholder and success-criteria lines with the suggested patch, so you are not forwarding a summary that quotes someone who left the account.
A presentation built as a Spek. A rep builds the deck as a Spek and presents it in buyer meetings. As priorities and timelines change across calls, Spekit flags the affected sections so the rep updates the deck before the next conversation, instead of manually reworking a slide file after every call.