Business hours and send windows

Crispy paces automated sends to the account's working day. Campaign invitations, campaign messages, and follow-ups only fire inside the account's send window.

Defaults

The default window is 9:00 to 18:00 in the account's timezone. If Crispy cannot determine a timezone, the window is treated as always open rather than silently blocking your sends.

The timezone is resolved in this order:

1. A timezone you set explicitly.
2. The account's location captured when it was connected.
3. The location shown on the LinkedIn profile.

Changing the window

Use manage_outreach_settings with action 'business_hours':

• start_hour: 0 to 23, the hour the window opens
• end_hour: 1 to 24, the hour it closes
• timezone: optional IANA name like 'Europe/Amsterdam' to pin the timezone explicitly

Checking the window

get_account returns a send_window block per account with the resolved timezone, whether the account is currently inside the window, and when the window next opens.

What out-of-window means

Being outside the window is a pause, not an error. Campaigns are not stopped, nothing fails, and no action is lost. Sends simply wait and resume when the window opens. If a campaign looks quiet in the evening or early morning for the account's timezone, check the send window before assuming something is broken.

Actions you trigger directly through your MCP client run when you call them; the window governs Crispy's automated campaign sends.

Keeping sends inside plausible working hours is one of the simplest ways to keep an account's activity looking like a person's, which is exactly what protects it.