Glossary

Glossary

Key terms used throughout the Message Center documentation.

A

Adapter The module that handles communication with a specific SMS operator or aggregator. The uniqubic adapter connects Message Center to the Uniqubic SMSC platform. Different deployments may use different adapters.

Archive A flag-based state that hides a campaign from the main list without deleting it. Archived campaigns are accessible in the Archive workspace and can be restored. See Archive & Restore.

Author A workspace role that can create, edit, and submit campaigns for moderation. Authors cannot approve or reject their own or others' campaigns.

C

Campaign An SMS dispatch job: a message text, a sender name, a list of recipients, and a send schedule. Campaigns must pass moderation before they are dispatched.

Cabinet Synonym for Workspace. The Russian UI uses "кабинет" (cabinet/office). In English documentation we use "workspace".

Core The stateless SMS dispatch engine (sms-sender/core). Core handles job scheduling, SMPP communication, and delivery tracking. Message Center is the management layer on top of Core.

E

ESME External Short Message Entity — the logical channel between Message Center and the SMS gateway (proxy). Each ESME has a numeric ID and a configured rate limit (RPS). Selected in step 2 of the campaign wizard.

external_id A UUID generated by Message Center when a campaign is created. Used as the stable identifier in UI URLs and the BFF API. Never changes. Contrast with job_id.

J

job_id (sqid) The opaque identifier assigned by Core to a campaign when it is created. It is a short alphanumeric string (sqids encoding). Used internally for API calls to Core. Never appears in URLs or user-facing interfaces — use external_id instead.

M

Master workspace A synthetic cross-workspace view available to Super Admins. Shows campaigns from all workspaces in a single list. Accessible at /w/master.

Message Text The content of the SMS that every recipient in the campaign will receive. Standard SMS is 160 characters; longer messages are split by the carrier.

Mode The send schedule type of a campaign. Four modes are available: OnDemand, OnTime, Spread, Trigger.

Moderation The review process that every campaign must pass before it can be dispatched. A moderator (or admin) reviews the campaign parameters and either approves or rejects it. Campaigns are never auto-started.

O

OnDemand Campaign mode: dispatch messages to all recipients immediately after approval. No scheduling required.

OnTime Campaign mode: dispatch messages at a single specified date and time.

R

Revision A versioned snapshot of a Sender Name's parameters (saddr, ston, snpi, dton, dnpi). Every change to a sender creates a new revision that must be approved. The current approved revision is what campaigns use.

RBAC (Role-Based Access Control) The permission system that controls what each user can see and do. See Roles & Permissions for the full matrix.

S

saddr The actual sender ID string that appears on the recipient's phone as the message sender — e.g. MyShop, BankAlert, or +998901234567. Part of the sender name revision.

Sender Name A logical entity representing an SMS sender identity. Contains one or more revisions. Must have an approved revision to be used in campaigns. See Sender Names & Revisions.

Spread Campaign mode: distribute the recipient list evenly across a date range, sending a portion each day at the scheduled time.

Super Admin A system-level role with unrestricted access across all workspaces and system settings. Distinguished from workspace roles — assigned at the user level, not per-workspace.

T

Trigger Campaign mode: recipients are submitted one at a time via API calls after the campaign is approved and started. Used for transactional messages like OTP codes and order notifications.

TTL (Time to Live) The automatic expiry time for audit log records. Configured via the AUDIT_RETENTION_DAYS environment variable (default: 90 days). After this period, audit entries are automatically deleted by MongoDB.

W

Workspace An isolated environment scoping campaigns, sender names, members, and audit records. Similar to an "organization" or "tenant" in other SaaS products. Each workspace has a URL slug (e.g. /w/marketing-team). See Getting Started.

Abbreviations