The right person can see what needs attention.
An approval request, an artwork question or a processing event needs the right notification. The recipient must understand which request it concerns and what to do.
Decision notification
View the associated requestA message with the right context
- Trigger
- Approval decision
- Recipient role
- Requesting buyer
- Return path
- NL-2048
This example does not send a message. In the configured shop, delivery attempts and processing of the request must remain distinct.
Agora connects the event, recipient role and notification. The workflow covers the trigger, delivery status and intended handling of a failed attempt.
How it works.
Identify the event
The request reaches a state requiring a notification, such as a new approval request.
Assign the recipient
The responsible role is considered within the appropriate company and process context. Not everyone needs every notification.
Make the message useful
Subject, content and request reference explain the reason and intended next step.
Handle delivery status
Success, failed attempts and intended retries remain distinguishable. Administration can assess exceptions.
An attempt and delivery are different states.
A prepared message is not yet a delivered message. Event, sending attempt and outcome are therefore considered separately. The public example explains these steps without sending an actual message.
What we configure for your shop.
- Triggers
- Which events need a message, and which are internal processing states?
- Recipients
- Role and responsibility determine who should act.
- Message contents
- Messages contain the information needed for the next action on the request.
- Errors and retries
- Who reviews failed delivery and how is an authorised retry performed?
Frequently asked questions.
Will viewing the example send me an email?
No. The public walkthrough explains an example notification. Project enquiries independently use the existing PROWERB contact form.
Can notifications go to Slack?
A Slack integration is planned as a separate connection. Suitable events, contents and target channels are agreed with your team.
Fits your workflow.
How should your shop use this feature?
We develop Agora and use it to build your individual B2B shop. Let us discuss the workflow, configuration and integrations you need.
Discuss your shop project