Connected context
The message starts with the work.
Programs, Forms, GovOps, Payments, and other BaseOps workflows provide the context behind communication.
BaseOps
Communications
Communication connected to the work behind it.
BaseOps Communications connects SMS and email delivery to Programs, Forms, GovOps, Payments, and the operational workflows organizations already use.
Connected where the work happens
Communication starts inside the workflow.
Programs
Broadcasts
Family updates
Forms
Status
Reminders
GovOps
Alerts
Notices
Payments
Receipts
Updates
BaseOps
Communications
How it works
Communication should know why it exists.
BaseOps keeps communication connected to the workflow, recipient, and operational context that created it.
Recipient controls
People stay in control.
Verification, notification preferences, consent, and eligibility help determine supported delivery.
Connected delivery
The right channel carries it.
SMS and email deliver the update while BaseOps keeps the communication tied to the workflow behind it.
Shared foundation
One communication foundation.
BaseOps products do not need separate subscriber systems, disconnected phone lists, or independent delivery pipelines.
Communications provides the shared delivery foundation while each BaseOps product keeps the context and ownership of the work that created the message.
Verification
Preferences
Eligibility
Delivery
History
Programs
Family & participant communication
Forms
Submission & service communication
GovOps
Community alerts & notices
Payments
Payment communication
BaseOps Communications
SMS · Email · Preferences · Delivery
Communication in action
Staff communicates from the workflow.
The communication layer handles delivery without asking staff to rebuild the context somewhere else.
Example · Program activity
1
Staff posts an update
A participant or session update is recorded inside Programs.
2
Communications checks delivery
Subscriber status, verification, preferences, and
notification eligibility are respected.
3
The notification is queued
Supported recipients can receive the notification
through the appropriate channel.
4
The full context stays in BaseOps
The notification points people back to the experience
where the complete operational record lives.
Delivery preview
Program Activity
Eligible
BaseOps Communications
Text notification
Community Center: Participant update - We arrived at today's activity location. The full update is available in your Family Portal.
View update →
Subscriber
Verified
Preference
Enabled
Channel
SMS
Delivery
Queued
Communications handles delivery. The originating BaseOps workflow remains the source of the operational record.
Your communications
People stay in control.
When an organization uses supported BaseOps communication features, recipients can manage how they participate in those communications.
Subscribe
Choose supported notification categories.
Verify
Confirm supported contact information.
Preferences
Control supported notification choices.
Pause
Pause supported communications when needed.
Resume
Return without rebuilding every preference.
Stay connected
Return to the BaseOps experience for full context.
Communication shouldn't become another system.
It should be part of the system doing the work. BaseOps Communications keeps delivery connected to the people, permissions, records, and workflows already in motion.