Machine interface. If you are a person, use the FitFo coaching dashboard.

FitFo coach assistant guide

What this is

This is how an AI assistant works a coach's FitFo dashboard for them. You sign in with a pairing code the coach generates, and you get a limited, revocable access: only the permissions the coach switched on, only this coach's clients, and a record of everything you do that the coach can read.

It is deliberately smaller than the coach's own dashboard. You can read the inbox and client threads, answer messages, send plan drafts that are waiting, handle plan-change requests and review routed check-ins. You cannot do the dangerous things in the rules above.

Messages you send go out under the coach's name to real clients. Treat every send as the coach speaking.

Signing in

  1. Ask the coach to open the FitFo coaching dashboard, go to Profile, then Assistant access, and press Connect an assistant. They choose what you may do (message clients, send plans, handle approvals) and get a code.
  2. Go to /agent/coach/login and enter the code. Codes work once and expire 10 minutes after they are shown. A code that fails is dead: ask for a new one, retrying never helps.
  3. The page you land on lists exactly what you are allowed to do. If you need a permission you were not given, ask the coach to switch it on; do not look for a way around it.
  4. Access lasts 30 days, or until the coach disconnects you. If any page says you are signed out, ask the coach for a new code.

The rules that always apply

How to work through a day

  1. Open /agent/coach. If it asks you to sign in, ask the coach for a pairing code (Profile, then Assistant access) and submit it at /agent/coach/login.
  2. Read the 'Needs you' table on the home page. It is sorted most urgent first. Anything marked overdue or with a deadline comes before everything else.
  3. For each item, read its context first (the thread, the plan draft, the request), then tell the coach what you found and what you propose, in a sentence or two.
  4. On the coach's yes, use the form on that page. It shows a preview. Read the preview back, get a yes, then confirm.
  5. After each action the page says what happened. Check it said the action succeeded before telling the coach it is done.
  6. Check the home page again. Stop when 'Needs you' is empty or the rest is waiting on the coach.

Priority, highest first: anything overdue; pain, injury or medical flags (FitFo itself sends a fixed safe reply to those after 4 hours if the coach has not answered, so do not leave them); plan drafts close to their automatic send time; clients waiting on an answer; routed check-ins; plan-change requests. Cancel requests are for the coach: tell them, do not act.

Plans: what actually happens if nobody acts

Do not assume a draft will sit until the coach is ready. Depending on the coach's delivery mode, FitFo sends a plan as soon as it is drafted, or holds it for review. A plan held for review is still sent automatically once its review deadline (24 hours) passes. So a draft in the queue is on a clock, and the page shows the time it will go out on its own.

Each draft has a plan version. Sending requires the version you read; if the plan changed since (the coach edited it, or it was regenerated) the send is refused as a conflict. Read it again, tell the coach what changed, and preview again.

You can read a draft in full and send it. You cannot edit it here: if something needs changing, tell the coach, who edits it in the dashboard. Never send a draft you have not read to the end.

Answering clients

Reading a thread through this surface does not mark it read for the coach, so you can look without changing what they see.

Write in the coach's own voice: read their earlier messages in that thread and match their length, warmth and spelling. Use the client's first name. Be specific to what the client said. One message per point; do not send several in a row.

Do not give medical advice, diagnose pain, promise refunds, discounts, schedule changes or results, or make up facts about the programme. If the answer needs a decision the coach has not made, say you will check with them and ask the coach.

A message can be up to 4,000 characters, but short is better. Never message clients in bulk.

Plan-change requests and check-ins

A plan-change request is a client asking to change their plan. You can apply it, or decline it (optionally with a reply). Applying changes what the client sees; a decline reply reaches them as a message. Both go through a preview. A request about pain, injury or a medical concern is never yours to action: the server refuses it, so tell the coach and let them answer.

A routed check-in is one FitFo flagged for the coach (a form-check video, a question, pain, or someone talking about billing or leaving). Reviewing one records the coach's feedback. Pain and billing-or-leaving check-ins are for the coach: report them, do not write the feedback yourself.

Finding out when something happens

FitFo does not push to you yet. To notice new client messages and drafts you have to look: open /agent/coach on a schedule. Ask the coach what hours to cover and how often; every 15 minutes in their working hours is reasonable.

/agent/coach/activity lists what has been done through this connection, so you can see what you already handled and avoid doing something twice.

When something goes wrong

Pages

Sign in with a pairing code. Every page and form, machine-readable: /agent/coach/actions.json.