Quickstart
This is the whole path — from signing up to your first routed ticket. Most teams finish in under 30 minutes. You’ll connect Slack and your issue tracker, choose which channels Qalibr watches, report a bug, and approve it into your tracker.
You’ll need permission to install a Slack app in your workspace and to connect your issue tracker (Linear today). If you don’t have that, invite whoever does — they can complete the connect steps, and you can take it from there.
Create your account
Go to qalibr.io and start a free trial. Enter your company name and work email — no credit card required. Your 14-day trial is provisioned immediately, and you land on a screen with one button: Add Qalibr to Slack — the first of three quick setup steps your dashboard tracks for you.
Connect Slack
Click Add Qalibr to Slack and authorize the app in your Slack workspace. This is how Qalibr receives the bugs your team reports. Slack is the only place Qalibr reads from today — it never posts or listens anywhere you haven’t connected.
Connect your issue tracker
Next, connect the tracker where bugs should land. Today that’s Linear: authorize Qalibr to create and update issues in your Linear workspace. This is where approved bugs become tickets.
Linear is the supported tracker today. Jira, GitHub Issues, and GitLab Issues appear in the integrations list marked Coming soon.
Choose the channels Qalibr watches
Pick the Slack channels Qalibr should listen on — for example #qa-bugs or
#support. Qalibr only reads the channels you select; everything else in your
workspace stays untouched. You can change this selection any time from
Settings → Integrations.
Report your first bug
In one of the watched channels, post a bug and mention @Qalibr in the
message — for example:
@Qalibr Checkout spins forever after you tap "Pay" on iOS — happens every time
on the latest build, started this morning.Mentioning Qalibr is the trigger. (Prefer a keyword to a mention? An admin can
switch the trigger to a keyword — !bug by default — in your intake settings.)
Watch it get triaged
Open your dashboard and go to the Inbox. Within seconds your bug appears as a row with a Signal score (0–100) and a severity. Behind that row, Qalibr has read the report, scored it, checked it against everything it has seen before, and enriched it into a clean, structured write-up.
Approve it into your tracker
Open the bug to see the full Report and the Signal score breakdown. If it’s a real bug, click Approve — Qalibr routes it to Linear and confirms with the ticket it created (for example, Approved · routed to ENG-412). If a close duplicate already exists, Qalibr surfaces the closest match and can link to it instead of opening a second ticket — your call. Not a real bug? Click Reject with a short reason — nothing is created.
That’s it
You now have the full loop running: bugs reported in Slack arrive triaged and scored in your dashboard, and reach Linear only when you approve them. From here:
- Learn how the scoring and deduplication work in Core concepts.
- See every dashboard surface in The dashboard.
- Manage connections, approvals, and your data in the Reference.
Stuck on a step? Your dashboard tracks setup progress — connect Slack, connect a tracker, and process one bug to light up all three. Questions any time: contact@qalibr.io.