Notification Examples¶
Why This Exists¶
This document provides realistic examples of Notification Domain behavior in Algosure.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Examples show how Notification supports procurement execution without owning the underlying business facts.
Example 1: Tender Deadline Reminder¶
Opportunity owns the tender and closing deadline. It requests a deadline reminder. Notification creates a critical notification schedule for 7 days, 48 hours, and 4 hours before close.
Notification owns:
- Reminder schedule.
- Channel plan.
- Delivery attempts.
- Read and acknowledgement state.
- Escalation if required.
Business value: the customer is less likely to miss a tender close date.
Example 2: Expiring Compliance Document¶
Compliance owns the document expiry fact. It requests a notification for an expiring tax compliance document. Notification applies preferences and sends an in-app and email message.
Business value: the customer can act before compliance readiness is affected.
Example 3: Team Approval Required¶
Bid owns the approval workflow. A bid reaches submission approval. Notification sends the approver an in-app, email, and WhatsApp notification based on policy. If unread after the threshold, escalation begins.
Business value: bid submission is not blocked by silent approval delays.
Example 4: Contract Milestone Reminder¶
Contract owns the milestone. Notification schedules reminders to responsible users before the due date and records delivery history.
Business value: delivery teams stay aware of obligations and reduce milestone slippage.
Example 5: Learning Reminder¶
Learning owns a recommended course. Notification sends a reminder when the user has not started a high-priority lesson linked to a compliance gap.
Business value: users receive education prompts connected to real procurement needs.
Example 6: Subscription Payment Notification¶
Billing owns subscription and payment facts. Notification sends payment due and payment failed notifications across allowed channels.
Business value: customers understand payment actions before access or service continuity is affected.
Example 7: Future Calendar Integration¶
A compulsory briefing is scheduled. Opportunity owns the briefing fact. Notification may create a future calendar item through Outlook, Gmail, or a calendar connector. Notification owns connector delivery state, while Opportunity remains owner of the briefing.
Business value: procurement events can appear in the customer's existing work calendar without duplicating tender ownership.