Within your BaaS platform, we continue to develop based on user feedback and situations we encounter in practice. In doing so, we noticed that information regarding work activities and events is often scattered across various systems.
Situation data, for example, is stored in Melvin, while stakeholder communication is subsequently managed manually via other tools or separate emails. As a result, preparing and sending updates often takes more time than necessary, especially when multiple parties are involved.
The new Melvin module originated from that need.
One central workflow around Melvin situations
With the Melvin module, users can view and manage Melvin situations directly within your BaaS platform. Situations are assigned their own detail page where relevant information is centrally gathered.
Consider:
- Title and location
- Periods and closures
- Diversions
- Urgency
- Map information
- Linked campaigns or projects
This provides a better overview of situations that affect accessibility and communication.
Inform stakeholders faster
In addition to insight, the Melvin module is primarily about communication.
Users can compose and send emails from the same environment based on current Melvin data. Selected contact groups or individual contacts can be directly included in the workflow.
This is particularly relevant for organizations that regularly need to inform external stakeholders, such as:
- Emergency services
- Implementing parties
- Collaboration partners
- Stakeholder contacts
Instead of manually transferring information from various systems, a single central working method is created for both situation management and stakeholder communication.
Less switching between systems
In practice, this primarily means less manual work.
Users no longer need to separately look up situation data, rebuild emails, and manually transfer information from Melvin. The relevant context remains available within the same environment where campaigns and projects are managed.
As a result, communication is faster and more consistent, especially in situations where multiple parties need to be informed simultaneously.
From situation to communication
For example, a user can open a Melvin situation within your BaaS platform, select the appropriate stakeholder groups, and enter additional information regarding passage for emergency services or community communication.
Next, a preview is built based on the current situation data, after which the update can be sent directly from the same workflow.
This creates a direct link between availability situations and stakeholder communication, without users having to switch between separate systems or processes.
