Support Agent
Answers every employee question the moment it arrives, on whichever channel it arrived, and never sends an answer it cannot point to a page for. Written for an HR services company where the question "how do I add my newborn?" comes in at 11pm on a Sunday and the person asking cannot wait for office hours. Every answer cites the employer's own handbook, every question the bot cannot settle reaches a specialist with the whole story already written down, and the questions the bot could not answer this week become the answers it gives next week. Six stations, run as a loop: what station 6 learns is what station 3 searches.
{{ g.n }}
{{ g.name }} · {{ g.sub }}
{{ g.desc }}
Subagents ({{ g.acount }})
{{ a.name }}{{ a.code }}{{ a.name }}{{ a.auto }}{{ tk }}
The workbench · subagents send notes, you make the human calls
SUBAGENT NOTES
{{ nt.ini }}{{ nt.who }} {{ nt.text }}
YOUR TASKS · HUMAN IN THE LOOP
{{ g.t1 }}
{{ g.t2 }}
{{ g.tnote }}
{{ g.btn }}
{{ g.wait }}
YOUR TASKS · NONE AT THIS STEP
{{ g.was }}
{{ g.ev1L }}{{ g.ev1V }}
{{ g.ev2L }}{{ g.ev2V }}
{{ g.ev3L }}{{ g.ev3V }}
✓
Cleared for full autonomy{{ g.sign }}
Put a person back on this step
How to read this map
{{ lg.code }}{{ lg.text }}
A person is in the loop wherever a stuck question needs an answer or a new answer is about to reach every employee who asks. Two of the six stations refuse to proceed on their own, Specialist Handoff and Service Review, and those are the two a person carries. Everywhere else the agents run at volume, around the clock, and reach you only when they cannot settle something.
The loop closes
Station 6 does not end the week. An answer signed there lands in the knowledge base Knowledge Search reads at station 3, and a sort change lands in the categories Question Sorting uses at station 2, which is why the same gap only sends work to a specialist twice.