Twelve years of continuous evolution.

HR gets a recruitment pipeline, deal access follows the org chart, and the customer screen shows the live state of every fibre line. Inventory opens on a Store Board built for the storeman, and the field app, the Breaks board and the debit-order rail gain new detail.

• Recruitment pipeline — a new HR group with a CRM-style board from candidate to hired, an interviews list, a report and settings; each candidate has a five-step record with result buttons, files and a full history; ID numbers are masked, revealing one, exporting and anonymising are separate rights and each is audited, and the ID check follows the operator’s regional settings and flags a mismatch without ever blocking a save
• Access explained — the employee record shows, read-only, every role a person holds and why: given directly, by an org unit they sit in, through another role or as overseer, worked out by the same logic that enforces access; a role declared on an org unit reaches everyone placed beneath it
• Deals follow the org unit — every deal carries an org unit, and a person sees the deals of the units they are seated in and of the units beneath; one separate right sees every deal, the rule fails closed, and country territories are retired
• Removed deals can be brought back — a Removed list shows who removed each deal and when, and Restore, a right of its own, puts the deal back in its stage or refuses and says why
• Partner activation from the deal — on a reseller or referral-partner deal waiting in the stage where partners are activated, a user holding the finance right and the Resellers menu right sees Activate as partner: the deal’s own company joins the chosen partner group and is marked an active partner, the audit log and the company’s history both record it, where the deal’s type has a next stage an optional tick-box (for anyone who may move deals) also moves it on, and a deal that cannot be activated is refused with a plain reason and nothing is changed
• Live line status in every fibre contract header — a chip shows the unit’s state with a running timer, updated by server push, and where the customer holds the unit the contract card shows the same as a colour, an icon and a word; pressing Reboot shows the unit as rebooting and tells whoever pressed it when it is back
• Network Health and Infrastructure as live boards — counters and a status lamp, an alert strip for access nodes that stopped responding, only the parts that changed are re-fetched, the project chosen in the header limits its counters and lists, and customers behind a dead node are counted
• Move PON port — on supported OLT models, re-point every customer on one PON port to another OLT in one action when a port migrates to a replacement; the target’s live ONU list is checked first, the move is applied all-or-nothing, operator labels are never overwritten, and moving the port back is the rollback
• Phone, portal and API agree on a mass outage — the phone line, the customer portal and the network API ask the same rule, a power cut no longer reads as an area outage, and the thresholds are settings
• A redesigned Customers page — a summary band (line status, balance, contracts, open items) above a contract index grouped by what needs attention, the selected contract beside it and a side rail of customer, billing and journal cards; the cashbox opens as its own card and warns before a cash payment is confirmed with no register open; it is given by role or to one person, and staff without it keep the classic page
• Breaks as a presence board — where fingerprint punches are recorded, managers, team leads and HR see who is in, arrived, not scheduled, without a punch yet or gone, with clock-in and clock-out beside each name; the board also takes several teams at once and steps day by day with past days read-only; the times are for display and do not change attendance or payroll
• Fingerprint terminals read directly — where ZKTeco-protocol terminals are connected, the ERP reads their punches itself, resets a drifting terminal clock, raises one task when a terminal cannot be reached, and backs each terminal up every night, clearing its log only after a verified backup
• Companies in more than one country — each of the operator’s own companies records its country of registration, and its registration and VAT numbers are formatted and checked on the server against that country’s rules
• A Store Board for the storeman — Inventory opens on an item search that takes scanner input, a strip for what needs attention, three large job buttons (vehicle keys, receive a delivery, issue stock) beside the queue of requests from other teams, and it updates itself without a reload; every Inventory screen now shares one flat, tablet-sized look in light and dark
• Managers of one store — a manager is limited to the stores their team runs and lands on the Store Board, with receiving, issuing, transfers, counts and reports for their own stores only, no prices and no other store’s stock; access is handed to the team through the org chart, so leaving the team ends it
• Van Keys inside Inventory — filter buttons (All, Keys out, In the yard, Permanent), a red days-out marker for keys not back in time with the limit set by the operator, an alert on the tile for a licence disc that is missing, due or expired, and a History tab of recent sign-outs with the return-check answers
• Debit-order batches to the bank — in South Africa a batch can go to the bank’s collections API after a dry-run preview, a Status check lists each rejected collection with the customer and the bank’s reason, a lock stops a batch being sent twice, and bank-feed monitoring alerts Billing after a configurable period without a good run
• The field app, seen from the office — a job completed on the app carries a Field App badge and the device used on its task card, the Activity Log records when it was started and completed there, and the Protocol Register and Protocols to Bill mark protocols done on the app; tapping I’M ON SITE records the arrival and starts the job, and a job type can optionally require the agent’s own signature and selfie before COMPLETE JOB
• Handover protocols you can check — each protocol PDF carries a security code worked out from the stored record, staff can check a number and code on a Verify a protocol screen, and the stored copy can be e-mailed to the customer again from the note
• Sharper task views — My Open Tasks gets one-tap quick filters with live counts, and a closed task’s Schedule strip marks the actual close with a caption in words; a job finished on the app without signal uses the technician’s phone time, labelled as such

