Inspect outreach delivery

An outreach message passes through a trigger, decision, safety checks, and channel delivery before a customer receives it.

Inspect the path#

1. Open the related skill or outreach record.
2. Verify the real trigger event and target customer.
3. Check cooldown, quiet hours, consent, and permission gates.
4. Confirm that an execution task was created.
5. Open the delivery record and inspect the final channel status.

Common reasons for no send include missing event data, an active cooldown, quiet hours, an unavailable channel identity, pending human confirmation, or channel delivery failure.

No generated message is not always an error. A safety gate may have correctly blocked outreach.