Aelita is your embedded AI operations partner. Powered by Claude, she drafts responses, explains invoices, scans supplier documents, and detects billing anomalies. All within your permission boundaries; all requiring your approval.
Most AI tools are general-purpose chatbots bolted onto a search bar. Aelita is different. She is embedded directly in your ERP workflows. When a support agent opens a ticket, Aelita has already read the customer's contract, checked their billing history, queried their ONU signal quality, and prepared a draft response.
When a finance clerk receives a supplier invoice photo, Aelita extracts every line item and matches them against the purchase order.
Critically, Aelita never acts alone. Every suggestion is a draft. Every action requires human approval. She operates within the same ACL permissions as the logged-in user. If you can't issue a credit note, neither can she.
This is not AI replacing your team; it is AI making your team faster while keeping humans in control.
Each capability is context-aware. Aelita pulls from contracts, billing, network telemetry, and inventory data to produce relevant, actionable drafts. Grouped by where she shows up in the day.
When the customer is on the other end. Ticket, phone call, after-hours IVR. Aelita drafts the reply and runs the diagnostics before the agent has finished reading the message.
When a support agent opens a customer ticket, Aelita assembles the full context automatically: active contracts, recent billing events, device signal quality, and past interaction history. She drafts a response tailored to the specific issue and suggests the most likely next action, whether that is a plan change, a technician dispatch, or a billing adjustment.
Customers ask "why is my bill higher this month?" and agents spend 10 minutes cross-referencing ledger entries. Aelita answers in seconds. She reads the invoice, identifies the delta, traces it to the specific event (plan change, addon activation, proration), and produces a plain-language explanation the agent can send directly or adapt.
Aelita processes incoming support tickets automatically: reading the customer's message, pulling their contract and billing context from the ERP, running network diagnostics where relevant, and drafting a categorized response. Tickets are routed through session-based workflows (drafting, HQ routing, verification) with learning hooks that improve accuracy over time based on agent corrections.
When a customer calls outside business hours, the IVR system captures their details and hands them to Aelita. She performs a full diagnostic sequence (billing status, ONU signal quality, active outage zones), then creates an osTicket entry with the diagnosis attached and sends the customer an email summary. No human involvement needed until morning, and the technician starts their day with full context.
When a customer complains their connection is down and their address falls inside a maintenance window your engineers already announced, Aelita doesn't treat it as a new fault. She checks the complaint against the scheduled work, recognises the customer is in scope while the window is open, and leads the reply with a calm acknowledgement: planned work is under way, here is when it is expected to finish. No needless diagnostics, no escalation to the NOC, no truck roll for an interruption you planned on purpose. The moment the window has not yet started or has already closed, she treats the report as a genuine fault again, so a real problem is never waved away as maintenance.
Eyes on the network. Telemetry interpretation, outage clustering, infrastructure drawing parsing. The parts of the day where minutes saved on a truck roll add up.
When two or more customers in the same neighbourhood drop offline within a short window, Aelita recognises the pattern as a single infrastructure event, not a handful of unrelated tickets. She groups the affected customers, flags the OLT port and location, and raises one coordinated incident so the NOC can dispatch a cable team once instead of chasing each report separately.
Before a technician is dispatched, Aelita reviews the customer's network stack: ONU signal levels, OLT port status, WiFi configuration, DHCP profile, and recent reboot history. She flags issues that can be resolved remotely (a misconfigured WiFi channel, a DHCP conflict, an ONU that just needs a reboot), saving a truck roll.
Network engineers draw infrastructure diagrams: fiber routes, OLT placements, splice closures, patch panels. Aelita converts these drawings into structured topology data that feeds into the coverage map and network inventory. No manual data entry from a Visio export or a whiteboard photo.
Paperwork, money, stock. Supplier invoices read by Claude Vision; billing exceptions surfaced before they age; coverage-qualified leads pulled from the network footprint.
A warehouse clerk photographs a supplier invoice. Aelita uses Claude Vision to extract every line item (product names, quantities, unit prices, totals, tax breakdowns) and maps them to your inventory catalog. She pre-fills the Goods Received Note and highlights discrepancies against the original purchase order: wrong quantities, price mismatches, missing items.
Aelita continuously monitors billing cycles for exceptions that need human attention: failed payment retries, contracts with expired payment methods, suspended accounts approaching grace period limits, and credit notes that exceed threshold amounts. Each exception comes with a recommended action and priority level.
Aelita cross-references coverage maps with contract data to identify addresses within your network footprint that aren't yet customers (coverage-qualified leads). She generates segmented promotional lists based on plan type, location, or contract age, and normalizes messy address data for campaign targeting.
AI for the people who keep the operation running. Daily supervision, semantic KB search across the SOP library, an onboarding atlas for new hires, live promo lookups so quotes are always current, a category suggestion on every new note, and management-facing reporting on AI usage, cost, and answer quality.
A daily automated review of team activity across all notes and tasks. Aelita identifies overdue work, unassigned tasks, missing schedules, and quality issues, delivering a prioritized summary to team leads so nothing falls through the cracks.
Aelita searches your internal documentation library (SOPs, guides, vendor manuals, policy documents) using v9 semantic search powered by a local voyage-4-nano embedding model. Multilingual: an English question finds the relevant Bulgarian SOP. ACL-filtered: agents only see documents they have access to.
When a staff member hits the "Report a Bug" button, Aelita walks them through it. She checks whether the issue is truly a system defect or actually a customer-specific case that belongs on a walk-in note, asks clarifying questions to fill in the missing context, assembles a clean ticket, and routes it to the right owner. Fewer vague bug reports, faster fixes.
Atlas is Aelita's welcome mat for new hires. On day one, a new agent, billing clerk, or technician can open a single illustrated guide that walks them through the ERP by concept (money, network, people, places) so they learn which module opens for which task. Discoverable from inside the Knowledge Base, designed to be read end-to-end in one sitting.
When staff ask "what promos are running right now?", Aelita doesn't guess. She pulls the current active promotions directly from the pricing engine in real time. Every answer reflects today's live rules: promo names, validity dates, applicable plan groups, discount details. No stale documentation, no outdated spreadsheets.
When a staff member writes a new note, Aelita reads the text and suggests the right category — so notes are filed correctly the first time. Correct filing keeps everything downstream accurate: reporting, escalation, and team routing all depend on the category being right. The suggestion is advisory; the agent stays in control of the final pick and can accept it or choose another.
Management-facing reports track every AI interaction: session counts, token breakdowns, month-to-date spend against a monthly credit, and per-model and per-feature cost. Alongside the spend view sits an answer-quality queue where supervisors rate Aelita's help answers and flag any that need the knowledge base improved. A credit-usage banner gives a green / amber / red read on the budget at a glance. Governance and budget oversight are built in, not bolted on.
What every capability above rides on. Reasoning depth, persistent context across follow-ups, and one-click hand-off into the staff member's actual workflow.
Aelita now takes a deeper thinking pass on every multi-step job (verifying invoices, drafting ticket replies, running daily operations reviews) so her answers hold up across complex cases, not just simple ones. Document scanning also gained full-colour vision, letting her read faded handwriting, recognise ID cards by their colour cues, and handle higher-resolution supplier invoices without losing small-print details.
Aelita is not a one-shot Q&A box. Each interaction opens a persistent conversation session. Ask a question, get an answer, then follow up with "tell me more about that" or "what about the billing part?" and Aelita remembers the full context of your prior exchange. No need to repeat yourself or re-explain the situation.
Every response Aelita generates can be copied to your clipboard with a single click. Paste it directly into a ticket reply, an email to a customer, an internal note, or a Slack message. No manual selecting and formatting. The response is ready to use the moment Aelita produces it.
The call. A customer phones in: "My internet was fine until yesterday, and now my bill is different from last month." The support agent opens the customer record. Before they have finished typing the ticket subject, Aelita has already assembled the context.
What Aelita found. The customer's ONU shows -24.5 dBm receive power (marginal but within spec). Their plan was upgraded from 50 Mbps to 100 Mbps on the 15th, mid-cycle, which triggered a pro-rata charge. Aelita drafts a response explaining the billing difference and notes that the signal quality, while acceptable, is trending downward and may benefit from a technician visit within the next month.
The result. The agent reviews Aelita's draft, adjusts one sentence to match their style, and sends it. They flag the signal quality note for the NOC team. Total call time: 3 minutes. Without Aelita, the agent would have navigated 4 different screens, manually calculated the pro-rata, and missed the signal quality trend entirely.
Aelita is designed to accelerate human decisions, not replace them. Every safeguard is structural, built into the architecture, not just a policy document.
Aelita is powered by Claude, Anthropic's frontier AI model. Claude excels at understanding complex operational contexts, producing accurate structured data from unstructured inputs (invoices, diagrams, tickets), and following nuanced instructions. Exactly the skills ISP operations demand.
Claude's vision capabilities enable document scanning (supplier invoices, network diagrams), while its language understanding powers ticket copilot, billing analysis, and exception detection.
Anthropic's focus on AI safety aligns with ISPCQ's draft-only, human-in-the-loop architecture. Aelita is both powerful and predictable.
Embeddings for semantic search use voyage-4-nano running locally; the vector store is sqlite-vec. Retrieval and customer data stay on your infrastructure; only the answer-generation step calls Anthropic's API.
Captain Memo is an open-source Claude Code plugin built and maintained by ISPCQ. It gives Claude Code a persistent memory layer across sessions: indexed observations, skill-aware search, and corpus-wide retrieval over the developer's own knowledge. The same memory primitives we use internally to keep Aelita's working context coherent across long ERP work sessions.
Released under an open-source licence because the AI-tooling community benefits when memory infrastructure is shared, and ISPCQ benefits when more developers help harden the layer we depend on.
Local-first by design. Captain Memo's embeddings, search index and observation log all live on the developer's own machine — SQLite for storage, no cloud component, no API key required to run it. The same data-sovereignty constraints we apply to Aelita itself.
If you're building Claude-powered tooling for your own operations team, Captain Memo is a useful starting point. Pull requests welcome.
Captain Memo is the open layer. Captain Fleet is the commercial product we built on top of it — a private hub that brings a whole fleet of AI captains, running on machines you own, together under one cockpit, with a relay in the middle that never reads a byte of what it carries. It's a different product from this ISP ERP, made by the same people who build Aelita.