Dornorium — Operations Manual
Operations Manual

Operating Dornorium

A complete guide to every page in Dornorium — one chapter per page, walking through what each screen does, how to use every control on it, and worked examples for the situations you'll actually run into.

Roles admin · manager · tl · agent Chapters Dashboard · Settings · Users · Newsletter · Reviews · Order Reply · Reports

Chapter 1 — Getting Started

1.1 Logging In

Dornorium has no self-serve signup — an admin creates your account first (see Chapter 4).

  1. Open dashboard.html — this doubles as the app's login screen.
  2. Enter your email and password and submit.
  3. Five failed attempts locks your account for 15 minutes, enforced at the edge — retrying faster won't help.
  4. On success, your session token and profile (permissions, access scope) are stored locally, and the dashboard loads your ticket queue.

Forgot your password? Use the "Forgot password?" link on the login screen. It sends a reset email; the reset-password page validates your token and lets you set a new password before redirecting you back to login.

⚠ Session expiry

Logged out unexpectedly mid-session? Your token likely expired (24h lifetime), or your access changed server-side. Just log back in.

1.1b Resetting a Forgotten Password

Reset-password.html is a standalone page reached only via the emailed reset link — you can't type its URL directly and get anywhere useful without a valid token.

  1. Request a reset — click "Forgot password?" on the login screen and enter your email. If that address has an account, you'll receive a reset email; the page doesn't reveal whether the address exists, so no confirmation message beyond "check your email" is shown either way.
  2. Open the link — it lands on reset-password.html with a token in the URL. The page validates the token before showing the form; an expired or already-used token shows an error instead of the form.
  3. Set a new password — enter and confirm it, respecting whatever minimum-length policy is set in Settings → Security (§3.3).
  4. Submit — on success you're redirected to login to sign in with the new password. The old password stops working immediately.
Reset link didn't arrive

Check spam first. If it's genuinely missing, an admin can't manually "resend" it from Users (§4.1) — the person has to request a fresh one from the login screen. Confirm the account's email address is correct if repeated requests don't arrive.

1.2 Layout & Navigation

Every page shares the same shell: a top nav to the pages you have access to, a user badge (initials, name, role, team) in the corner, and a 🌓/☀️ theme toggle.

Pages you don't have permission for stay visible in the nav but greyed out and unclickable — intentional, so you always know what exists even if you can't open it.

1.3 Roles & What They See

🎫
Dashboard
admin · manager · tl · agent
Everyone gets a ticket queue, narrowed by your allowed languages, categories, and email addresses.
⚙️
Settings
admin (edit) · manager (view)
System, security, general, SLA, categories, languages, incoming email, outgoing email.
👥
Users
admin · manager · tl (view all)
Create/edit accounts. Who can edit whom depends on role.
📧
Newsletter
admin · manager (edit) · tl (view)
Compose and send per-language newsletters to subscribers.
📦
Order Reply PAID
admin · manager (edit) · tl · agent (view)
Payment-confirmation templates plus a payment-ticket composer. Requires the Order Reply add-on license.
📊
Reports
admin · manager (edit) · tl (view)
Volume, SLA compliance, categories, top senders.

Land on a page you don't have access to and you'll see a plain ⛔ Access Denied screen with a link back to the dashboard — expected, not a bug.

Chapter 2 — Dashboard

2.1 The Ticket Queue

Your ticket queue, paginated server-side at 25/50/100 per page. Each row shows sender, subject, category, language, SLA status, and assignee.

The dashboard is organized into three tabs — Active, Resolved, and Closed — each showing the statuses relevant to that stage. A count badge on each tab shows how many tickets currently sit in it. Click any row to open the ticket detail panel (§2.4).

Stats bar

Above the queue, a small stats strip totals your tickets per tab so you can see queue size at a glance without opening filters.

2.2 Filtering & Sorting

ControlEffect
SearchMatches ticket number, sender, or subject. Press Enter to apply.
LanguageRestricted to languages your account is scoped to.
CategoryAll categories, or one specific category.
SortLast Updated · Created Date · SLA Status.
Page size25 / 50 / 100 per page.
"Assigned to me"Checkbox — narrows the queue to your own open tickets.

Every filter change re-queries the server and resets you to page 1, so results always match what your role and scope are allowed to see.

2.3 Realtime Updates

The dashboard opens a WebSocket connection to the ticket hub as soon as you log in. New tickets, status changes, assignments, and comments from teammates appear live — no manual refresh needed. If a ticket you're currently viewing changes, the detail panel updates in place.

If it feels stale

Check the connection indicator. A brief network drop reconnects automatically with backoff; a persistent "disconnected" state means a manual refresh is your best move.

2.4 Working a Ticket

Opening a ticket shows the full thread, sender identity, an assignment dropdown, an internal comment box, and a customer-facing reply box. If the ticket came from a completed storefront order, an Order Summary block also renders with items, shipping address, and totals.

  1. Assign — pick from the agent dropdown, or leave Unassigned. Assignment also happens automatically the moment you modify a ticket you have open — not on view alone.
  2. Internal comment — visible to your team only, never sent to the customer. Comments are timestamped in an Activity Log so the full history of who touched the ticket is visible.
  3. Reply — sent to the customer via email; change status from the same panel.
  4. Status — update via the dropdown; this recalculates the SLA state.
  5. Compare tickets — if the sender has multiple open tickets, a compare view shows them side by side to avoid duplicate replies.
Read-only fields

If comment/reply boxes appear disabled, you either don't have write access to tickets, or the ticket is currently locked by another agent — check §2.6.

2.5 The Reply Editor

Replies are composed in a rich-text editor. Every control on it, in the order it appears:

ControlWhat it doesHow to use it
B / I / UBold, italic, underline the selection.Highlight text, click the icon. Click again on already-formatted text to remove it.
❝ BlockquoteTurns the current line into a quoted block — useful for repeating what the customer wrote.Click into the line, then click ❝. No selection needed.
HConverts the current line to an <h3> heading.Click into a line, then click H — useful for structuring longer troubleshooting replies.
1. List / • ListStarts a numbered or bulleted list.Click the button, type the item, press Enter for the next line.
✕ Remove formattingStrips bold/italic/underline/lists back to plain text.Select the formatted text, click ✕.
🔗 Insert linkWraps the selection in a hyperlink.Select text, click 🔗, enter the URL.
</> SourceToggles between formatted view and raw HTML, for hand-editing markup the toolbar can't reach.Click once to edit HTML directly, click again to return to formatted view. Edits carry over either way.
Tag buttons — 🎫 Ticket #, 👤 Customer Name, 📧 Customer Email, 📱 Phone, 📦 Order Items, 📦 Shipping, 📋 Order Ref, 📊 Order Summary, 👤 Customer InfoInserts a placeholder like {{customer_name}} that the server fills with the real value only when the email sends.Click into the editor where the value should appear, then click the tag. The order-related tags only resolve if the ticket came from a completed checkout.
Template dropdown + LoadLoads a previously saved reply template into the editor.Pick a template, click Load. Overwrites unsaved text — save or copy anything important first.
💾 Save (template)Saves the current text as a new reusable template for this category/language.Write the reply, click Save, name the template.
🗑 Delete (template)Permanently deletes the selected template. No undo.Select it in the dropdown, click Delete.
✏️ Editor / 👁 PreviewSwitches between the editable view and a read-only render of what the customer will actually receive.Click Preview before sending anything with tags you're unsure about.
Add CommentPosts an internal note to the Activity Log — never emailed.Type in the comment box, click Add Comment.
Send ReplySends the email to the customer immediately and logs it on the thread.Compose, optionally Preview, click Send Reply. No scheduled or delayed send.

