This quickstart guide gets you started with Conclude and demonstrates how quickly you can deploy custom apps for your team by using visual tools. If you are just interested in using apps, then read the first two sections and skip down to Using Conclude app.
Sign in to Conclude with Slack
Click Sign In at the top of this page to sign in. If there’s a Home button there, you’re already signed in and can skip this step.
After you authorize Conclude as a Slack app you will be redirected back to this page where you can continue with the next step.
If you’re having trouble with this step, check with your team admin. You may need to request approval to add Conclude depending on your team’s Slack permissions settings.
After signing in, you will be redirected back to this page to continue with the next step.
Open Conclude Home
Conclude Home is your Conclude command center in Slack where you can install and run apps, and view recent activities.
After you sign in you should see a Conclude Home button at the top of this page. If not, try reloading this page.
Click the button to go to Conclude Home, or locate Conclude in the Slack sidebar, under Apps.
If you have problems finding Conclude Home in Slack, type
/c home to get a link.
Conclude Home has four sub menus:
- Dashboard displays recent activities, upcoming deadlines, and urgent issues.
- Activities contains a list of open and closed activities.
- Apps shows information about installed apps, and lets you create new apps.
- Help is a rich collection of documentation and resources.
Conclude Home will have an empty dashboard if you are the first person to use Conclude on your team.
If someone on your team has already created apps, and you are eager to start using them, go straight to Using Conclude apps.
Create a custom app
We will create an app that helps us manage incidents that happen at our office, so we can become better organized and fix problems faster. The app should have a severity level setting so we can prioritize serious incidents that could block our work, and set deadlines for time-sensitive issues. We will start out with the incident app blueprint, and use visual tools to customize and deploy our app.
There are a few things you need to consider when deploying an app:
Where should you install the app? You can install a Conclude app in any private or public Slack channel. We suggest creating a new channel where you can invite colleagues for testing your new app.
Which app blueprint do you want to use as a starting point? Conclude comes with a number of app blueprints that you can build your app from. In this case, we will use the incident blueprint that works well for all types of incidents.
Who should have access to the app? You can make it available to the entire workspace (global), or just to the people who are members of #office-incidents (the default setting). We’ll stick with the default setting for now, but you can change this later.
Customize and install the app in two steps
First create a new channel, for example #office-incidents, where you will install the app.
In Conclude Home, click the Apps menu to go to the page where you can see installed apps, then
click the Install App button. Alternatively, you can use a Conclude Slack
/c app install incident #office-incidents to open the installer
with a pre-selected blueprint and channel.
Conclude will open a dialog that lets you install the app in two steps.
Step 1: Choose a channel and select the incident blueprint.
Step 2: Change the blueprint’s default settings that works for your new app:
- Give the app a name, for example abbreviate “office incidents” to “oi”.
- Change the label, description, and launch button text.
Click Install to complete the process and install your app in the #office-incidents channel.
That’s it! You have just deployed a custom app, and the team can start using it right away.
Head over to Conclude Home > Apps to see your new app:
Using Conclude apps
Anyone who is a member of the #office-incidents channel can use the office incident (“oi”) app to report office incidents.
There are several ways to launch the app:
- Click the app’s launch button in Conclude Home > Dashboard or Conclude Home > Apps.
- Type the Slack command
/c oianywhere in Slack.
/c[enter] to get a list of installed apps:
Clicking Report Incident will open up a window where you can enter information about a new incident.
When you submit the incident, your app will do the following:
- Send an alert to #office-incidents about the new incident.
- Create a dedicated activity channel #_office-incidents-1 where the team can focus on this incident.
Other incidents will get their own activity channels, #_office-incidents-2, #_office-incidents-3, etc.
- Automatically invite everyone in #office-incidents (where you installed the app) to the activity channel.
The new incident will appear as a new activity in Conclude Home > Activities:
Click on the “Coffee machine broken” or the channel link #_office-incidents-1.
At the top of the activity channel you’ll find information fields (called attributes) describing
Click Edit to update any attribute.
Attributes capture important information about an incident; you don’t have to read through the entire discussion to get the big picture.
Aside from the live attributes, #_office-incidents-1 is a regular Slack channel where the team can discuss and resolve the incident.
After the team has concluded the discussion and resolved the issue, click Conclude and enter a conclusion:
- Once you’ve done this, the activity will close and the channel will be archived. The activity will disappear from the channel list.
- The app will send a message (alert) to #office-incidents, notifying that the incident has been resolved.
- The closed activity is still available in Conclude Home > Activities and in Conclude Inbox.
Further customization and development
Conclude is a no-code development tool, and you do not need to be a software developer to add advanced features to your app.
Here are a few ideas for further development:
- Add an attribute where the user can specify the building or location of the incident from a list of choices.
- Invite different members to the activity based on the building/location.
- Change the activity channel name to something more intuitive.
- Only give certain team members the permission to conclude and close the activity.
- Escalate the incident by sending a mobile text message to a manager if the severity level is ‘critical’.
Take a look at the developer’s guide to learn more.