ClickUp Forms for Request Intake: One Queue, Two Languages, No More WhatsApp Tickets

Quick answer

ClickUp Forms turn intake into structured tasks: anyone with the link can submit, and each submission creates a task in a chosen List with answers mapped to task fields and Custom Fields. Settings add auto-assignment, task templates, and conditional logic, so requests arrive already routed rather than as chat messages.

Ask an operations manager in Dubai how work reaches their team and you get a list of channels rather than a process: a WhatsApp message to whoever answered last time, an email to a shared inbox nobody owns, a request made in the corridor and confirmed by nobody. Every one of those is real work; none of them is a record. The queue lives in the memory of two or three people who are good at remembering, and it leaves the building when they do.

This is the seventh article in our product-education series, and it covers ClickUp Forms — the feature that turns an unstructured request into a task with the fields already filled in. The mechanics take an afternoon. The decisions that make intake work — where the Form lives, which fields it writes to, and what happens the second somebody presses submit — are awkward to change once requests are flowing.

A Form is a public front door onto a List

Forms are also called Form view: you create them from the Views Bar, Forms Hub, or the sidebar create button, at Space, Folder, Subfolder, or List level. Whichever route you take, the choice that matters is the same — the List where submission tasks are created.

What makes them useful for intake is who can use them. Anyone with the link can submit: no ClickUp account, no seat, no login. That covers the finance colleague who will never open the tool, the client in Doha raising a change request, and the site engineer on a phone. Forms can also be submitted from the mobile app, though not created or edited there. They exist on every plan, but usage limits and the more advanced options vary by plan and user role — check the current documentation against your own subscription before designing around a specific capability.

Two front doors, one queue: the bilingual intake pattern

The most common mistake we see in Gulf rollouts is running Arabic and English intake as two systems: one form feeding one list, another feeding a second, and a manager reconciling them on Thursday afternoon. A Form question maps to a task field or a Custom Field, and it is the field — not the question label — that decides where the answer lands.

Renaming a Custom Field on a Form changes the name only on that Form; the field keeps its name everywhere else in your Workspace. So build one Form in Arabic and one in English, point both at the same List and the same Custom Fields, and you get a single queue with two front doors. The requester reads Arabic labels and Arabic help text; the dashboards, automations, and reports underneath read one consistent set of fields. Write the Arabic labels as native questions, not translations.

Decide the location before you write a single question

Forms can only use Custom Fields that already exist in the hierarchy where the Form was created, and the rule follows the tree: a Form created from a List can use fields from that List, its Folder, and its Space; a Form created from a Folder can use fields from the submission List, the Folder, and the Folder's Space; and so on up to the Workspace. Create the Form in the wrong place and the field you need is simply not offered.

So decide where requests should live and who should see them, then create the Form there. If several departments share a field — a "Requesting entity" dropdown listing your UAE, Qatar, and Kuwait offices — that field belongs high in the hierarchy, not buried in one List. New Custom Fields created from the Form are added to its location, so other tasks there can use them too.

Question types, and where each answer ends up

Questions come in two flavours. A task-field question writes to a property of the submission task itself — Due Date, Priority, Status, Assignee, Tags, Task Description, Time Estimate, attachments. A Custom Field question writes to a Custom Field, either one you map to or one you create on the spot. The distinction matters: task fields are what your views, filters, and automations already understand without extra configuration.

• Text: short and long text, mapping to Task Name and Task Description
• Single-select: dropdown, status, checkbox, priority, rating, voting, manual progress
• Multi-select: Labels, which can map to task Tags
• Contact info: email, website, phone, and location — for external requesters
• People: maps to Assignee, so a requester can name the owning department
• Uploads: files mapping to attachments — the site photo, the signed LPO, the scanned invoice
• Numbers: number, money, time estimate, and Sprint Points where that ClickApp is active
• Signature, plus an Information Block for rich content such as images or tables

Three defaults worth changing on day one

