CUSTOMER SUPPORT
Route missed onboarding topics to owner tasks in Asana
After a Zoom kickoff, an agent reviews the transcript against the onboarding checklist and, for each missed topic, creates an owned.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom kickoff recording completedZoom
- ActionAgent fetches transcript and checklistZoom
- LogicAgent classifies items as unresolved, deferred, or N/A
- LogicFilter to items needing action
- OutputCreate owned follow-up tasks in AsanaAsana
What it does
Treats each missed onboarding topic as work that needs an owner. An agent reads the kickoff transcript, decides which checklist items still need action, and creates a specific Asana task per gap — with a title, the relevant context, and a suggested due date — instead of a single vague reminder.
When to use it
Use this when onboarding follow-through is tracked as real tasks, not checkboxes, and you want each gap routed to the right owner with enough detail to act without re-watching the call.
How it works
- 1A completed Zoom kickoff recording triggers the flow.
- 2The agent fetches the transcript from Zoom and the account's onboarding checklist.
- 3The agent reasons over the transcript to determine which items were genuinely unresolved versus deferred or N/A.
- 4A logic step filters to items needing action.
- 5For each remaining gap, the agent writes a clear Asana task with context and a due date and assigns it to the account owner.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect AsanaTasks, projects, milestones — everywhere.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.