Notifications: overview

Delivery channels

tikento sends notifications through two channels:

Email

The primary channel for all notification types. Emails are sent to the address provided by the participant during registration (the registrant_email field). The organizer receives notifications at the email linked to their account.

Capabilities:

• HTML templates with organization logo and brand colors (Pro+)
• Multilingual templates via i18n-service (7 languages)
• Delivery, open, and click tracking
• DKIM configuration for sending from your own domain (Business+)

Telegram

Instant notifications via the @tikento_bot. Available for users authenticated through Telegram or who have linked their Telegram account in settings.

Capabilities:

• Instant delivery via Telegram API
• Inline buttons for quick actions (open ticket, go to event)
• Formatting and links support

Notification types

Registration confirmation

Sent to the participant immediately after successful registration. Contains:

• Event name, date, and location
• Registration number
• Ticket QR code (if applicable)
• Link to the registration page

Payment receipt

Sent after a successful payment. Contains:

• Amount and payment method
• Ticket name and options
• Transaction number
• Link to receipt

Event reminder

Automatic reminder 24 hours before the event starts. Contains:

• Start date and time
• Venue address or online stream link
• Preparation reminder (if configured by the organizer)

Event changes

Sent to all registered participants when key event parameters change:

• Date or time change
• Venue change
• Event cancellation

Team notifications

Internal notifications for organizers and team members:

• New registration
• New payment
• Refund
• Approaching participant limit

Queue processing

All notifications are processed asynchronously through the BullMQ queue in notifications-service. This ensures:

• Reliability -- if a delivery channel is temporarily unavailable, the message will be retried
• Scalability -- peak loads (mass broadcasts, start of a popular event) do not affect the main application's performance
• Prioritization -- transactional notifications (payment confirmation) are processed with high priority, marketing ones with normal priority

Automatic retries are performed: 3 attempts with exponential backoff (10s, 30s, 90s).

Delivery tracking

The status of each notification is displayed in Event -> Notifications -> Delivery log:

The delivery log is retained for 90 days and can be filtered by channel, status, and date.

Limits by plan

Limits on the number of email notifications per month:

Telegram notifications have no limits on any plan.

When approaching the limit (80% and 95%), the organizer receives a warning. After the limit is exhausted, automatic email notifications are paused until the start of the next billing period. Transactional notifications (payment confirmations, receipts) continue to be sent.