A white-label AI employee
for every Linewize IT admin.
Donely proposes to build, operate, and white-label an AI employee that handles the day-to-day work an IT admin does inside Linewize - so the admin never has to log in to the content filter again. Qoria sells it. Donely runs it.
School IT admins spend 20–40% of their day inside the Linewize content filter - triaging teacher requests, tuning policies, verifying safeguarding alerts, and chasing bypass attempts.
Donely will deliver a white-label AI employee that does this work for them. It lives in the messaging tool the school already uses (Teams, Slack, Telegram, WhatsApp), drives the Linewize UI on the admin's behalf, and only pings the admin for a one-tap approval when a human decision is required.
Phase 1 ships in weeks using front-end automation over the existing Linewize UI - no Qoria engineering required. Phase 2 swaps the browser layer for direct MCP / API calls as Qoria ships them. Same product, same UX, lower latency.
We are asking for: NDA, a Linewize QA tenant, and 1–2 pilot districts.
The school IT admin spends 20–40% of their day in the filter.
One person, often one per campus, sitting between teachers, students, parents, principals, and Linewize. Their day is a steady stream of "unblock this for my class," "why is this getting through," and "the test starts in 10 minutes."
They also own the rest of the school network. Every minute they spend triaging filter requests is a minute not spent on the things only a human IT admin can do.
An AI employee, not another dashboard.
The admin keeps working where they already work. The agent does the filter work in the background and surfaces a clean approve/decline only when policy or judgement requires it.
Microsoft Teams, Slack, Telegram, WhatsApp. The admin gets a DM, taps a button, the work is done in Linewize.
Day 1: computer-use over the existing Linewize web app - login, navigate, create policy, set expiry, log out.
If the school has a hard rule (no YouTube during class), the agent auto-declines and tells the teacher why. Admin never touched.
Temporary unblock → time-bound policy → reminder before expiry → reply to teacher when done. One thread, zero context-switching.
Past requests, prior IT responses, classroom calendars, and risk signals - used to suggest the right action, not just any action.
When Qoria opens backend APIs, Donely swaps the browser layer for direct calls. Same persona. Lower latency. No re-training the admin.
A teacher asks. The admin taps once. Done.
Worked example - a teacher requests an unblock 10 minutes before a test.
- 1Teacher posts in Teams
“Need khanacademy.org unblocked for Yr 9 Maths, 11:30.”
- 2Donely classifies & checks policy
Reads the request, checks the school's rules and history, plans the Linewize action.
- 31-tap approval to admin
Telegram DM: “Allow Khan Academy for Yr 9, 11:30–12:30?” [Approve] [Decline]
- 4Agent drives Linewize UI
Logs in as the admin, creates a time-bound policy, sets auto-expiry, signs out.
- 5Closes the loop
Replies to the teacher in Teams. Notifies admin: done. Reminds before expiry.
See it run end-to-end.
Three scenarios, click-through, across the real Linewize UI, Microsoft Teams, and Telegram. Built so Hansa, the Head of Engineering, and the CPO can each walk it themselves in under two minutes.
- YouTube unblock - auto-decline by hard policy
- Gambling-help site - 1-tap Telegram approval, time-bound
- VPN bypass - daily triage + remediation
Qoria sells it. Donely runs it. Schools see Linewize.
Shipped as a managed service under the Linewize brand. Qoria sales enables it per customer in one click - no engineering involvement to onboard a district.
- 1. Qoria sales hands a school an email-gated linkBranded Linewize / Smoothwall onboarding URL.
- 2. School registers - chooses the IT-admin persona“Next → Next → Next”. Enters tenant URL + admin credentials, stored encrypted.
- 3. Connects the messaging tool the admin already usesTeams, Slack, Telegram, or WhatsApp. One OAuth click.
- 4. Agent goes liveFirst alert lands in the admin's DM within minutes. No login, no training, no dashboard to learn.
Ship value now. Re-platform onto APIs when Qoria is ready.
We are explicit with Qoria leadership: no backend APIs exist today, and we are not asking for any. Phase 1 proves the product on the front end. Phase 2 swaps the integration layer underneath, with zero change to the IT admin's experience.
Front-end automation over Linewize
- Computer-use agent drives the existing Linewize web UI
- Map top 5 IT-admin scenarios end-to-end with full QA harness
- Messaging layer: Teams / Slack / Telegram / WhatsApp
- Per-school knowledge base of past requests & responses
- Pilot in 1–2 districts; measure minutes saved / admin / day
MCP / direct API integration
- Donely converts Qoria APIs into an MCP / CLI backend for the agent
- Same agent, same DM UX - browser layer retired
- Sub-second policy actions instead of UI roundtrips
- Login-with-Qoria SSO for onboarding
- All 15+ IT-admin scenarios in production
Three things from Qoria to move forward.
Nothing requires Qoria engineering effort. We are asking for access, not work.
So we can sign NDA, scope, and have a working pilot in front of a real district before the new school year.
Reply with approval to proceedWho builds this.
Donely is a venture-backed team based in San Francisco, building the AI-employee layer for the tools schools and businesses already pay for. We've shipped computer-use agents into production - on real workloads, not demos - and we're bringing that to Linewize.
