Illustrative hearing · 17 November 10:30
Follow events and manage each channel’s conditions.
Hearing, task, payment and due-reminder events are processed for an authorized recipient. All five channels are not enabled automatically: company/member preferences, current record access, channel quota and provider setup apply. Timing and recipient delivery are not guaranteed.
- In-appConditional
- EmailConditional
- SMSConditional
- WhatsAppConditional
- PushConditional
01/05 · Event × channel
Distinguish events from channel support
Hearing creation, task assignment, completed payments and due reminders can produce member notifications. Marks below indicate conditional channel support, not proof of sending to every team member or a client. Calendar and agenda, legal deadline tracking and the e-notification guide describe separate source operations.
Channels selected through company defaults and personal preferences are rechecked against current permissions and source state before sending. Online payments require their own provider setup. Webhook management, signed test requests and optional automatic event delivery for a selected branch exist; delivery is at-least-once.
| Event | In-app | SMS | Push | ||
|---|---|---|---|---|---|
| Hearing created | ● conditional | ● conditional | ● conditional | ● conditional | ● conditional |
| Reminder due | ● conditional | ● conditional | ● conditional | ● conditional | ● conditional |
| Task assigned | ● conditional | ● conditional | ● conditional | ● conditional | ● conditional |
| Payment completed | ● conditional | ● conditional | ● conditional | ● conditional | ● conditional |
| Platform bulk notification | no | ● conditional | ● conditional | ● conditional | no |
02/05 · Path
Queue, checks and sending
- 01/0709:41
Illustrative hearing record: 2026/42 E. The event’s authorized member recipient and current source scope are checked; agenda/search processing is not guaranteed to complete at the same instant.
- 02/0709:41
In-app: an enabled preference and current record scope allow an entry in the recipient’s own inbox. Opening a link still requires current access.
- 03/0709:41
Email: the member recipient needs an enabled preference, current address, company email connection and quota. A sending record does not prove the recipient read it.
- 04/0709:42
SMS: a member needs a current phone, preference, quota and company provider. A client copy is available only for a custom hearing/deadline/appointment reminder with explicit selection and current channel consent.
- 05/0709:42
WhatsApp: an eligible active company connection and current approved template/mapping are required. A registered client phone alone is insufficient; custom-reminder and channel-consent conditions also apply.
- 06/0709:42
Push: an authorized member, registered device and device notification permission are required. Lock-screen content is limited; the operating system may delay or suppress a notification.
- 07/0709:42
Webhook: automatic sending runs only for an enabled subscription and its selected branch; permissions and plan conditions are rechecked before each send. A signed test request from management is not acceptance of a live event subscription.
The hearing is saved
03/05 · Bulk
Bulk sending belongs to platform management
Bulk sending requires platform-management authority; company web/mobile panels provide no bulk-send operation. Platform staff explicitly select recipients and email, SMS or WhatsApp; channel, provider, quota and recipient-limit conditions apply separately.
A job accepted by the platform is processed in the background. This is not a company bulk-marketing tool or automatic messaging to every client. Queue acceptance, provider acceptance and personal delivery are separate stages, with no fixed-minute or read guarantee.
- SMS
04/05 · Record
Read sending records within their scope
- 01/02
The log shows a processing result
Within your permissions and current case/branch scope, log entries show channel, recorded recipient and processing result. A failed or uncertain result does not always provide a definitive cause or permission to resend.
Sent describes provider acceptance or the relevant channel operation; it alone does not prove personal receipt/reading or timely completion of a legal notification.
Illustrative record · Email · Authorized member · Review outcome
- 02/02
Manually match an existing email record to a case
An eligible manual email record in the panel can be linked to a case you may access. This does not read your mailbox automatically or import every incoming message; automatic notification records do not enter this manual matching flow.
Matching cannot change until a pending queued job finishes. Current company, case and branch access is required; manual selection does not eliminate mistakes. The illustration starts no operation.
Illustrative record matching
Client A
Document about 2026/42 E.
Case
2026/42 E. · Receivable case
Example matching step
Illustrative view
05/05 · Questions
What do people ask about notifications?
- 01/05
Which channels are supported?
Code supports in-app, email, SMS, WhatsApp and push. Enabled preferences, current permissions/source, eligible address/device, quota and necessary provider setup determine availability. Email/SMS/WhatsApp bulk sending is platform-management only, not a company-panel operation.
- 02/05
Can a client get a reminder on WhatsApp?
Only when a client is explicitly selected for a custom hearing, deadline or appointment reminder, with current source/client access, phone and channel consent, preferences/quota, an active company connection and a current approved WhatsApp template/mapping. Hearing creation, task or payment events do not automatically create a client copy.
- 03/05
How can I follow notification results?
You can inspect recorded processing results in logs you may access. Sent is not proof of personal delivery/reading; a provider or device outcome may be uncertain. Real provider and device acceptance needs separate verification.
- 04/05
Is an incoming mailbox read automatically?
This feature makes no such promise. You manually link an eligible existing email record to a case you currently may access. Matching restrictions apply to automatic records and unfinished queued jobs.
- 05/05
What is the in-app notification inbox?
Every member has a personal inbox on web and mobile that holds only their own notifications: the unread count is shown, notifications can be marked as read one by one or all at once, and the list can be limited to unread items. The inbox can be opened even when the company subscription is restricted; subscription notices appear there. Opening the related record from a notification depends on your permission to see that record.
Review preferences and record-level reminder settings. Check the company setup and acceptance conditions on the integrations page before using external channels.