> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/getting-started/getting-started-in-slack/how-to-manage-goals-from-slack.md).

# How to manage goals from Slack

Priorities don't hold still for a whole quarter. A metric gets more ambitious once you see the pipeline, a team reshuffles and someone else owns the work now, the plan changes and the goal should say so. **The short answer** Tell Rhythms what changed in the channel or a DM

`@Rhythms we're raising the Q3 revenue target to $2M`

It shows you the edit before anything saves, and it can tell you whose check-ins are missing.

***

## **Before you start**

* [**Setup Rhythms in Slack**](/getting-started/getting-started-in-slack/getting-started-with-rhythms-in-slack.md)

***

## **Step 1: Update a goal as priorities shift**

## **The target got more (or less) ambitious**

Say what changed and why. Rhythms updates the metric, not just the number.

**Try it:** `@Rhythms we're raising the Q3 revenue target to $2M, pipeline's ahead of plan`

> **Also works**: "drop the activation target to 40%, we cut scope", "push the renewals goal out to Q4"

## **The owner changed**

Reassign it the way you'd tell someone in the room.

**Try it:** `@Rhythms move the onboarding redesign goal to Dana, she's picking it up from Sam`

> **Also works:** "hand the renewals goal to Priya" · "Sam's off this quarter, move his goals to Dana" · "who owns the activation goal?"

## **The goal itself needs to say something different**

Update the title or description when the plan moves, not just the number.

**Try it:** `@Rhythms rename "Reduce onboarding time" to "Cut onboarding time to under 3 days" and update the description, we scoped it down to just the signup flow`

Nothing changes until you confirm. Reply in the thread to adjust anything first. **Tip: Say everything that changed in one message** Meetings rarely change one thing, and Rhythms drafts every edit together so you approve the whole set once instead of going goal by goal.

***

## **Step 2: See what's on track, and what's slipping**

Ask instead of opening the grid.

***Try it:*** `@Rhythms what's at risk this quarter?`

***Try it:*** `@Rhythms why is the onboarding goal at risk?`

Rhythms answers from the current state of the goal, not a snapshot. Ask a follow-up and it can explain the trend or point to what's behind a status.

> **Also works:** "show me my goals", "what's slipped since last week?", "how's the revenue team tracking?"

***

## **Step 3 · Optional: See who has not checked in**

Priorities shift, ownership moves, and check-ins fall behind while everyone catches up. Before you chase anyone, ask Rhythms who is actually behind. Rhythms reports what it finds so you follow up with the right people; it does not message your team on your behalf.

**Try it in a DM:** `@Rhythms who on the revenue team hasn't checked in this week?`

> **Also works**: "which of Sam's goals are overdue for a check-in?" · "what hasn't the revenue team updated in a while?"

***

## **Worth knowing**

**Edits are drafted together, then saved together.** Say six things in one message and you approve one set of six changes, not six separate confirmations.

**This is the same goal as the web app.** Anything changed here shows on the goal in the product, and the other way round.

**A delegate takes over the reminders.** If a goal has a delegate, check-in reminders go to the delegate instead of the owner. Assigning one moves the reminder rather than duplicating it — and unlike an owner change, being made a delegate *does* send a notification.

***

## If something didn't work

**It edited the wrong goal** Say so in the thread and it redrafts against the right one. Naming the goal explicitly in your first message avoids this when you own several similar ones. **It says it can't find the goal** Either the goal is still a draft, or it's worded differently than you're describing it. Try providing more context or use the exact title. **It won't let me change a goal** Slack follows the same permissions as the product. If you can't edit that goal in the web app, you can't edit it from Slack either. **Check-in reminders never arrived in Slack** Check that Slack is switched on as a delivery channel for the workspace: **Settings → Workspace → Notifications**.

***

## Explore Next

* [**Check in on your goals from Slack →**](/getting-started/getting-started-in-slack/how-to-check-in-on-your-goals-from-slack.md)
* [**Work on documents from Slack →**](/getting-started/getting-started-in-slack/how-to-work-on-documents-from-slack.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/getting-started/getting-started-in-slack/how-to-manage-goals-from-slack.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.