How to collect requests from your team without another form tool
New laptops, a broken monitor, a parking spot, a software licence. The usual ways to collect requests from coworkers, what each is good at, and a page your agent writes that knows who asked, shows each person their own requests, and grows into an app when it needs an approver.
Every office has a queue of small requests. A new starter needs a laptop. A monitor in room 4 flickers. Someone wants a licence for a design tool. Someone else needs a parking pass for a month. The requests arrive in chat, in email, in the corridor, and the person who handles them keeps the list in their head or in a spreadsheet only they understand.
The obvious fix is a form. This article looks at the usual ones fairly, and at what a request queue needs that a form doesn't always give it. We make Spryloom, and the last option is ours, so read that section knowing who wrote it.
What a request queue actually needs
Collecting the request is the easy part. A queue that works for a team does four things:
- Knows who asked, without a typed name. Anyone can type anyone's.
- Shows each person their own requests, and whether each is done. That ends "did you get my request?"
- Shows the handler everything, in one place, with a way to mark each one done.
- Keeps requests private. A chair request can mention a medical reason; a software request, a client.
Option 1: Google Forms or Microsoft Forms
If your company is on Google Workspace or Microsoft 365, you already have a form tool, and that counts for a lot. Both can be limited to people in your organisation and can record the address of the person responding, so "who asked" is handled. Answers land in a spreadsheet, which the person handling them already knows how to use.
Where it strains is everything after the form is sent. The requester gets a confirmation and no page of "my requests" with their status. The handler adds a "status" column to the response sheet by hand, and telling someone their laptop is ready is an email you write yourself. For a few requests a month, that's fine. For a steady stream, the sheet becomes the tool, and it wasn't built to be one.
Option 2: Typeform and similar
Typeform and tools like it make forms people enjoy filling in: one question at a time, branching logic, good design, and many integrations. For anything that faces customers, they're often the best choice.
For an internal queue, the trade-offs are different. It's another account, often another paid seat, and respondents usually aren't signed in, so "who asked" is whatever they type unless you set up more. The answers still go somewhere else to be worked.
Option 3: a helpdesk or ticketing tool
Jira Service Management, Zendesk, Freshservice and tools like them are built for exactly this, at volume: queues, statuses, assignment, service levels, a portal where people see their own tickets. If an IT team handles hundreds of requests a month, this is the honest answer, and you should use one.
For a 30-person office where one person handles a dozen requests a week, they're a lot to set up, and everyone who works the queue usually needs a seat.
Option 4: a page that saves data
This is what we built for the space between a form and a helpdesk. Your coding agent writes the request page you have in mind, and Spryloom keeps the records, signs people in, and stamps each request with who sent it. There's no server and no database to set up.
Ask
Dana is the office manager at a 30-person company. In Claude Code, Dana asks: "Make a page where people can send office and IT requests: what they need, which category, how urgent. Each person should see their own requests and whether they're done. I need to see all of them and mark them done."
The agent writes the page and declares one list in spryloom.yaml:
runtime:
frontend: static
backend: none
data:
lists:
requests: own- A page, not an app.
- Built files only.
- No server to run or set up.
- Spryloom keeps the records.
- One list.
- own: each person sees their own; the owner and admins see all.
own is the important word. It is the privacy rule from the list above, enforced by Spryloom when the page asks for records, not by the page hiding rows.
Know who asked
The form has no name field and no email field. When Sam sends "Monitor in room 4 flickers", Spryloom stamps the record with Sam's email and the time, from Sam's sign-in. The page can't get it wrong, and nobody can send a request as someone else.
Only the person who saved a record, or the page's owner and admins, can change it. Sam can edit or withdraw Sam's own request, and Dana can mark it done. Each change is stamped with who made it and when.
Publish and invite
The agent publishes the page, live in seconds behind sign-in, and asks who it's for: people Dana invites, or, if Dana signed in with a work address whose mail runs on a service such as Google Workspace or Microsoft 365, anyone at the company. With a personal address such as Gmail, invite people by name:
spry invite office-requests --email sam@yourcompany.com --email alex@yourcompany.com
Each person gets an email with one button that signs them in. There's no account to create and no password.
Subject dana@yourcompany.com invited you to Office requests
You have been invited to Office requests
dana@yourcompany.com invited you to use it.
What it does: Office and IT requests.
Open Office requestsIt signs you in as sam@yourcompany.com. It works once, for 7 days; after that, sign in with an emailed link.
Read the queue
Dana works the queue in the page itself. Outside it, spry data office-requests shows how many requests the list holds, and spry data export office-requests saves every one as JSON and CSV, with who sent it and when, for the end-of-quarter "what did we spend on equipment" question.
Grow, when it needs an approver
A few months in, Dana's manager asks for something a page can't do: "Anything over $500 should go to Chris for approval, and Chris should get an email when one is waiting." That needs a server and a schedule. The agent adds them, along with a database and email: true, and the next publish turns the page into an app at the same address, with the same people. Every saved request is copied into a table named page_requests in the app's own database.
From there, the app can send Chris one email a day saying how many requests are waiting, with a button that opens the approvals view. How that works is in how to send a daily email reminder, and the approval flow itself is in how to build a purchase approval app with an AI agent.
What it doesn't do
- No email from a page. A page that saves data keeps records. It doesn't email Dana when a request arrives, or Sam when it's done. That's an app's job, and the move is one publish.
- No file uploads. People can't attach a photo of the broken monitor. Uploads aren't available, so ask for a description instead.
- No rules on a server. The page can't enforce "requests over $500 need approval" beyond what its own script does. When a rule matters, it belongs in an app.
- Not a helpdesk. No service levels, no assignment between several handlers, no reporting beyond what your agent writes. If requests outgrow one or two people, a ticketing tool is the better fit.
- For people you know. Everyone who sends a request is invited or at your company, and signs in first. It isn't a form for the public.
Which one to pick
Start here
In Claude Code, add the plugin once:
/plugin marketplace add spryloom/claude-plugin
/plugin install spryloom@spryloom
In Codex:
codex mcp add spryloom -- npx -y spryloom mcp
Then ask: "Make a page where my team can send office requests. Each person sees their own; I see all of them. Publish it with Spryloom." The agent picks a page that saves data when a list is all it needs, and says why.