Skip down to the research record

Daily flow email caps: 3 domain rules to check

Quota Forecast Editorial Team · Published · 12 min read

Gong groups daily email counts by company domain, excludes generic domains, and counts all email types toward a limit that restricts only flow emails.

Key takeaways

  • Group corporate contacts by domain before scheduling a push.
  • Add manual sends to your planned flow email total.
  • Confirm unfamiliar domains and the current limit with your admin.
  • Read warnings before deciding which contacts to prioritize.

When more than one contact at one company is in a sequence, the email volume at that company adds up faster than it looks. Each contact gets their own series of messages, each step fires on its own timing, and before long one company is receiving a lot of automated mail in a single day.

The rules that control this are easier to plan around once you know how they count. The three below come from Gong's documentation on sending limits for flow emails. They describe what gets counted, what gets left out, and what the limit actually restricts.

Why the cap exists

Gong's documentation explains the reason for the controls. As its sending limits page puts it, "To protect your company's sender reputation and keep your emails out of spam, your admin can set sending limits on flow emails." That sentence tells you two things. First, the limit is a setting an admin controls, so you should not assume a number and build a schedule around it without checking. Second, the purpose is deliverability. The cap protects the sending reputation your company depends on.

For a revenue leader, the practical result is that a campaign can be slowed by a rule nobody planned for. A push that looks reasonable on paper, with a handful of contacts at one account each getting a multi-step sequence, can reach the limit on a single day. Nothing about the list looks wrong. The problem is only visible when you add up the sends by company and by day.

The three rules below explain how that count works. After them, this post covers how to plan a push around the count, the mistakes teams make most often, what to do when Gong warns you, and what to ask your admin before you launch.

Rule 1: the count groups company domains by day

The first rule is about what gets counted. Gong's sending limits page describes the count as "Flow emails your company sends to recipients in the same domain (company) in a day." Read that sentence slowly, because each part matters. The unit is the recipient's domain, which Gong calls the company. The window is one day. The limit restricts flow emails, while all email types count toward reaching it.

That means the count is not separate for each contact or sequence. If three people at one account are enrolled in a sequence, the flow emails to all three go into the same bucket for that company. If a second sequence also reaches two people at that account, those emails join the same bucket. Five sequences that each touch two people at one company are still one company and one day. The sequences may be separate in your tool, but they are not separate in the count.

This rule can catch teams off guard. It is easy to plan a push by counting contacts, because contacts are what a list shows you. That habit can undercount badly, because the list is organized by person and the limit is organized by company. The fix is to plan by domain instead. Take the full set of people you intend to contact at a company, group them by domain, and add up the flow steps that will land on that domain on each day of the sequence. Add manual and other counted emails to that scheduled flow total before comparing it with your admin's limit.

It also helps to think about the calendar, not just the total. Two people at one company may be fine on their own, but their first steps can add to the same day's count if they land on the same morning. The count is for the day, so the timing of each step is part of the plan.

Rule 2: generic email domains are excluded

The second rule is an exception. The same page states: "Generic domains such as Gmail, Yahoo and Outlook are excluded." The rule takes those providers out of the company count, so the domain grouping from rule one does not apply to them.

This matters when you build the list. A prospect's contact list often mixes corporate addresses with personal ones, and the two groups behave differently under the cap. Before you do the domain math, sort your contacts into corporate domains and generic domains. Only the corporate group goes into a company count. Do not assume that every address with the right person's name belongs to the company. Check the domain itself, because a name in a list does not tell you where the mail is going. For related record checks, see check the buying company on a deal.

The page gives those three providers as examples rather than a complete list, so do not assume it covers every provider you see. If a contact uses an address you are unsure about, ask your admin how that domain is treated before you plan around it. This is one of the questions worth settling before a push starts, because a wrong guess here changes the math for the whole account.

Excluded from the company count is not the same as excluded from everything. Rule two is about how the domain grouping works. It does not mean that every message to a personal address is free of limits or free of other considerations. Plan each contact on the basis of the rules that apply to that contact's address, and keep your own sending practices sound throughout.

Rule 3: every email counts toward reaching the limit, but only flow emails are restricted

The third rule has two halves, and people tend to remember only one. The same page says: "All types of emails count toward reaching a limit, but once a limit is reached, only flow emails are restricted."

The first half is broad. Any email counts toward reaching the limit, including a note a rep writes by hand to a contact at the account or a one-off message sent outside any sequence. The second half is narrow. Once the limit is reached, the restriction applies only to flow emails. Manual emails are not the thing being held back.

Put together, this means your reps' personal outreach uses up room under the count while the flow steps wait. A manual email sent in the morning to someone at a company may be the reason a flow step later in the day is restricted. That is a surprising result if you were only watching scheduled flow emails.

So count manual sends when you plan a push. Ask reps who are working the same account to tell you what they are sending to the company's corporate addresses. Whatever you track, the total you care about is every email counted toward the limit for that company, not only the ones the sequence generated. A plan that ignores the manual side will be wrong on the days that matter most. For related tracking checks, see log seller emails to the right deal.

Putting the three rules together

Here is how the rules combine in a simple case. Suppose you plan a push to four people at one company. Two of them use corporate addresses at that company's domain, and two use personal accounts at a generic provider.

Under rule one, the two corporate addresses form one company group for each day. Under rule two, the two personal accounts are excluded from that company count, so they do not add to the group. Under rule three, any manual email your team sends to the two corporate addresses counts toward reaching the limit, even though it is not a flow email. The sequence may look light on paper, but the count for the company is the corporate flow steps plus whatever your team adds by hand.

