Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Real-World Example

Jane misses a step after receiving a campaign message. The portal creates a scheduled follow-up. Each morning, the scheduled communication command checks whether the follow-up is still valid, sends it if allowed, or removes it if the condition is already resolved.

​
Visual Flow

​
How It Should Work

  • It should send scheduled follow-ups only while the triggering condition still applies.
  • It should stop follow-ups for deactivated, expired, resolved, or opted-out consumers.
  • It should increment send counts and calculate the next send time consistently.

​
How It Should Not Work

  • It should not keep messaging consumers after the account condition is resolved.
  • It should not ignore unsubscribe or communication permissions.
  • It should not repeatedly send follow-ups beyond the configured expiration rules.

​
Developer Notes

  • ProcessScheduledCommunicationsCommand is scheduled daily at 06:00.
  • ScheduledCommunicationService commonly creates follow-ups with a three-day cadence and expiration windows.
  • app/Console/Kernel.php
  • app/Console/Commands/ProcessScheduledCommunicationsCommand.php
  • app/Services/ScheduledCommunicationService.php
  • app/Jobs/TriggerEmailAndSmsServiceJob.php
Last modified on May 25, 2026