Run many client stax
The coach board is one read across every client stax you run. The ones that need a push come first, each with the next move.
Why it matters to you
You coach eight clients. Each has a stax, a goal and a bot sending for them. On Monday you do not want to open eight boards to find the one where a reply sat unanswered since Thursday.
How to do it
- Name your clients. With your own token, ask your AI app to run
coach_board_configurewith each client stax and the client’s handle, such as@rahul. - Read the board. Ask for
coach_board. Rows come ranked: needs a push, then moving, then closed. - Make the move. Each row leads with one verb-first move and who makes it: you, the client or a role. Its one-tap routes name the call to make.
- Nudge the client. The nudge route comments on the row’s card, in the client’s Telegram group if the stax has one.
Why a row needs a push
| Reason | Means |
|---|---|
| Blocked card | A card is blocked, failed, escalated or waiting for a go-ahead |
| Reply waiting | A prospect replied after the last send |
| No goal | The stax has no open goal |
| Silent 48 hours | Nothing moved on the stax for two days |
| No outreach in 7 days | No send recorded this week |
Each row also shows this week’s sends and replies, and the stax’s spend this month. A row closes when a campaign membership reaches won. There are no countdowns or alarms.
An agent sees only the client stax its grants let it read. The rest are listed as left out, with the reason.
Now you can open one list on Monday and push the right client first.