Basic Commands

Basic Commands

Quickly takes plain language, not a command syntax. There are no flags to memorise and no fixed word order. What follows is a map of the things teams ask for most, and the details that change the quality of the answer.

How Requests Work

Address Quickly the way you would address a colleague. In the dashboard, type into Chat. In Slack, mention it: @Quickly summarize this thread and open a ticket.

Quickly reads your request, decides which of your connected tools it needs, and either runs the work or asks for approval first depending on your workspace's autonomy mode. Read-only requests never need approval.

Creating Work

@Quickly create a bug in MOBILE about the Safari login crash
@Quickly open a task from this thread and assign it to Sarah
@Quickly file a High priority incident for the checkout outage

Naming the project key, the issue type, and the priority up front saves a round trip. Anything you leave out, Quickly either infers from the conversation or asks about.

Finding Things

@Quickly what is the status of PROJ-123?
@Quickly show open High priority bugs in MOBILE
@Quickly list the issues assigned to me this sprint

Searches are read-only, so they run immediately in every autonomy mode.

Updating Work

@Quickly move PROJ-123 to In Progress
@Quickly add a comment to PROJ-123: root cause found, fix in review
@Quickly assign PROJ-456 to michael@example.com
@Quickly set PROJ-789 to Highest priority

Producing Documents

@Quickly draft a postmortem in the ENG space for this incident
@Quickly write up this thread as a decision record

Asking What Is Possible

@Quickly what can you do? returns capabilities based on the integrations you have connected, not a generic feature list. Two people in the same workspace can get different answers.

Getting Better Results

• Reply in the thread. Quickly uses the surrounding conversation. A mention in the main channel gives it far less to work on.
• Name the destination when you know it. "in MOBILE", "in the ENG space", "to Sarah" all remove a guess.
• Describe the outcome, not the tool. Quickly picks tools from what you have connected; naming an internal tool name is not necessary.
• Ask follow-ups in the same thread. Quickly keeps the task context, so "actually make that Highest" works without repeating the issue key.
• Check the log when a result surprises you. Action Logs shows the exact tool calls behind any answer.

Where Defaults Come From

If your team always uses the same tracker or the same conventions, an Admin can write that into the workspace instructions rather than everyone repeating it in every request. See Channel Defaults and Instructions.