Notification System#
The biggest problem with interstellar communication isn't messages getting lost — it's messages arriving too late. Finding out your server crashed yesterday morning is nobody's idea of a good time. The VeriTeknik notification system exists to solve precisely this: the right message, through the right channel, at the right moment.
6 channels. 8 categories. Infinite peace of mind.
Channels#
| Channel | How It Works | Setup |
|---|---|---|
 In-App |
Real-time via SSE, bell icon in the hub | Automatic — if you have an account, it's on |
 Email |
HTML-templated emails over SMTP | Automatic — goes to your registered email |
| :iphone: SMS | Via Bird.com, falls back to email on failure | Active if your phone number is on file |
 Telegram |
Bot integration, instant messages | Settings → Connections → Link Telegram |
 Slack |
Workspace OAuth connection | Settings → Connections → Slack |
 Push Notification |
Web push via service worker | Grant permission in your browser |
SMS fallback logic
If an SMS delivery fails, the system automatically falls back to email. Your message never vanishes into the void — worst case, it arrives through a different channel. The Hitchhiker's first rule: don't panic. We don't either.
Categories#
Every notification belongs to a category. You can choose which channels to enable for each category independently.
| Category | When It Fires | Example |
|---|---|---|
| billing | Invoices, payments, balance changes | "New invoice issued: #2026-0042" |
| contracts | Contract creation, renewal, cancellation | "Your contract expires in 30 days" |
| vps | Server status changes, provisioning | "Your VPS is ready: 185.x.x.x" |
| domains | Domain registration, transfer, expiry | "veriteknik.com expires in 14 days" |
| support | Support tickets and replies | "Ticket #1234 received a reply" |
| monitoring | Uptime and performance alerts | "Server cpu-alert: CPU above 95%" |
| security | Login attempts, 2FA, security events | "Login from a new device detected" |
| system | Platform updates, maintenance notices | "Scheduled maintenance: 03:00-04:00 UTC" |
The security category cannot be disabled
Security notifications are always delivered through at least one channel (in-app + email). Think of it as a fire alarm — you can't mute it, and you shouldn't want to.
Managing Preferences#
Go to Settings → Notification Preferences to configure which channels are active for each category.
Preference Matrix#
You'll see a matrix that looks like this:
| In-App | SMS | Telegram | Slack | Push | ||
|---|---|---|---|---|---|---|
| Billing |  |
|
|
|
- | |
| Contracts | |
|
- | |
- | - |
| VPS | |
|
|
|
|
|
| Domains | |
|
- | - | - | - |
| ... |
Click any cell to toggle it. Changes are saved instantly.
Unlinked channels
If you haven't connected your Telegram or Slack account yet, those columns will appear disabled. Link first, configure later. Priority order: grab your towel first, then explore the galaxy.
Channel Details#
In-App (SSE)#
Real-time notifications appear via the bell icon in the top-right corner of the hub. Powered by Server-Sent Events (SSE) — notifications arrive live as long as the page is open.
- Unread count badge displayed on the bell
- Clicking a notification takes you to the relevant page
- Past notifications are accessible from the list
Email#
HTML-templated, brand-consistent emails. Every email includes a "Manage notification preferences" link at the bottom.
SMS#
Delivered via the Bird.com infrastructure. Messages are kept short and to the point — within the 160-character limit.
When SMS fails
If the number is invalid, the carrier is unreachable, or Bird.com has an outage, the system automatically redirects the same notification to the email channel. This fallback mechanism ensures critical notifications are never lost.
Telegram#
Link our Telegram bot to your account to activate this channel. For detailed setup instructions, see the Telegram Integration page.
Slack#
Connect via OAuth to your workspace. Notifications arrive in your chosen channel or as a DM.
- Settings → Connections → Slack
- Click Connect Slack
- Select your workspace and grant permissions
- Choose a notification channel
Push Notifications#
When you grant permission in your browser, you'll receive push notifications via a service worker. Notifications can arrive even when the browser is closed (depending on OS support).
- Click "Enable push notifications" in the hub panel
- When the browser asks for permission, click Allow
- Done — you'll now see notifications on your desktop too
Priority Levels#
Every notification carries a priority level:
| Priority | Behavior |
|---|---|
| low | In-app only |
| normal | All active channels |
| high | All active channels + emphasized display |
| urgent | All channels (regardless of preferences) |
You cannot block urgent notifications
Notifications with urgent priority are sent to all channels, no matter what your preferences say. This is how we tell you your server is on fire — and you don't want to receive fire alerts in "do not disturb" mode. When the Vogon fleet approaches, silent mode is not a sensible strategy.
Frequently Asked Questions#
Can I turn off notifications entirely? Except for security and urgent categories, yes. But we don't recommend it — ignoring infrastructure alerts is the ostrich-head-in-sand strategy, and ostriches don't run data centres.
Does SMS cost extra? No. SMS delivery is provided at no additional charge through VeriTeknik's infrastructure.
How fast are notifications? In-app and push notifications arrive in milliseconds. Email and SMS take a few seconds. Telegram and Slack land in 1-3 seconds. Slower than the speed of light, but perfectly respectable by galactic standards.
Can I receive push notifications on multiple devices? Yes. Just grant permission on each device/browser separately.
Continuous improvement
The notification system is under active development. Coming soon: WhatsApp integration, notification digest/grouping, and scheduling rules ("outside business hours, urgent only"). The Guide's pages never end — neither do ours.