Sending Requirements
An email action needs:- a connected sender inbox
- a known recipient email
- sender permission in the Team
- a valid Flow Plan step
- completed approval if approval is required
- available sending capacity
- an open Work Schedule window
Work Schedule
The sender Work Schedule controls when automated email can run. If an email becomes due outside the Work Schedule, it waits until the next eligible window. The Settings page may show this as Sending Schedule, but the behavior is the sender Work Schedule.Capacity And Reservation
Each connected inbox has a configurable daily capacity that defaults to300.
- Sent includes outbound messages observed from the inbox during the capacity window, including messages sent outside FirstTouch.
- Reserved includes pending FirstTouch messages scheduled in that window.
- Available is daily capacity minus sent and reserved units, never below zero.
- For FirstTouch messages, the primary recipient and each CC or BCC recipient consume one unit. A pending message reserves those units before send.
- An outbound message detected outside FirstTouch consumes one unit as one provider message.
New Threads And Replies
Flow Plans can send a new-thread email or a reply-style follow-up. A reply-style step uses an earlier FirstTouch new-thread email on the same branch. If the branch has no earlier new thread, FirstTouch normalizes the step to a new thread.Credit Gate
FirstTouch compares the Team’s available credits with the Flow Plan’s maximum estimated run cost. If the balance is lower, enrollment startup and all actions that have not started yet can pause until the balance is sufficient. This gate is not limited to the next billable action.Why Email May Wait
Common wait reasons include:- outside the Work Schedule
- missing sender account
- missing recipient email
- approval task not completed
- sender capacity reached
- account provider backoff
- available credits below the Flow Plan’s maximum estimated run cost