The Ops Scorecard shows how each operator uses the platform. It counts the AI drafts
they actioned and how fast they answered. It also shows how much of the AI's work is being used at
all. It needs a manager login.
Open the scorecard
Why this matters: it is the only screen that measures the people side of the
system rather than the properties.
Sign in at app.hostassist.ai with a manager account. A specialist login opens the address but sees an empty page. That is a permission limit, not a bug.
Click Operations in the left menu, then click Ops Scorecard. You should see a page headed Ops Scorecard, with four tiles and a table below them.
Step 2Window selector top right, four tiles, then one row per operator.
Choose the window
Why this matters: every number on the screen is counted inside the window you
pick, including the table.
In the top right, click 7d, 14d, 30d or 90d. 30d is selected when you arrive. The table heading changes to match, for example operators, last 30 days.
Use 7d for a stand up and 90d for a review. Short windows on a small team swing a lot, so do not read a 7d dip as a trend.
Steps 3 and 4One control, four choices. Everything below it obeys the choice.
Read the four tiles
Why this matters: adoption is the number that says whether the AI work is
being used or quietly ignored.
Read active operators, shown as a count out of the team size. 0 of 4 means nobody on the team actioned anything inside the window.
Read drafts actioned and the small line under it. The line gives the total drafts created in the window, which is the pool the count came from.
Read draft adoption and pricing adoption. Adoption is the share of drafts that reached an outcome and were actioned by a person rather than left to expire.
Read the sentence under the tiles. It splits the guest lane and the pricing lane into ignored, auto sent or auto approved, and still waiting.
Steps 5 to 8No decided items yet means nothing has finished, so a percentage would be made up.
Step 8The definition sits on the screen so nobody has to guess what adoption counts.
Read the operators table
Why this matters: this is where a team average turns into a name, which is
the only level where you can actually coach.
Find the operator you care about in the left column. Each row shows their role badge and their email under the name.
Read approved, edited, rejected and escalated across that row. Those four count guest message drafts the operator actioned.
Read the pricing column next to them. It counts pricing queue decisions, kept apart from guest drafts on purpose.
Read median response and median pricing. Median response is the middle time from a draft being created to the operator acting on it.
Read team share and last action on the right. Team share is that person's slice of the team's actioned work in the window.
Steps 9 to 13A dash in a cell means no data yet in this window. It does not mean zero performance.
Three things that catch people out
A dash and a zero are different answers. A zero is a measured none. A dash means there was nothing to measure.
Machine and probe accounts appear in the table alongside people. Check the email before you read a row as a colleague.
Adoption only counts drafts that reached an outcome. Drafts still waiting are not in the percentage yet, so a fresh window can look empty.
Why adoption is measured, and not just volume
Counting drafts sent flatters the system. If the AI writes a hundred drafts and every one is
ignored until it expires, the volume looks healthy and the product is doing nothing.
Adoption asks the harder question: of the work that reached an ending, how much did a person
actually use. That number moves only when the AI is genuinely helping somebody.