Skip down to the research record

Departed rep's mail: 3 steps to save deal evidence

Quota Forecast Editorial Team · Published · 12 min read

To save a departed rep's Microsoft 365 mail, check the deletion date, restore the account, and move the mail before the recovery window closes.

Key takeaways

  • Ask IT for the account's deletion date and time today.
  • Confirm who has the privileges needed to act.
  • Check the moved threads before deleting the restored account.
  • Link forecast notes to saved buyer messages.

When a sales rep leaves, the CRM usually looks fine on the surface. The stage is set, the amount is entered, and the close date is filled in. The real evidence sits somewhere else, in the rep's inbox. It's the message where the champion said budget was approved, pending one signature. It's the reply that quietly pushed the close date two weeks out. When the mailbox disappears, that evidence goes with it, and the quarter-end forecast review is left with numbers nobody can defend.

This post is for revenue leaders who have a departed rep's account in front of them right now and a forecast deadline coming up. It gives you three steps. The first is to find out how much time you actually have. The second is to restore the account and move the mail somewhere safe before it's deleted for good. The third is to turn what you saved into forecast evidence, and to change the process so the next departure doesn't become a race against the clock.

A note on scope first. The recovery timelines below apply to Microsoft 365; the Google Workspace guidance concerns the privileges needed to restore a user. Your email platform may handle deleted accounts differently, so use these as a reference point and confirm your own settings with IT.

Why the 30-day clock matters

Microsoft 365 keeps deleted mailboxes recoverable for 30 days by default. Microsoft's guidance describes a recovery window, and it is explicit about how long that window lasts: "You have 30 days to restore the account before the user's data is permanently deleted."

Two things follow from that. First, the clock the documentation describes starts when the account is deleted, not on the rep's last day in the office. An account can sit disabled for a week before anyone deletes it, and that disabled period is not what the 30 days counts. Second, 30 days is the outer limit of what you have, not a plan. If you spend the first three weeks deciding who owns the problem, you'll have little time left to recover and review the mail.

Quarter-end makes this worse. The threads you lose are often the ones from the last few weeks of the quarter, because that's when buyers are negotiating terms and approvals are moving. Those are the messages your forecast depends on most, and they are also the ones most likely to be in a rep's inbox on the day they leave.

Microsoft Entra also gives administrators a way to see recently deleted users. In its documentation, "You can see all the users that were deleted less than 30 days ago." That list is where you check whether the account is still inside the recovery window at all.

Step 1: find out whether the account is still recoverable

Start today, and start with the deletion date rather than the departure date. Those two dates are often different, and the recovery window depends on the deletion date. Ask IT for the exact date and time the account was deleted, and write it down. If IT can only give you the departure date, ask them to confirm the deletion date in writing before you rely on it.

Next, check the deleted-users list. If the account appears there, it's still inside the window and you have something to work with. Note the time remaining in hours, not days. A count of days hides how little time is left, and hours make it clear how fast the rest of this has to move.

Then confirm who can actually act. Google's restore documentation puts the issue plainly: "Without the correct privilege, you won't see all the controls needed to complete these steps." Get the name of an administrator who holds the right role, and ask them to take the task today. Don't spend time trying to work around missing permissions. That time is better spent on the threads.

It also helps to decide, before you call anyone, what you need from the administrator. Write down three things: the account name, the deletion date and time, and the list of deals you need to protect. A short request with those three items gets a faster response than a long email that asks for "help with a departed rep's mailbox."

If the account was deleted more than 30 days ago, say so plainly to your leadership team. The recovery window described above has closed, and the mailbox data may be gone. Ask IT what other copies exist, such as backups or exports the company keeps for other reasons. Don't promise the forecast review a recovery until you have confirmed one. A forecast built on a mailbox that can't be restored needs to say so out loud, and the sooner the better. If the missing evidence is in the CRM itself, check the separate sales record recovery rules.

Step 2: restore the account, move the mail, then delete

This is the step that matters most, and the order is the whole point. Microsoft's documentation lays out the sequence for an account that has already been deleted: "If you've already deleted the account: if it's been less than 30 days you can restore it, then move the email data, then delete the account." Delete last, and only after you've confirmed the move worked.

The same page notes that "you can even move the data up to 30 days after deleting the account."

Once the account is restored, decide where the mail goes. Good choices are a shared mailbox the whole revenue team can search, the mailbox of the successor who will own the deals, or an archive that you control. Avoid parking the mail in the personal mailbox of a manager who might also leave. The destination should be somewhere the team keeps working after the next reorganization.

Next, narrow what you move. You don't need every newsletter and calendar invite from the last three years, and moving everything wastes time you don't have. Start with the threads that bear on the forecast:

  • Any conversation with a buyer on an open opportunity.
  • Any message where the buyer made a commitment, such as a price, a date, a signature, or an approval.
  • Any message where the buyer raised a risk, an objection, or a delay.
  • Any thread that mentions a deal name, a buyer's company, or a close date that appears in your forecast.

Check with legal or compliance about what your company's policies require you to keep. Don't assume a narrow filter satisfies a retention rule you haven't read. If the two conflict, the policy wins, and you can still move the forecast threads first while the rest of the decision gets made.

After the move, verify. Open a sample of the moved threads and confirm that the successor can see them in the new location. Count the threads for each open deal and compare the count with what the rep's CRM notes suggest should exist. A gap between the two is a signal to check for missing threads before the forecast call.

