Skip down to the research record

Gong to-do rules: 7 checks before your deal review

Quota Forecast Editorial Team · Published · 11 min read

Why paused contacts can leave a flow before your review

Gong flow to-dos can expire and remove paused contacts; reply handling can also trigger removal, while out-of-office replies can snooze to-dos.

The key takeaways

  • Check the age and type of each paused contact's open to-dos.
  • Review reply handling before clearing the queue.
  • Compare snooze return dates with the deal review date.
  • Confirm flow membership before reporting contact status.

If your team runs Gong flows, you have probably seen a contact sit in a paused state while a to-do waits in the queue. It is easy to read that as a holding pattern: the contact is parked, the to-do is only a reminder, and nothing changes until someone acts. Gong's help page on working through flow to-dos describes a different picture. Some to-dos expire, and when they do, the person can be removed from the flow.

That matters most in the days before a deal review. A leader who walks into the meeting assuming every paused contact is still in its flow may be working from a stale list. The contact might have left the flow weeks earlier, and nobody on the call would know unless someone checked the to-do itself.

This post covers two removal rules and one snooze rule from that help page. For each rule, we suggest a check you can run before the meeting. Confirm flow membership separately when reviewing a snoozed to-do. We are not Gong's product team, and we do not describe behavior beyond what the page states.

Rule 1: An expired flow to-do removes the person

The first rule is the most direct, and it covers three to-do types. The help page says that "Email response, Email bounced, and Meeting booked to-dos expire after 30 days."

The page then explains what expiry does: "When a flow to-do expires, it is dismissed and the person is removed from the flow."

The page also covers the case where the flow is paused: "If one expires while the flow is still paused, the person is removed from the flow."

What this means in practice is simple. A paused contact with an Email bounced or Meeting booked to-do that has been open for 30 days or more may already have been removed. Check the age of every open to-do of those types before you treat the contact as still in the flow. A to-do that looks ordinary in a list can be older than you think if nobody has looked at it since it was created.

Illustrative example: Check an expired to-do

Suppose an account on the review agenda has a paused contact with an Email bounced to-do that is already old enough to have passed the 30-day life the page describes. Under the rule quoted above, that to-do would have been dismissed and the contact removed from the flow. If your list still shows that contact as paused, the list is out of date. Open the to-do and the flow record before you report the contact's status.

Pay extra attention to Meeting booked to-dos for accounts on the agenda. Confirm what follow-up depends on the flow before assuming the meeting is still driven by the flow after a removal. Ask the rep who owns the account what they expected the flow to do next.

Rule 2: Handling a reply can remove the person, but only while the flow is paused

The second rule starts with a prospect's reply. The page says: "When a prospect in your flow replies to an email within 14 days, Gong generates a Response to-do." The same page's removal rule calls it the Email response to-do, so the two names appear to refer to the same item.

The removal condition comes next: "The person also leaves the flow when the Email response to-do is completed, dismissed, or deleted, and only if the flow is still paused."

Read that sentence carefully, because it has two parts. First, the flow must still be paused. Second, the to-do must be completed, dismissed, or deleted. This is the rule that catches well-meaning reps. A rep who works the reply and marks the to-do complete while the flow is paused has, under this rule, removed the contact from the flow. That may be exactly what the rep intended. It may not be what the revenue leader wanted, especially if the contact sits inside a deal that is on the review agenda.

Check the flow's state at the time the to-do was handled, rather than relying on its current state alone. If you need to know how a specific flow behaves, check its current status and ask your Gong admin to confirm.

The 14-day window is the other detail to check. Do not assume a late reply created a Response to-do. If a paused contact replied a few weeks ago and nothing appears in the queue, look for that reply in your email and in your CRM before you conclude that nothing happened. A missing to-do is a finding to investigate, not proof of anything.

For the pre-meeting check, go through each paused contact who has replied. Confirm whether a Response to-do exists, when it was created, and whether anyone has completed, dismissed, or deleted it. If you can tell whether the flow was still paused at that moment, note that too. If you cannot tell, flag the contact as unknown rather than guessing.

Rule 3: An out-of-office reply with a return date snoozes the to-do

The third rule works differently from the first two. The page says: "An out of office response with a return date snoozes the to-do until that date."

A snooze is not an expiry. Treat the snooze date and flow membership as separate checks. Check it directly in your account: find a contact with an out-of-office snooze, and confirm whether that contact is still in the flow while the to-do is held.

This matters for a deal review because a snoozed to-do is easy to forget. The snooze lasts until the return date. If the return date falls near the review, compare that date with the team's decision schedule. If the return date falls after the review, the contact may not be able to respond until after the decision is made, and the deal forecast should reflect that.

For each snoozed to-do, record the return date and compare it with the review date. Write down the contact's name, the account, and whether the contact is still in the flow, if you can confirm it. A short line like "snoozed until after review, flow status unconfirmed" is more useful than a silent gap in the list. Use a close date change log when documenting a related date change.

A pre-review check you can run

