Public Sentiment Overview
View All82%
Overall
Positive Sentiment
- Very Positive42%
- Positive36%
- Neutral10%
- Negative5%
- Very Negative3%
Solutions · CPaaS
Reach people where they already are.
Public communication fails in the last mile: a message goes to a list nobody consented to, on a channel half the ward cannot receive, and the report says it was sent. Civiq.plus puts every channel behind one delivery layer that knows who agreed to what, records what actually arrived, and meters what it cost.
Delivery
Sent is not the same as received
A campaign that reports dispatch volume tells you about your own systems, not about citizens. Every message here carries a per-recipient state, so a ward with poor delivery shows up as a delivery problem rather than as apathy.
- Per-recipient state across every channel
- Consent basis recorded against each send
- Fallback attempts recorded, not hidden
- Cost metered as the campaign runs
Citizen Feedback Trends
View All- Service Satisfaction82%↑ 8%
- Infrastructure68%↑ 5%
- Cleanliness61%↑ 4%
- Safety & Security74%↑ 6%
- Transparency79%↑ 7%
Service Delivery Monitoring
View All78%
Overall
Service Index
- On-Time Delivery81%
- Quality of Service76%
- Resolution Rate74%
- Citizen Reach79%
Capabilities
What the communications layer provides
One interface, many carriers
A campaign names an audience and a message. Which provider carries it is configuration, so switching aggregator does not change how anyone works.
Consent bounds the send
What members agreed to is recorded on the community. A connector cannot widen it, so an opt-in for service updates does not silently become a campaign list.
A ledger, not a send count
Delivery is tracked per recipient and per channel. Reporting reflects what reached people rather than what was dispatched.
Fallback across channels
When a rich channel fails or is unavailable on a handset, the message can fall back to SMS with the attempt recorded rather than silently dropped.
Spend visible per campaign
Cost is metered as messages go out, so a channel mix can be judged on what it actually cost to reach a ward.
Audited end to end
Who approved a broadcast, when it went, and to whom — recorded, because outbound communication at this scale needs an answerable trail.
Channels
The routes a message can take
Which of these are live in a given deployment depends on the accounts and provider credentials connected to it — the platform is explicit about which connectors are configured rather than implying all of them are.
| Channel | What it carries |
|---|---|
| Template messaging to opted-in recipients, with delivery state per person | |
| SMS | The fallback that still reaches everyone, including feature phones |
| RCS | Richer messaging where the handset and carrier support it |
| Voice | Outbound calls and IVR for people who do not read messages |
| Social | Managed pages on Facebook, YouTube, Instagram and X |
| In-app | The platform's own channel, where no external provider is involved |
The ledger
What is recorded for every message
| Field | What it captures |
|---|---|
| Recipient | Who it was addressed to, resolved from the geography, not a pasted list |
| Consent basis | What that person agreed to at joining, which bounds what may be sent |
| Channel | Which route carried it, including the fallback if the first failed |
| State | Queued, sent, delivered, read or failed — per recipient, not per campaign |
| Cost | Metered per message so a campaign's spend is observed rather than estimated |
| Provider reference | The identifier the carrier returned, for reconciliation |
Ready to transform civic outcomes?
See how Civiq.plus can help your teams make better decisions, faster.