The pipeline now speaks fibre wholesale: deals have a type and a lifecycle, a route is a set of services each priced in its own currency, and a report by country is ready for the board room. Files can live in the operator’s own Microsoft 365, and the vans are on a live map inside the ERP.

• Deal types and a lifecycle — your own types, for example capacity lease, IRU, build-to-suit, managed service or one-off project, each with the stages that fit it; a deal counts as won when the contract is signed, and only finance can move it on to delivery; stages, sub-stages and deal types are the operator’s own, configured from the CRM screens
• A new deal in under a minute — one question per screen (type, company, name and country, optional contact), then a check screen; the contact person is created with the deal, and everything else waits for the deal page
• Services, each in its own currency — a route is itemised into services, each priced in its own currency with its own SLA tier; totals are shown per currency and never silently converted
• A pipeline report by country — per-country tables, Excel export and a clean A4 print to PDF; every reached, open, won or lost figure opens the deals behind it, found by the stages they passed through, including stages since retired
• Duplicate checks that warn, never block — a likely twin account or person is shown before saving; the user confirms and the decision is audited
• Territories — a salesperson can be limited to the deals of chosen countries, and a sales-only seat opens straight onto the pipeline: each role can have its own home page
• Microsoft 365 SharePoint as an optional file storage backend, for operators already on Microsoft 365 — files land in readable folders (per note, per deal and document category, per call) in a library restricted to the right people; an upload that cannot reach the cloud is refused out loud, never parked somewhere else
• Every file shows where it lives — a small storage label beside each attachment, and a nightly sync moves anything still held in the database to the operator’s cloud
• The fleet on a live map — a mission-control cockpit that updates every few seconds: moving, parked and offline at a glance, with light, dark and satellite maps and vans on the network map too
• Route history over any period — up to 31 days with the km for exactly that period, a replay coloured by speed, stops named after home, offices and depots, and Excel or CSV downloads
• Vans with keys, homes and owners — stores hand out and take back van keys on a big-tile screen; each van belongs to org units that decide who sees it, and a van leaving home outside its driver’s rostered shift, or with a service or licence falling due, raises a task by itself

Last release put a deal pipeline in Sales. This one gives each deal a memory: a single timeline that merges every stage move, call, meeting and file into one story, documents filed on the deal the way a salesperson actually thinks about them, and a way to file paperwork that already carries a number from somewhere else without being forced to mint it a second one.