Also check what comes back with the restored account. Look at its settings and what it's connected to before you hand anything to anyone. Don't give the successor the departed rep's login.

Step 3: turn the saved mail into forecast evidence

Saving the mail is only half the job. A folder full of threads doesn't change the forecast by itself. Someone has to read them and write down what they say.

Go deal by deal. For each open opportunity, record five things in the CRM:

  1. The date of the last real message from the buyer, not the last internal note.
  2. The next step the buyer agreed to, in their words where possible.
  3. The name of the person who can approve the deal.
  4. Any commitment the buyer made in writing, such as pricing, dates, or terms.
  5. Any risk or objection the buyer raised that hasn't been answered.

Link each entry to the saved thread so the next person can check your reading. A summary without a source is just another opinion, and the forecast review will treat it that way. Use the email linking checks when connecting those messages to deals.

Then adjust the forecast to match the evidence. A deal in a late stage whose last real buyer message is weeks old is not the same as a deal that moved forward last week, even if both show the same stage. Move those deals down, or mark them as needing confirmation, based on what the threads show. Be specific about which deals have written support and which are carried on the rep's last known view. That distinction is the most useful thing you can bring to the review.

Next, get the successor talking to the buyers. Ask the new owner to read the saved threads for each open deal and reply to the buyer, using the thread as context. A reply from the buyer before the forecast call gives you evidence of continued engagement. If a buyer doesn't answer, record that. Silence is information, and it belongs in the forecast review. Don't let a silent buyer quietly stay in the commit column because nobody has the energy to chase them.

Finally, record what you could not recover. If some threads are gone, list the deals they belonged to and mark those deals as unverified. The forecast call goes better when the leadership team knows which numbers rest on evidence and which rest on memory. A forecast with an honest gap is more useful than a clean number nobody can trace.

Illustrative example: separate saved mail from confirmed deals

You recover threads for 8 and cannot verify the remaining 2. Record those 2 as unverified. For each of the 8, read the buyer's last message and record the next step, approval contact, written commitment and unresolved risk. Recovering a thread does not confirm a close date; use what the buyer actually wrote to decide whether the forecast needs to change.

What to say in the forecast review

When the review arrives, you need to explain your numbers in a way that a skeptical finance partner can follow. Start with the scope. Say how many open deals the departed rep owned, how many of them you verified from saved threads, and how many you could not verify. That one sentence tells everyone how much weight the forecast can carry.

Then walk through the deals that changed. For each one, say what moved and why, and point to the thread that supports the change. If you moved a deal down, say which written buyer message drove the decision. If you left a deal where it was, say whether the successor has confirmed it with the buyer. Keep each explanation short. Two or three sentences for each deal is usually enough, and it keeps the review on the buyers rather than on the mailbox.

Be honest about what you don't know. A deal can look likely and still need a confirmation before it goes in the commit column. Use plain categories such as confirmed, likely, and unverified, and define them once at the start of the review so nobody argues about the labels.

Finally, separate the recovery work from the forecast itself. The mail rescue is a project with its own owner and its own deadline. The forecast is a judgment about the quarter. Mixing the two makes it hard to tell whether a lower number reflects real buyer risk or just a gap in the records. Keep them apart, and the review will focus on the right questions.

Build the handoff before deletion

The three steps above are a rescue. The better outcome is a departure process where nobody has to race a deletion date. Build these into your offboarding:

  • Preserve the mailbox during offboarding. When a departure is announced, ask IT to preserve the mailbox for the revenue handoff while removing access and carrying out other necessary offboarding controls. Ask for this in writing, and name the person who signs off.
  • Export open-deal threads before the rep's last day. The rep is still there, can explain which threads matter, and can help you sort them. This is far easier than doing it after the account is gone.
  • Assign a successor the same day. A deal without an owner keeps getting worse. Name the new owner for each open opportunity, and have them introduce themselves to the buyer.
  • Require current CRM notes on every open deal. The notes should say what the buyer last said, not just what the rep planned to say. A note that reflects the buyer's last message is worth far more than one that reflects the rep's hopes.
  • Make deletion the last step, not the first. For your revenue workflow, complete the handoff before deleting the account. Build that order into the checklist itself.

Mistakes that cost the most

A few errors show up again and again in these situations, and each one costs time you can't get back.

The first is waiting for the forecast review to ask IT for help. By then the recovery window may be nearly closed, and the administrator who could have acted on Monday is now on a long trip. Make the request the same day you learn about the departure.

The second is assuming the CRM has the deal. CRM fields are often a summary someone wrote in a hurry. The thread is the evidence, and the summary is only as good as the last person who updated it.

Another mistake is forwarding threads to a personal address to keep them safe. That can break company policy and create a new problem on top of the one you're trying to solve. Use the company's approved location, even if it takes a few extra steps.

The short version

Today, send IT a request containing the account name, deletion date and time, and the open deals whose mail needs protecting.

What if recovery fails?

Can you promise the mail will come back?

No; confirm recovery before promising evidence for the forecast review. Ask IT about existing backups or exports if the account cannot be restored.

Does saved mail confirm a deal will close?

No; saved mail lets you check the buyer's commitments and unresolved risks. Mark gaps plainly and ask the successor to confirm the next step with the buyer.

Related guides: Quote expiry checks: 5 steps before you move a close date · Cancellation billing day: 8 steps to check credit · CRM seat prices to check before adding a seat: 5 steps.

Sources