Vasyka 85ef2f6e00 Stage 13 — Notifications: Telegram bot + multi-channel + service reminders
Schema:
- clients.telegram_chat_id (linked via /start contact-share)
- clients.notify_prefs (per-client channel order override)
- service_reminders_sent (dedup ledger for the daily cron)

Telegram (per tenant):
- TelegramService (sendMessage, getMe, setWebhook with auto-generated secret)
- Bot token stored in companies.settings.telegram.bot_token
- Webhook /telegram/webhook/{slug} validates X-Telegram-Bot-Api-Secret-Token,
  matches client by last 9 digits of phone, persists chat_id, replies confirm
- /start prompts share-contact; /stop unlinks chat_id

NotificationDispatcher refactor:
- Multi-channel: telegram first if chat_id + bot configured, then email
- Backwards-compat with legacy boolean notify.{type} flags
- 4 HTML-formatted Telegram messages (wo_ready with tracking link, payment,
  appointment, reminder)

Service reminders:
- `reminders:send` artisan command with --slug / --dry-run
- Policy: vehicles whose last closed WO is older than reminder.after_days
  (default 365). Skips if sent within reminder.cooldown_days (default 30).
- Schedule daily 09:00

Filament UI:
- Settings page: Telegram bot token field + "Test bot" + "Set webhook" actions
- Settings page: reminder_after_days + reminder_cooldown_days inputs
- ClientResource: telegram_chat_id readonly badge

Tests (6 new, all pass):
- webhook links client via shared contact
- webhook rejects wrong secret → 401
- dispatcher uses telegram when chat_id present (Http::fake)
- dispatcher falls back to email otherwise
- dispatcher returns false when no channel available
- reminder cron respects 30-day cooldown

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-27 20:14:17 +00:00

AutoCRM

SaaS CRM multi-tenant pentru autoservice și magazin piese auto.

Stack

  • Laravel 12 + Filament 5
  • Octane (FrankenPHP runtime)
  • MariaDB 11.4
  • Redis 7
  • Stancl/Tenancy v3 (single-DB multi-tenant)

Domenii

  • service.mir.md — panou central super-admin
  • <slug>.service.mir.md — instanță tenant

Documentație

Vezi /root/service/docs/00-index.md în repo-ul părinte (separat de cod) pentru:

  • Arhitectură + decizii
  • Setup multi-tenant (3 niveluri izolare)
  • Toate cele 31 module preluate din prototip
  • Operațiuni (deploy / backup / add-tenant / troubleshoot)

Dev local

cp .env.example .env
composer install
npm install
php artisan key:generate
php artisan migrate
npm run build
php artisan octane:start --server=frankenphp

Deploy

Push pe main → Coolify auto-deploy.

License

Proprietary. © 2026.

S
Description
AutoCRM SaaS multi-tenant
Readme 3.3 MiB
Languages
PHP 78.5%
Blade 21.2%
Dockerfile 0.2%
Shell 0.1%