2.6 Ticket Locking

Only one person can actively edit a ticket at a time, so two agents can't overwrite each other's reply.

  • Opening a ticket for editing acquires a lock automatically.
  • Locks release when you close the ticket, navigate away, or close the tab — a crashed tab releases its lock too, via a background signal.
  • An idle lock clears itself after roughly 45 seconds (write) or 30 seconds (read).
  • Admins can force-release any lock if someone is stuck; everyone else can only release their own.

2.7 Reading SLA Status

BadgeMeaning
✅ On TrackUnder 80% of the SLA window elapsed
⚠️ At Risk80%+ elapsed — act soon
🔴 Critical95%+ elapsed — respond now
❌ BreachedSLA window has passed
⏸️ PausedClock stopped — ticket is resolved or closed

Sort the dashboard by SLA Status to triage the most urgent tickets first.

2.8 Auto-Close

Marking a ticket Resolved starts a per-category grace timer, configured in Settings → SLA. When it elapses, the ticket auto-closes. A category with its grace window left at 0 never auto-closes.

⚠ Not a fixed window

The grace window is per category and admin-configurable — check Settings → SLA for the actual value rather than assuming a fixed number of days.

Chapter 3 — Settings

3.1 Overview & Permissions

Admins configure platform-wide behavior across eight tabs. Managers can view most tabs but can't save — fields render disabled for view-only access.

Every "Save" button on this page ultimately calls one low-level function, saveSettings(), which sends the whole tab's changes to the server in a single request — so nothing on a tab saves field-by-field as you type, only when you click its Save button.

3.2 System Config

The low-level guardrails for the platform itself, separate from day-to-day business settings. Built by buildSystem(), saved by saveSystem().

FieldWhat it does
CORS originsWhich domains may call the API from a browser. Add every domain that hosts a Dornorium page (storefront forms, admin UI, etc).
Login rate-limit windowHow long the login endpoint's failed-attempt counter is measured over before it resets.
Session timeoutHow long an issued session token stays valid before requiring a fresh login.
Max failed loginsHow many wrong-password attempts are allowed before lockout kicks in.
Lockout durationHow long an account stays locked after hitting the failed-login limit.

Because a bad CORS value can lock everyone out of login, saveSystem() shows a confirmation dialog before saving whenever CORS is enabled — read it before clicking through.

🗑️ Purge Cache clears the server-side ticket cache so the next dashboard load rebuilds it from scratch — a one-off action with no confirmation, so only use it when you genuinely suspect stale cached data.

Worked example: adding a new admin subdomain

You launch admin2.dornori.info as a second admin panel. Add https://admin2.dornori.info to CORS origins (comma-separated with existing entries), click Save System Config. Skip this and login on the new subdomain silently fails with a CORS error in the browser console.

3.3 Security

Password-policy and account-protection controls layered on top of System Config — minimum password length, reset-token lifetime, and related fields. Built by buildSecurity(), saved by saveSecurity().

Worked example: tightening password policy

Raise the minimum length field, click Save Security Settings. Existing passwords aren't retroactively invalidated — the new minimum only applies the next time someone sets or resets a password.

3.4 General

Built by buildGeneral(), saved by saveGeneral().

FieldWhat it does
TimezoneUsed to display and calculate all dates/times platform-wide, including SLA countdowns.
DomainThe primary domain the platform is served from.
Default languageApplied to tickets/newsletters that arrive without a detectable language tag.
Default From addressUsed when a category/template doesn't specify its own sender.
Product data feed URLWhere product names/images come from for Order Reply auto-fill tags.
Worked example: onboarding a new region

Set timezone to Europe/Vienna and default language to your primary market's code, click Save General Settings. Every SLA countdown and unlabelled ticket now uses this as its baseline.

Product Data

A separate card just below General, holding the two base URLs Order Reply and review-request emails use to fill in product names and thumbnails: Product Data Base URL (product records) and Product Images Base URL (image lookups). Save Product Data writes both in one request.

ControlWhat it doesHow to use it
Save Product DataPersists both base URLs.Fill in the URLs, click Save Product Data.
Test (server-side)Calls the URLs exactly the way the Worker does when it builds an order-reply or review-request email, and reports HTTP status plus item count per URL.Click after saving, to catch failures the browser's own preview wouldn't — e.g. an auth-gated host, a wrong path, or a host that blocks non-browser requests.
🧑‍🎓 Beginner walkthrough: setting up Product Data from scratch

If you've never touched this card before, here's exactly what to do. Product Data is what lets your order-confirmation and review-request emails show the actual product name and photo instead of a blank space.

  1. Ask whoever manages your storefront/product catalog for two things: a URL that returns a JSON list of products (this becomes Product Data Base URL), and a URL that returns product images or image metadata (this becomes Product Images Base URL). Example values might look like https://cdn.myshop.com/data and https://cdn.myshop.com/products — don't worry about the exact JSON shape, that's your storefront platform's job, not something you configure here.
  2. Paste each URL into its matching field in the Product Data card.
  3. Click Save Product Data. You'll see a "✅ Product data saved" toast in the corner if it worked.
  4. Now click Test (server-side). This is the important step most people skip — it doesn't just check the URL loads in your browser, it checks whether the Worker (the actual backend sending your emails) can reach it too. A result panel appears below the button.
  5. Read the result for each URL: a green ✅ OK line with an HTTP status and item count means it's working end-to-end. A red ❌ Failed line tells you exactly what went wrong — wrong URL, the host requires a login the Worker doesn't have, or the response wasn't valid JSON.
  6. If a test fails, don't panic — the most common causes are a typo in the URL, or the feed being behind authentication. Fix the URL or ask your catalog provider to make that endpoint public/token-free, then Test again.

Why "Test (server-side)" matters: your browser and the Worker are two different network paths. A URL can load perfectly when you paste it into your own browser tab (because your browser is logged in, or the host allows browser traffic) but still fail when the Worker tries to fetch it — Test (server-side) is the only way to know for sure before a real customer email goes out broken.

Worked example: diagnosing a missing product thumbnail

If order-confirmation emails go out with no product image, open Product Data and click Test (server-side) first — a ❌ Failed result with an HTTP status or parse error tells you whether the URL is wrong, unreachable from the Worker, or returning unexpected data, before you start debugging the email template itself.

3.5 SLA

Per category, sets the response and resolution hour budgets driving the SLA badges from §2.7, plus the grace windows driving auto-close (§2.8). Built by buildSla() — shows an empty-state message if no categories exist yet, since SLA rows depend on Categories being configured first. saveSla() writes every category's numbers in a single request.

