Workday and sending limits

GenLink sends inside firm limits so your outreach stays healthy and human-paced. This page is the reference for the workday, the caps, and why a send might not go out.

The workday#

Set the workday once per workspace on Settings > Sending, in the Workday card. Its description: "When your agents are on the clock. Every agent in this workspace works the same hours; changes reach them within a minute."

• Timezone, Clock in, and Clock out set the hours. The default is 10:00 to 22:00.
• A weekday picker sets which days agents work, defaulting to Monday to Friday. At least one day must stay on.
• Shortcuts: Use my timezone sets the timezone to yours, and Around the clock runs sending across the full day.

Agents only send inside the workday. Change it and every agent picks up the new hours within a minute.

The daily send cap#

Each agent has its own Daily send cap on the agent's Sending settings: "Max emails this agent sends per day, inside the workspace workday. Sends are at least 30 minutes apart, so a 12-hour workday fits about 22. Your mailbox cap applies too."

• Default is 20, settable from 1 to 500.
• The mailbox's own cap applies on top, so the real limit is whichever is lower.

The 30-minute rule, and the arithmetic#

Sends from one agent are spaced at least 30 minutes apart, plus up to 5 minutes of jitter so the timing is not robotic. A send asked for too early is refused, not queued for later.

That spacing is why a 12-hour workday fits about 22 sends: twelve hours is 720 minutes, and 720 divided by 30 is 24, so with jitter you land around 22. If you want more volume than one agent's day allows, hire another agent rather than raising the cap past what the spacing supports.

Every reason a send is refused#

A send is refused, in this order, when:

1. The agent is paused.
2. The row was already sent.
3. The row belongs to another agent.
4. There is no resolvable address for the row.
5. The address is on the do-not-send list.
6. The address was already emailed by someone else in this workspace (workspace-wide dedupe).
7. The daily cap is reached.
8. The 30-minute gap has not elapsed.

A refusal for too-early timing or a reached cap is not a failure; the send simply waits for the next valid window inside the workday. See deliverability and safety for the do-not-send list and bounce handling, and approve and send for the approval gate that comes before all of this.