• Life of the Deal — a collapsible, chronological timeline on the deal page merging every stage move, logged activity and file change into one story, one chapter per stage visited; a stage that overstays its welcome ages amber then red against the pipeline board’s own existing threshold — but never for a deal that’s closed, whose history reads as settled rather than alarming
• Deal files, filed the way a salesperson thinks — KYC/Compliance, Signed Contract, Proposal/Quote and Correspondence as their own categories directly on the deal, plus one flat documents folder per route leg; upload, thumbnail and count all live on the page the deal already has, with no separate document tab to remember
• An existing reference can be recorded, not just generated — paperwork that already carries a number from somewhere else, such as a scanned legacy protocol or a prior system, keeps that number instead of being forced into a new one; gated per reason, so it only appears where it makes sense

A deal pipeline arrived inside Sales, shaped for the deals an operator makes rather than the deals a software vendor does: routes with legs, three kinds of money, stages the operator defines, on the same customer record the contract will bill. Around it, coverage now answers from the fibre map, building maintenance gets a dated queue, a voicemail becomes the ticket, and access follows the org chart. The CRM has its own page.

• Deal pipeline — a board of deals in stages, colours and stale-after thresholds the operator edits as rows, not code; drag a card to move it, with the reason and the competitor asked for on a lost stage; the board refreshes itself when a colleague moves something
• Three kinds of money — one-off, monthly and annual figures kept as three numbers per currency, never lumped together, with a contract value priced over the term as the only combined figure; probability and the owner’s forecast call are separate fields, and both are kept
• A deal can be several legs — a cross-border route itemised into legs, each with its own country, distance, fibre pairs, builder, term and price; the deal total is the sum of them, priced over each leg’s own term
• Activity is a task — calls, meetings, tasks, notes and sent emails file as ordinary notes tagged to the deal; a dated next step shows on the board, the list and the deal, and climbs the escalation ladder when it goes overdue
• Money is a separate permission — without it the amounts are removed before the page is built: from the board, the deal, the CSV, the rendered documents and the change history; a save over a colleague’s edit is refused, naming them
• A funnel report that shows its own sample size — per stage: reached, open, won, lost, win rate among decided deals only, median stay and median age sitting now, every figure with its n=
• Coverage asks the fibre map first — an address inside a built footprint is covered; one inside a sold but unbuilt area becomes a pre-order that stays in the pipeline instead of vanishing, and a Pre-orders view groups that waiting demand by suburb so the build team can rank the next area by who is already asking
• Building maintenance requests get a dated queue — a structured request states the work and the customers it affects, cannot be filed without a date, assigns itself to the responsible team and lists nearest-scheduled-first; a declined request keeps its reason on record
• A voicemail from a known customer becomes the ticket — the message is transcribed within minutes of being left and opens the ticket with the customer’s actual words, day or night; an after-hours message also shows on the customer’s call history with its opening words, and a customer with no email on file still gets a ticket
• Tasks carry a delivery target — each job type can set a working-day target counted from the planned date, shown on the task row as 3 of 15: green while there is room, amber as the target closes in, red past it, with time spent on hold given back
• Access follows the org chart — a division, team or crew declares which system roles its members, leaders or crew leaders hold, so placing someone grants them and moving them away takes them back; every change is audit-logged with its before and after, and the dialog states how many people a declaration reaches before it is saved
• A stale agreement can no longer be installed against — where the operator switches it on, a first activation on an unapproved standard-service agreement older than a configurable window is refused at every point where a line can be switched on, the contract wears a Re-sign badge and a warning on its account page, and the customer signs again before the line goes live; helpdesk agent accounts likewise now follow a tick-box on the employee record where a helpdesk is connected

Field work generates documents — acceptance protocols, billing states, sign-offs — and most systems treat them as attachments nobody can query. This release turns them into structured, conditional, auditable records: the right form appears on the right job by itself, a job cannot close while its paperwork is missing, and what was captured becomes a column you can filter and a question you can answer.

