Omnichannel Communications
| Feature Name | Omnichannel |
| Feature ID | CrestApps.OrchardCore.Omnichannel |
The Omnichannel modules provide Orchard Core building blocks for coordinating communication across channels such as SMS and event-driven integrations.
The management experience layers a lightweight Customer Relationship Management (CRM) workflow on top of those building blocks, including contacts, subjects, campaigns, subject flows, dispositions, activities, and batches.
Available Orchard modules
| Module | Docs |
|---|---|
| Base orchestration module (includes the Omnichannel - Azure Communication Services feature) | This page, Azure Communication Services |
| Event Grid integration | Event Grid |
| Management UI (CRM), including re-engagement cadences | Management, Cadences |
| Leads, accounts and opportunities (Omnichannel CRM) | CRM |
| SMS automation (AI) | SMS |
| Automated Voice (AI voice conversations over any telephony provider) | Telnyx AI Voice Agent |
| Omnichannel Channel Endpoints (the Omnichannel Addresses screen, turned on by the features that need it) | Management |
| Omnichannel Messaging - Azure Blob Storage | Messaging - Azure Blob Storage |
| Messaging workspace (human two-way, every non-voice channel) and its SMS Messaging Channel | Messaging Workspace |
| DNC Registry (national and local do-not-call screening) | DNC Registry |
| Contact Center Business Hours (calendars that gate automated sends) | Business hours |
What the base module does
- provides the shared Orchard communication layer
- supplies the shared message, endpoint, preference, and processing contracts used by the management and channel modules
- ships the Omnichannel - Azure Communication Services feature
(
CrestApps.OrchardCore.Omnichannel.AzureCommunicationServices), which only enables Orchard Core'sOrchardCore.Email.AzureandOrchardCore.Sms.Azureproviders alongside Omnichannel
Enable the feature
- Go to Tools -> Features in Orchard Core.
- Enable Omnichannel.
- Add the related management or channel modules you need.
Inbound webhooks
The base feature defines no HTTP endpoint of its own. Inbound events arrive through the channel feature that owns the provider:
| Feature | Endpoint |
|---|---|
| Omnichannel - Azure Event Grid | POST ~/api/azure/webhook/eventgrid |
| SMS Omnichannel Automation or the SMS Messaging Channel, with Orchard Core's Twilio SMS feature (Twilio inbound SMS) | POST ~/api/twilio/webhook/sms |
| Telnyx SMS (Telnyx inbound SMS) | POST ~/api/telnyx/webhook/sms |
Enable the channel feature that matches how your provider delivers events, and configure its authentication before pointing a subscription at it.
Reports
When Omnichannel Management and the shared Reports feature (CrestApps.OrchardCore.Reports) are enabled, CRM
reports are contributed to the reusable Reports framework and appear under the
top-level admin Reports menu. Omnichannel contributes 29 reports: 5 activity reports (Activity summary, Campaign performance, Disposition breakdown, Dialer call detail, and AI handoff & containment), 21 workload and performance reports, and the 3 CRM reports of the Omnichannel CRM feature. They are grouped across the
Operations, Queue & Routing, Agent Performance, CRM & Campaigns, Compliance & Audit, and
Technical & IT categories. Each report shares the standard from/to date-range filter and adds
Campaign group, Campaign, Channel, Source, and Status filters. Reports export to CSV, and
to Excel (.xlsx) when the Reports (OpenXml) feature is enabled.
Examples include:
- Activity summary - activity volume and completion, broken down by source, channel, and status, with a daily created-activity trend.
- Campaign performance - per-campaign completed vs pending progress across the CRM activity inventory.
- Disposition breakdown - how completed activities were dispositioned in the period.
- Activity backlog and Activity aging - open workload, assignment, reservation, and overdue work.
- Campaign source, channel, disposition, and attempt mixes, Channel endpoint usage, and per-user productivity and completion-time reports.
See Management: Reports and Reports in the user manual.
Access is gated by the View Omnichannel reports (ViewOmnichannelReports) permission, which is
implied by Manage activities and granted to administrators and the built-in Supervisor role by default.
Notes
- The base module does not provide the full management UI by itself.
- Use the related module pages for channel-specific or management-specific setup.