Use Case · Internal Requests
Ops requests without
the Slack thread graveyard.
Small ops teams describe an internal request form in Claude or ChatGPT, get a live URL back, and read incoming IT, HR, and finance requests by asking their AI. No Jira, no ticket system, no Slack DM chain.
Why internal ops requests always end up in Slack limbo
The usual pattern: someone needs a software license, a desk swap, a contract signed, or an expense reimbursed. They post in Slack. The ops person sees it, thinks “I'll get to that,” and then it disappears under 40 other messages. Three days later, the requester follows up. The ops person apologizes and handles it, but there's no record of what was requested, when, or by whom.
At five people this is annoying. At twenty it's a liability. HR requests get missed. IT tickets stack up. Finance reimbursements slip past month-end close. Every team eventually tries a ticket system, then gives up because Jira is overkill for a 10-person company and nobody fills in the fields correctly anyway.
Brieform sits in the middle. Structured enough that you always get the right information, simple enough that teammates actually use it. One link, one form, one row in the Brieform dashboard per request. Since you can read those requests by asking your AI, you don't need a ticket system to keep up.
What a Brieform internal request form does
How a Brieform request flow works
- 1
Teammate opens the internal request link, pinned in Slack or your Notion workspace
- 2
Selects request type (IT, HR, Finance, Facilities, Other). Conditional fields appear based on their choice
- 3
Marks priority (Urgent / Normal / Low) and fills in the relevant details
- 4
On submit, they see your success message: "Request received. Reference #042. Expected response: 1 business day."
- 5
When you next open Claude or ChatGPT, you ask: "Show me today's urgent requests". Your AI calls get_responses and returns them inline
- 6
You ask the AI to forward the urgent IT request summary to #it-ops. If your AI already has Slack connected, this happens in the same thread
- 7
Whenever you need a paper trail, export the full request log as CSV from the Brieform dashboard
How to set up a Brieform internal request form
- 1
Connect Brieform to your AI. One OAuth click from /install/claude, /install/chatgpt, or any MCP client
- 2
Say in chat: "Create an internal request form with a Type dropdown (IT, HR, Finance, Facilities), a Priority radio, and conditional fields per type"
- 3
Ask your AI to publish it. It calls publish_form and returns the public /f/[slug] URL
- 4
Edit the success message to include a reference number and expected turnaround
- 5
Post the link in your pinned Slack messages and Notion workspace nav
- 6
Read submissions in your AI. Ask Claude or ChatGPT to surface today's urgent requests or filter by team
What this replaces
| Tool | Cost | The pain |
|---|---|---|
| Slack threads + memory | $0 + burnout | Requests get buried, no log, no accountability |
| Jira / Linear | $8–$17/user/mo | Overkill for 10 people, teammates don't fill it in |
| Google Forms + manual Sheets triage | $0 + 30min/day | No routing, no auto-Notion, someone has to manage the sheet |
| Brieform | $0 free, $29 Starter | Built in chat, read requests in your AI, route through your AI |
Who this is for
Ops and office managers
Handling IT, HR, facilities, and finance requests across a 10–50 person team without a dedicated ticket system.
HR and people teams
Collecting onboarding requests, policy questions, and equipment orders without losing them in a Slack DM chain.
IT support at small companies
Triaging software license requests, access issues, and hardware orders with a simple log and routing system.
Finance teams at startups
Processing expense reimbursements and purchase approvals with structured data and a Notion paper trail.
Related
FAQ
Can I have different fields for each request type?
Yes, conditional logic is built in. Say in chat: 'If request type is IT, show the software/hardware selector. If Finance, show the amount and reason fields.' Brieform's update_form tool rebuilds the branching automatically.
Can I read requests without opening the Brieform dashboard?
Yes. Connect Brieform's MCP server to Claude, ChatGPT, or any MCP client and ask your AI to call get_responses. It returns submissions inline, filterable by team, priority, or date in natural language.
Is employee data stored securely?
Yes. EU-hosted (Frankfurt), TLS in transit, encrypted at rest. No third-party ticket vendor ingests your employee data. Brieform is the only system that stores the submissions.
Can one form handle requests from multiple teams?
Yes. One form with a team selector at the top and conditional fields per team. Read submissions in your AI and ask it to filter by team. If your AI already has Slack connected, ask it to forward urgent IT requests to #it-ops and HR requests to #people. No extra config in Brieform.
Build your internal request form today
Free forever for your first form. No card. EU-hosted.
No credit card · Works with Claude, ChatGPT, Cursor