Worked example: a tighter Billing SLA

On the Billing row, set Response to 4 hours and Resolution to 24 hours (tighter than a default General Inquiry row of 24/72), leave the grace window as your auto-close policy dictates, click Save SLA rules once at the bottom.

3.6 Categories

Add, edit, or delete ticket categories. Each has a slug (used internally and in routing rules), a description, and a colour used throughout the dashboard and reports.

ControlWhat it doesHow to use it
Add categorySlugifies the typed name (lowercase, spaces→hyphens, strips anything not a-z0-9-) and creates it.Click Add category, type a name, add a description, pick a colour swatch, click Save on that row.
Save (per row)Writes changes to that one category only.Edit the row's fields, click Save on the same row.
Delete categoryDoesn't hard-delete — flags the category as removed, which every other page then filters out.Click Delete category on the row. See the warning below first.
▸ (expand/collapse)Shows/hides a row's full detail fields.Click the caret to expand a row before editing.
⚠ Deleting a category

Existing tickets keep their category label even after deletion, but new incoming email can no longer route to it — repoint your Incoming Email rules first.

Worked example: adding a "Returns" category

Click Add category, type Returns (slugifies to returns), description "Return & refund requests," pick a red swatch, Save. It now appears as a dashboard filter — give it an SLA row (§3.5) and an Incoming Email routing rule (§3.8) next, or it won't actually receive mail.

3.7 Languages

Add or edit the languages the platform supports. The first language in the list is the default applied to any ticket or subscriber that isn't tagged with a specific language. Every language you add becomes its own tab across Newsletter, Order Reply, and the auto-reply editors.

ControlWhat it doesHow to use it
Add languageAppends a code + display name pair to the list.Click Add language, enter a code (e.g. de) and display name (e.g. "German"), save.
RemoveRemoves a language from the list.Click Remove on that row. Existing tickets already tagged with it aren't affected, but new content in that language (auto-replies, newsletter tabs) disappears.
⚠ Order matters

The first row is the platform's default language. Reorder carefully — untagged tickets and subscribers fall back to whichever language sits first.

Worked example: adding German

Code de, name German, add. It becomes a new tab everywhere language-specific content lives. Nothing auto-populates those tabs — go add German templates in §3.8, Chapter 5, and Chapter 7 next, or German-tagged mail gets no auto-reply.

3.8 Incoming Email — Routing & Auto-Reply

This tab covers three things: routing rules, auto-reply templates, and Cloudflare domain configuration (§3.9). It's split into three collapsible sections — click each header to expand or collapse it.

Routing rules

Map an inbound address to a category AND a language, so mail lands in the right queue automatically. Rules can be created directly as Cloudflare routing rules from this tab if your domain is connected.

ControlWhat it doesHow to use it
Add EmailCreates a new inbound-address → category/language mapping row.Click Add Email, type the address, pick a category and language, click Save Incoming Settings.
Category / Language dropdowns (on an existing row)Changing either re-saves that single mapping immediately.Just pick a new value — no separate save click needed for this one field.
🗑️ (delete rule)Removes the mapping, and if it was Cloudflare-backed, offers to delete the underlying Cloudflare rule too.Click the trash icon on the row you want to stop routing.
🔴 / 🟢 (toggle rule)Activates or deactivates the live Cloudflare rule without deleting it.Click the coloured dot — useful for pausing an address without losing its configuration.
Create RuleCreates a brand-new Cloudflare routing rule directly from a mapping you've defined here.Set up the category/language mapping first, then click Create Rule next to it.
Save Incoming SettingsPersists all routing-rule changes on this tab.Make your changes, click it once at the end.

Auto-reply templates

One template per category, per language, sent automatically the moment a new ticket is created from an inbound email.

ControlWhat it doesHow to use it
Category / Language tabsSwitches which template you're viewing/editing — your choice is remembered across a refresh.Pick the category tab, then the language tab, before editing.
Tag buttonsInsert placeholders like {{ticket_number}} into the template.Click into the template text, then click a tag button.
Enabled checkboxTurns the auto-reply for this category/language on or off without deleting it.Uncheck it to temporarily silence auto-replies for one category/language pair.
Save auto-replySaves the subject and body for the currently selected category + language.Write the template, click Save auto-reply. Repeat per language — see the note below.
Remove (auto-reply)Deletes the template for that category/language entirely.Click Remove — that combination will send no auto-reply going forward.
New category, new reply

Auto-reply is per category AND per language — add a template for every language you support, or that category sends no auto-reply in the missing language.

Worked example: routing a new support address

Launching returns@dornori.info: click Add Email, enter the address, choose category Returns and language en, save. Then in Auto-Reply, switch to Returns / English, write "We've received your return request, ticket #{{ticket_number}}.", check Enabled, click Save auto-reply.

3.9 Cloudflare Domains

This is how Dornorium receives mail at all — a domain has to be connected and routed through Cloudflare here before any address on it can generate tickets in §3.8.

ControlWhat it doesHow to use it
Save Cloudflare SettingsSaves your Cloudflare account ID, API token, and Worker name.Do this first — nothing else on this section works without it.
🔄 RefreshRe-fetches domains and rules from Cloudflare and re-renders the list.Click if a domain's status looks out of date.
Add DomainStarts the setup wizard (3 steps) for a new domain.Click Add Domain, type the domain name, follow the numbered steps.
I've updated nameservers → Check StatusStarts polling Cloudflare every few seconds for DNS propagation.Click after pointing your domain's nameservers at Cloudflare — you don't need to keep re-clicking, it checks itself.
Check StatusManually re-checks a domain's verification/routing status on demand.Use it any time you want a fresh read, or to resume a check that got interrupted by a page refresh.
Enable RoutingTurns on Cloudflare Email Routing for the verified domain. Refuses if the domain already has conflicting non-Cloudflare MX records.Click once the domain shows verified.
DisablePauses routing for an already-configured domain without removing it.Click Disable — routing rules and addresses stay configured, just inactive.
Cancel (mid-setup)Aborts an in-progress setup and removes the partially-configured domain from Cloudflare.Click Cancel if you started adding a domain by mistake.
RemoveFull teardown: deletes the domain from Cloudflare, all its routing rules, and all configured email addresses on it. No undo — the confirm dialog spells this out.Only use this when you're certain — read the confirmation text carefully.
Worked example: connecting a brand-new domain

Incoming Email → Cloudflare Domains → Add Domain → type support.dornori.info. Follow the nameserver instructions, click "I've updated nameservers → Check Status." Once verified, click Enable Routing. You can now add routing rules for addresses on that domain in §3.8.

Web Routing & Live Status

Separate from email routing above, each connected domain also has a web route — where the bare domain itself points when someone opens it in a browser. This lives in its own "Web Routing" box under each domain's DNS Records, and reads DNS + Cloudflare Pages status live, straight from Cloudflare, every time you open it.

