Built-in templates
tikento provides five built-in templates that are automatically sent when the corresponding events occur. Each template is available for email and Telegram.
Registration confirmation
Sent immediately after a successful participant registration.
Contents:
- Greeting with the participant's name
- Event name, date, and location
- Registration number
- Ticket QR code (for paid tickets -- after payment)
- "Open ticket" button
Trigger: registration created with status registered.
Payment receipt
Sent after payment confirmation via webhook from the payment gateway.
Contents:
- Payment amount and payment method
- Ticket name and selected options
- Transaction number
- Organizer details
- "Download receipt" button
Trigger: payment status changed to succeeded.
Reminder (24 hours before)
An automatic reminder sent 24 hours before the event starts.
Contents:
- Start date and time adjusted for the participant's time zone
- Venue address or online stream link
- Additional organizer instructions (if provided)
- "Open event" button
Trigger: BullMQ scheduler, 24 hours before starts_at.
Event cancellation
Sent to all registered participants when the organizer cancels the event.
Contents:
- Cancellation notice with reason (if provided)
- Refund information (if applicable)
- Organizer contact
Trigger: event status changed to cancelled.
Event changes
Sent when key parameters of a published event are changed.
Contents:
- Which parameter changed (date, time, location)
- Old and new values
- "View update" button
Trigger: changes to starts_at, ends_at, location, venue fields on an event with status published.
Template variables
Templates use variables that are automatically substituted when sending.
Participant variables
| Variable | Description | Example |
|---|---|---|
participant.name | Participant name | Ivan Petrov |
participant.email | Participant email | ivan@example.com |
participant.registrationId | Registration number | REG-2026-00042 |
Event variables
| Variable | Description | Example |
|---|---|---|
event.title | Event name | Tech Conference 2026 |
event.date | Start date (localized) | July 15, 2026 |
event.time | Start time | 10:00 |
event.timezone | Time zone | Moscow time |
event.location | Venue | Moscow, Tverskaya St., 1 |
event.url | Event page link | app.tikento.com/events/tech-conf |
Payment variables
| Variable | Description | Example |
|---|---|---|
payment.amount | Payment amount | 3,500 RUB |
payment.method | Payment method | Bank card |
payment.transactionId | Transaction number | TXN-20260715-A1B2 |
ticket.name | Ticket name | Standard |
Organizer variables
| Variable | Description | Example |
|---|---|---|
organizer.name | Organization name | EventPro LLC |
organizer.email | Contact email | hello@eventpro.com |
Template preview
Before sending, you can check how a notification will look:
- Open the event and go to the Notifications tab.
- Select the Templates section.
- Click Preview next to the desired template.
- The system will show a ready email with test data inserted.
- Switch the preview language to check the translation in different languages.
- Click Send test to send to your email.
Multilingual support
All built-in templates are translated via i18n-service into supported languages: Russian, English, Spanish, Arabic, Italian, German, and French.
The notification language is determined automatically:
- Language chosen by the participant in the registration form
- Interface language in which the participant filled out the form
- Event's default language
The number of available languages depends on the plan:
| Plan | Languages |
|---|---|
| Free | 2 (ru, en) |
| Pro | 4 |
| Business | All 7 |
| Enterprise | All 7 |
Template customization
Free
Built-in templates used without changes. Emails include the "Powered by tikento" watermark.
Pro
- Email subject line customization
- Adding custom text (header and footer)
- Uploading organization logo
- No watermark
Business and Enterprise
- Full HTML template editing
- Brand colors and fonts
- Custom content blocks
- Conditional logic in templates (show a block based on ticket type)