Skip to content

Lustrew AI Ticketing

Every ticket read, sorted and drafted before anyone opens it.

Lustrew AI Ticketing sits on top of ConnectWise or the helpdesk you already run. Each new ticket is classified, routed, summarised and given a draft reply in seconds, grounded in your own documentation and what your team has corrected before. Built for MSPs. Your technicians stay in control of every write-back.

Interface previewSample data · not connected

Ticket #48213

Lustrew AI WorkingConnectWise PSA · Service Board

VPN drops every 20 minutes on new laptops

Credits

1.8

Latency

4.2 s

Tokens

18.4k

Corrections

0

Incoming Ticket

Today, 09:14

Priya Natarajan · Harbor Dental

Hi team, the three new Dell laptops we received last week keep losing the VPN connection roughly every 20 minutes. The older machines are fine. Users have to reconnect manually and it is interrupting patient check-ins. Can someone look at this today?

Pipeline Trace

6 features · 4.2s wall time
  1. Classification

    94% · 1.4s

    network high urgent
  2. Field Extraction

    93% · 2.1s

    affected_devicessymptomimpact
  3. Routing

    91% · 1.7s

    Network Engineering alt: Field Services
  4. Response Suggestion

    88% · 3.9s

    Draft ready for agent review
  5. Summary

    90% · 2.6s

    Summary · 3 key facts · 2 action items
  6. Duplicate Check

    97% · 1.9s

    30 open tickets checked · 0 duplicates

Ticket Thread

  • Priya Natarajan09:14

    Three new laptops keep dropping the VPN every 20 minutes. Older machines are fine.

  • Lustrew AIinternal note09:14

    === Classification === network · high · urgent (0.94). Routed to Network Engineering (0.91). No duplicates among 30 open tickets.

  • Lustrew AIinternal note09:15

    === Suggested Response (for agent review) === Thanks Priya. This pattern on new devices usually points to the VPN client’s idle timeout…

Lustrew AI Resolution

Preflight passed

Lustrew AI can attempt to resolve this ticket automatically. Nothing runs until a technician approves the plan.

Plan · 4 stepsAwaiting approval
  1. 1Read VPN client logs on the three affected laptopsdevice.read_logsidempotent
  2. 2Compare idle-timeout and adapter power settings with a healthy devicedevice.inspect_configidempotent
  3. 3Push the updated VPN profile and disable adapter power savingdevice.apply_profile
  4. 4Watch for 60 minutes and confirm no disconnectsmonitor.verifyidempotent
Approve & RunCancel

Progress, a verification result with its confidence and evidence links appear here as it runs. A technician reply or a manual status change cancels the job.

Context Enrichment

  • Knowledge base5 chunks used
  • Corrections fed back2
  • Positive examples3
  • Client profileHarbor Dental
  • IT GlueHarbor Dental · 2 configurations

Suggested Response

for agent review

Thanks Priya. This pattern on new devices usually points to the VPN client’s idle timeout or a power-saving setting on the new Wi-Fi adapters. We will push the updated VPN profile and adapter settings to the three laptops this morning and confirm with you once a reconnect-free hour has passed.

tone: professional2 follow-up questions3 suggested actions

WHAT RUNS ON EVERY TICKET

Six analyses in parallel. One confidence score each.

Turn each one on or off per integration, and decide feature by feature whether it only informs your team or writes back to the ticket.

  • Auto-Classify

    A short title, category, priority, sentiment and language for every ticket the moment it lands, with a confidence score and the reasoning behind it.

  • Auto-Extract

    The facts a technician needs pulled out of the ticket text: affected devices, users, products, order numbers, each one traced to where it was found.

  • Auto-Route

    The right team from your board, an alternative, and a flag when something needs escalating. Written back to the ticket in ConnectWise if you turn that on.

  • Draft Responses and Summaries

    A reply in your tone ready for the technician to review, plus a summary of the thread with key facts and action items. Nothing goes to the requester on its own.

  • Duplicate Detection

    Each new ticket is compared with the open ones on the same board, so the same outage does not become five tickets.

  • Resolve with approval

    When a fix is within reach, Lustrew AI proposes a step-by-step plan. A technician approves it, it runs, verifies the result and leaves the evidence in the ticket.

  • Grounded in your knowledge

    SOPs, SLA policies and environment notes you upload, IT Glue configurations, client history and past corrections all feed every decision.

  • It learns from your team

    Every override in Decision Review becomes an example for the next similar ticket. Accuracy, correction rates, time and cost saved are tracked per feature and per client.

Works with your PSA

Nothing to migrate. Your tickets stay where they are. Lustrew AI reads them, and writes back only what you allow.

  • ConnectWise PSA

    Registered integrator. Tickets, notes, boards and teams read automatically, notes and routing written back.

  • Zendesk

    Webhook intake

  • Freshdesk

    Webhook intake

  • ServiceNow

    Webhook intake

  • Jira Service Management

    Webhook intake

  • IT Glue

    Knowledge source

  • Any tool

    Signed inbound and outbound webhooks, scoped API keys

Start in audit mode: every feature on, every write-back off. Turn write-back on per feature once you have watched its accuracy in AI Quality. Each organisation is isolated, credentials are encrypted, webhooks are signed, and keys are scoped and shown once.

Lustrew AI · Ticketing

Stop triaging. Start resolving.

Connect your PSA, choose the features, and watch the first tickets come through in audit mode.