dev modeloading tenant…
Dev Director

Background jobs

Same tasks Celery beat runs on schedule, exposed as one-shot triggers for testing. Production: run `make worker` + `make beat`.

Nurture · §6.11
Re-engage cold leads

Scan for leads with no engagement >N days; enrol into MSA cold-lead nurture.

Capture · §6.12
Run event chain

Send 24h reminders + post-event follow-ups; promote linked enquiry leads to tour_booked.

Attract · §6.4
Process social queue

Publish scheduled posts whose time has come — Facebook/Instagram/LinkedIn.

Optimize · §6.16
Recompute A/B winners

Walk running experiments; mark concluded when one variant reaches ≥95% confidence.

Celery schedule (when running)

  • · 06:00 Brisbane daily — re-engage cold leads (§6.11)
  • · every hour at :00 — event 24h reminders (§6.12)
  • · every hour at :10 — event follow-ups (§6.12)
  • · every 5 minutes — social publish-due (§6.4)
  • · 07:00 daily — A/B conclude (§6.16)