A call centre that lives in a browser tab

Almutakamela tests and registers vehicles in Dubai. Its customers ring all day, in Arabic and in English. This platform runs the whole call centre as one web app: agents answer in the browser, supervisors watch the floor live, and every call ends up in a report nobody has to compile.

مركز اتصال كامل داخل المتصفح
5 screensConsole, softphone, staff chat, WhatsApp inbox and vehicle data, behind one login
8 rolesFrom agent to administrator, plus read-only auditors and a voice-prompt editor
1.2 millionVehicle records searchable in milliseconds, with every look written to an audit log
332 checksAssertions covering permissions, vehicle routes, campaigns and time handling

Roles

One login, a different app for each person

Nobody types a SIP password. People sign in as themselves, and the server decides what they see and which extension their browser registers.

Agent

Lands straight on the softphone: dial pad, today's figures, callbacks to return and a personal list of customers to ring.

Supervisor

Runs the floor. Sees who is ready, sets languages and break allowances, creates accounts and hands out campaign lists.

Manager and administrator

Everything a supervisor has, plus the extension pool, WhatsApp gateway settings and who may open customer data.

Auditor and quality control

Read-only. They can listen to recordings and read reports, and the server refuses every change they attempt.

Voice editor

One tab only: the recorded prompts and the switch that turns the auto-attendant on or off.

Outside caller

Works from a personal mobile. Sees only the names sent to them, and a number only while that name is open.

The floor

Watching the floor

A supervisor needs to know one thing at a glance: can somebody pick up the next call, in the right language?

Live status

Every agent on one line: language, answer priority, availability, headset, break time used and when they signed in.

  • Breaks are a daily budget, so three ten-minute breaks cost thirty minutes of sixty.
  • A supervisor can raise one person's allowance for today only.
  • A banner appears the moment nobody can take a call.

Staff and phones are separate things

Accounts live in one store and extensions in another. A supervisor assigns a person to a phone without ever seeing the credentials that could register it.

Voice and auto-attendant

The greeting, the language menu and the after-hours messages are edited here: upload a recording, or type the text and generate speech.

  • Switches are stored in the phone system's own database, so the call routing file is never rewritten by the app.

Softphone

The agent's phone is a web page

Calls arrive over WebRTC. The page registers itself the moment the agent signs in and stays open for the whole shift.

Softphone

Beside the dial pad sits everything the agent needs between calls.

  • Today's calls made, received and missed, and the break budget left.
  • Callbacks waiting: customers who rang after hours or gave up in the queue. One agent claims each, so nobody is called twice.
  • My list: campaign customers to ring. The number stays masked, and the server places the call.

Records

Every call, kept and counted

Reports read the phone system's own call records directly. There is no second copy to drift out of step.

Call history

Each call with its outcome, who handled it, how long the caller waited, their rating, the recording and the form the agent filled in.

  • Search inside transcripts to find what was actually said.
  • Click a number to see that customer's whole history.
Reports. A missed call is split by cause: rang and nobody picked up, nobody free, or the caller hung up first. Exports to Excel.
Incoming leads. One row per outside number: new or returning, how many times they tried, and whether anyone reached them.

Outbound

Outbound campaigns on protected data

The company holds over a million vehicle records. The platform turns them into call lists without handing anyone a spreadsheet of phone numbers.

Search and filter

Find an owner by name, mobile, plate or chassis, or filter by fleet size, vehicle type, make, nationality and licence expiry.

  • Duplicate company files are merged, so one company is one row.
  • Numbers are masked on the server for everyone below the top rung.
  • There is no export button, for anybody.

Campaigns

A supervisor builds a list from a filter and hands it out by count. Each agent works their share and writes a note after every call.

  • A customer can sit in only one list at a time, and rests 15 days after being called.
  • Leads nobody attempts go back to the pool by themselves.
  • "Reached" comes from the call record, not from what the agent ticked.
Audit log. Every search, open and call is written to an append-only database. If the log cannot be written, the data does not open.
Access. Permission to open customer data is granted per person, on its own ladder, independent of their call-centre role.
Outside caller. A colleague off-site gets a plain list on their own phone. A note is required, and Done is final.

Messages

Written conversations, same place

Customers who prefer to type, and colleagues who need a quick word, are handled without leaving the app.

WhatsApp inbox. One company number, shared. An agent takes a conversation, hands it to a colleague or closes it, and supervisors see all of them.
Staff messages. One-to-one chat with attachments and a team-updates board with read receipts. Messages cannot be edited or deleted once sent.

Architecture

How it is built

A small, deliberately plain stack: one Node server, the phone system it sits beside, and SQLite. No build step, and no framework on the front end.

CallerRings the company number
Office exchangePasses the trunks on
AsteriskGreets, records, queues by language
Browser softphoneJsSIP over secure WebSocket
Panel serverNode and Express behind nginx. Talks to Asterisk through its command line and key-value store.
Call recordsRead straight from Asterisk's own log and joined to recordings by call id.
Vehicle and campaign dataSQLite with full-text search, queried in a worker thread so a heavy search never stalls a live screen.

The app never rewrites the phone system's routing. Every switch it offers, such as the auto-attendant, weekend closure and an agent's language, is a value the routing reads at call time. A mistake in the panel cannot take the phones down.

Decisions

Decisions worth explaining

The parts that took the most thought are mostly invisible in the screenshots.

Deny by default

Role rules are enforced at one point every request passes through, so a new route is closed until someone opens it. Read-only roles are refused there, not page by page.

Masking happens on the server

A masked number such as 97150***567 is all the browser ever receives. Click-to-call sends a lead id, and the server dials from the agent's extension.

Two lists can never claim one customer

Checking who is already listed and inserting the new leads happen in one uninterrupted step, so two supervisors building campaigns at once cannot both take the same owner.

An audit trail that cannot be tidied

The audit database rejects updates and deletes with triggers. Notes on leads, chat messages and announcements are append-only for the same reason.

Answered means a person answered

A call counts as taken only if it reached an agent's phone, and an outbound call as reached only if talk time was above zero. The two tests differ on purpose.

One clock for everyone

Sign-in and call times are stamped by the server in Dubai time, so a report reads the same from any laptop in any timezone.