How to contact Rhythms support

There are two ways to reach the Rhythms support team. Both go to the same place — use whichever is easier.

From inside Rhythms (fastest)

Click Help at the bottom of the left sidebar, next to My connectors and Settings. This opens a message window without leaving the app, and automatically includes details about your workspace, so there is less for you to explain.

If you do not see Help in your sidebar, use email instead.

By email

Write to support@rhythms.ai from the address you use for Rhythms. Emailing from a different address slows things down, because we cannot immediately tell which workspace you belong to.

Best practices for getting a fast answer

Support can usually resolve an issue in one reply if the first message answers three questions: what you were doing, what you expected, and what happened instead. The rest of this section is how to make that easy.

Describe the outcome, not just the symptom

“Check-ins are broken” takes several rounds to pin down. “I submitted a check-in on OBJ-014 and the progress bar still shows last week's value” can often be answered immediately. Name the thing you were working on and what you saw.

Give us a way to look at it ourselves

• Paste a link to the goal, document, view, or page. This is the single most useful thing you can include — it tells us the workspace, the record, and the context in one step.
• Include the short ID if it is a goal, for example OBJ-052 or KR-118.
• Add a screenshot when the problem is visual — a layout issue, an unexpected number, an error message. Capture the whole window rather than a tight crop, so we can see where you were.

Tell us the scope

Whether something affects only you, your team, or everyone in the workspace changes how we investigate and how urgently we treat it. If you know that a colleague can reproduce it, say so.

Say when it started, and what changed

If it used to work, roughly when did it stop? If it began after a specific action — a new integration, a permissions change, an import — mention that. Recent changes are usually where the answer is.

Things that slow a request down

• Multiple threads for one problem. Keep a single issue in a single conversation so the history stays in one place.
• Screenshots of text. If you have an error message, paste the text as well — we can search it.
• Emailing from a personal address. Use the address you sign in to Rhythms with.
• “Let me know if you need anything else.” Rather than waiting to be asked, include what you have up front — even a partial description with a link beats a perfectly worded message that arrives two days later.

For anything urgent

If work is blocked for a group of people, say so explicitly in the first line. We prioritise on impact, and we cannot see that unless you tell us.

Requesting an API token

API tokens are issued by support rather than self-serve. When you ask for one, tell us:

• Whether the person who needs the token is a workspace admin or a member
• If they are a member, their name and email address

Admins receive a token scoped to the whole organization; members receive one scoped to themselves. For what you can then do with it, see Accessing and Integrating with the Rhythms REST API.