Articles in this section

[Rep Guide] Update a deck with suggestions from a call

After a call with your buyer, Spekit reviews the content in that buyer's Deal Room and flags anything the conversation made out of date. That includes decks. You review each suggestion and accept or ignore it. Nothing changes until you approve it.

ℹ️ How it fits together: a call is linked to a buyer through the Salesforce opportunity tied to the Deal Room. If that link is missing, suggestions will not appear.

 

1. What you need

All 4 have to be true. If suggestions never appear on a deck, work down this list.

RequirementWhy
A connected call sourceCall insights come from your connected call intelligence integration (Gong, Teams, etc.)
Salesforce Revenue Insights connectedLinks the call to the right account and opportunity
The Deal Room linked to an opportunityThis is what connects the call to the room
The deck already in the Deal RoomSuggestions run on Deal Room content, not on a deck that lives only in a Topic

ℹ️ Decks in a Deal Room are in scope. A deck is a Spek underneath, so suggestions work on it the same way they work on any other Deal Room content. A presentation file you synced in from Google Slides or PowerPoint is not in scope, because it is a file rather than a Spek.

 

2. Find suggestions on a deck

You do not start this. It runs after a qualifying call and tells you in the room.

WhereWhat you see
The Deal RoomA banner naming the call and the number of suggested updates, with a Review button
The deck itselfAn AI insights tab in the AI Content Builder, with a count
NotificationsThe deal owner and collaborators get an email and an in-app notification

If there is nothing to review, the AI insights tab shows an empty state explaining when updates appear.

 

3. Review a suggestion

  1. Open the deck in the Deal Room and select Edit.
  2. In the AI Content Builder, go to the AI insights tab.
  3. Each change is its own card. It shows the old text struck through in red and the new text underlined in green.
  4. Read the reasoning line. It names what was said on the call that triggered the change.
  5. Select Accept or Ignore on each card. Accept all takes every suggestion at once.
  6. Save.

💡 Pro Tip: read the reasoning before you accept. The suggestion is only as right as the call it came from, and you are the one who knows what the buyer actually meant.

 

4. Suggestions on locked slides

This is specific to decks. A slide pulled from your team library is locked and read-only in your deck, so you cannot apply a change to it in place.

What you wantWhat to do
The change is just for this dealSelect Make editable on the slide, then apply the change. This breaks the link to the library version
The change is true for everyoneLeave the slide locked. Ask the content owner to update the library version, which updates every deck using it

ℹ️ Think before you unlock. A slide you make editable stops receiving updates from the source. For a pricing or positioning change that affects the whole team, fixing the source is the better move.

 

5. Use cases

These are the moments a stale slide costs you something.

SituationWhat the suggestion does
The timeline slips on a callFlags the slide with the old date so the buyer never opens a deck with a dead date in it
A new decision maker appearsFlags the stakeholder slide, so your next deck does not quote someone who left
Pricing or seat counts changeFlags the old figures with the new ones beside them, with the call as the reason
The buyer raises a new priorityFlags the sections your deck should now speak to before the next meeting

 

6. Best practices

These 4 habits keep this useful rather than noisy.

Best practiceWhy it matters
Check the room after every callThe flag does not clear itself
Read the reasoning before acceptingAccept only if the change is actually right for this deal
Fix shared problems at the sourceA locked slide that is wrong for everyone should be fixed in the library
Ignore anything that overwrites a deliberate editThat feedback improves suggestions over time

 

Was this article helpful?
0 out of 0 found this helpful