Notifications
Control which scheduled messages members receive and send broadcast messages to the whole team.
Notifications
Scheduled messages
PayMe sends several automatic Telegram messages per member. Each can be toggled globally by admins in Settings → Messages, and individually by each member in Account → Notifications.
| Message | Schedule | Description |
|---|---|---|
| Morning briefing | 9:00 AM Mon–Fri | Today's agenda, scheduled tasks, open tasks summary |
| Evening recap | Work-end time Mon–Fri (per member) | What was logged, remaining tasks, tomorrow preview |
| Task reallocation | 1h after work-end Mon–Fri | Notifies about unclosed scheduled tasks moved to tomorrow |
| Stuck task alert | 10:00 AM Mon–Fri | Tasks that haven't progressed relative to their estimate |
| Deadline nudge | 9:30 AM Mon–Fri | Deadline proximity alerts (overdue, critical, morning-of, weekly) |
| Zero-estimate nudge | 10:30 AM Mon–Fri | Tasks without hour estimates (invisible to planner) |
| Stale scheduled check | 3:00 PM Mon–Fri | Scheduled tasks still open after their time slot |
| Deadline collision | 9:45 AM Mon–Fri | Multiple tasks due same day with insufficient capacity |
| Inactivity nudge | Event-driven (watchdog) | Reminder if no time logged or timer started |
| Capacity overload | On agenda recalculation | Daily load exceeds 110% of capacity (near-term days) |
Per-member preferences
Each member controls their own notifications at Account → Notifications (37 toggles across 8 groups). PM/admin see an extra "Alert amministrativi" group.
Resolution: admin global OFF = disabled for everyone. Admin ON + member OFF = disabled for that member. Quiet hours (default 21:00–08:00) suppress all notifications except timer checks.
Broadcast messages
Use broadcasts to send a one-time Telegram message to the whole team (or a subset). Go to Settings → Messages → Broadcast:
- Write the message (supports Telegram HTML formatting).
- Optionally attach a GIF.
- Select recipients: all active members, or a specific subset.
- Send immediately or schedule for a specific time.
Broadcasts are processed in the background and delivered via Telegram.
Watchdog notifications
The timer watchdog sends automatic alerts to members with long-running timers:
- 3h check — after a timer has been running 3 hours: "Still working on this?"
- End-of-day alert — at work-end time: timer is still running, reminder to stop it
- Auto-stop — if a timer runs past midnight, it auto-stops and notifies the member
Members can disable watchdog alerts individually in Account → Notifications (Timer e attività group).
Task lifecycle events
Ready for review
When a task with a reviewer transitions to done, the reviewer receives a Telegram message with the client, project, task, assignee, estimate, and logged hours. The message always carries Open task and Open project buttons; an Open Drive button is added when the project (or the task) has an explicit Drive link configured in the project's settings (Project → Settings → Resource links).
Delivery is routed to the project's forum topic when one exists. The message is suppressed when the reviewer preference or the global "Ready for review" setting is off.
Responsible PM updates
Every project has one responsible PM/account: the member who created the project (when they are an active PM/admin). The responsible PM receives Telegram events for:
- Task opened — a task was created in an open status, or reopened from done
- Task completed — a task transitioned to done
Events cover every write path: web, Telegram bot (including NL and checklists), quick-log, allocation pinning, and recurring automation. Each message shows the client > project > task hierarchy, estimate and logged hours, who performed the action, and task/project buttons. Events are emitted post-commit into a durable PostgreSQL outbox. A unique event and recipient key makes retries idempotent. A Trigger.dev worker claims bounded rows, sends through the existing Telegram sender, and acknowledges only after Telegram returns a message ID. Failures retain the row, error, attempt count, and next backoff time for retry; no delivery failure is reported as success.
Projects without a valid responsible PM log an actionable warning instead of broadcasting to all admins. Reassigning project ownership requires transferring creation responsibility (contact your admin).
Task budget threshold
When a member's logged hours on a task cross the configured threshold (default 80%, adjustable in Settings → Messages → Timer and alerts), the responsible PM for that project receives a Telegram alert naming the member, the task with its client and project, and the logged vs estimated hours. Crossing 100% sends a separate overtime alert.
Alerts fire once per crossing: moving from 79% to 80% sends one message, further progress within the band sends nothing. Dropping below the threshold (entry edited or deleted) rearms the alert. Changing the task estimate re-baselines the evaluation. The assignee continues to see the in-app warning; zero-estimate tasks never trigger percentage alerts.