How to Set Up an Asana Intake Form That Routes Requests With AI

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Set Up an Asana Intake Form That Routes Requests With AI.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Set Up an Asana Intake Form That Routes Requests With AI.

To route client requests in Asana, build one intake form (Starter or above) whose questions fill custom fields such as request type and urgency. Add plain rules that assign and date each request by those fields, then one AI Studio rule that corrects the category and urgency and flags duplicates. Branching questions need Advanced.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Let the fields do most of the routing and keep AI for the messy part: clients who pick the wrong category, or mention the emergency in their last sentence. Plain rules cost nothing to run. Each AI run uses AI Studio credits from the plan's monthly pool, 50,000 on Starter and 75,000 on Advanced, and a busy week can double or triple your usual volume.

The roofing firm this setup is built around

The worked example is an illustrative eight-person roofing company: an owner, an office manager, an estimator, a claims and warranty coordinator, and two repair crews. Requests come from the website, from phone calls the office logs, and in bursts after storms. A normal month brings about 120; a storm week can bring that many in four days.

Before the form, requests arrived by email, voicemail and social messages. The office manager forwarded them by hand, and the estimator once spent a morning on a "quote" that was an active leak. The goal is simple: every request reaches the right owner within minutes, with a due date that matches what the client was promised, and emergencies never wait for someone to read the inbox.

Who owns what:

Request typeOwnerResponse target
Active leak or storm damageOn-call crew lead (round robin between two)Same day
Quote for a new roof or replacementEstimator3 days
Help with an insurance claimClaims and warranty coordinator2 days
Problem with work we didOwner2 days
Gutters and small repairsOffice manager to schedule5 days
Something elseOffice manager2 days

Write your own version of this table before you open Asana. Every rule you build later is one row of it.

What fields does an Asana intake form need to route requests?

An Asana intake form needs single-select custom fields such as Request type, Urgency and Active leak, because a rule can check a value picked from a list and route on it reliably. Create a project called "Client requests" with sections New, Emergency, Quotes, Claims and warranty, Small jobs, Needs info and Spam check. Then create single-select custom fields: Request type (the six values above), Urgency (Emergency, Soon, Planned) and Active leak (Yes, No). Custom fields and forms are on Starter and above.

The fields are what make routing possible. Asana's project intake page says form questions can map to custom fields that then feed automation rules, and that requests can be routed to different owners with rules triggered by those field values. A request type typed into a paragraph box can't trigger anything; a request type chosen from a list can.

How do I build the form questions?

Build the Asana form with one question per custom field, plus a required description, an optional photo upload and a confirmation message that states your response target. Add a form to the project. Asana forms take text, numbers, dates and drop-down lists, file uploads for photos, your logo and cover image, and a confirmation message shown after submission. Each submission becomes a task in the project with the answers in its details. The roofing firm's questions:

  1. Your name, email and phone number (required).
  2. Property address (required).
  3. What do you need help with? Single choice, mapped to Request type.
  4. Is water coming in right now? Yes or No, mapped to Active leak.
  5. Tell us what's happening (paragraph, required).
  6. Photos (file upload, optional).
  7. Best time to call you (single choice).
  8. Which of these is a roofing material? Tile, Banana, Carpet (required; the spam check in step 6).

Set the confirmation message to state the response target honestly: "Thanks. If water is coming in now, we'll call you today. For anything else we'll be in touch within two working days."

Branching on Advanced, or several forms on Starter

The claims coordinator wants the insurer name and claim number; the owner wants the date of the original job for warranty requests. On Advanced, branching logic shows those questions only when the matching request type is chosen. Asana describes it as forms that change their questions based on earlier answers. On Starter you can't branch, but you can create several forms for one project: a short "Insurance claim help" form and a "Problem with our work" form, linked from the website next to the main one.

The sum for this firm: Asana sells seats in steps of five past five users, so eight people need ten seats. Starter at $10.99 is $109.90 a month on annual billing; Advanced at $24.99 is $249.90, so branching would cost an extra $140 a month. Advanced also adds approvals, proofing and portfolios. For intake alone, three Starter forms do the job. If the estimator later wants approvals on quotes, revisit it.

Can clients without an Asana account submit the form?

