The company's shared system for sales, finance and network operations across Ghana, Nigeria, Liberia and Uganda. Everything you enter saves instantly to the shared database, syncs to your colleagues within seconds, and is recorded in the audit trail.
Your administrator creates your account. You'll usually receive an invitation email — click the link, and the app asks you to choose your own password before letting you in. From then on, sign in at the company address with your email and that password.
If you were given a temporary password instead, sign in with it, then change it any time via "Forgotten your password?" on the sign-in screen (a reset link is emailed to you).
Everyone who signs in can see everything — transparency is deliberate. What you can edit depends on your role — and roles are configurable: administrators manage them in Team & access → Roles & permissions, a matrix of roles against modules where a tick grants edit access, applied to everyone with that role immediately and recorded in the audit log. The defaults:
| Role | Can create & edit |
|---|---|
| Administrator | Everything, plus Team & access (users, roles, passwords) |
| Director | Nothing — full read visibility for executives and the board |
| Commercial | Leads, accounts, contacts, deals, quotes, tasks |
| Finance | Quotes, invoices, expenses, accounts, tasks |
| Project Manager | Projects, circuits, project expenses, tasks |
| NOC Engineer | Tickets, circuits, tasks |
| Storekeeper | Inventory items and stock movements only, plus tasks |
| HR / People | Employee directory, tasks |
| Viewer | Nothing — read-only across the suite |
Administrators can also create entirely new roles (e.g. a Site Supervisor with just projects and tickets) and tick exactly the access that job needs. Every rule is enforced by the database itself, not just hidden buttons, so it holds everywhere.
If a screen shows "Read-only" for you, that's your role working as intended. If you believe you need edit access, ask an administrator.
Two ways: the green + New button at the top right opens a menu of everything your role can create, grouped by area; or use the + New … button on any module's own page. Fields marked with a red star are required.
Click any row (or pipeline card) to open its drawer — the panel that slides in from the right with the full details and every related record. From there, Edit changes it, Delete archives it.
The search box at the top searches everything at once — leads, accounts, deals, circuits, tickets, invoices and more. Type two or more characters and pick from the results.
Deleting archives a record rather than destroying it, and the audit log keeps the full history. If something was deleted by mistake, an administrator can restore it.
Your morning view. The cards across the top show open pipeline, receivables, circuits (active and in delivery), running projects, open tickets (with critical P1s highlighted) and low-stock items. Below: pipeline by stage, deals by country, your tasks due, and the latest team activity.
USD figures combine all currencies at indicative rates for the roll-up only — every record keeps its true currency underneath.
A lead is someone you're talking to before they're real business. Capture them early, update the status as conversations progress (New → Contacted → Qualified), and when it's real, open the lead and click Convert to account + deal — the system creates the account, the contact and a prospecting-stage deal in one step.
An account is a company (MNO, ISP, government, bank, DisCo partner); contacts are the people there. Open any account to see its whole relationship on one screen: contacts, deals, quotes, invoices, circuits, projects, tickets.
Each deal carries a value, currency, service type (dark fibre IRU/lease, managed capacity, backhaul, colocation…) and route-km. On the Pipeline view, drag a card between stage columns to move it — the change saves and is audit-logged instantly. Use the List toggle for a sortable table. Keep expected close dates realistic; reports use them.
Create the quote, choose the account and currency, then add line items — description, quantity, unit price — and watch the total build. Move the status through Draft → Sent → Accepted (or Declined). When a client accepts, open the quote and click Convert to invoice: line items and currency carry straight into a draft invoice.
Invoice statuses are computed, not typed: record payments against an invoice (partial payments welcome — amount, method, date and reference) and it moves to Part-paid or Paid by itself, while a daily check flips anything unpaid past its due date to Overdue. Each invoice shows its total, paid-to-date and balance due, with the payment history beneath.
Recurring billing: on the 1st of every month the system generates one draft invoice per client from all their Active circuits carrying an MRC (set the monthly recurring charge and its currency on each service order) — one line per circuit. Finance reviews the drafts and sets them to Sent. Finance also receives a weekly receivables digest by email listing overdue invoices, and the Receivables aging report breaks balances into current / 1–30 / 31–60 / 61–90 / 90+ buckets by account — rolled up in USD using the exchange rates administrators maintain in Settings → Exchange rates.
Quotes at or above the USD approval threshold cannot be sent until an approver signs off: request approval on the quote, approvers are emailed, and their decision — who, when, and any note — is stamped on it. Editing the line items after approval honestly voids it, forcing re-approval. Large expenses work the same way: only the approver role (Director by default) or an administrator can approve them; smaller ones flow normally. Administrators set the thresholds and the approver role in Settings → Approval rules. All of it is enforced by the database, so it holds no matter which screen someone uses.
Log spend with category, amount, currency and country, and link it to a project so build costs stay visible. Approval path: Submitted → Approved → Reimbursed.
One record per circuit, from paperwork to live service: Survey → Design → Permits → Build → Splicing → Testing → Active. Record the A-end → B-end route, route-km, fibre count or capacity, and the target RFS date. Link the order to its deal so commercial and delivery stay joined up.
Build programmes and surveys, each with a manager, timeline, budget and progress bar. Open a project to see its expenses. Keep the progress percentage honest — the dashboard reads it.
Every ticket runs against an SLA clock set by its priority (P1 responds in 15 minutes and restores in 4 hours by default; admins tune targets in Settings). The ticket list shows each clock live — time left, "due soon," or breached — and raising a P1 emails the NOC team the moment it's created.
Work an incident with the action buttons on the ticket:
Post updates to the worklog on each ticket — a permanent, append-only timeline of comments and status changes with who and when. A server-side watchdog re-checks all open tickets every 10 minutes and emails the NOC the moment any response or restoration SLA is breached — even if nobody has the app open. The NOC / SLA performance report rolls it all up: MTTA, MTTR, SLA compliance and open breaches by priority.
Service-affecting faults also run against the Vobiss NOC escalation matrix. As unresolved time accumulates (hold time excluded), the system escalates automatically — Level 1 (NOC) at 50 minutes, through Business Development, Client Experience and the Operations Managers, up to the CTO at 7 hours — emailing each contact in turn, stamping the ticket's current level, and logging every escalation on the worklog. Each ticket shows its current level and who's next. Resolving a fault resets the chain. Administrators edit the contacts and timings in Settings → Escalation matrix; changes take effect from the next 10-minute check.
Field issues track what stops the build — right-of-way disputes, permits, community matters, materials, safety, access — each with severity, an owner and a target date (overdue shows red); crews can raise them from site. Work each issue with its action buttons — Start, Mark blocked (with the reason), Resolve (a resolution is required), Close — and every change lands on the issue's worklog, an append-only history from raised to closed. Attach photos of the issue, letters or permits — right on the create form (the photo uploads the moment you save), when editing, or directly onto the saved issue (on a phone, Choose File opens the camera; each upload is noted on the worklog). Open issues appear on their project. Network designs form a design register: route, km, fibre count, poles, closures, version — moving Draft → In review → Approved (who/when stamped automatically) → As-built. Each design also carries its own file library — upload the KMZ route, PDF drawings, CAD exports and as-built photos directly onto the design record (private to signed-in users; uploading follows the Designs permission; files open via short-lived secure links) — plus a route map link to the live geometry in GridFibre-Map or Google Earth. Milestones are the deployment plan: dated steps per project with owners; completing one stamps the time, anything past its date shows At risk, and the project rolls up percent-complete. Opening a project now shows the plan, progress, blockers, designs, work orders, materials and spend on one card.
Five reports now carry a Trend section — Receivables/aging, SLA & tickets, Field productivity and Pipeline — with a 6- or 12-month toggle. Each shows monthly spark-charts (collections, invoiced, faults, MTTR, SLA %, km strung, pipeline added) with direction arrows coloured by whether the move is good for the business, plus a plain-English read-out above the charts summarising what changed. These trend only event-dated figures (payments, tickets, field reports, deals) so the history is real, never reconstructed. Separately, the system now takes a monthly snapshot on the 1st of each month of the figures that only exist as "now" — MRR, receivables balance, headcount, contracts under management, stock value — so that balance-style trends (like the receivables line) become available once two months of snapshots exist and grow richer over time. Register-style reports (stock, contract list, people) stay point-in-time, where a trend would add nothing.
When an administrator assigns someone a role in Team & access (or changes it), that person automatically receives a branded welcome email — a short introduction to what the suite is, a section explaining exactly what their role can see and do, a button to sign in, and a note asking them to add alerts@vobissgh.com to their contacts so our mail reaches their inbox. It sends once per role assignment (editing someone's name won't resend it); to send it again, open Team & access and use Resend welcome beside the person.
Financial records are visible only to finance, directors and administrators — invoices, payments and credit notes are theirs alone; quotes and contracts are also visible to commercial; and expenses are visible to those roles plus the person who submitted the claim (so anyone can follow their own reimbursement). This is enforced by the database itself — other roles receive no rows even if they query directly — and the app matches it: the finance sections disappear from the sidebar and from account cards for unauthorised roles, and audit-log entries about financial records follow the same walls. Everything else in the suite remains open-book by design.
Invoices carry a VAT %; the card and printed document show subtotal, VAT and grand total. Payments can record a withholding tax (WHT) portion — cash and WHT are tracked separately and the invoice closes when cash + WHT + credits cover the total, so WHT-settled invoices stop haunting your receivables. Corrections go through credit notes (auto-numbered CN-YYYYMM-NNN; issuing one reduces the invoice balance through the ledger, never by editing history). Set a billing email on each account and overdue invoices are chased automatically — reminder at 7 days, firmer at 14, final notice at 30, each exactly once; tick Pause payment reminders on an account to exempt it. Documents: every invoice, credit note and account statement can be Printed (or saved as PDF via the print dialog), Downloaded, or Emailed to the customer directly (finance, commercial and admin roles). The contract register tracks each agreement's term, notice period, MRC and escalation: renewal alerts go to finance/commercial/admin at 120/90/60/30 days (each window once), expiry flips the contract to Expired with the MRC flagged at risk, and the Contract register & renewals report carries the investor metrics — MRC under contract, MRC at risk within 90 days, and weighted average remaining term.
Three behaviours run suite-wide. Creating a record opens it — save a new employee, issue or design and you land on its card, ready to attach files or add related items. Drilling in leaves a trail — open a certification from an employee (or a design from a project) and a ← Back link at the top of the card returns you exactly where you were, scroll position included; the trail runs as deep as you go. And on the HR card, rows expand in place: click a certification, training, review or KPI and its full detail unfolds right there — including certificate files with Open buttons — click again to fold; "Open full record ↗" inside the expansion takes you to the record itself for editing, with the back-trail waiting.
The employee register carries status (Active / On leave / Suspended / Exited), employment type, start date, contract end (flagged amber within 90 days), manager, and the suite sign-in email linking the person to their login. Employees are emailed automatically when a review or KPI is created for them and on every update, using the email on their employee record. Certifications carry a file vault: open one and upload the scanned certificate (private; uploads follow the Certifications permission). Record certifications on each employee — work-at-height, HSE, first aid, splicing — with expiry dates: HR is emailed automatically at 60, 30 and 7 days and on expiry (renewing the date restarts the cycle), and exited staff generate no reminders. Marking someone Exited stamps the departure and, if they hold a sign-in, emails administrators to disable it the same day — the dashboard's People & compliance card keeps a count of any exited staff still holding access. The Employees view is an HR cockpit: live chips (active staff, on leave, contractors, contracts ending, certs expiring, exited-with-access) with team and status filters, and each person's card tells their full story — staff ID, tenure, contract countdown, certifications with health tags, and their actual field activity (work orders and site reports linked by name and sign-in). The People & compliance report breaks headcount and certification health down by team for management review. Beyond compliance, the module carries the full people cycle: training needs captured per person and walked Needed → Planned → Completed (date stamped, with provider and cost); performance reviews per period — overall rating, strengths, improvements, goals — where finalising locks the review (only an administrator can amend it, and the lock is enforced by the database); and KPIs per person per period with target, actual and rating. Reviews and KPIs are visible only to HR, directors and administrators — other roles cannot read them even by asking the database directly. Field staff cards also show live operational numbers — work orders completed and km strung in the last 90 days — computed from site data, so the KPI conversation starts from facts. The HR role manages all of it without seeing sales, finance or network data.
Directors and administrators also get a Six-month trends section — spark-charts for pipeline added, cash collected, faults, MTTR, km strung and SLA compliance, with direction arrows coloured by whether the move is good for the business (others can enable it via ⚙ Customise). The dashboard is built from decision sections — sales pipeline, revenue & receivables (MRR, overdue, collected), network health (open tickets, P1s, breaches, MTTR), deployment & milestones, field operations, stores, and approvals awaiting action. Your role picks the default sections (finance sees money, the storekeeper sees stores, directors see everything), and ⚙ Customise lets each person tick sections on or off. The country selector in the top bar switches the whole suite — dashboard and every list — between All countries and each of your configured markets — administrators add or remove countries in Settings → Countries (removing one leaves existing records intact under "All countries"). Records inherit their country from their account (or their project's account), and tickets from their state — so keeping account countries set is what makes the tabs accurate. Reports remain all-country views.
Three reports turn operations into a story: Network performance trends (12 monthly rows — faults, MTTR, SLA compliance, controllable share — the "are we getting better?" view), Faults by state/region (where the network hurts — set the state on each ticket), and Network availability (downtime from resolved tickets measured against your Active circuits over 30 days, with a downtime budget against the target administrators set in Settings → Availability target).
Work orders dispatch crews: survey, pole make-ready, stringing, splicing, testing, maintenance or restoration — linked to the project (and circuit), with crew, site/section and date. Move them Planned → Dispatched → In progress → Completed; the completion time is stamped automatically. Field reports are the daily truth from site: one per crew per day per project, with the activity, the numbers (km strung, poles dressed, closures, splices) and any issues. Reports are append-only — site history is never rewritten; a correction is a new report. Everything rolls up onto the project automatically, and the Field productivity report ranks crews over the last 30 days. Crews sign in with the Field Crew role — work orders and reports only, usable from a phone browser on site.
Stock is managed with movements, never by typing quantities — this is what makes the numbers trustworthy. The buttons at the top of the Inventory page cover the five events that can happen to stock:
The system tracks stock per location and will refuse to issue more than a location actually holds — you'll get a clear message showing what's available. Every movement is recorded permanently in the Movements ledger (toggle at the top of the page); mistakes are corrected with a reversing entry, never by editing history. Each item shows its per-warehouse breakdown, dollar valuation, and a Low stock flag when it falls to or below its reorder level.
Tasks are to-dos with a due date and owner, optionally linked to any record — a deal to chase, a ticket to close out, a circuit to test. Tick the checkbox when done; overdue tasks show red. Employees is the team directory (name, role, team, country). Sign-in access itself is managed separately under Team & access.
Open Reports and pick from the dropdown:
Download CSV gives a file that opens straight in Excel. Print / PDF strips the menus and prints a clean page — in the print dialog choose Save as PDF to produce a file for a board pack or an email.
Every create, change and delete across the suite is recorded automatically — who, what, which record, and when. Filter by module. This is the company's accountability layer: nothing changes silently, and deleted records remain in the history.
On a person's row: change their role with the dropdown (it saves immediately and is audit-logged), or click Set new password to issue a fresh temporary one.
Deletes are archives. If something must come back, it can be restored in the database — contact the system owner.
| Problem | What to do |
|---|---|
| I can't edit something | Your role doesn't cover that module. If it should, ask an administrator. |
| My invitation email hasn't arrived | Check spam/junk first. Invite links also expire after about a day — ask your admin to re-invite you, or to set a temporary password. |
| I forgot my password | Sign-in screen → "Forgotten your password?" → follow the emailed link. |
| The app looks out of date | Hard-refresh: Cmd+Shift+R on Mac, Ctrl+Shift+R on Windows. |
| I deleted something by mistake | Tell an administrator — deletes are archives and can be restored. |
| Numbers on the dashboard look "wrong" | USD cards are roll-ups of several currencies at indicative rates; open the records for true amounts. |
| Who changed this record? | Open the Audit log and filter by the module — every change lists the person and time. |