When it acts
- Support ticket escalated by the team
Connect Asana and turn the ticket into a task without copying it
When Intake cannot resolve a support ticket alone, it creates structured tasks in Asana with full context, saving your team from copying and pasting messages.
What it solves
From ticket to task without copy and paste
When a conversation needs someone to do something, the usual move is to open Asana, create the task and summarise by hand what just happened. That summary always loses half of it. The agent creates the task with the conversation inside, so whoever receives it understands the case without going back to the inbox.
What it solves
The customer finds out without asking
The silence between "we passed it to the team" and the fix is where patience runs out. With Asana connected, when the task moves the agent can say so in the original conversation. The customer stops writing every three days to check their case is still alive.
What it solves
Nothing ends up ownerless
The cases needing internal work are the ones most likely to fall between two teams, because they live in an inbox only support looks at. Turned into a task with an owner and a date, they land where the team already looks every day.
What it does
What the connection triggers and what the agent does with it
An integration is not useful for being on the list: it is useful for what it lets the agent do. This is what Asana puts on the table, and what the agent does with it without anyone watching.
What it can do
- Create Task in specific project
- Link Task status to Intake Inbox
How Asana helps the agent resolve with context
Three concrete things that change the team day, not a feature list.
Tasks with context
The Asana task includes the problem, the affected user, and what Intake already verified.
Fewer loose messages
Stop having cluttered channels. Intake sends the clean request straight to your Asana board.
Clear follow-up
When the task moves forward, Intake can notify the user.
How it works
Three steps, and only the first needs a Asana admin. The rest you change later without reconnecting anything.
Authorise the connection
You open the integrations panel, pick Asana and authorise access with the account your team already uses. You need to be an admin in Asana, so if you are not, this is the only step you will have to ask someone for.
You choose what the agent sees
You tick the channels, events and account fields it can reach. What you do not tick does not exist for it, and you can change that whenever you want without reconnecting anything.
It answers with that context
From the first conversation the agent looks that data up before replying, resolves what it can close on its own and passes to a person what it cannot, with the case already assembled.
Frequently asked questions
How long does connecting Asana take?
Minutes, not an afternoon. You authorise access and choose what it can see; nothing needs rewriting and no development work is needed to start.
Can I revoke access later?
Yes, and from either side: revoking the connection in Intake or withdrawing the permission from Asana. The agent stops reading that data immediately and keeps answering with the rest.
Does using Asana cost extra?
No. Every integration sits inside the per-resolved-conversation price: 0.41 EUR on annual billing. There is no add-on to buy and no call meter.
What happens if Asana stops responding?
The agent answers with what it does have and, if the question depended on that data, hands off to a person explaining why. It never invents the value it could not look up.
Are tasks created automatically or manually?
Both. You can define rules in Intake to create tasks or do it manually from the inbox.
Can I see the Asana status from Intake?
Yes, Intake shows the progress of the linked task right in the original user conversation.
