Client requests arrive complete, structured, and already assigned. A signed-in intake form inside the portal collects exactly what your team needs to start work, so nobody spends two days asking follow-up questions before the job can even be scheduled.
The nearest thing in the gallery is the Team Wiki Portal, a live Taskade Genesis app you can open on this page. Watch how an incoming request is captured and routed, then choose "Use this app" to clone it in about ten seconds and swap its intake questions for your own.
The build gives you a form with real logic behind it. Fields change based on the request type, so a bug report asks for steps to reproduce while a new-work request asks for budget and deadline. Required fields stop incomplete submissions at the door. Because the person is already signed in, you know who is asking without making them type their account details again, and the request is filed against their record automatically. Each submission becomes a row in a Requests project with type, priority, description, attachments, and status.
The value shows up on the receiving end. A request that arrives with the type, the affected account, the urgency, the desired date, and a screenshot attached can be scheduled immediately. The same request as a two-line email costs two days of clarifying questions before anyone can even estimate it. Multiply that across a month of requests and the intake form is the highest-return screen in the whole portal. Because the client is signed in, you also skip the account fields entirely, which keeps the form short enough that people actually finish it.
Workspace DNA is what turns a form into a workflow. Memory keeps every request and the account it belongs to. Intelligence, powered by 15+ frontier models from OpenAI, Anthropic, Google, and open-weight providers, classifies the request, sets a first-pass priority, and writes a one-line summary for your team. Execution assigns the owner, starts the clock, and confirms receipt to the client.
The request queue renders in every layout you need:
- Table view for the full queue with type, priority, owner, and age
- Board view for dragging requests through new, in progress, and delivered
- List view for the client's own history of what they have asked for
- Calendar view for requested-by dates and scheduled work
- Plus Mind Map, Gantt, and Org Chart across the 7 project views
Automations turn submissions into action. Connect Taskade automations so a new submission notifies the right owner in Slack, an urgent flag pages the on-call person, and a delivered request asks the client to confirm. Across 100+ bidirectional integrations, web forms and Gmail pull requests in, while Slack, email, and your project tool push assignments out. See Forms trigger and Build a form with logic.
Write the questions from your own follow-up emails. Look at the last twenty requests you received and note what you had to ask afterwards, then make each of those a field. That is a better form design method than guessing, and it usually produces something shorter than you expected.
The AI agents in the app carry 34 built-in tools including persistent memory and web search. An agent reads the incoming request, checks the client's history, and flags a duplicate of something already open rather than letting two people work the same thing.
Clone the app, invite the team, and the queue is yours. Client sign-in is available on Business plans and up, $25/mo billed annually, and App Users is in beta.
Read Build a form with logic for conditional fields, Automation actions for routing, or browse intake builds in the Community Gallery. Start at Taskade Genesis. Pair this with Give Clients a Support Ticket Thread in the Portal and Give Clients a Live Project Status Page.
Frequently Asked Questions
Why put the form behind a login instead of on my website?
Because a signed-in request already knows who is asking. You skip the account fields, you can show the client their own request history, and you avoid spam submissions entirely.
Can the form change based on what the client picks?
Yes. Conditional logic shows and hides fields as the client answers, so a short request stays short and a complex one asks the extra questions it needs.
Does the client see what happened after they submitted?
Yes. The same portal shows their request history with the current status, so the follow-up email asking "any update" mostly stops happening.
Can clients attach files to a request?
Yes. Attachments land on the request row and an agent can summarize them before your team opens the item.
How does priority get set?
You define the rules in plain English, for example "anything marked outage is urgent, anything from an account tagged vip starts at high." The agent applies them and your team can override any call.
Can I limit how many open requests a client has?
Yes. Set the rule and the form tells the client they have reached their limit, with a link to the requests already open. It is a fair way to manage capacity without a difficult conversation.
Where do the requests go?
Into a connected Taskade project that your team works in directly, and out to whichever tools you connect through the 100+ integrations.
How many fields should the form have?
As few as possible while still being actionable, which is usually five to seven with conditional logic hiding the rest. Every extra required field costs completions, so only ask for what changes what you do next.