Clients without an Asana account can submit a form when you share it with anyone on the web, and you can copy an embed code to place it on your website. Asana also lets you keep a form private to people in your organisation, but a client form has to be open to anyone. Enterprise admins can disable form embedding for a whole domain, which won't affect most small firms.

Embed it on a page of your own site rather than sharing the raw link on social media. The page is where clients expect it, and it's where your website's own protections sit.

How do Asana rules route a request to the right owner?

Asana rules route a request when you build one automation per row of your ownership table, each with a condition on the Request type field. Open Customize, then Automations. Each uses the trigger for a task being added to the project (or the form submission trigger), and actions to set the assignee, move the task to a section and set a relative due date. For the emergency row:

  • Condition: Active leak is Yes, or Request type is "Active leak or storm damage".
  • Actions: set Urgency to Emergency; set assignee by round robin between the two crew leads; move to Emergency; set due date to the trigger date; add a comment for the crew lead: "Call the client within the hour. Photos attached if provided."

Round robin has been part of Set assignee since August 2026 on Starter and above, and it's a standard rule with no AI and no run limit. It rotates through people, not roles, and doesn't know who is on holiday, so update the list when a crew lead is away. The other rows are simpler: quotes to the estimator with a three-day due date, claims to the coordinator with two days, and so on. The full method for these building blocks is in five starter Asana automation rules for a small team.

Add one more pair of rules for response targets: when a due date is approaching, comment to the owner; when it's overdue, add the office manager as a collaborator. That turns the table's targets into something people see, not a promise on the website.

How can AI fix requests filed under the wrong category?

An AI Studio rule fixes wrongly filed requests by reading each description and correcting the request type and urgency the client chose. Clients choose categories quickly. In the firm's first month (illustrative), 14 of 118 submissions had the wrong request type: leaks filed as "Gutters and small repairs", warranty problems filed as "Quote". The fields route those confidently to the wrong person. This is the job for AI.

AI Studio is Asana's no-code builder for rules with AI steps, included on every paid plan as AI Studio Basic with rate limits. Asana's AI Studio page describes exactly this kind of intake work: checking completeness and duplicates, classifying and applying service targets, and routing to the right owner. Build an automation triggered when a task is added to the project, with an AI step given these instructions:

You triage roofing requests submitted by clients.
Read the task name, the description and the answers to
"What do you need help with?" and "Is water coming in right now?".

1. If the description shows water coming in now, ceiling stains spreading,
   missing tiles after a storm or a tarpaulin in place, set Urgency to
   Emergency even if the client chose another request type.
2. If the client chose a request type that doesn't match the description,
   set Request type to the correct value and add a comment:
   "Recategorised from [old] because [reason]".
3. If the property address or a phone number is missing, move the task
   to Needs info and add a comment listing what is missing.
4. If another task in this project from the last 14 days has the same
   address, add a comment "Possible duplicate of [task name]".
5. Do not reply to the client. Do not change due dates.

Then point the existing routing rules at the corrected fields, so the AI fixes the data and the plain rules still do the assigning. Asana's community team notes that assigning by expertise or workload needs an AI-assisted step using the Use AI variable, which is an option if you'd rather the AI choose the owner directly. Keeping assignment in plain rules makes the routing easier to audit.

Two submissions and what the rule did (illustrative)

Submission A. Chose "Gutters and small repairs". Answered "No" to water coming in. Description: "Gutter overflowing at the back. Also there's a brown patch on the bedroom ceiling that's got bigger since Sunday."

Rule result: Urgency set to Emergency, Request type changed to "Active leak or storm damage", comment: "Recategorised from Gutters and small repairs because the ceiling stain is growing, which suggests water getting in." The emergency routing rule then assigned the next crew lead.

Submission B. Chose "Quote for a new roof". Description: "Your team replaced our flat roof in spring and it's pooling water again."

Rule result: Request type changed to "Problem with work we did", comment explaining why, routed to the owner with a two-day target.

What the owner corrected in week one: the rule marked "tarpaulin on the roof since last year" as an emergency because of the word tarpaulin. The instruction now reads "a tarpaulin put in place in the last week".

The credit sum, including a storm week

