AMIT CRM

Customer	Mobile	Program	Status	Source	Created by	Owner	Distribution	Created	Updated	Last activity	Last comment

Advisor workload

	Student	Mobile	Program	Created by	Source	Status	Current owner	Last comment	Created	Updated	Distribution

Student	Mobile	Program	Invoice	Amount	Evidence	Advisor	Sale	Recorded

Date from

Sales performance

Agent?	Day, Date?	Calls?	In?	Out?	Missed?	Duration?	Updated?	Registered?	Cash L.E.?	Review?

Understand this report

This report answers one question: what did each advisor actually do, day by day? Every number comes from the phone system and the CRM itself — nothing is estimated.

How each number is worked out

Agent

The advisor. Click a row to open it up into one row per day.

Day, Date

The day in Cairo time. A call at 00:30 at night counts for that day.

Calls

In + Out. Missed calls are not included here. So In + Out + Missed will not add up to this number — that is on purpose: a call nobody picked up isn't work the advisor did.

In

Incoming calls the advisor picked up. Counted straight from the phone system, which knows exactly when a desk phone is answered.

Out

Every call the advisor made, whether or not anyone picked up. Dialling is work, so it counts either way.

Missed

Incoming calls that rang this advisor's phone and nobody picked up. A count only — it adds no time.

Duration

Time on the line, added up across the day.

A call the advisor made: from the moment they dialled to hang-up. Waiting through the ringing counts — that is real effort and real time spent, whether or not the customer ever picked up.
A call the advisor received: from pick-up to hang-up. The ringing before they answered is not counted — a phone ringing at an empty desk isn't effort.
A missed call adds nothing.

Every second is measured by the phone system. Nothing here is estimated or rounded up.

Updated

How many different leads the advisor got on the phone about that day — called, or picked up a call on. Calling the same lead five times still counts as one. Only a call counts. Changing a status, leaving a comment or reassigning a lead is not an update on its own — that work still appears under "What changed" when you open the figure, but only for leads that were actually called. A missed call doesn't count: nobody called and nobody answered.

Registered

Students who actually enrolled, counted on the day Finance confirmed the deal — not the day the advisor submitted it.

Cash L.E.

Money collected on those Finance-confirmed deals, on the same day basis.

Review

Opens that day's leads so you can see what the advisor actually did.

What this report does not claim

It does not say which of your outgoing calls were actually answered — and that is deliberate, because the equipment cannot tell us honestly. Outgoing calls leave through a gateway onto the mobile network, and that gateway starts the clock the moment it grabs the line, before the customer's phone has even rung. So it reports almost every call as "answered", including calls that just rang out. Rather than show you a number built on that, the report shows what is certain: how many calls were made, and how long the advisor was on the line. Making this measurable is a known open item.

Two things that surprise people

Calls doesn't equal In + Out + Missed. Missed calls are deliberately left out of the Calls total. Nothing is broken.
An advisor can work a lead all day and still score 0 Updated. Updated counts calls, and only calls. Someone who spent the day changing statuses, writing comments and reassigning leads — without picking up the phone — will read as 0 here. That is the rule this report is asked to measure by, not a fault: if you want to see that work, open the lead's own timeline.
A call can belong to nobody. If a call came in on a line that isn't assigned to any advisor — a queue, a shared line, or an extension nobody has been linked to on the Team page — it is real, and it will show on the customer's timeline, but it can't be credited to a person so it appears in no one's row here.

Call counts should match the phone system's own report for the same days. If they don't, the extension-to-advisor links on the Team page are the first thing to check. Duration will read a little higher than the phone system's "billable time" column on outgoing calls — that is correct: billable time leaves out the dialling and ringing seconds, and this report counts them.

Leads created

Marketing performance

Created by?	Channel?	Leads?	Qualified?	Qual. %?	Won?	Converted?	Conv. %?	Revenue L.E.?	Rev/lead?	Junk?	Junk %?	Days to convert?

Checkout-link funnel

Channel?	Link sent?	Opened?	Opened %?	Started checkout?	Leads?	Lead %?	Won?	Paid?	Paid %?	Reached checkout, unpaid?	Revenue L.E.?	Refunded?	Paid before the call?	↳ token deal?	↳ no call logged?	Advisor-closed?

Date from

Advisor Manager review activity

Manager?	Day, Date?	Reviewed calls?	In?	Out?	Call duration?	Reviewed duration?	Updated leads?

Understand this report

This report answers one question: which recorded calls has each Advisor Manager actually listened to?

How a review gets here