• Capture forms attach by condition — a form appears on the jobs it belongs to, chosen by category, type or a field’s value, rather than being wired up one category at a time; office staff can now complete them too, not only the field app
• Close gates — each attached form is set to ignore, warn or block, enforced on every path that closes a job, so “the paperwork exists before this is finished” is a rule rather than a habit
• Captured values become columns and filters — “which acceptance protocols have not come back?” is now a saved view instead of an afternoon of opening records
• Every capture is audit-logged as it is written, so a completed form and who completed it survive in the job’s history
• Billing state follows the job — proforma, invoiced, awaiting payment and paid progress on the job’s own billing sub-task, and the protocol register reads through to show a live count (0 of 1, 2 of 3) instead of a tick-box that locked on first save
• Sub-task schedule tree — a parent job and its sub-tasks as bars on one calendar axis with a NOW line and zoom that adapts from three-hourly to weekly; scheduling a sub-task past its parent’s window offers to move the parent so the clock re-arms from a date that is actually ahead
• New Signal track — the survey visit that precedes an installation is now its own step with its own numbered document series, and the time a job takes on site is recorded separately from the window it was promised within
• Network operations board — a live status lamp, a sixty-second refresh with a visible countdown, nodes that carry their own names, and a failed refresh that says so instead of silently blanking the board
• A third operator went live on the platform, on its own database and domain, from the same codebase

Staff systems are easy to switch on and easy to forget to switch off. This release closes that loop: hiring someone provisions their accounts, and a termination date takes them away again the same night — no ticket, no checklist, nobody remembering. It also gives the paperwork field crews produce a register you can actually search.

• Staff mailbox auto-provisioning — the mailbox is created on hire and de-provisioned on termination, from the same nightly sweep that manages cloud accounts. ISPmanager today; FastPanel and cPanel in development
• Protocol Register — every numbered acceptance and handover document in one searchable place, each reference carrying a check digit so a mistyped number fails instead of matching the wrong job
• Protocol numbers are searchable from the journal, landing you on the job that produced them
• The employee form now states what saving it will create, and fills a missing staff address from the name

Support calls stopped being unsearchable audio. Every answered call is now transcribed automatically, separated by speaker, attached to the customer’s record and searchable as text — so “what did we actually promise that customer in June?” becomes a search box rather than an afternoon of scrubbing recordings.

• Automatic call transcription — every answered call is transcribed within minutes of the handset going down, with nobody having to remember to start anything
• Exact speaker separation — the agent and the caller are captured on physically separate audio channels, so who said what is a property of the recording rather than a statistical guess; the transcript reads back as a conversation, turn by turn
• Transcripts on the customer timeline — the text sits on the call in the customer’s own history, beside the notes and tickets it relates to, so the context is where someone is already looking
• Call Transcripts screen — one searchable view over every transcribed call, by free text, account number, caller number or the extension that answered — including the calls that never matched a customer record, which is where the awkward ones tend to hide
• Recordings play in the browser — the audio sits next to its transcript on the same screen, with no download and no separate player
• Transcription runs on self-hosted hardware — call audio is processed on a machine the operator owns, with an external service only as a fallback

The release where the platform started facing outward. Customers can buy their own hardware without phoning anyone. The public marketing site moved inside the ERP, so the people who set the prices are the people who publish them. Staff sign into a connected application with their ERP identity, permissions included. And a 24/7 operation stopped being rostered in spreadsheets.

• Equipment Shop — customers browse the hardware catalogue, build a cart and check out from the portal; the order lands as a billing-routed ticket on their own account, so there is no separate order system to reconcile and no new place for a sale to go missing
• Staff single sign-on — the ERP is now an OpenID Connect identity provider, so a connected application signs staff in against their ERP account and receives their effective permissions in the token; no second user directory to keep in step, and no chance of the two drifting apart
• Built-in website CMS — pages, blog posts, a media library, categories and promotional splashes for the public marketing site are all edited inside the ERP, with best-seller badges calculated live from real contract counts instead of a hardcoded favourite that rots at the next reprice
• Shifts Calendar — a whole month of rosters on one board with every team and crew in view, set by dragging across a person’s row; periods that are finished or already have attendance recorded lock themselves against edits, and every change is audit-logged
• Out-of-Office tracker — the paper log at reception, replaced: staff request a step-away with a reason, reception approves it, the ERP locks itself behind a cover screen while they are gone, and shared keys are checked out and back against a registry so two people can never hold the same one
• Leave Payout — a statutory carry-over calculator with permission-gated encashment straight to the ledger, plus a self-service leave statement PDF that answers the “where did my days go?” question without an HR ticket
• Bonus incentives — four new bonus types including six-month milestone accrual, attendance and no-show fees, all defined in configuration rather than code, so the comp scheme changes without a release
• Coverage import, made first-class — importing a coverage footprint moved from a command-line job to a real screen, and it now re-checks previously-declined addresses against the new footprint; one import handed eighteen forgotten leads back to sales
• Notes close-gate — a parent note can no longer be closed while its sub-tasks are still open, and closed-note filters arrived across the hub, the personal radar and the calendar