Asana doesn't publish a fixed credit cost per run; the rule editor shows credits per task in its top right corner, and cost depends on input size, output size, the model and how often the rule runs. Suppose this rule shows about 200 credits per task (an illustrative figure; read your own). A normal month of 120 requests uses 24,000, about half of Starter's 50,000. A storm month with 400 requests would need 80,000, which is more than Starter includes. Two ways to stay inside it: add a condition so the AI step only runs on submissions with a paragraph longer than a few words, or buy additional credits before storm season, which Asana's pricing table says are available on top of the included amount. Admins get alerts at 80% and 100% of credits, so make sure the office manager receives them. More detail on how far credits stretch is in Asana AI Studio pricing and credits per plan.

Does Asana have a CAPTCHA for a public form?

Asana's form documentation showed no CAPTCHA setting in November 2026, so a public form needs protection you build yourself. Requests for one on Asana's community forum go back to 2021, when Asana's community team replied that it wasn't possible. Build three cheap layers:

  1. Your own page. Embed the form on a page of your website, behind whatever protection your site already has, and don't publish the raw form link.
  2. A check question with a rule. A community workaround: ask a required question with one sensible answer (question 8 above), map it to a field, and add a rule that moves any submission without "Tile" to Spam check and assigns nobody. Humans answer it in a second; most junk doesn't.
  3. An AI flag. Add a line to the triage instructions: "If the description contains links, advertising, or no roofing problem at all, move it to Spam check and set nothing else." Review Spam check once a day, because a real client in a hurry sometimes picks the wrong answer.

How do clients find out their request arrived?

A public form's confirmation message is the only automatic acknowledgement you can count on, so use it to tell clients what happens next. Asana has features for emailing form submitters, but users on its community forum reported in October 2026 that some of them, such as adding submitters as collaborators, depended on the form being restricted to the organisation, which a client form can't be. Test any email update in your own account before promising it on the website.

What the firm does instead: the office manager sends a short personal acknowledgement for quotes and claims within the target, and the crew lead phones emergencies. That keeps a person on every first reply, which matters when the request might become an insurance claim.

Step 8: test with twelve fake requests before going live

Submit twelve test requests from a personal email address, covering every row of the ownership table plus the edge cases. The firm's filled-in test log (illustrative):

TestExpected owner and sectionResult
Leak, chose correct typeCrew lead, Emergency, due todayPass
Leak, chose "Gutters"Recategorised, crew lead, EmergencyPass
New roof quoteEstimator, Quotes, 3 daysPass
Claim, no claim numberCoordinator, Claims and warrantyPass
Warranty filed as quoteOwner, Claims and warrantyPass
No address givenNeeds info, comment listing gapsFail: the address question wasn't required; fixed
Same address twice in a dayPossible duplicate commentPass
Wrong check answerSpam check, nobody assignedFail: routing rule ran first and assigned the estimator; added a condition
Advert with a linkSpam checkPass
"Tarpaulin since last year"Soon, not EmergencyFail, then pass after the instruction change
Gutters, photos attachedOffice manager, Small jobs, 5 daysPass
Something else: "moss on roof"Office manager, 2 daysPass

The two failures are the useful ones. Rule order matters: the spam rule must win over routing, so add a condition to each routing rule that skips anything in Spam check. Read each test task's activity feed to see which rule acted, and the AI rule's Activity tab to see what each run cost.

Can an AI Teammate review the daily request queue?

Asana's prebuilt Work Intake Specialist AI Teammate is described as reviewing the day's queue: triaging requests, flagging ones close to breaching a service target and suggesting form improvements to reduce incomplete submissions. Rules handle each request as it arrives, but nobody is watching the whole queue. A recurring task assigned to it each morning ("Review Client requests: anything unassigned, overdue or stuck in Needs info for over 24 hours") uses one AI request per successful run. On Starter, with eight people, the account gets 40 requests a month, so a weekday review uses about half. More on setting one up is in the tutorial on AI Teammates for meeting prep and follow-ups.

If you want help fitting request routing into how your own client requests actually arrive, I offer one-to-one AI consultations for small businesses.

