← Mira AI Front #1 · Ticket Triage

Every ticket, read and acted on before your team sees it.

The moment a subscriber or the portal opens a ticket, Mira pulls the full context — invoices, RADIUS state, payment history, last five interactions — decides what to do, and either acts or hands off with reasoning attached.

flow · ticket → triage → action
live
STEP 1 Ticket in from portal or email STEP 2 Context snapshot ↦ subscriber record ↦ RADIUS radcheck + acct ↦ invoices last 6 ↦ payments last 5 ↦ prior tickets STEP 3 Mira decides reads the full case picks one action rates her confidence drafts a reply ≥ 90% conf.Act & reply Info missingAsk subscriber UncertainEscalate to human
In production

Three real tickets from last week.

Anonymised. All three came in within 4 minutes of each other. Mira handled the first two without a human touching them, and correctly escalated the third.

✓ Auto-resolved TKT-2842

"Please unblock — paid last night"

Mira found matching payment PMT-8834 (Telr, ref matches), removed the Auth-Type block, issued CoA disconnect to bounce the session.

96% · 2m 04s · unblock_radius
? Info requested TKT-2844

"Speed slow"

No specifics. Mira replied asking which device, wired vs wireless, and requested a Cloudflare speedtest link. Reply came back in 8 minutes — issue was wifi range, not the plan.

74% · request_info
↑ Escalated TKT-2843

"Down for 2 hours, want a discount"

Mira flagged the outage in radacct (matches NAS silence 12:04–14:11), summarised the case for the agent, and marked the subscriber as eligible for a pro-rata credit. Human made the call.

45% · escalate
Safety by design

Mira picks one action. Server code executes it.

She never writes SQL. She never calls tools freely. She returns a JSON action from a whitelisted enum. Your server runs a switch statement.

enum TicketAction {
unblock_radius // remove radcheck.Auth-Type=Reject + CoA
block_radius // insert radcheck.Auth-Type=Reject
reactivate_subscriber // status: active, clear suspension
suspend_subscriber // status: suspended
reset_password // generate + SMS new password
escalate // assign to human queue + summary
request_info // draft reply asking specific question
no_action // note-only, no side effect
}
More Mira fronts

See how she works elsewhere.

Ticket volume, quieter

Let Mira read every ticket first.