Use Case — Internal Corporate Notifications

Use Case — Internal Corporate Notifications

Large organizations regularly send SMS to their own employees — shift reminders, IT outage alerts, payroll notifications, emergency broadcasts. The challenge is not throughput (volumes are modest) but governance: who is allowed to send what, to which employees, on behalf of which department, and with what approval chain.

Message Center's workspace isolation and RBAC make it a natural fit for multi-department corporate messaging.

The Challenge

Corporate SMS programs run into predictable governance problems:

• No separation between departments — IT can accidentally send from HR's sender name (or vice versa)
• No approval workflow — anyone with access can blast the entire employee list
• No audit trail — no record of who authorized which message for compliance or incident review
• Shared credentials — a single SMS account used by multiple teams, with no per-user attribution
• Shadow systems — departments bypass corporate tools and use personal SMS gateways, creating security gaps

How Message Center Handles It

One Workspace Per Department

Each business unit or department gets its own workspace:

HR workspace         → HR sender name, HR campaigns, HR team only
IT workspace         → IT sender name, IT campaigns, IT team only
Finance workspace    → Finance sender name, Finance campaigns, Finance team only
Corporate workspace  → Executive broadcasts, managed by comms team

A single Message Center installation supports all departments simultaneously. Members of the HR workspace cannot see or send from IT's workspace — the isolation is enforced at the API level, not just the UI.

Approval Workflow Per Workspace

Each workspace has its own moderation queue. An HR administrator can approve HR campaigns without needing access to IT campaigns. The separation prevents cross-departmental approvals and keeps the audit trail clean.

Typical departmental setup:

Scheduled and Spread Modes for Internal Comms

Internal notifications often follow patterns that benefit from scheduling:

• Scheduled mode — send shift reminders at a fixed time the day before; send payroll notifications at the exact cutover time
• Spread mode — distribute a large employee notification over 30 minutes to avoid overwhelming the HR helpdesk with simultaneous inbound calls

Practical Example: IT Maintenance Window

1. IT coordinator prepares the message: "Planned maintenance tonight 22:00–02:00. Internal systems will be unavailable."
2. Campaign created in IT workspace, scheduled mode, delivery at 18:00 to reach employees before they leave the office
3. IT manager reviews in the moderation queue and approves
4. SMS Core dispatches at 18:00 to the uploaded employee number list
5. Audit log records: who created, who approved, exact send time, delivery status per number

If the maintenance is cancelled at 17:45, the IT manager can archive the campaign from the list view — before the scheduled send fires.

Compliance and HR Considerations

Attribution without shared passwords: every message created by a specific coordinator is stamped with their user ID in the audit log. When compliance asks "who sent employees their payroll notification on March 3rd?", the answer is two clicks away in the audit tab.

Sender name control: employees receiving an SMS from "CorpIT" or "HRTeam" expect that sender to be the real source. Message Center's sender name revision approval prevents a department from spoofing another department's approved SADDR.

Separation of creation and approval: the four-eyes principle is enforced by the moderation workflow. An author cannot approve their own campaigns — they need a separate moderator to review.

Scale

For most corporate deployments, employee lists are small enough that this is not a throughput concern. A 5,000-employee broadcast in on-demand or scheduled mode typically completes in under a minute at standard SMPP throughput.

For organizations with tens of thousands of employees in geographically distributed locations, spread mode allows pacing the send to avoid simultaneous delivery (and simultaneous helpdesk spikes).

Summary

Next Steps

• Core Concepts — workspaces and roles explained
• Settings and Members — adding team members and assigning roles
• Roles and Permissions — full permission matrix