Skip across the chapter
Quota Playbook

Slack history: 4 checks before a rep review

Quota Playbook Editorial Team · Published · 10 min read

On a free workspace, Slack says you can view and search messages and files from the last 90 days.

Key takeaways

  • Confirm whether the workspace is on a free plan and ask the owner or admin which retention setting is in place.
  • Write down the date range you can cover.
  • Decide which examples you will use before the meeting, using material you can open inside that range.
  • Note any older material you searched for but could not find or open, and tell the rep what you checked.

That window shapes which examples you can bring into the conversation and which ones may no longer be there. This post walks through what Slack's usage-limit page says about that window, what workspace owners can change, and how to prepare without assuming older history is available.

This is written for front-line managers of B2B software sales teams who review a rep's Slack history before a coaching 1:1. If that is your job, the question is not whether Slack has the history you want, but which part of it you can actually open, and how to say so in the room.

The limits in this post come from one source: Slack's Usage limits for free workspaces page. They are written for free workspaces.

A coaching 1:1 works best when you and the rep are looking at the same evidence, and when the evidence is fair to both of you. Slack history can feel like a complete record, but what you can see depends on the workspace's limits and settings. Knowing the window before you open the history helps you avoid a conversation built on partial material.

The 1:1 has one main job: helping the rep see what to do differently next time. Evidence from Slack supports that job when it is specific and current. It works against the job when a manager spends the meeting on material that is hidden or gone, or on a window the rep did not know about. A short check before the meeting keeps the focus where it belongs.

Today, ask your workspace owner which plan and retention setting apply, then check whether you can open the examples you want to discuss.

What can you view and search on a free workspace?

Plan your review around that viewing and search window. Anything you need from before that window should be treated as unverified until you confirm it is still available.

Write down the date range you can cover before you open any channel or direct message. Count back 90 days from the day you prepare, not from the day of the 1:1, because the window moves each day. If the review is about a deal that closed months ago, expect that the story of that deal may sit partly outside the window.

When does Slack start hiding older messages?

According to Slack's usage-limit page, Slack starts hiding messages and files older than 90 days once your workspace reaches the visibility limit. It does this to make room for new ones. Check what you can actually open before you build examples around it.

Open one message from inside the window and one from before it, and note what opens. If an older message no longer opens, record that fact in your notes rather than guessing why.

What can a workspace owner choose for deletion?

On Slack's usage-limit page, Workspace Owners can choose between keeping all messages and files for one year or deleting them after 90 days. Slack describes these as basic data retention settings. These options change how long history is retained; neither extends the free workspace's viewing and search window.

For a manager, the practical question is which option the workspace uses today. Ask the owner or admin directly, and avoid relying on what you remember about the setting from an earlier period.

What happens if an owner chooses to delete after 90 days?

On Slack's usage-limit page, Slack says that if an owner chooses to delete messages and files after 90 days, this will automatically delete any that become hidden by the message and file limit. In practice, that means material the limit has hidden may no longer be available, so do not plan a review around older examples without checking first.

This is the setting where a review can go wrong without anyone noticing. A manager may open a channel, see nothing older than the window, and assume the rep was quiet. That silence may reflect the setting rather than the rep.

Can history older than one year be deleted?

On the usage-limit page, Slack says that starting August 26, 2024, Customer Data such as messages and file history older than one year may be deleted on a rolling basis from workspaces on the free plan. The page ties this to the terms in Slack's Main Services Agreement and Trust and Compliance Documentation. For a rep review, that means a history older than one year may not be there at all, so plan with that possibility in mind.

If the timing matters to a decision, read those documents rather than relying on this summary.

What does Slack say about upgrading?

On the usage-limit page, Slack says upgrading to a paid plan will remove message, file, and app limits, plus provide more data retention options. The page is written for free workspaces, so whether these limits affect your team depends on its plan. Ask your admin which plan the workspace is on and which retention setting it uses before you plan a review.

How should you check the window before the 1:1?

Confirm the plan and retention setting with your Slack admin, then check which messages you can actually open. Retention alone does not establish what is visible.

Write the answers down, the date you asked, and the name of the person who answered. If the answer changes later, you will know which facts you used. Then build your prep notes around the material you have confirmed you can open.

How do you handle examples outside the window?

Use confirmed examples for the review, and treat gaps as gaps rather than evidence about the rep's work.

Look for patterns across the window instead of a single day. If the same kind of issue appears in several threads over several weeks, that is a stronger basis for coaching than one bad afternoon. Note the dates so you can show the rep the spread, not a snapshot.

