Skip to content
AI Tagging & Field Filling

Zero manual ticket classification. Ever.

Once you turn on creation-time filling, Pluno tags, categorizes and fills ticket fields as soon as a ticket is created, using AI that reads the full context, not just keywords. Agents spend zero time on admin work.

149,000+

Tickets tagged at Tekmetric since December

30s–2min

Saved per ticket

0

Manual classification

Trusted by 200+ B2B and B2C support teams handling 500K+ tickets per month

Smartness
Case study
Kojo
Case study
Crexendo
Lightspeed
Case study
Lovable
LinkedIn post
Innovorder
Case study
RunPod
LinkedIn post
Accelya
LinkedIn post
Waste Vision
Case study
Velotric
Case study
MaintainX
LinkedIn post
Happeo
BudgetBakers
Capterra review
HelloBetter
Bluetti
LinkedIn post
DAPARTO
COBB Tuning
LinkedIn post
Ferry Pay
Dune
LinkedIn post
Confluence

Every field filled before agents even look

With creation-time filling turned on, priority, type, tags, custom fields and ticket forms are filled automatically when a ticket is created, based on the full conversation, not just the subject line. By the time an agent opens the ticket, it's already classified.

  • Auto-fills new tickets once creation-time filling is on
  • Reads the full conversation context, not just keywords
  • Handles custom fields, dropdowns, checkboxes, and tags
  • Respects validation rules and conditional requirements

Smart enough for complex field logic

Real ticket forms have conditional fields, required fields that change based on other values, and regex validation. Pluno handles all of it, evaluating parent field dependencies and filling nested requirements correctly.

  • Evaluates conditional required fields based on parent values
  • Respects regex validation patterns on custom fields
  • Merges tags without overwriting existing ones
  • Selects the right ticket form automatically

Works on every trigger, not just new tickets

AI Tagging runs on ticket creation, after call transcripts are ready, when tickets auto-resolve, or on-demand from the Zendesk sidebar. It adapts to the latest conversation state every time.

  • Auto-fills new tickets once creation-time filling is on
  • Re-runs after call summaries are transcribed
  • Fills required fields before auto-resolve
  • Manual one-click trigger from the Zendesk sidebar
Intelligent classification

Handles the edge cases other tools miss

Conditional fields, regex validation, nested dependencies: AI Tagging handles the complexity of real Zendesk setups, not just simple dropdowns.

Ticket form selection

AI picks the right ticket form based on the conversation, so downstream fields, routing rules, and SLA policies all work correctly from the start.

Custom instructions per field

Add field-specific instructions like 'only set priority to urgent if the customer mentions a production outage', and the AI follows your rules.

Never overwrites existing data

Tags are merged, not replaced. Fields that already have agent-set values are respected. AI only fills what's empty or what you configure it to update.

Re-runs on new context

When a call transcript arrives or a ticket is auto-resolved, AI Tagging re-evaluates with the latest information and fills any remaining gaps.

Full conversation analysis

Reads the last 12 messages, ticket metadata, user and org fields, and even Shopify context to make accurate classification decisions.

Retry logic built in

If the AI can't determine a field value on the first attempt, it retries up to 3 times with refined context, reducing missed classifications.

How AI Tagging works

From ticket creation to fully classified, before an agent even opens it.

1

Ticket arrives

A new ticket is created via email, form, chat, or voice. With creation-time filling turned on, AI Tagging runs automatically. No manual trigger needed.

2

Context analysis

Pluno reads the full conversation, ticket metadata, customer info, and configured field rules to understand the context.

3

Fields filled

Priority, type, tags, custom fields, and ticket form are set, with a justification for each decision the AI makes.

4

Agent picks up a clean ticket

By the time an agent opens the ticket, it's fully classified and routed, ready for resolution, not admin work.

Tekmetric uses AI Tagging & Field Filling to tag and fill fields on about 16,000 support tickets a month. Without it, the 149,000+ tickets processed since December would have taken about 2,500 extra agent hours, and their ticket data would be inconsistent.

Tekmetric customer result

Tekmetric

~16,000

Tickets tagged and filled per month

~265

Agent hours saved per month (about $5.3k)

~85%

Less manual tagging time

Frequently asked questions

Setting up AI Tagging & Field Filling? Follow the AI Tagging & Field Filling docs, or see what it costs on the pricing page.

AI Tagging can fill priority, type, tags, the assignee, custom dropdown fields, text fields and checkboxes, and even select the right ticket form. It can also rewrite the ticket subject when an agent uses Fill, update & draft message in the sidebar. Description, status and group are not filled.

No. Tags are merged with existing tags, never overwritten. For other fields, AI Tagging respects values that have already been set by agents. It only fills what's empty or what you've explicitly configured it to update.

Yes. Each field has its own toggle and custom instructions text box. You can add rules like 'only set priority to urgent if the customer mentions a production outage' or 'tag as billing-issue when payment or invoice is mentioned.'

It can run on four triggers: automatically on new ticket creation (once creation-time filling is turned on in settings), after a call transcript is ready, before auto-resolve (to fill required fields), or manually via a one-click button in the Zendesk sidebar.

When enabled, the AI reads the conversation and selects the most appropriate ticket form from your configured forms. This ensures downstream fields, routing rules, and SLA policies all work correctly from the start.

AI Tagging reads the full conversation context, not just keywords or subject lines, and Loqbox rates its tagging accuracy as high. It also provides a justification for each field decision, so you can audit and refine as needed.

Yes. AI Tagging evaluates conditional requirements (where a field becomes required based on another field's value) and fills nested dependencies correctly. It also respects regex validation patterns on custom fields.

Stop wasting agent time on ticket admin

Pluno fills every field, tag, and category automatically, so your agents can focus on solving problems, not classifying them.