跳到主要内容
Docs/Features/Inquiry Classifier

Inquiry Classifier

Reads every incoming email/DM/inquiry and labels it (PRE_SALE, ORDER_STATUS, TECHNICAL, COMPLAINT, OTHER) plus extracts intent, urgency, and any quoted SKUs. Powers Tom (the support AI employee) and the routing rules in Workflow.

![Inquiry Classifier](/docs-img/inquiry-classifier.png)

What It Does

  • Classifies inbound messages within 800ms (DeepSeek flash).
  • Extracts urgency on a 1-5 scale.
  • Pulls out any SKUs, order numbers, or money figures mentioned.
  • Auto-tags the originating contact and creates an Activity.
  • When to Use

    Always-on. Once enabled, every inbound message is classified — there's no "should I classify this one?" decision.

    Classification Categories

    CategoryExampleRecommended routing
    `PRE_SALE`"Got a price for 2k units?"Sarah (BD) drafts reply
    `ORDER_STATUS`"Where is PO 12345?"Lisa (Order ops)
    `TECHNICAL`"Voltage spec?"Tom (Support) + KB lookup
    `COMPLAINT`"Wrong item received"Human escalation
    `OTHER`Newsletters, spamAuto-archive

    Routing Rules

    Configure rules at **Settings > Inquiry Routing**. Each rule combines a classification + a tag/score filter to dispatch to an AI Employee or a human owner.

    API Endpoints

  • `POST /api/v1/ai/classify-inquiry` — synchronous classification (for your own inbound).
  • Classification fires automatically on inbound channels: email, WhatsApp, Telegram, social DMs.
  • Pricing & Limits

    PlanClassifications / month
    Starter1,000
    Pro50,000
    Enterpriseunlimited

    Gotchas

  • Classifications are based on the latest message in a thread, not the entire thread history. Long threads can drift category — Anvil emits a `category_changed` activity when that happens.
  • The model can be wrong; tune its confidence threshold under **Settings > AI > Inquiry**. Below the threshold, the message is left in `OTHER` rather than mis-routed.
  • Edge case: messages in non-supported languages (anything outside our 9 locales) default to `OTHER`.