Where AI triage goes wrong, and the checks that catch it

  • A downgraded emergency. The worst failure, so the rule only ever upgrades urgency from the client's answer; it never downgrades a "Yes" to water coming in. Keep that line in the instructions.
  • Confident recategorising. If the AI moves too many requests, clients' own choices stop meaning anything. Review every "Recategorised" comment for the first month; 10 to 15 a month is normal for this firm, 40 would mean the form's choices are confusing.
  • Personal details in comments. The AI comments quote the description. Claims requests can include policy numbers. Decide whether that's acceptable in your project, and check how Asana handles client data before switching AI on; Asana says its AI partners don't train on customer data and must delete it after each query.
  • Rules built by someone who leaves. Since September 2026, standard rules run with their owner's current permissions, so build them from an account that will stay.

Storm leads have their own pattern of volume and follow-up; the tutorial on triaging roofing storm leads with AI covers that end. If you're comparing tools, ClickUp forms with Brain summaries is the same job in ClickUp, and requests that still arrive by email can be pulled in with email-to-Asana tasks with AI-drafted subtasks. For the general method behind sorting and routing incoming requests, see AI ticket triage.

What to measure in the first month

Five numbers, each readable from the project in a few minutes or from a dashboard (reporting dashboards are on Starter):

  • Minutes from submission to owner. Should be under five for every request. Anything longer means a rule didn't fire.
  • Emergencies called back the same day. Target: all of them. An illustrative before-and-after: 7 of 11 before the form, 12 of 12 after.
  • Recategorised requests. Count them weekly and read a sample; this is your AI quality check.
  • Requests past their response target. By type, so you can see whether quotes or claims are the bottleneck.
  • Credits used. Read the AI Studio usage tab mid-month and project forward before storm season.

When those numbers hold for a month, the form has done its job: clients get a clear promise, owners get requests they can act on, and the office manager stops being the routing system.

If you want to chart those first-month numbers in a spreadsheet, try The Complete Excel Course with AI Integration on Coding Liquids.

Asana intake forms: questions owners ask

How do I route Asana form submissions to different people?

Map a drop-down question to a single-select custom field, then build one rule per owner that triggers when a task is added and checks that field. Each rule sets the assignee, moves the task to a section and sets a due date. Round robin lets one rule rotate between two people, such as two crew leads.

Which Asana plan do I need for intake forms with branching?

Forms start on Starter, at $10.99 per user per month billed annually. Branching logic, where later questions change based on earlier answers, needs Advanced at $24.99 per user per month billed annually. On Starter you can get a similar effect with several short forms in the same project, one per request type.

Can people without an Asana account submit the form?

Yes. Asana lets you keep a form private to your organisation or open it to anyone with the link, and you can embed it on your website. Clients don't need an account to submit. Some follow-up features, such as adding submitters as collaborators, were reported by users in October 2026 to depend on organisation-only access, so test them before relying on them.

Does Asana have a CAPTCHA for public forms?

No CAPTCHA setting appeared in Asana's form documentation in November 2026, and requests for one on Asana's community forum go back to 2021. Protect a public form with a page on your own website, a required check question routed by a rule, and an AI step that flags likely junk for a person to review.

Should I use an AI Teammate instead of an AI Studio rule for triage?

No, use both for different jobs. Use the AI Studio rule for every submission and a teammate for the daily review. A rule runs on each new task and uses AI Studio credits; Asana's prebuilt Work Intake Specialist teammate can triage the day's requests and flag ones close to breaching a target, using one AI request per successful run from the plan's monthly allowance.

How do I test an Asana intake form before going live?

Submit twelve test requests from a personal email address, covering every row of your ownership table plus edge cases such as a missing address, a duplicate and a wrong check answer. In the roofing example, some tests failed and were fixed before the form went live, which is the point of the log.

Further reads

Sources: Asana pricing page and FAQ; Asana forms, rules, project intake, AI Studio and AI Teammates product pages; Asana community forum Q&A from the Q3 2026 release webinar, the round robin announcement and user threads on form spam and submitter updates (checked 17 and 18 November 2026).

Ready to put AI on the jobs that eat your week?

No data team or big budget needed. In a 1:1 consultation I show small and medium-sized businesses and self-employed people which AI tools they can use, one workflow at a time.

Book a 1:1 call with me