Now run it across a week. On the first day, the corporate contacts each get a first step. That is a small total, but it is the start of the day's count. Later that day, a rep sends a short follow-up by hand to one of the corporate contacts, because the account is active. That manual email counts toward reaching the limit. On the second day, the sequence schedules another step for both corporate contacts, and if the company's count has already been pushed up by manual sends, the margin for that step is smaller than the sequence alone would suggest.

The lesson from the example is that the cap is a count over the company, not over the list. A push that looks like four contacts is really two contacts for the purpose of planning, plus whatever your team adds by hand. Once you see it that way, the planning steps below become much easier to apply.

Planning a follow-up push

The practical part comes in five steps. Start with the list, then the calendar, then the people, then the messages, and keep the limit in view the whole time.

First, group the list by domain. Separate the corporate addresses from the generic ones. For each company, write down every person who will receive a flow email and the days on which those emails are scheduled to go out. This is the most reliable way to see whether a single company is likely to reach the limit on a given day.

Second, stagger the enrollments. If a sequence would send to several people at one company on the same morning, consider spacing those enrollments across days so the company's daily total stays lower. Spread touches across the week rather than stacking them. Keep the sequence logic intact, though. The goal is to avoid a single burst, not to change what each message says.

Third, count the manual work. Ask the reps on the account to log their own sends to the company's corporate domains. Each manual email uses room that a flow step might have needed, so the plan has to include it. A rep who sends a few hand-written notes in a day has changed the count for that company, even if the sequence tool never shows those notes.

Fourth, plan the messages, not just the cadence. A cap is a good reason to make each email count. Fewer, better emails to the right people usually beat a wide blast. Remove contacts who have no reason to be in the push, and reduce steps that repeat the same ask. A sequence with a clear reason for each step is easier to explain to a prospect and easier to defend to an admin.

Fifth, do not try to get around the limit. Do not split a company's contacts across extra domains or rotate addresses to slip under the count. The limit exists to protect sender reputation, and working around it defeats that purpose. The cost of a delayed step is small next to the cost of harming the sender reputation the limit is meant to protect.

Common mistakes to avoid

These are possible planning mistakes to check before a push. Knowing them ahead of time is cheaper than discovering them mid-push.

The first mistake is planning by contact count. Check the total by domain before you launch.

The second mistake is forgetting manual sends. A plan that only tracks sequence steps will be off by exactly the amount your reps are sending by hand. The gap is hardest to see when the account is most active, which is when the push matters most.

The third mistake is assuming personal addresses solve the problem. Treating the exclusion as a loophole is the wrong reading of the rule.

The fourth mistake is reacting late to warnings. Gong gives you signals on the To-dos page and in the email composer, and those signals are most useful before you have reached the limit, not after. Teams that wait until restrictions appear end up deciding under pressure which contacts to drop.

The fifth mistake is relying on a limit you remember from somewhere else. Your admin can set the limit for your company. A number from another team, another workspace, or an old conversation may not match what applies to you today. Confirm the current setting before you commit to a schedule.

What to do when Gong warns you

Gong tells you when you are near the limit. The sending limits page says: "When you are close to a flow email limit or have reached one, Gong tells you on the To-dos page and in the email composer." Treat those messages as planning signals, not just notices. They give you time to decide which contacts to prioritize before the limit is reached.

The page also gives an example of the wording you might see: "You're close to your daily limit for flow emails: You have x flow emails left for today." The x is a number that changes as your sends go out, so it is worth reading the message each time rather than assuming the situation is the same as yesterday. When the message appears, identify the limit it refers to; if it identifies a company-specific limit, prioritize contacts at that company.

Do not respond by switching flow steps to manual emails and expecting that to free room. The count does not go away when you change the channel. If a step can wait until tomorrow, move it to tomorrow. If a step is important today, accept that the day's room is limited and give that step the priority. The choice is about which contacts matter most, not about finding a way around the count.

A good rule for the day is to decide in advance which kind of contact gets a personal note and which one waits for the sequence.

Your next step

Today, choose one company in your planned push, total its scheduled flow and manual emails for each day, and ask your admin to check that schedule against the current limit.

What to ask your admin before you start

Because your admin can set limits, the conversation belongs before the campaign launches, not after the first warning. Bring a short list of questions to that conversation. The answers will tell you whether your plan fits the setup you actually have.

What limit is set for flow emails, and over what period is it applied?

Ask your admin for the current setting and its period before committing to a schedule.

Does the limit count flow emails by company domain, as the sending limits page describes?

Yes, Gong describes a daily company-domain count; confirm the setting with your admin.

Which generic domains are excluded from the count?

Gmail, Yahoo and Outlook are examples; ask your admin about other domains that matter for your contacts.

Do manual emails count toward reaching the limit in our setup, and is there a way for the team to see that total?

Manual emails count toward reaching the limit; ask your admin how your team can check the total.

When a company approaches its limit, who decides which contacts keep their flow steps?

Agree on who makes that decision before the push starts.

These questions turn a general rule into a plan you can check. They also help the admin see what your team is doing, which matters because the limit exists to protect your company's sender reputation. An admin who understands the push is more likely to help you plan it than to be surprised by it halfway through.

Related guides: Deal label caps: 100 on one deal, 1000 in an account · Deal link caps: 10,000 in HubSpot, 1,000 in Close · Forecast pull published caps: 8 figures from vendor docs.

Sources