A trust-and-control release. Notes gained a real privacy primitive, account credit can move between customers in a few clicks with a full audit trail, managers can delegate reach to an assistant, and the debit-order rail to FNB closed its last manual step.

• Private (DM) notes — mark any note or task private so it’s visible only to its officer and assignees, hidden even from admins with view-all rights, with need-to-know area visibility and a Confidential category for management-only matters
• Internal Credit Transfer — move account credit from one customer to another by name or UCN, with a live before-and-after preview, an automatic service re-check on the receiving account, and a full audit trail
• Personal Assistants — assign a PA to a manager so they’re reachable and escalatable wherever the manager is, with per-link “can see notes” and “auto-escalations” toggles and zero added authority
• Note Groups & configurable auto-close — organise the category/reason picker into named, drag-reorderable groups, and set per-type inactivity windows so throwaway quick-notes close themselves as “Auto-closed (stale)”
• FNB debit-order automation — submit debit-order batches through FNB’s EFT Collections API and import FNB’s load-result files to flag rejected collections automatically
• Notes Journal polish — a per-user selectable sort order, an “Awaiting you” reply indicator, a closed-note freeze that keeps the record honest, and the unread bell count mirrored into the browser tab title

A focused point release on two operator wins: a new way to take money up front, and an assistant that stops treating planned-maintenance complaints as emergencies.

• Optional prepayment bills — staff can offer a customer a multi-month prepayment that defers service activation until it is paid, with one-off optional charges, a period/tier picker (“pay six, get seven”), and a three-layer guard that makes accidental double-payment impossible
• Maintenance-aware AI triage — when a customer complains during a scheduled-maintenance window, Aelita recognises it and replies with the planned window instead of escalating the ticket as a fault
• NAS & IPACCT spotlight — a new deep-dive on the IPACCT NAS integration brings contract-driven provisioning, the tolerance grace period and live in-contract usage together in one place, at /network-nas

A tight stabilisation cycle that turned three of v3.4's biggest investments into the experiences they were meant to be. Status workflows became a visual graph editor. The Field PWA on-site flow lost every "what do I do next?" moment. The Schedule Calendar acquired a lens so dispatch managers see capacity, not coverage. Plus illegal-ONU enforcement on the network side and ONU-lifecycle config integrity.

• Visual Status Workflow editor — drag-to-connect transitions, inspector side-panel, inherited rules ghosted in, system transitions visually locked, per-(type, area) layout persisted across sessions. The list view stays as a fallback toggle
• Field PWA on-site capture, idiot-proofed — spec-driven flow always on, step-by-step guide as the visual spine, live photo-phase progress indicator, persistent camera-blocked banner instead of a one-shot toast, dead "Phase-1 fallback" retired
• Schedule Calendar v3.9 — capacity-focus lens that dims unrelated events, team-scoped roster respecting user access, header lens-hint strip, hover tooltip with note detail on every event card, footer legend cleaned up
• Illegal ONUs page — OLT and slot/port filters surface unauthorised ONUs before they reach the billing path
• Dedicated SVLAN preserved through ONU lifecycle — the SVLAN provisioned at contract activation survives ONU replace, return, and re-issue cycles; IPACCT gating prevents the "active service on a non-billing record" drift
• aj_table cascading filters — second-level filter dropdowns auto-narrow when a parent filter changes, across every admin list that uses aj_table