First, the task name. Without a question mapped to Task Name, submissions are named Form Submission followed by a Zulu timestamp. Forty tasks all called "Form Submission" are technically a queue and practically unusable. Add a short-text question mapped to Task Name and label it as the one-line summary.

Second, exports. You can download responses as a CSV, but the export includes standard fields only — Custom Field answers are not in it. If your intake data lives mostly in Custom Fields, the file will be empty of exactly what you wanted. Plan to report inside ClickUp instead.

Third, the rate limit: 500 responses per hour per IP address — irrelevant for most teams, and not at all irrelevant if an entire office sits behind one public IP during a company-wide submission drive.

Conditional logic: shorter forms, better answers

Long forms get abandoned; short forms get vague answers. Conditional logic asks follow-up questions only when they are warranted. Rules attach to Assignee, Checkbox, Dropdown, Label, People, Priority, and Status questions, with multiple conditions per rule and up to twenty-five rules on a field, and the action adds one or more fields when the condition is met — select Urgent priority, and a Due Date field appears.

Used well this is a triage instrument, not a convenience. The three questions that decide routing — what kind of request, which entity, how urgent — stay on the first screen for everyone; everything else appears only for the branch it belongs to. Availability depends on your plan, so confirm before designing the whole intake around it.

What happens the second somebody submits

The settings tab is where a form stops being a form and becomes a process. You choose the List submission tasks land in, and you can assign them automatically — for anonymous submissions the activity log shows ClickBot making the assignment. More usefully, you can apply a task template on submission, so the request arrives with its checklist and subtasks attached: the IT access request that always needs three approvals arrives with three approvals on it.

Depending on your plan, the same area offers a custom submit button label, an editable end-page message, a redirect URL for public links (redirects deliberately do not work inside embeds), a resubmit button, reCAPTCHA, an option to copy every answer into the task description, and your own logo in place of ClickUp branding. Write the end-page message properly in both languages — it is the only confirmation most requesters ever see, and the right place to state your response time.

Sharing it without leaking anything

Forms are published by default, so the link works as soon as you copy it. In the sharing settings you can set the link to expire, decide whether search engines may index it — off by default, and it should stay off for anything internal — and copy an embed code for your website or intranet. Guests with the link can submit regardless of permission level, while sharing, embedding, and exporting stay with members, admins, and owners.

Two controls matter for sensitive intake. Authenticated Forms restrict viewing and submission to people with Workspace access, which suits HR and finance requests; availability depends on your plan. And a Share Task automation shares the created task with the person who submitted it without giving them access to anything else in the List — that is how a requester follows their own ticket and nothing more.

A 30-day intake rollout

Week one: pick the noisiest intake channel — usually IT or creative requests — and decide where those requests should land. Create the Custom Fields at the right level of the hierarchy, then build the English Form with no more than eight questions, three of which drive routing. Week two: build the Arabic Form against the same List and fields, and have a native Arabic speaker write the labels rather than translate them.

Week three: close the old channel. Teams skip this step, and it is the only one that decides the outcome — if WhatsApp still works, WhatsApp wins. Publish the link, embed it where people already look, add auto-assignment and the task template, and answer any off-channel request with the link and nothing else. Week four: build a dashboard over the List — volume by type, ageing by requester, time to first response — and delete the questions nobody used. ClickUp Brain also answers questions about submission tasks from the Ask button in the location header, which beats building a card for a question you will ask twice.

How BuyClickUp helps

BuyClickUp is an independent ClickUp partner operated by Inspark, working with organisations across the UAE, Qatar, and Kuwait, with our sister company Dtech serving Saudi Arabia. We handle ClickUp licensing with local, procurement-friendly invoicing, and we design intake with the team that actually receives the requests — in English and Arabic, so one queue serves both languages.

If your requests still arrive as chat messages to whoever answers first, start with our free readiness assessment or reach us through the contact page. Intake is usually the fastest visible win in a rollout — it changes something every person in the business touches, in the first month.

Next in this series: security and compliance — what ClickUp publishes about its certifications, and which questions belong to your legal team rather than ours.