One-click account linking
Authors, reviewers, and editors connect Telegram from the Contact tab in their OJS profile with a secure t.me authorization link.
Instant, automated communication with reviewers and authors—beyond the traditional email ecosystem.
Email notifications can be delayed, filtered as spam, or ignored by busy reviewers and authors. SRPRO Telegram Notifications connects the OJS workflow with users’ mobile devices through the Telegram Bot API, delivering instant push alerts for review requests, submissions, and editorial decisions. Telegram messaging is free, allowing journals of every size to scale communication with zero message overhead.
Authors, reviewers, and editors connect Telegram from the Contact tab in their OJS profile with a secure t.me authorization link.
The plugin safely hooks into OJS Mail::send events and mirrors critical editorial templates as concise Telegram messages.
A secure webhook handler maps Telegram chat IDs to OJS profiles and processes bot updates in real time.
Built as a PKP Generic Plugin for OJS 3.3 LTS, with GNU gettext i18n and centralized SRPRO licensing.
The journal manager creates a bot using Telegram BotFather and enters the Bot Token in plugin settings. Users opt in from their profile, then standard OJS events continue to send email while matching Telegram push notifications are instantly delivered to linked accounts.
Serbia is invoiced in the RSD equivalent at the NBS middle exchange rate; the region can be invoiced in EUR. SEF e-Invoices and Treasury Administration payments are supported.
| Package | Activation pool | Perpetual / one-time | Maintenance · Year 2+ | Annual subscription | Key inclusions |
|---|---|---|---|---|---|
| Starter | 1 instance (1 journal) | €220 | €70 / year | €120 / year | Telegram Bot API, one-click profile linking, Mail::send interception, instant reviewer/author alerts, unlimited free messages. |
| Standard | Up to 10 instances | €540 | €160 / year | €310 / year | All Starter features for up to 10 journals across any servers/domains. |
| Pro | Up to 20 instances | €890 | €270 / year | €510 / year | For faculties with many journals and modern review communication. |
| Campus | Up to 40 instances | €1,390 | €420 / year | €790 / year | For faculty groups, institutes, and university publishing centres. |
| University / Enterprise | Up to 300 instances | €2,100 | €600 / year | €1,190 / year | University-wide license for up to 300 active journals. |
Pay via Stripe, PayPal, or international SWIFT transfer.
| Package | Activation pool | Perpetual / one-time | Maintenance · Year 2+ | Annual subscription | Key inclusions |
|---|---|---|---|---|---|
| Single Journal | 1 instance | $280 | $90 / year | $160 / year | Telegram Bot API, one-click linking, Mail::send interception, real-time alerts, and $0 message cost. |
| Standard | Up to 10 instances | $690 | $210 / year | $390 / year | Up to 10 journals across any servers/domains, with dedicated bot-token routing. |
| Pro | Up to 20 instances | $1,150 | $340 / year | $650 / year | For mid-size academic publishers and multi-journal faculties. |
| Campus | Up to 40 instances | $1,750 | $520 / year | $990 / year | Campus-wide deployment for university press operations. |
| Enterprise / University | Up to 300 instances | $2,650 | $750 / year | $1,490 / year | Master license, high-volume webhook throughput, and priority SLA. |
Included (€0 / $0)
Visual guide for BotFather bot creation, token retrieval, OJS configuration, and license-key entry.
+ €70 · Global: $90
For 1–10 instances: bot configuration, bot profile image, SSL webhook verification, and editorial-team test notifications.
+ €150 · Global: $200
For 20–40 instances: bulk rollout, multiple editorial-bot configuration, and server throughput verification.
+ €280 · Global: $360
Centralized setup for a university-wide deployment.
+ €80 · Global: $110
Up to 45 minutes remote: encouraging account linking, delivery-status analysis, and user phone/account change procedures. Recording included.
A license is consumed when the Telegram plugin is activated in a specific journal’s settings.
Packages can be allocated on one server or across independent domains and servers, including separate faculty installations.
The key stays assigned to activated journals. Cyclical key movement to bypass purchased capacity results in suspension.