In the meeting, say the window out loud. If the workspace is a free one, you might say: "On this free workspace, Slack lets us view the last 90 days, so I focused there." That sets expectations and keeps the rep from wondering why older work is missing.

Illustrative example: check a missing thread

A manager can open a thread from 30 days ago but cannot open one from 90 days ago. The manager records what opened, asks the owner about retention, and uses the accessible thread for discussion. The missing thread remains a gap, not proof that the rep did no work.

What should the rep bring to the 1:1?

Ask the rep to bring their own examples from the same window, so the review covers both sides of the record. A rep's view of their own work is useful evidence, even when it differs from yours. Ask them to pick two or three examples from the window that they are proud of and one that they think went poorly. Give them the same date range you are using, so you are both looking at the same period. This also makes the 1:1 a shared review rather than a verdict you deliver from a list of messages. You may find that the rep remembers a thread you cannot open because it was hidden or deleted, and that is worth recording as a gap in the record, not as a judgment.

What should the 1:1 rely on?

Rely on the examples you can verify inside the window, and say clearly where the record stops. A deal thread, a handoff note, or a customer question the rep answered in the last 90 days are good starting points. Keep the 1:1 focused on behavior you saw there, and invite the rep to add context from anywhere else. If the rep disagrees with what you found, write down the disagreement too. A review that records both sides is more useful later than one that only records your view.

How should you explain the window to the rep?

Explain the limit as a feature of the workspace, not as a judgment about the rep. If you can, show the rep how you checked the range, so they can see that the gap comes from the settings and not from a choice you made.

Keep the tone plain. You do not need to apologize for the setting, and you should not blame the rep for what the setting hides.

Why should you avoid judging from one message?

One message is a single data point, so it is weak evidence for a pattern. A short reply in a busy channel can look curt without context, and a long thread can look thorough when it was really one person doing most of the work. Before you use an example, read the surrounding messages, check who else was in the conversation, and ask what the rep was trying to accomplish. Then decide whether the example supports a pattern or only a moment. Coaching points that rest on one moment are easy for the rep to challenge.

How do you write up the review afterward?

Write a short note that records the date range, the examples you used, and the follow-up. Keep the note short enough that the rep will read it, and specific enough that you can check it in a month. Include the date you prepared, the range you covered, and whether the workspace was on a free plan at that time. List the examples by date and channel, and describe what each one showed in plain words. Then record the follow-up: what the rep will try, what you will look for next time, and when you will look. If you could not check something, say so in the note as well, so the next review starts from an honest baseline.

Share the note with the rep before the next 1:1, not during it. That gives them time to add context from their side and correct anything you got wrong, and it means the next conversation starts from a document you have both read.

What do you do when the history is thin?

When the history is thin, shorten the claims you make and widen the questions you ask. A thin history is a reason to ask more questions, not to fill the gaps with guesses. Instead of saying that a rep avoided a difficult customer, ask what happened in that conversation and what they would do differently. Instead of saying that a rep did not follow up, ask how they tracked next steps. Those questions bring in the context that the window cannot show. They also treat the rep as a source of information, which is what a coaching conversation needs.

Can other records fill the gap?

Other records can help explain context missing from Slack. Call notes, meeting summaries, and deal records may hold context that the Slack window may not show, if your team keeps them. Use them with the same care you use Slack. A note written by someone else is still a summary, and a summary can leave out what matters. Name the source each time you cite it, so the rep knows whether a point came from a message, a note, or your own recollection.

Do not let other records replace the window. If you use a call note to fill a gap, say that the point comes from the note and that the Slack record for that period was not fully visible to you.

When should you check the window?

Check the window on the day you prepare, and again if the 1:1 moves to a later date. The window moves every day, so a check you ran last week may no longer match what you can open today. Write the date at the top of your notes, so the range is on record. This also helps when you review a rep over several months. Each review should record its own window, so a later reader can tell what was visible at the time.

What should you not do with the history?

Do not forward channel excerpts to people outside the coaching conversation, and do not use old messages to rank reps against each other. Keep the history in the review itself. Your company's own policies may set stricter rules, so check them before you pull anything from a workspace, especially where messages involve customers or deal terms.

Sources

  1. Multicurrency deals: 5 value checks before coaching
  2. Get back an old coaching doc version: 4 tools to check
  3. CASL email opt-outs: 3 checks for sales managers
  4. Pipeline risk checks for a rep one-to-one
  5. Average call scores by rep

More plays