Auto-triage Webflow contact form submissions

By General Input

Classify every Webflow contact form submission, file support tickets in Linear, ping the right Slack channel, and quietly drop recruiter spam.

Integrations

  • Webflow
  • Linear
  • Slack Bot

Type

Agentic Task

Categories

  • Operations
  • Customer Support

Build an agent workflow that triages every new submission from my Webflow contact form and routes it to the right place without a human triaging first.

Trigger: a webhook from Webflow on the form_submission event, scoped to my contact form (filter by form name so other forms on the site are ignored).

On each submission, the agent should read the message body plus any subject, category, or topic field on the form and classify it into exactly one of: support_issue, sales_lead, recruiter_or_spam, partnership, or other.

Routing rules by category:

- support_issue: call Linear Create Issue in the support team. Write a clean one-line title that summarizes the actual problem (not the raw form text). Put the customer's email and the full original message in the description. Infer a priority from urgency cues in the message (Urgent for outage / can't access / paying-customer-impacting language, High for blocking-but-not-down language, Normal otherwise). Then call Slack Send a Message to the support channel with a short summary and a link to the new Linear issue.

- sales_lead: call Slack Send a Message to the sales channel. Include a one-line qualification summary (company, role if available, what they're asking for, any size or timing signals) plus the contact name and email.

- partnership: call Slack Send a Message to the partnerships channel with a one-line summary of who they are and what they're proposing, plus contact details.

- recruiter_or_spam: log silently and stop. Do not notify any channel.

- other: post to the partnerships channel as a fallback with a note that it didn't fit a category, so a human can decide.

Use the Slack Bot integration for all Slack messages (not the user OAuth one), so posts are attributed to the bot and don't depend on any one person's account.

The classifying, the priority decision, and the qualification summary are the judgement calls that make this an agent rather than a static workflow. Keep the agent's instructions explicit about category definitions and priority cues so behavior is consistent across submissions.

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seatsPause marketing emails to escalated customers, then restore them