GuidesBy professionOperations leads routing incoming requests without an engineer
Building no-code intake routing an ops lead owns
For Operations leads routing incoming requests without an engineer.
Asana AI Studio is a no-code builder where you can design AI-powered workflows that handle intake, routing and alerts. An ops lead sets the trigger and writes the rules in plain language, and keeps a human approval step over anything with cost, contract or customer impact.
When to use this
New requests land in one place and someone has to read each one and send it to the right team, and you want to automate the routing without waiting on engineering.
- Gives you a no-code builder to design AI-powered workflows
- Handles intake, routing and alerts from a trigger you set
- Classifies and routes each request by rules you write in plain language
Workflow
Pick the trigger, such as a new request arriving in the intake project
Write plain-language rules for how the AI should classify and route each one
Deploy it into the live project and route a small share of requests first
Watch for mis-routes and refine the rules before you widen it
Keep a human approval step on anything with cost, contract or customer impact
Prompts to try
Use it, adapt it, and make it your own.
Draft plain-language routing rules for our intake project: for each request type, say which team should own it, and which conditions must send it to a human for approval, especially anything with cost, contract or customer impact.
Human lens
- You write and own the routing rules, not the tool
- You keep approval over anything with cost, contract or customer impact
- You monitor mis-routes and refine the rules over time
What to avoid
- Routing affects SLAs and ownership, so a mis-route has a real cost
- A plain-language rule can be read more loosely than you meant, so test it on real requests
- Keep approval over anything that involves money, contracts or customers