Atlas in Slack
Most problems get noticed in the middle of something else — a front-desk person spots a wrong price while checking a client in, a provider notices a form isn't sending while they're between appointments. Asking them to stop, open a separate tool and write a report means most of what they notice is never reported at all.
So Atlas sits in your Slack instead. Invite it to a channel, describe the problem in the channel you already use, and it takes it from there.
Get it into a channel
Invite Atlas to any channel the way you'd invite a colleague. It only sees channels it has been invited to — it cannot read the rest of your workspace, and it does not watch direct messages.
Most organizations use one channel for this, often something like #ready-practice, so reports stay in one place and colleagues can see what has already been raised.
Reporting something
Describe the problem the way you'd describe it to a co-worker. You don't need a format, and there's no ticket template to fill in.
Atlas reads what you wrote and does three things: works out what kind of report it is, checks whether it's already been raised, and replies in the thread. If the report is already tracked it tells you so and links the existing one, rather than creating a duplicate that splits the conversation in two.
If something essential is missing — which client, which screen, what you expected instead — it asks in the thread. Answer in the same thread and it picks the answer up.
If you can see the problem on screen, post the picture. "The price shows $0" plus a screenshot of the screen showing it is far faster to act on than either alone.
Atlas can read a client's record when you ask it to inside Ready Practice, where the request is permission-checked and audited. A Slack channel is different: anyone in that channel can read it, and it stays there. Describe the problem without the identifying details — "the intake form isn't attaching for a new client booked on Tuesday" says everything needed, without naming anyone.
What happens after you report
Your message becomes a tracked item, and the thread stays attached to it — so follow-up questions land back in the channel you're already reading rather than an inbox you're not.
When something is fixed, the person who reported it is told. You should not have to remember to check.
Asking rather than reporting
Atlas answers questions in Slack too. "How do I put a client on a payment plan?" gets the same answer it would give inside Ready Practice, drawn from the same documentation.
The difference is context. Inside Ready Practice, Atlas knows which client's screen you're looking at and can act — book, draft, change a schedule. In Slack it has no such context and cannot make changes. Ask Slack "how does this work", and ask Atlas inside Ready Practice to actually do it.
Next steps
To have Atlas do things rather than describe them, use it inside Ready Practice — see Meet Atlas, which covers what it can act on directly.
To understand what it reads when answering "how do I" — it uses this documentation, so a gap in these pages is a gap in its answers. If it ever tells you something is impossible that you know works, that's worth reporting in exactly the same way.