Support · Hilfe

Every request enters through one door and climbs only as far as it must. Each rung carries its target time, the number of requests standing on it right now, and how many of those have passed that target. Safety skips straight to rung 4. Press a rung to open what is on it.

Students and families press one button; it calls raise_help_request, opens the request and notifies every active admin and staff member. This is the console's half of that: what each press becomes, how many arrived today, and the second door — somebody on the telephone.

The routing decision is not a black box and not a model: it is the matrix below, read out of this organisation's settings and applied by the same function that draws every rung and every countdown. Ariadne classifies and drafts — she decides nothing here.

The working view. Filters are predicates on the query, the header counts come from the server, the clocks tick against each rung's target, and every assignment, reply and closure is a write the rest of the team sees.

A handover is two writes and one promise: the owner changes, the reason is recorded with the previous owner's name, and nobody is asked to repeat their story. The briefing and the transcript sit in the pane above — these are the rules they follow.

Read at three in the morning by somebody who was asleep ninety seconds ago: absolute times, named people, and what happens next if nobody does anything.

Same engine, different door — and the policy that enforces each one, so a wrong line here is a migration and not a paragraph.

She is invited, never lurking. She reads this request with your permissions, answers with a trace, and hands back a draft — C2, which means a person approves it before one word reaches a family.

Ask her about this request

C2 · Act with approval

Select a request in §D. She answers about one case, not in general.

Rules of summoning

Invited, never lurking. She reads this request only when you press the button, and the record says she did.

Caller’s scope. She answers with your permissions — your session token goes with the question.

Draft, not send. C2: the words reach nobody until a person presses send in §D.

Every command has a manual twin. The composer and the block builder in §I do all of this without her.

She runs on this server’s ANTHROPIC_API_KEY. Without one she says so in as many words and this queue carries on without her — which is the test that she is an accelerator and not a dependency.

A reply can carry an appointment, a document, a place, a form or a status. Built here by hand — no model involved — and attached to the reply in §D, where a person presses send.

Beside the conversation sits the person, read live. What your role may not see is shown as a locked row with the reason — never omitted, so nobody wonders what they are missing.

Nobody edits somebody else's record silently. You ask its owner, with a reason and a deadline, and the ask becomes a request in the same queue with the same clock — because a promise tracked somewhere else is a promise nobody keeps.

Measured on outcomes, not activity. A rising request count is not failure; a rising time to a human when one was needed is. Every figure opens the requests it was counted from.