Leaders can give the following sequence to whoever prepares the paused-contact list. Each step uses only the rules above, and none of them needs a number beyond what the page states.

  1. List every paused contact tied to a deal on the agenda. Include contacts from related accounts and parent companies, not just the primary buyer.
  2. For each contact, list open to-dos by type: Email response (the Response to-do), Email bounced, Meeting booked, and any snoozed to-dos.
  3. For Email bounced, Meeting booked, and Email response to-dos, check how old each one is. Any to-do at or near 30 days needs a decision before the meeting, because the page says expiry removes the contact.
  4. For contacts who replied, confirm that a Response to-do exists. If one does not, check the reply manually instead of assuming it was handled.
  5. For Response to-dos, check whether anyone has completed, dismissed, or deleted them while the flow was paused. Those actions can remove the contact under the second rule.
  6. For out-of-office snoozes, record the return date and whether it falls before the deal review.
  7. Choose one action for each contact. You can leave the contact and its to-do alone and accept the expiry outcome. You can act on the to-do with the expiry rule in mind. Or you can take the contact out of the flow on purpose and follow up by hand, with the owner's agreement.

One warning belongs at the top of the process, and the team should hear it before anyone starts. Do not clear a Response to-do just to tidy the queue before the meeting. A cleaner list can hide a flow that just lost a contact.

What to do when the list and the flow disagree

Sometimes the spreadsheet or dashboard will say a contact is paused, while the to-do itself shows that it has expired. The page says that an expired flow to-do leads to removal, so the to-do record is the better source for that question. Do not rely on an older export. Recheck the to-do, note the date you checked it, and update the list. If the record is unclear, ask the rep who owns the account and record the answer as their statement, not as confirmed fact. For the wider review, use the guide to reconcile sales dashboard totals.

The same logic applies in reverse. If the list says a contact has left the flow but the to-do is still open and the flow is still paused, the contact may still be in the flow. Confirm the status before you tell the deal team that the contact is out of the sequence.

Common mistakes to avoid

The first mistake is treating a paused flow as a safe place to wait. A pause is not protection.

The second mistake is assuming that a to-do nobody has touched is safe. Include untouched items when checking to-do ages.

The third mistake is clearing to-dos to tidy the queue. Cleaning up is a real action with a real effect on the flow.

The fourth mistake is assuming a reply after 14 days gets the same Response to-do as a reply inside that window. Check for the actual to-do before adding it to your list.

The fifth mistake is forgetting out-of-office snoozes until the week of the review. A to-do can remain snoozed until its return date, and the return date may land in the middle of a decision.

The sixth mistake is deciding how a snooze affects flow membership based on what seems reasonable. Check the live behavior in your account instead.

Talking points for the deal review

When you present paused-contact status, lead with the questions the review needs answered, not with a list of to-dos. How many contacts on the agenda have an open to-do of a type covered by the 30-day expiry? How many have a reply with no Response to-do? How many are snoozed past the review date? Those three counts tell the room where the flow may have already changed the picture.

Then name the owner for each open item. A count without an owner turns into a status meeting. An owner for each contact turns into a decision. For each item, say what the owner will do before the deal review, and what changes if they cannot.

Keep the language careful. Say "the to-do expired, and under Gong's help page the contact is removed from the flow" instead of "the contact is out." Say "the snooze runs until the return date, and we have not confirmed flow status" instead of "the contact is still in." Precise wording protects the forecast from guesses that look like facts.

If someone asks whether the flow will fix this on its own, check the current records before answering. The flow behaves according to the rules on the page. A person has to read the to-do state, the flow state, and the reply history together, then decide what to do. That is the work this check is meant to make visible.

Limits of this guidance

This post uses quotes from Gong's help page on working through flow to-dos. It does not cover other Gong pages, your account's specific settings, or how other sales engagement tools handle similar states. Gong may change how flows and to-dos work, so check the current behavior before changing your process. Before you change a process based on this post, check the current help page and ask your Gong admin to confirm how your flows are set up.

We have not tested these rules in a live account, and the hypothetical case above is meant to help you think through your own list, not to record what happened in any account.

The short version

A paused flow is not a safe parking spot. Two rules establish removal conditions, while the third describes snoozing; confirm membership separately for snoozed contacts.

Check all three before the meeting. Look at the age of each to-do, confirm whether each reply produced a Response to-do, and record every snooze and its return date. Then tell the room what you confirmed, what you could not confirm, and who owns each open item.

Today, choose a paused contact on your review agenda, open its to-do and flow record, and update your list with the confirmed status.

Related guides: Activity linking: 8 rules for deals and visibility · AI call scorecard checks: 5 rules before the forecast · Check 8 data rules before the weekly sales call.

Questions before the deal review

What should you check before clearing a reply to-do?

Check whether the flow is paused and whether you intend to remove the contact. Confirm the expected next action with the account owner before changing the to-do.

How should you report a snoozed contact?

Report the return date and the flow membership you have confirmed. Keep any unconfirmed status explicit rather than treating the snooze as proof of membership.

Sources