Spark ERP

Spark ERP HCM · Communications

One rule engine behind every announcement, email, and SMS.

HR Communications runs on one real, no-code Notification Rule engine — event, condition, recipient, template, channel — behind announcements, email templates, SMS templates, and push notifications alike. Every send is tracked to real delivery status in one unified Communication History, not scattered across separate systems with no shared record of what actually went out.

HR Communications in Spark ERP HCM AnnouncementsEmployee Commun…Email, SMS & Pu… Communication Histo…Delivery Tracked Notification RulesRule Configured
What Communications covers
AnnouncementsEmployee CommunicationsEmail, SMS & Push Templat…Notification RulesCommunication HistoryCommunications
How Communications works
Rule Configured

Event, condition, recipient, template, chan…

1
Event Fires

The matching rule triggers a real send.

2
Delivery Tracked

Sent, Delivered, or Failed — never assumed.

3
Visible in History

One unified timeline across every channel.

4

What Communications actually does

Real, shipped capability — not a roadmap slide.

Announcements

A real publish lifecycle — draft, review, approve, publish, archive — with real view and acknowledgement counts once live.

Employee Communications

A real two-way HR inbox with SLA-oriented status and escalation, not a one-way broadcast.

Email, SMS & Push Templates

Real versioned templates with live character/segment counting for SMS, so you know your send before you send it.

Notification Rules

The no-code engine — event → condition → recipient → template → channel — every other Communications screen routes through.

Communication History

One unified, searchable timeline across every channel, with real delivery tracking — sent versus actually delivered versus failed.

See Communications in Action

Product screenshots are being finalized as Communications nears general availability — the frames below stand in for them.

Communications — Announcements AnnouncementsEmployee Commun…Email, SMS & Pu…Notification Ru…Name
Communications — Announcements · Illustrative screen, not a real screenshot
Communications — Notification Rules AnnouncementsEmployee CommunicationsEmail, SMS & Push Templ…Notification RulesCommunication HistorySummarySave
Communications — Notification Rules · Illustrative screen, not a real screenshot
Communications — Delivery History AnnouncementsEmployee Commun…Email, SMS & Pu…Notification Ru…Name
Communications — Delivery History · Illustrative screen, not a real screenshot

How it works

A single Notification Rule engine — not a different mechanism per channel — is what actually sends an announcement, an SMS, or a push notification, so every channel gets the same real delivery tracking.

Rule Configured

Event, condition, recipient, template, channel.

1
Event Fires

The matching rule triggers a real send.

2
Delivery Tracked

Sent, Delivered, or Failed — never assumed.

3
Visible in History

One unified timeline across every channel.

4
The employee lifecycle, and the HCM modules behind each stage
  1. Attract and hire

  2. Onboard

  3. Work and pay

  4. Grow and develop

  5. Reward

  6. Support and retain

Part of one connected HCM

Communications shares the same employee record, workflow engine, and Country Pack framework as every other HCM module — nothing here is a bolt-on.

Customer Stories

Customer stories are being collected and will appear here.

No testimonial content is fabricated on this site.

Frequently Asked Questions

Real — Communication History and the Notifications inbox both distinguish Sent from Delivered from Failed, not a single generic success flag.

Related solutions

See Communications on your own data

Explore HR Communications in a live walkthrough, or start a free trial and try it yourself.