A call counts as reviewed once you have heard enough of it — by default half the recording, or five minutes, whichever comes first. Both numbers are in Settings. Below that bar nothing is recorded, and the player tells you how much more is needed rather than leaving you guessing.

It counts each second of the recording once. Replaying the same passage does not get you closer to the bar — you have to hear new parts of the call. Skipping through does not either, because the parts you skip were never heard.

One review per call. The first manager to listen owns it. If a colleague has already been through a call, its green label says so before you start — and if you listen anyway, no second review is recorded and nothing is added to your figures. That is the point of the label: nobody spends ten minutes on a call somebody else has covered.

What “Reviewed duration” counts

It is the time the manager actually spent listening — measured while the audio is playing, and paused when they pause. Two consequences worth knowing, because they are choices and not accidents:

Listening at double speed counts as half the time. A ten-minute call heard at 2× is five minutes spent, because that is what it cost them.
Replaying a passage counts twice. Going back over the same thirty seconds three times is ninety seconds spent, because it was.

So this column answers “how long did they spend?” — not “how much of the call did they hear?” A manager who replays one tense minute six times will show more time than a colleague who heard a whole call once, and that is the intended reading.

Time keeps counting while the tab is in the background, since the audio is still playing. It stops if the computer sleeps — those hours are not counted.

Some rows show the call’s own length instead. Reviews recorded before listening time was measured have no real figure to show, so they fall back to how long the call was. The note under the table says how many of the rows you are looking at are which — worth checking before reading a total, because it mixes the two.

Two dates, deliberately kept apart

Every figure here is bucketed by the day the manager listened. The call keeps its own date and time, which you can see in the detail behind any number.

Things worth knowing

It only knows what happened after it was switched on. Nothing recorded who listened to a call before that, so reviews made earlier cannot appear here.
A call belongs to the advisor who made it, not to whoever owns the lead now — those are different people on most calls, and lead ownership keeps moving.
A call is reviewed once, by one person. Listening again — whether it is you or a colleague — changes nothing.
Two different measures, deliberately. Whether a call counts as reviewed is about how much of it you heard; Reviewed duration is about how long you spent. Replaying a passage adds to the second and not the first.

Attributes?

Metrics?

Break down by up to 2

Drag attributes here (rows)

Columns

Drag metrics here

Filters optional

Drag attributes here to limit values

New report

Add team member

Assign leads

Team members

Name	Email	Role	Team	Ext	Capacity	Target EGP/mo	Assign leads	Auto-assign	Pending Review	Auto-assign settings	Active

📊 Analytics

—

Revenue

Sales operations

Team performance

Programs booked

Pipeline funnel

Channels — leads & revenue by source

Agent engagement — conversations → leads by channel

How often a chat the agent handled turned into a lead. A low rate on a busy channel is where the agent needs to improve.

Settings

Distribution

How leads are spread across the advisor team.

Default capacity for a new advisor (max active leads)

Refresh the Leaderboard every (the live board on the sales-room screen auto-updates at this interval)

Count a call as reviewed once the manager has heard % of it, or at most minutes, whichever comes first

Counts each second of the recording once, so replaying the same passage does not clear the bar. Below it, nothing is recorded and the manager is told how much more is needed.

Programs

Your program catalog, and what the rest of the CRM reads off it.

1 · Catalog & prices

Import pulls the same catalog the AI agent quotes; edit any price the deal actually closed at. Closed-won leads are valued by matching their program to this list — until we can read the actual invoice amount from the CRM.

2 · Matching leads to a program Last scan: never

Every lead's free-text interest is matched to a program from the catalog above, including by a program's former name — that's what the Distribution Center's Program filter offers. Anything that matches nothing, or matches two programs at once, is filed as “Other” rather than guessed. Re-scan after the catalog changes: new programs make previously “Other” leads matchable.

Re-scan automatically every

A scan only writes where the mapping actually changed, so leaving this on costs almost nothing. It also keeps newly created leads mapped after a restart.

Import leads

Upload a CSV to bulk-add leads. Flexible columns: Name · Phone/Mobile · Email · Program/Interest · Status · Source. Deduped by phone; rows without a phone or email are skipped.

Facebook comments → leads

Scan Facebook page comments (back to 1 Jan 2026) for phone numbers that aren't leads yet, then import the ones you want — one click each. Each scan remembers what it read, so later scans only check what's new. Needs the page token's comment-read permission; until then this returns nothing.

Chats → missed leads

Scan the AI agent's chats for customers who left a phone number that never became a lead or a ticket, then import the ones you want — one click each. A customer who is already a lead under another number is shown as covered, never imported twice.

🏆 Sales Leaderboard

—