ControlWhat it doesHow to use it
Route this domain to (dropdown)— Not routed — / Cloudflare Pages project / Redirect to another website. Determines what the bare domain resolves to.Pick an option; the field below it relabels itself to match (Pages project name, or destination URL) and shows a short hint.
Save RoutingWrites the chosen mode and target, then re-provisions the DNS/Pages configuration on Cloudflare.Set the dropdown and target, click Save Routing. A toast reports the resulting Cloudflare status if it isn't immediately active.
Clear RouteSets the domain back to — Not routed — — it stops pointing anywhere. Only appears once a route is set.Click Clear Route, confirm. Existing email routing (§3.8) is unaffected — this only touches the browser-facing web route.
🔄 Refresh (DNS Records header)Re-fetches every DNS record Cloudflare has for the apex domain and re-renders the DNS Records table.Click any time the DNS table looks stale.
🔄 Recheck (inside the status box)Re-pulls the web-route status specifically — badge, Cloudflare Pages domain detail, and any pending validation — without reloading the whole domains list.Click while waiting on DNS/SSL to finish provisioning, instead of refreshing the whole page.

The status badge reads ✅ Live, ⏳ Provisioning, ⚠️ Needs attention, or — Not configured. Underneath it, the DNS Records table shows every record found for the apex domain (type, name, content, and whether it's proxied through Cloudflare — a proxied record shows the little orange-cloud "Proxied" tag; anything else shows "DNS only"). If Routing mode is set to Pages and the required CNAME record is missing, Dornorium creates it automatically and reports so in the status panel — no dashboard action needed on your part. When Cloudflare is still validating a custom domain (SSL/TXT validation), the panel shows the exact TXT record name and value it's waiting on, so you can double-check it against your registrar if you manage DNS anywhere other than Cloudflare.

🧑‍🎓 Beginner walkthrough: pointing shop.dornori.info at your storefront

Say you've built your storefront as a Cloudflare Pages project called my-storefront-prod, and you want shop.dornori.info to actually show it when someone types that address into a browser. Here's the whole thing, start to finish:

  1. Go to Settings → Domains (this is §3.9's tab). If shop.dornori.info isn't listed yet, follow "Worked example: connecting a brand-new domain" above first — Web Routing only appears on domains that are already added and verified.
  2. Find the domain's row and scroll to the Web Routing box underneath its DNS Records table.
  3. Click the Route this domain to dropdown. You'll see three choices — pick Cloudflare Pages project. The field below instantly relabels itself to "Pages project name" and the placeholder text changes to something like my-pages-project.
  4. Type your project's exact name — my-storefront-prod — into that field. This has to match the Pages project name character-for-character (check it in your Cloudflare dashboard's Pages section if you're not 100% sure).
  5. Click Save Routing. A toast pops up in the corner — usually "✅ Domain routing saved," but if Cloudflare's still catching up you might see "⏳ Saved — Cloudflare status: pending" instead. Either way, the save itself worked; it just takes Cloudflare a little time to finish provisioning.
  6. The status badge under the Web Routing box will read ⏳ Provisioning at first. This is completely normal — DNS and SSL certificates aren't instant.
  7. Wait a minute or two, then click 🔄 Recheck (the small button right next to the badge — you don't need to reload the whole Settings page). Keep clicking Recheck every minute or so.
  8. Once it flips to ✅ Live, open shop.dornori.info in a new browser tab (an incognito/private window is a good idea, so your browser's cache doesn't fool you into thinking it worked when it hasn't). You should see your storefront.
  9. If it's stuck on ⚠️ Needs attention after several minutes, look at the "Cloudflare Pages domain object" detail box that appears underneath — it will usually spell out exactly what's missing, such as a pending TXT validation record. Copy that record into your DNS provider if you're not using Cloudflare-managed nameservers, or just wait it out if you are.

Changed your mind and want to point the domain somewhere else, or take it offline for maintenance? Click Clear Route, confirm the dialog, and the domain goes back to — Not routed —. Nothing about your email routing rules (§3.8) is touched by any of this.

3.10 Outgoing Email

ControlWhat it doesHow to use it
Add AddressAdds a new sender address available across replies, newsletters, and auto-replies.Click Add Address, type the email address, click Save Outgoing Settings.
RemoveDeletes a sender address. Anything still configured to send from it needs repointing.Click Remove on the address row.
Save Outgoing SettingsPersists sender-address changes, plus default-from and password-reset-from addresses.Add/remove addresses and set defaults, click Save Outgoing Settings once.
Save footerSaves the HTML footer for one address only.Write or edit the footer HTML in that address's box, click Save footer.
Clear footerConfirms, then blanks that address's footer.Click Clear footer — the address sends with no footer until you add one again.
📧 Send Test EmailSends a real email through the selected sender address so you can confirm deliverability and footer rendering.Pick the sender address, click Send Test Email, check the inbox it lands in.
Worked example: setting a legal footer

Find billing@dornori.info's row, paste your HTML footer (company address, unsubscribe link, etc.), click Save footer. Then Send Test Email to your own inbox to confirm it renders correctly before agents start replying from it.

3.11 Software Updates

Checks the Dornorium update server for a newer release, downloads and verifies the files in your browser, then applies them via this Worker — no separate installer run required for routine updates.

ElementWhat it does
Current version badgeThe version this Worker is currently running.
Update status badgeNot checked yet / Checking… / Up to date / Update available: vX.Y.Z / Applying update to vX.Y.Z… / Check failed.
Serial badgeThe instance's registered serial number, used to authenticate the update check. If it reads "—", the instance was never registered — register it via the desktop installer, or the /api/admin/serial/register endpoint.
ControlWhat it doesHow to use it
Check for UpdatesCalls the update server with your serial number and current version; shows the latest available version, its publish date, and changelog if one exists.Click any time. The tab also checks silently on load and shows a toast if an update is available and you're not already on this tab.
Apply UpdateDownloads the release manifest and every changed file, verifies each against its listed hash, then deploys static assets, updates the Worker, and runs any pending migrations — reporting progress step-by-step. Confirms before starting.Only appears once a newer version is found. Click, confirm the version in the dialog, then watch the progress bar and step list — don't close the tab mid-update.

The progress bar walks through eight fixed steps — Starting, Downloading manifest, Downloading files, Validating files, Deploying static assets, Updating worker, Running migrations, Finalizing — each logged with a timestamped line in the Update log panel underneath, useful for confirming exactly what happened if an update fails partway through.

Worked example: a routine version bump

Open Settings → Updates, click Check for Updates. If the badge reads "Update available: v1.4.0", read the changelog, click Apply Update, confirm. Leave the tab open until the log reaches Finalizing and the badge returns to Up to date.

🧑‍🎓 Beginner walkthrough: your very first update check

Never used this tab before? Here's the complete, nothing-assumed version.

  1. Go to Settings → Updates. Look at the Serial badge first. If it shows an actual code, you're registered and can skip to step 3.
  2. If Serial shows "—", your instance was never registered with the update server, so it can't check for updates yet. Register it either through the original desktop installer application (re-run it, there's a registration step), or ask whoever set up your instance to hit the /api/admin/serial/register endpoint once. Come back to this tab afterwards and the Serial badge should populate.
  3. Click Check for Updates. The Update status badge changes to "Checking…" briefly. This is normal — it's contacting the outside update server, not your own database, so it can take a couple of seconds.
  4. One of two things happens:
    • "Up to date" — you're running the newest release. Nothing more to do. No Apply Update button appears.
    • "Update available: v1.4.0" (for example) — a new release exists. An "Available version," "Published," and "Changelog" block appears below the badge, and an Apply Update button shows up.
  5. Before clicking Apply Update, actually read the changelog — it tells you what changed, which matters if the release touches a feature your team relies on daily (e.g. "Reviews: fixed CSV export encoding").
  6. When you're ready, click Apply Update. A confirmation dialog names the exact version you're about to install — read it, then confirm.
  7. Watch the progress bar. It moves through eight labelled steps (Starting → Downloading manifest → Downloading files → Validating files → Deploying static assets → Updating worker → Running migrations → Finalizing), each one appearing as a checkmark once done and a ▶ arrow while active. The Update log underneath prints a timestamped line for each action — this is your evidence trail if something goes wrong.
  8. Do not close the browser tab while this runs. The update process is driven from your browser (downloading and verifying files), even though it's ultimately deployed by the Worker — closing the tab mid-update can leave things half-applied.
  9. Once the log reaches "Finalizing" and the status badge flips back to "Up to date," you're done. Give the platform a quick look — open the Dashboard, click into a ticket — just to confirm everything still behaves as expected.
  10. If the badge instead shows "Check failed," read the red-highlighted line in the Update log — it will usually say exactly why (network issue reaching the update server, a bad/expired serial, etc.). Try Check for Updates again in a minute; if it keeps failing, note the exact error text before asking for help.

Chapter 4 — Users

4.1 Managing Accounts

Create and edit accounts, assign roles, and scope each agent's visibility.

FieldControls
Roleadmin, manager, tl, agent — determines default page access
Allowed languagesWhich language-tagged tickets/newsletters this user can see
Allowed emailsWhich inbound support addresses this user can see
Allowed categoriesWhich ticket categories this user can see
TeamUsed by team leads to scope who they can edit; type a new team name to create one
Page permissionsOptional per-resource view/edit/create/delete overrides beyond the role default
ControlWhat it doesHow to use it
+ Add UserOpens the Add User modal with a blank form.Click it, fill in the form below, click Add User inside the modal to submit.
EditOpens the same form pre-filled with that user's current settings.Click Edit on a user's row. Fields you can't change render disabled rather than hidden, so you still see the full picture.
Role dropdownSets the account's base role, pre-filling sensible default permissions.Pick a role first — it changes what the rest of the form pre-fills, so set this before fine-tuning checkboxes.
Allowed languages / categories checkboxesScopes exactly which language- and category-tagged tickets this user can see.Check every language/category this person should see. Leaving all unchecked means they see nothing, regardless of role.
Add → (email)Adds an email address to this user's allowed-emails list.Pick an address in the box next to it, click Add →.
✕ (remove email)Removes one email address from the allowed list.Click the ✕ next to the address.
Team dropdown / CreateAssigns an existing team, or creates a brand-new one on the fly.Pick from the dropdown, or type a new team name and click Create — there's no separate "manage teams" screen.
Page permissionsOverrides beyond the role default.Only touch this if the role's default doesn't match what this person should be able to do — e.g. an agent who should also edit categories.
Add User / Save ChangesSubmits the form.Fill in the form, click this at the bottom of the modal.
DeletePermanently removes a user account. No undo.Click Delete on the user's row — see who-can-delete-whom below.
⚠ Who can edit whom

Managers cannot edit admin accounts. Team leads can only edit agents on their own team. Only admins can grant the admin role.

Worked example: onboarding a new agent

Click + Add User, set Role to agent, fill name/email/password, check the languages and categories they should handle, add their support email address, assign them to a team, click Add User. A new hire seeing nothing after login almost always means an empty scope — go back and check languages/categories/emails are actually checked.

Chapter 5 — Newsletter

5.1 Overview & Layout

Newsletter is fully per-language: subscribers, the subscribe-confirmation auto-reply, and campaigns are each scoped to a language tab. "All Languages" sends to active subscribers across every language at once. Language tabs are sticky — your choice is remembered across a refresh, and switching one resets any active search and view mode.

5.2 The Editor

ControlWhat it doesHow to use it
B / I / U / StrikethroughStandard text formatting on the selection.Select text, click the icon.
❝ / 1. List / • ListBlockquote, numbered list, bulleted list.Click into the line or select text, click the icon.
Align left/centre/rightSets paragraph alignment.Click into a paragraph, choose an alignment icon.
↩ Undo / ↪ RedoSteps backward/forward through recent edits.Click to undo a mistake, or redo if you went too far.
✕ fmtStrips all formatting from the selection.Select text, click ✕ fmt.
🖼 ImageInserts an image into the campaign body.Click it, provide the image URL when prompted.
🔗 LinkWraps selected text in a hyperlink.Select text, click 🔗 Link, enter the URL.
</> SourceToggles raw HTML editing for the body.Click to hand-edit markup, click again to return to the visual editor. Content stays in sync between the two.
Tag buttons — {{subscriber_name}}, {{subscriber_email}}, {{unsubscribe_link}}Inserts a placeholder filled in per-recipient at send time.Click into the body, click the tag. Always include the unsubscribe-link tag — recipients need a working opt-out.

5.3 Compose, Draft & Preview

ControlWhat it doesHow to use it
💾 Save draftSaves the current subject+body without sending it.Compose, click Save draft — it appears in Sent & Drafts (§5.4) to resume later.
✏️ Edit / DuplicateLoads a draft back into the editor to continue it, or duplicates a previously sent campaign as a new draft — the label changes depending on which.Click the button on a history row.
👁 PreviewShows the fully rendered email as a recipient would see it, tags resolved. Shows a toast instead if subject and body are both empty.Click Preview before sending anything you're unsure about.

5.4 Sending a Campaign

ControlWhat it doesHow to use it
🚀 Send to subscribersValidates subject/body are filled, calculates the exact recipient count for the active language (or all), and opens the confirmation modal showing that count.Click once composing is done — it doesn't send immediately, it opens the confirmation step below.
Yes, send nowDispatches the campaign to every active subscriber in scope. This is immediate and irreversible.Review the recipient count shown in the modal, then click. Always Preview first — there's no retry-safe partial state once this is clicked.
CancelBacks out without dispatching anything.Click Cancel if the recipient count or content looks wrong.

5.5 Sent & Drafts

ControlWhat it doesHow to use it
History listShows every past draft and sent campaign for the active language.Scroll to find a past campaign — an empty-state message appears if there's none yet.
Delete (history)Removes a draft or sent-campaign record from the list.Click Delete on the row. Deleting a sent campaign's record does not unsend it — it already went out.

5.6 Subscribers

ControlWhat it doesHow to use it
Active / Unsubscribed tabsSwitches which subscriber list you're viewing.Click a tab to filter the list by status.
SearchLive-filters the subscriber list as you type.Type an email or name fragment.
Delete (subscriber)Removes one subscriber entirely.Click Delete on their row.
⬇ Export CSVDownloads the currently filtered list as a CSV file.Switch to the list you want, click Export CSV.
Worked example: cleaning up bounced addresses

Search for the address, confirm it's the right one, click Delete. To archive the whole list first, click Export CSV before deleting anything.

5.7 Subscribe Confirmation

The automatic email sent when someone signs up, editable per language.

ControlWhat it doesHow to use it
Enabled checkboxTurns the confirmation email on or off for this language.Uncheck to silence it without deleting the template.
Save auto-replySaves the subject and body for the active language's subscribe-confirmation email.Write the template, click Save auto-reply. Repeat per language — nothing is copied across languages automatically.
Worked example

Switch to the German tab, write "Danke für dein Abo!" with the unsubscribe-link tag included, check Enabled, click Save auto-reply.

5.8 General Settings

Field / ControlWhat it doesHow to use it
Batch sizeHow many emails are sent per outbound batch (default 10).Lower it if your email provider rate-limits large sends.
Save settingsSaves batch size and related newsletter-wide defaults.Adjust the fields, click Save settings.
Worked example: throttling a large send

If your provider rate-limits you, lower batch size from 10 to 5 and save — sends go out in smaller chunks, taking longer but reducing the chance of throttling errors mid-send.

Chapter 6 — Reviews NEW

6.1 Filter & Search

The Reviews tab lists every product review submitted by customers through their review-request link. Built and loaded by loadReviews()/fetchReviews(), filtered entirely server-side.

FilterEffect
ProductRestricts the list to reviews for one product ID.
RatingAll · 5 Stars · 4+ · 3+ · 2+ · 1 Star.
StatusAll · Pending · Approved · Rejected.
SearchMatches customer name/email or review text.
Date From / Date ToRestricts to reviews submitted in that window.

Each row shows the customer, product, star rating, a truncated snippet of the review text, its status badge, submission date, and response time (how long it took to reply, if it has been replied to).

Row actionWhat it doesHow to use it
ViewOpens Review Details — full text, rating, customer info, any submitted photos, and your reply if one has been sent.Click View on any row.
ApprovePublishes a pending review so it becomes visible on the public review page. Only shown for pending reviews.Click Approve on the row, or from inside the Review Details modal.
ReplyOpens Reply to Review, a text box for a company response attached to that review.Click Reply, write the response, click Submit.
RetractPulls an approved review back off the public page without deleting it — its history and text are preserved.Click Retract on the row.
DeletePermanently removes the review. No undo — confirmed before it runs.Click Delete, confirm.

Review Stats, shown above the list, totals reviews (Total, Pending, Approved) and the platform-wide average star rating, refreshed every time the filters change.

Worked example: moderating a new batch

Filter Status to Pending, work top to bottom: View each one, Approve if it's genuine and on-brand, Reply with a short thank-you or a fix if they raised an issue, or Delete if it's spam.

🧑‍🎓 Beginner walkthrough: moderating your first batch of reviews

Brand new to this page? Here's the whole flow with nothing skipped, imagining you've just gotten your first 5 reviews in.

  1. Open the Reviews tab. You'll land on the "Reviews" sub-tab by default (the first of the five tabs at the top: Reviews, Orders, Email Template, Reports, Settings).
  2. Look at the Review Stats strip at the top — it might read something like "Total: 5 · Pending: 5 · Approved: 0 · Avg: 4.2★". That tells you nothing has been moderated yet.
  3. In the Status filter dropdown, choose Pending — this hides anything already handled and gives you a clean to-do list.
  4. Click View on the first row. A "Review Details" popup opens showing the full review text, the customer's name/email, the star rating, and any photos they attached.
  5. Read it. Three outcomes:
    • It's genuine and positive/neutral — click Approve right there inside the modal. It instantly becomes visible on your public review page.
    • It's genuine but raises a real problem (e.g. "arrived a day late") — Approve it if you're comfortable with it being public, then close the modal and click Reply on that row to post a public response like "Sorry about the delay — we've flagged this with our courier."
    • It's spam, abusive, or clearly fake — close the modal, click Delete on the row, confirm. It's gone permanently, so only do this for content you're sure shouldn't exist at all.
  6. Repeat down the list. As you Approve/Delete each one, it drops out of the Pending filter automatically, so the list gets shorter as you go — a satisfying way to know you're making progress.
  7. Made a mistake and approved something you shouldn't have? You don't need to delete it — click Retract on that row instead. It comes off the public page immediately but the review record itself (and its history) stays intact, so you can Approve it again later if you change your mind.
  8. Want a spreadsheet copy of what you just reviewed? Set your filters the way you want (e.g. Status: Approved, this month's date range), then click ⬇ Export CSV at the top of the tab — see §6.5.

6.2 Review Orders — Requesting Reviews

A review order is a tracked request for a review, tied to a specific purchase. It's what generates the customer-facing review link and tracks whether it's been sent, completed, or has expired.

Starting a request (manual override)

Review requests are normally created automatically by the scheduled worker (§6.4) once an order's wait period has passed. This panel is for creating one by hand — re-sending a lost link, or requesting a review for an order the automatic worker won't catch.

ControlWhat it doesHow to use it
Load from TicketLooks up a ticket by ID/number and auto-fills order number, customer name/email, and product rows (with thumbnails) from its stored order data.Enter the ticket ID, click Load from Ticket.
Load from Order NumberSame auto-fill, keyed by order number instead of ticket ID — useful when you don't have a ticket to hand.Enter the order number, click Load from Order Number.
+ Add product rowAdds a blank Product ID / Name / SKU row.Click it for each additional product on the order — at least one product with an ID is required.
✕ (remove product row)Removes that product from the request.Click the ✕ on the row.
Create Review OrderSaves the request record (status: pending) with an order number, customer, and product list.Fill in order number and customer email at minimum, click Create Review Order.

Review Orders list

ControlWhat it doesHow to use it
Status filterAll · Pending · Sent · Completed · Expired · Cancelled.Narrow the list to one stage of the review-request lifecycle.
SearchMatches order number or customer.Type and the list re-queries.
Send / ResendSends (or re-sends) the review-request email immediately for that order, using the Email Template from §6.3. Confirmed before sending.Click Send (Pending orders) or Resend (already-Sent orders) on the row.
CancelDeactivates the request — its review link stops working immediately. Available on any order that isn't already Cancelled or Expired.Click Cancel, confirm.

Every review order carries an expiry date, shown in its own column — after that date its link stops accepting submissions and its status becomes Expired automatically.

Worked example: re-sending a lost review link

A customer says they never got their review-request email. Orders tab → search their order number → click Resend. If the order shows Expired instead, create a fresh one instead: Load from Order Number, adjust products if needed, Create Review Order, then Send.

🧑‍🎓 Beginner walkthrough: manually requesting a review for order #10456

Let's say a customer named Priya Sharma (priya@example.com) just had a great support experience on ticket #4021, bought a "Wireless Keyboard" (product ID WK-BLK-01), and you want to ask her for a review right away instead of waiting for the automatic worker.

  1. Open Reviews → Orders tab, and scroll up to the "Start a Review Request (manual override)" panel at the top.
  2. In the Ticket ID field, type 4021 and click Load from Ticket.
  3. Watch the form auto-fill: Order Number, Customer Name, Customer Email, and a product row appear pre-populated — for this example you'd see order number 10456, "Priya Sharma," "priya@example.com," and a product row for the Wireless Keyboard, complete with its thumbnail if one was on file.
  4. Didn't have a ticket ID handy, only the order number? Skip step 2–3 and instead type 10456 into the Order Number field further down and click Load from Order Number — same auto-fill, different starting point.
  5. Check the pre-filled product row is correct. If a second item was on the same order, click + Add product row and fill in its Product ID, Name, and SKU by hand.
  6. Everything look right? Click Create Review Order. A green confirmation message appears ("Review order created"), the form clears itself, and the new request shows up in the Review Orders list below with status Pending.
  7. The request isn't sent yet — creating it just saves the record. Find it in the list (search "10456" if the list is long) and click Send. Confirm the dialog. Its status changes to Sent and a "Sent" date appears in that column.
  8. If Priya says a week later she still can't find the email, come back here, search "10456" again, and click Resend — same email, sent again, no need to recreate anything.
  9. If instead her request has already gone Expired (past its expiry date) and she wants to leave a review anyway, you can't resend an expired link — go back to step 2 and create a brand-new review order instead.

6.3 Email Template

The single review-request email template sent to every customer (not per-language — Reviews has one template, unlike Newsletter and Order Reply). Same rich-text editor as the rest of the platform: bold/italic/underline/lists, a block-format dropdown (Paragraph, Heading 1–3), image and link insertion, and a </> raw-HTML source toggle.

ControlWhat it doesHow to use it
Tag buttonsInsert a placeholder resolved per-recipient at send time: {{customer_name}}, {{customer_email}}, {{order_number}}, {{order_date}}, {{product_list}}, {{order_items_with_names}}, {{order_items_with_images}}, {{review_link}}, {{company_name}}, {{reply_signature}}, {{small_print}}, {{review_deadline}}, {{order_total}}, {{order_items_count}}.Click into the editor, click a tag button. Always include {{review_link}} — without it the email has no way for the customer to actually leave a review.
💾 Save TemplateSaves the subject and body as the live template.Write the email, click Save Template.

Email Preview

ControlWhat it doesHow to use it
👁 PreviewRenders the template with tags resolved. Optionally against a real ticket's order data, if you enter one in "Preview with ticket."Click Preview. Give a ticket ID first if you want order tags filled with real data instead of rendering blank.
Send Test EmailSends the current template as a live test email to an address you choose, optionally rendered against a ticket's real order data.Click, enter a recipient address when prompted.
Worked example: writing the review-request email

Draft the email, use the tag buttons to insert {{customer_name}}, {{order_items_with_images}} and {{review_link}}, click Save Template. Then Preview with a real ticket ID to confirm images and totals render correctly, and Send Test Email to your own inbox before it goes live.

🧑‍🎓 Beginner walkthrough: writing your very first review-request email

Starting from a completely blank template? Here's a full example you can basically copy.

  1. Go to Reviews → Email Template tab.
  2. In the Subject Line field, type something like: How was your order, {{customer_name}}?
  3. Click into the Body editor and write your message in plain text first, e.g.: "Hi {{customer_name}}, thanks for your recent order! We'd love to hear what you thought." Then click a new line and click the tag button for {{order_items_with_images}} — this inserts a placeholder that will show the actual products with thumbnails.
  4. Add a closing line: "Got 30 seconds? Leave us a review:" then click the {{review_link}} tag button on a new line right after it. This tag is not optional — without it, the email has no clickable link and the customer has no way to actually submit a review.
  5. Optionally add {{small_print}} at the very bottom for legal boilerplate, and {{reply_signature}} to sign off.
  6. Click 💾 Save Template. This is the one and only template — Reviews doesn't have per-language tabs like Newsletter does, so this single version goes to every customer regardless of language.
  7. Now check it actually works: in the "Preview with ticket (optional)" field, type a real ticket ID that has order data attached (e.g. 4021 from the earlier example), then click 👁 Preview. The Email Preview panel below shows the fully rendered email — you should see Priya's actual name, her actual product with its real thumbnail, and a working review link, not literal {{...}} text.
  8. If any tag shows up unresolved (still showing as {{something}} literally) in the preview, that usually means the ticket you tested with doesn't have that data — try a different ticket ID, or double-check the tag was spelled correctly by using the tag button rather than typing it by hand.
  9. Last step before trusting it in production: click Send Test Email, type your own email address when prompted, and actually open the email in your inbox. Templates that look perfect in the in-app preview can occasionally render differently in real email clients (Gmail, Outlook, etc.) — this is your final sanity check.

6.4 Timing & Page Settings

Email Timing

FieldWhat it does
Send review request N days after order closesHow long the scheduled worker waits after a ticket/order closes before creating and sending a review request automatically.
Daily sending time (UTC)The time of day the scheduled worker runs.
ControlWhat it doesHow to use it
Run Worker NowManually triggers the scheduled review-request job immediately instead of waiting for its next daily run — reports how many emails it sent.Click it. Useful to confirm the automation is wired up correctly right after configuring it, without waiting until the next scheduled time.

Review Page Settings

FieldWhat it does
Company nameUsed in review-request emails and reply signatures.
Shop website / review page URL *The public page customers land on to submit a review — required for the {{review_link}} tag to resolve to a working link.
Reply signatureAppended to your replies to reviews.
Small print (legal disclaimer)Boilerplate text available as the {{small_print}} tag, e.g. for terms around incentivized reviews.

All fields on this tab save together via Save Settings.

Worked example: turning on review requests for the first time

Settings tab → set Company name, set Shop website / review page URL, Save Settings. Then Email Timing → set the delay (e.g. 7 days after close) and daily send time, Save. Click Run Worker Now once to confirm an eligible order actually goes out before leaving it to the schedule.

🧑‍🎓 Beginner walkthrough: turning on automatic review requests, step by step

This is the one-time setup that makes review requests go out automatically forever after, with no manual work on your end.

  1. Go to Reviews → Settings tab. You'll see two boxes: Email Timing (top) and Review Page Settings (bottom).
  2. Start with Review Page Settings, since Email Timing's requests won't work correctly without it. Fill in Company name — e.g. "Acme Outdoor Co." — this shows up in the emails.
  3. Fill in Shop website / review page URL — this has a red asterisk because it's required. It's the public page a customer lands on after clicking the review link, something like https://myshop.com/leave-a-review. Without this filled in correctly, the {{review_link}} tag in your email template (§6.3) has nowhere to point.
  4. Optionally fill in Reply signature (e.g. "— The Acme Support Team") and Small print (any legal text about how reviews are collected).
  5. Click Save Settings — it saves the whole tab (both boxes) in one go, so this single click also covers anything you're about to set in Email Timing.
  6. Now set Email Timing: in "Send review request N days after order closes," type a number — 7 is a sensible starting point (gives the customer a week to actually use the product before you ask). In "Daily sending time (UTC)," pick a time like 09:00 — remember this is UTC, not your local timezone, so convert accordingly.
  7. Click Save Settings again to persist the timing fields.
  8. Here's the part most beginners miss: nothing has actually been requested yet — you've only configured when it will happen, and the built-in schedule only runs once a day at your chosen time. To confirm the whole pipeline actually works right now, without waiting up to 24 hours, click Run Worker Now.
  9. A small status message appears near the button, e.g. "Sent 3 emails" — this tells you the worker found 3 orders that had crossed the 7-day mark and successfully emailed them. If it says "Sent 0 emails," that's not necessarily a bug — it just means no order currently qualifies (either none have closed yet, or none have reached day 7).
  10. From here on, you don't need to do anything else — the same job now runs automatically every day at your chosen UTC time, picking up newly-eligible orders on its own.

6.5 Export

⬇ Export CSV, on the Reviews tab, downloads the currently filtered review list as a CSV file — apply Filter & Search (§6.1) first to scope the export to what you need.

🧑‍🎓 Beginner walkthrough: exporting last month's 5-star reviews for a marketing email
  1. Go to Reviews → Reviews tab (the export button lives here, not on the Orders tab).
  2. Set the Rating filter to 5 Stars.
  3. Set Status to Approved — you only want public, moderated reviews in a marketing export, not anything still pending.
  4. Set Date From to the first day of last month and Date To to the last day of last month.
  5. Click ⬇ Export CSV. Your browser downloads a file named reviews.csv containing exactly the rows currently shown by those filters — nothing more.
  6. Open it in Excel/Sheets/Numbers like any CSV. Each row is one review with its customer, product, rating, text, and dates.

Tip: the export always respects whatever filters are currently active on-screen, so double-check the filter bar before clicking — an export with Status left on "All" will include Pending and Rejected reviews too, which you probably don't want in a customer-facing use case.

Chapter 7 — Order Reply PAID MODULE

7.1 Payment Confirmations

⚠ This is a paid add-on

Order Reply is a separately licensed module, not part of the base Dornorium platform. It only appears and functions if your account/instance has the Order Reply license active. If the page shows Access Denied or appears unavailable, check your license status before assuming a permissions problem.

Configures the automatic payment-confirmation email sent after a storefront purchase — one template per language, with product name/image/order-summary tags filled in automatically from the product data feed configured in §3.4.

ControlWhat it doesHow to use it
Formatting toolbarSame rich-text controls as §2.5.Select text and click the icon.
🖼 Image / 🔗 LinkInserts an image or hyperlink into the template.Click the icon, provide the URL when prompted.
Smart tag buttons — {{product_name}}, {{order_summary}}, {{order_items}}, {{order_shipping}}, plus customer/ticket tagsInserts an order- or customer-specific placeholder, resolved automatically from the product feed and the order's stored breakdown — including any checkout discount.Click into the template, click the tag.
💾 Save as templateSaves the current composer content as a reusable template.Compose a reply, click Save as template, name it.
Save auto-replySaves the automatic payment-confirmation template for the current language.Edit the template, click Save auto-reply. Repeat for every language you support.
Save Product DataSaves manual overrides to product name/image data used by the order tags.Use if the automatic feed is missing or wrong for a specific item.
Payment Tickets listShows only tickets created from a completed storefront checkout.Scroll or search to find the order you need to follow up on.
Load moreLoads the next page of payment tickets.Click at the bottom of the list when more exist than are shown.
(click a ticket row)Opens that payment ticket's reply modal, pre-loaded with its order data.Click the row to open the composer for that specific order.
👁 Preview with ticketRenders the auto-reply using a real ticket's actual order data, not placeholder text.Click after picking a ticket, to sanity-check exactly what that customer would receive.
🚀 Send reply → Yes, send nowOpens then confirms the send for this specific payment ticket.Same immediate, no-undo behaviour as ticket replies and newsletter sends.
⬇ Export CSVExports order/ticket data for reconciliation with your storefront's own records.Click it — disabled if your role lacks export permission.

Chapter 8 — Reports

8.1 Reading Your Reports

Ticket volume, SLA compliance, status distribution, categories, and top senders — viewable by admin/manager (full) and tl (their team).

Panel / ControlWhat it doesHow to use it
📊 Status DistributionPie chart of how many tickets currently sit in each status.Hover a slice for the exact count if your browser supports it.
⏱️ SLA StatusBreaks down tickets by on-track/at-risk/critical/breached, platform-wide or scoped to your team if you're a tl.Use this as your daily triage check — a growing "breached" slice needs attention now.
📈 Daily Ticket VolumeBar chart of tickets created per day.Scan for spikes — a sudden jump often points to a bug, outage, or campaign that generated extra inbound mail.
🏷️ CategoriesTicket volume broken down by category, colour-matched to §3.6.Compare bar sizes to see which category drives the most volume.
📧 Top SendersLists the customers/addresses generating the most tickets.Check this to spot a single customer with a recurring unresolved issue.
📋 Status SummaryA plain numeric table version of the status distribution.Use when you need exact numbers rather than a visual read.
⟳ RefreshReloads all report panels with current data.Click if you suspect the numbers are stale.
Try AgainRetries loading reports after a failed request.Only appears if reports failed to load.
📥 Export CSVDownloads the underlying report data for use outside the platform.Click once reports have loaded — exports whatever date range/filter is currently applied.

Appendix

A.1 Theme & Preferences

Toggle light/dark mode with the 🌓/☀️ button in the top nav — your choice is remembered on this device.

A.2 Troubleshooting

SymptomLikely cause
Kicked back to login unexpectedlySession token expired — log in again
Nav item greyed outYour role/permissions don't include that page — expected, not a bug
Can't type in reply/comment boxEither read-only access, or someone else holds the ticket lock (§2.6)
New agent sees an empty dashboardCheck their allowed languages/categories/emails — empty scope means zero results, regardless of role
Ticket list feels staleWebSocket disconnected (§2.3) — check the indicator, or refresh
Settings changes not savedManagers have view-only access to most Settings tabs; only admins can save
A "resolved" ticket didn't auto-closeIts category's grace window may be set to 0, or hasn't elapsed yet — check §3.5
New category has no auto-replyAuto-reply is per category AND per language — add a template for every language you support
Order Reply page unavailableOrder Reply is a paid module — confirm the license is active, not just that your role has access
Cloudflare domain won't verifyDNS propagation can take time — use Check Status (§3.9) rather than assuming it failed
Review request never sentCheck Settings → Software Updates isn't the culprit; check Reviews → Timing that the worker is enabled and the delay/send-time are set, then use Run Worker Now (§6.4) to confirm
"Serial: —" on the Updates tabThe instance was never registered with the update server — register via the desktop installer, or the /api/admin/serial/register endpoint, then Check for Updates again
Dornorium Powered by Dornorium · © Dornori