Programs + Families
Send program broadcasts, participant updates, session notifications, reminders, and family communications from the program workflows staff already use.
Connected communications
Keep people informed — without creating another system to manage .
BaseOps Communications brings text and email delivery directly into the workflows your organization already uses — connecting program updates, family notifications, public alerts, reminders, and operational messages to the records behind them.
Communications snapshot
Connected Channels
SMS
Email
Connected workflows
Programs
Forms
GovOps
Payments
Delivery controls
Verified
Preference-aware
Tracked
Built into the work
Communication happens where the operation happens.
Staff should not have to export a list, open a separate messaging system, rebuild an audience, and send the same update again. Communications stays connected to the BaseOps workflow that created the message.
Attendance + Activity
Connect meaningful participant and session activity to family communication while the Family Portal keeps the complete operational record.
Forms + Services
Use the same communication infrastructure for submission updates, service notifications, reminders, and connected public workflows.
Community + Public Alerts
Keep residents informed about municipal alerts, closures, events, public notices, and other subscribed community updates.
Connected by design
Staff handles the operation. BaseOps handles the communication.
BaseOps already understands the tenant, program, participant, family, subscriber, and workflow behind the action. Communications uses that context to determine who can receive the notification and how it should be delivered.
Staff does not need to maintain a separate phone list or manually determine which subscribers requested a specific type of notification.
Something happens
Staff posts an update, sends a broadcast, or completes an operational action.
BaseOps understands the context
The message remains connected to the program, participant, family, form, or public workflow behind it.
Communications checks eligibility
Subscriber status, verification, consent, and notification preferences determine who is eligible.
The message moves
Eligible recipients receive the notification while BaseOps keeps the underlying operational record intact.
Communication with context
From one family to the entire community.
The audience changes, but the principle stays the same: the message should remain connected to the work that caused it.
Participant
Delivered
Participant update
Community Center: Jordan - Field trip. We arrived safely at the location.
View update in Family Portal
Staff can share a direct participant update while the full activity remains available to the family inside BaseOps.
Program
Eligible audience
SESSION UPDATE
Field trip arrival
We arrived at the activity location. Additional details are available in the Family Portal.
Eligible subscribers can be notified
Session-wide communication can reach eligible families without staff assembling another contact list.
Community
SMS + Email
Community notice
Municipal offices will open at 10:00 AM today due to weather conditions.
SMS
Email
Public subscribers choose the categories and channels they want for community information.
Subscriber control
People stay in control of how they hear from you.
Communications is not simply a phone-number database. Verification, consent, notification preferences, and channel status are part of the delivery decision.
Verified numbers
SMS numbers can be verified before text notifications are activated.
Choose what matters
Subscribers can choose the categories of updates they want to receive.
Pause and resume
Channel status can change without destroying the subscriber’s individual topic preferences.
Private stays private
Family and participant notification options remain connected to authenticated BaseOps relationships.
Delivery history
Queued, sent, delivered, and failed delivery states can remain visible to the communication infrastructure.
One communication layer
Programs, Forms, public alerts, and other BaseOps workflows can use the same underlying delivery service.
One connected platform
One communication layer. Multiple BaseOps workflows.
Communications works across the ecosystem instead of forcing every BaseOps product to build its own disconnected subscriber and delivery system.
BaseOps Communications
SMS
Email
Preferences
Delivery history
Programs
Families · Activity · Broadcasts
Forms
Applicants · Services · Status
GovOps
Residents · Alerts · Notices
Payments
Receipts · Status · Reminders
Operational communication
More than sending a text.
The value is everything around the message: identity, context, preferences, eligibility, delivery, and the operational record that remains behind.
Verified subscribers
Topic preferences
Consent-aware delivery
Delivery retry handling
Delivery status tracking
Connected workflow records
BaseOps connects communication events to the workflow that created them. Message delivery may use third-party communication providers, while BaseOps manages the operational context around the message.
Communication, connected
Communication shouldn't be another task.
Connect text and email notifications to the BaseOps workflows your staff already uses — and keep the people you serve informed along the way.