The biggest mobile addition since the platform began: the Field UI — a phone-first PWA that replaces paper-and-WhatsApp dispatch for field technicians. Same release ships a Mission Control cockpit for the admin dashboard, Dispatch Board v3 with eleven new affordances, and Aelita as a chat participant in Nextcloud Talk groups.

• Field UI — install-to-home-screen PWA with today's task list, GPS-logged on-site steps, ONU serial scan, photo uploads, customer signature, confirmation selfie, auto-emailed protocol PDF, 2FA, and an online/offline indicator
• Stats Mission Control cockpit — live sFlow uplink throughput, USER BANDWIDTH headline, pending/late split, payment-method collection bar, peering link, mobile pass
• Dispatch Board v3 — persistent URL routing, drag-to-resize duration, click-empty to quick-add, status filter chips, overdue chips, Field UI sync callout, keyboard shortcuts, hover tooltips, idiot-proof drag
• Aelita as a Nextcloud Talk participant — talk to Aelita inside any Nextcloud chat group; per-agent ACL across both tenants; group/DM wake-word gate
• Sales Directory phonebook, Note Forms template library (Phase 2.7a), Ask Aelita usage reporting, configuration dark-mode sweep across 47 templates, tablet responsive floor raised to 1199px

Walk-in Visitor Log, Bug Report System, Dispatch Board with crew presence, Org Units assignment, break scheduling. Walk-in flow on the customers tab. Self-service audit-trail exports.

• Walk-in Visitor Log with customer auto-matching
• Bug Report sidebar with auto page-URL capture
• Dispatch Board with crew presence toggle
• Org Units division/team/crew hierarchy
• Break scheduling with 30/60-min duration picker

NOC map enhancements, customer portal Portal Badger, smart-cleanup of stale records. Cluster-detect for fibre outages. Live PBX dashboard.

• Portal Badger one-click connection repair
• Fibre outage cluster-detect
• Live PBX dashboard with agent status
• Stale-record smart-cleanup

20-second auto-refresh on open notes. Draft-text preservation across refresh. Telegram NOC alerts. Nextcloud account auto-provisioning. Bulgarian EUR migration support.

• 20-second live auto-refresh on open notes
• Telegram NOC channel integration
• Nextcloud account provisioning on hire
• BGN to EUR migration handling (2026-01-01)

The biggest architectural addition since the platform began. Aelita ships with eighteen capabilities organized into five clusters: customer-facing, field & NOC, finance & inventory, internal staff helpers, capability fundamentals. Powered by Claude with voyage-4-nano embeddings and sqlite-vec.

• 18 AI capabilities shipped at v3 launch
• Draft-only safety, permission-scoped
• voyage-4-nano embeddings + sqlite-vec store
• Per-tenant scoping for SOP search

Notes Hub Dashboard with dynamic views and saved filters. Status Workflows with configurable state transitions. Operational KPIs (response times, resolution rates, SLA compliance). Outage Quick-Log. Configurable leave types with auto-login-block.

• Notes Hub Dashboard with dynamic views
• Configurable status state machines
• Operational KPIs with SLA tracking
• Outage Quick-Log from any view

Cabling-crew dispatch (v1, 2014). Multi-tenant kernel (v1.5). Smart Price Matrix (v2.0). Multi-vendor OLT abstraction (v2.2). IPACCT NAS integration (v2.4). Customer Portal with 2FA (v2.5). Cashbox supervisor with 4-role separation (v2.6). HR + payroll (v2.7).

• Cabling-crew dispatch & service journal (v1)
• Multi-tenant kernel (v1.5)
• Smart Price Matrix promotional engine (v2.0)
• Multi-vendor OLT (v2.2), IPACCT NAS (v2.4)
• Customer Portal (v2.5), Cashbox supervisor (v2.6), HR/Payroll (v2.7)