The product guide

There is a guide button in the header on the screens that have one. It answers questions about how Protocol works, on the screen you are standing on, in the words the help center uses.

It is software, not a person, and it says so at the top of the dialog. That matters for what you should expect from it, so this page is mostly about where the line sits.

Where it appears

Look for the guide icon in the row of icons at the top right, beside support.

It is deliberately not on every screen. It appears where the help center covers the subject properly, which today is your dashboard, your client list, the client record, tracking, plans, chat, your content library and the shop. On any other screen there is no button at all rather than one that opens and has little to say.

It never opens on its own. Until you have opened it on a screen the button pulses gently to say there is something there; once you have, it stops for good and sits quietly in the header for whenever you want it.

What it answers

Questions about how the product works. How to assign a plan, what a status means to your client, why a panel is not showing, what a control does before you press it.

It answers in the same shape each time: a short paragraph, then numbered steps when there are steps, then links to the screen it is talking about. Underneath it offers three follow-up questions, which are usually faster than typing.

If it cannot answer, it says so in one sentence rather than guessing, and offers to pass the conversation to a person. That opens a support ticket with the conversation already in it, so you do not retype the question and whoever picks it up can see what the guide already tried.

Where its answers come from

This help center, and nothing else.

The guide reads these pages and quotes them back at you. It has no access to your clients, their data, your messages or your files, and that is a property of how it is built rather than an instruction it has been given: the request it makes carries the screen you are on and the words you typed, and nothing else exists for it to send.

So it can tell you how the tracking tab works. It cannot tell you what Sarah’s last check-in said. For that, open Sarah.

Answers cite the pages they came from, and you can open any of them.

What it will not do

• It will not read a lab result or a biomarker for you. Protocol shows where a number sits relative to the range the laboratory printed. What it means is a conversation for your client and their doctor, and the guide will not step into it. See Reading lab results.
• It will not give training or nutrition advice. It explains the product. You are the coach.
• It will not describe a screen that does not exist. If the help center does not cover something, it says so rather than inventing a plausible-sounding button.

A note on cost

Asking the guide does not spend your AI credits. Protocol pays for it, because the product teaching you to use it should not come out of the budget you bought for your clients.

There is a daily limit, which scales with your plan, and it is high enough that you are unlikely to meet it while genuinely working. If you do, the guide keeps answering with the help center pages that match your question. It stops writing an answer; it does not stop helping.

Its answers are as good as these pages

The guide is this help center with a search engine and a writer attached. When it cannot answer something, that is usually because the page it needed does not exist yet, and we see those misses grouped by subject each week. If it gives you a poor answer, the thumbs down is worth pressing: it goes into that list, and the fix is a new page rather than a nudge to the guide.