Dashboard
Send secure, auditable text messages to approved student phone lists.
0
Messages Sent
0
Delivered
0
Pending
0
Failed
Recent Campaigns
No recent campaign data loaded.
System Guardrails
Authorized senders
Authenticated HCCTS staff with Sender permission
Recipient source
Phone-number CSV, manual entry, or both
Protection
Duplicate removal, opt-out suppression, validation, audit logging
Delivery window
Server-enforced messaging window and provider compliance rules
Recipients
Upload a phone-number CSV, paste numbers manually, or use both. Numbers are normalized and de-duplicated before server review.
Step 1 of 3
1Recipients
2Compose
3Review & Send
Upload Phone List
CSVChoose a CSV file
Required column: Phone Number
Example:
Phone Number\n9165550123\n9165550188\n5305550197
Add Numbers Manually
Paste / TypeEnter one number or a group. Commas, semicolons, tabs, line breaks, and common phone formatting are accepted.
Manual numbers will be combined with any uploaded CSV list.
0
Entries
0
Valid
0
Duplicates
0
Invalid
Recipient Preview
| Source | Original | Normalized | Status |
|---|
Duplicates are removed locally. Final opt-out, suppression, permission, and send-window checks happen again on the server before send.
Compose Message
Write a custom message or start from a saved template.
Step 2 of 3
1Recipients
2Compose
3Review & Send
Upload a valid recipient list before composing a message.
Campaign Details
V3.2 uses plain-text templates only. Legacy {{...}} student fields are not supported in phone-number-only messaging.
0 characters0 SMS segments
Do not include sensitive student information unless the messaging policy and intended audience allow it. The final send is logged to the authenticated staff account.
Review & Send
Verify recipients, message content, and delivery controls before sending.
Step 3 of 3
1Recipients
2Compose
3Review & Send
Complete Recipients and Compose before reviewing a send.
Local preview only. Server suppression and delivery validation must complete before the Send button becomes available.
0
Uploaded
0
Ready
0
Blocked
0
Invalid
Campaign
Name
—
Recipients
0
Segments / recipient
0
Message Preview
Recipient Validation
| Phone | Status | Reason |
|---|
Send is deliberately disabled until the secure server preview returns an approved draft token. This prevents the browser from bypassing suppression, permissions, or audit controls.
Message History
Campaign activity, sender identity, delivery outcomes, and audit trail.
| Campaign | Sender | Recipients | Sent | Failed | Date | Status |
|---|---|---|---|---|---|---|
| No campaign history loaded. | ||||||
Campaign history is loaded from the secure server and Coda audit records.
Message Templates
Reusable HCCTS messages. Templates are optional for each campaign.
Saved Templates
Select a template to preview it.
Create Template
AdminSuppression / Opt-Out List
Numbers blocked from receiving messages until appropriately re-subscribed.
Add Number Manually
Admin| Phone | Status | Source | Opted Out | Notes | |
|---|---|---|---|---|---|
| No suppression records loaded. | |||||
Users & Permissions
Grant Sender, Admin, or Super Admin access. Every permission is enforced again on the server.
Add Staff User
Super AdminNew accounts must change their temporary password before sending messages.
Current Staff Access
| Name | Role | Status | Last Login | Actions | |
|---|---|---|---|---|---|
| No user data loaded. | |||||
Settings
Connection health and messaging configuration. Secret values are never exposed to the browser.
—
Coda
—
SMS Provider
—
Authentication
—
Audit Logging
Deployment & Connection Check
Run Check Connections to verify the backend, Coda tables, Twilio configuration, and send window.
Backend
Netlify Functions, same-origin secure API
Coda
Existing Coda document and table environment variables
SMS
Twilio REST API with background delivery and status webhooks
Security
HttpOnly session cookie, server-side roles, suppression re-check, signed preview token, audit logging
My Account
Manage your staff password.
Your password must be changed before continuing.
Highlands Forward · HCCTS Communications Center · Authorized staff use only. Uploads, sends, opt-outs, permission changes, and exports should be audit logged.