Conclude is a “no-code/low-code” app platform that teams use to implement different workflows and tasks with minimal effort. This section gives an overview of common areas of use. If your planned use is very different from what’s described here, we’re interested in hearing from you.
Conclude comes with a number of blueprints you can use when implementing a specific workflow in any of these areas:
- Incident management
- Handling approvals
- Bug tracking
- Service desk tickets
- Making decisions
This doesn’t mean that Conclude only supports these types of workflows. It also comes with a couple of generic templates that you can use as a starting point for creating your own.
You can make your own Conclude app based on one of the existing app blueprints, or you can create your own from scratch. Conclude is not limited to the use cases discussed here, but can be adapted to any workflow involving information exchange that leads to a conclusion.
Conclude is easy to learn, and you will be able to customize and deploy most of the workflows below in just minutes.
Example: Responding to environmental pollution
When creating a new app for a specific incident workflow, you can start with the generic incident blueprint and customize it.
An app blueprint consists of several fields, called attributes, that capture relevant information about the workflow. You may want to add these fields for an environmental incident:
- Location: Where did the incident happen?
- Severity: What is the impact level? Low, high, or critical?
- Toxicity: Are toxic or dangerous substances involved?
An attribute is a text field or a popup menu with a list of options. Conclude’s interactive app builder lets you customize attributes without writing code.
Example: Handle approval workflows
Conclude’s generic approval blueprint is a great starting point for creating a custom approval workflow with added governance.
As in the example above, you can adapt the blueprint for any type of approval by adding or changing the attributes. However, you want to make sure there’s a real approval process and only certain people have the authority to approve a request.
You can protect any attribute and only give blueprint superusers permission to change them, for example, a manager. The approval can only be closed by a superuser.
Sensitive or confidential matters can be dealt with by using private channels.
Example: Reporting and tracking bugs
There are many great tools for managing software bugs, but most of them are made for engineers. What if you could discuss bugs with the actual users of the software in your organization directly in Slack?
Conclude comes with an app blueprint for bug tracking, which you can adapt and extend for your organization. It’s easier to engage a salesperson or someone in finance in a Slack discussion about a bug they just found, rather than invite them into your specialist tool.
Example: Global security operations center (GSOC)
GSOC is in many ways similar to incidents described above, but incidents often occur in other timezones when people are not in front of Slack. How can you make sure people get notified 24/7?
While attributes would contain information about a security incident, you can create triggers that execute actions based on the user input:
- Invite different people based on the location of the incident.
- Send an email to people outside the company to keep them in the loop.
- Send an SMS to the management team in case of a critical incident.
Yes, Conclude has an escalation path beyond Slack and can send emails and mobile texts to anyone inside or outside your team, automated by triggers and without any bureaucratic delays.
Example: Product decisions
Aside from saving the world, you can use Conclude for daily tasks such as getting feedback on proposals and making decisions faster.
When discussing multiple different issues in the same Slack channel, it’s easy to get lost in the noise. We’re just humans, after all.
Conclude’s proposal blueprint lets you have focused and structured discussions right in Slack, where you discuss and evaluate each idea separately. You can also set a deadline to create more urgency.
Example: Your own workflows (BYOW)
The app blueprints described above provide convenient templates for certain kinds of workflows. They have all been built using Conclude’s foundation of attributes and triggers, to capture information and make sure it flows to the right people.
You can use the same powerful yet simple tools to create your own custom workflows. Do you have a workflow that seems hard to implement with Conclude? Contact us! We’re here to help.