IBM Silver Business Partner
UCANLY for Business

Home/Products/Sales CRM

Ucanly Sales CRM

The admissions desk, without the spreadsheet.

The counsellor desk, the manager’s sheet and the follow-up, in one place. Leads arrive, get allocated to counsellors, get called, and turn into enrolments and payments — with the manager able to see all of it without asking anyone for an update.

A grid that behaves like a spreadsheet

Most admissions teams run on a shared sheet until it breaks. It breaks predictably: two people edit the same row, nobody knows who called whom, and the manager finds out a lead went cold a week after it did.

This keeps what people actually like about a spreadsheet — click a cell, type, move on — and adds the parts a spreadsheet cannot do. Every row has one owner. Every edit is kept with who made it and when. Select a range and bulk update it, then undo if that was wrong. Each user keeps their own column layout, so the manager’s view and the counsellor’s view do not have to be the same view.

Screenshot to addimages/products/sales-grid.pngDrop an .mp4 beside it later to make it a clip.

The grid, mid-edit. Column layout is per user.

Allocation, with a way back

Screenshot to addimages/products/sales-allocation.pngDrop an .mp4 beside it later to make it a clip.

New leads land here before anyone owns them.

  • An inbox for new leadsEverything unallocated sits in one place, so nothing arrives and quietly goes nowhere.
  • By hand or across the teamAssign individually, or auto-allocate a batch across the counsellors who are working. Both are undoable.
  • Segmenting, not stealingA lead can be given to a second counsellor as its own working copy without taking it from the first — for when a colleague speaks the language, or the parent calls back and someone else picks up.
  • Stale leads surfaceAnything untouched past a threshold you set comes back up, and escalation hands it to a manager rather than letting it rot in someone’s list.

A dial queue, in priority order

A counsellor opening a list of two hundred leads and deciding who to ring is a counsellor not ringing anybody.

Call mode hands them one lead at a time, ordered by how much attention it deserves rather than by row number. Log the outcome and the queue re-sorts. The statuses are the ones the work actually has — a switched-off phone is not the same as somebody who said no, and an engaged tone is a warmer signal than no answer, so they are filed separately and come back round differently.

Screenshot to addimages/products/sales-dial-queue.pngDrop an .mp4 beside it later to make it a clip.

One lead at a time, ordered by priority.

Enrolments, payments and what they add up to

Screenshot to addimages/products/sales-reports.pngDrop an .mp4 beside it later to make it a clip.

Revenue rolls up without a second spreadsheet.

  • Convert, and record the splitThe full programme price, what was collected up front, and when the balance is due. The balance is computed from those two rather than stored, so it cannot drift.
  • Payment reminders from a templateChase an outstanding balance without writing the same message for the fortieth time.
  • Reports a manager will openConversion and revenue by month, a team leaderboard, and a workload view you can reassign directly from.
  • Nobody maintains a second sheetThe revenue figure comes from the same rows the counsellors are working, which is the only way it stays true.

WhatsApp and email, from the record

A WhatsApp Cloud API inbox with the conversation attached to the lead it belongs to, plus templated email over Amazon SES. Broadcasts go to either channel. Meta’s webhook is verified by HMAC signature before a single field is read, and mail leaves under your own domain’s SPF and DKIM — which is what keeps it out of a student’s spam folder.

Screenshot to addimages/products/sales-whatsapp.pngDrop an .mp4 beside it later to make it a clip.

The conversation stays attached to the lead.

The parts you only notice when they are missing

  • Import you can reverse. Preview what will land, commit, or roll the whole batch back. Duplicates are found rather than silently created.
  • Three roles, enforced centrally. Counsellor, manager, superadmin — decided in one route table, not per screen.
  • A public intake form. Tokenised, for embedding on your own website so enquiries arrive directly.
  • One-click unsubscribe. RFC 8058, on every send, because Gmail and Yahoo have required it of bulk senders since 2024.
  • Audit, activity and email logs. Who changed what, when, and what went out.
  • Installs like an app. A progressive web app: add it to a phone home screen, and an offline page answers when the network does not.
  • Tasks and reminders. Per counsellor, with a live notification poll so the bell is current without a refresh.
  • Updates from the admin panel. Schema changes apply themselves when we ship a new version.

Who this is for

An institute outgrowing a sheet

Three or more counsellors working the same enquiry list, and a manager who currently finds out about problems by asking. This is the case it was built for.

A team that calls more than it emails

If most of your conversion happens on the phone, the dial queue and the call outcomes are the whole product. Mail is there, but it is not the centre.

Anyone who needs to show their working

If you have to evidence who contacted a student and when — for a partner, an auditor, or a parent — the audit log does that without anybody keeping notes for it.

Who it is not for. If you have one person handling enquiries, a spreadsheet is genuinely fine and we will tell you so. And if you need several brands in one place, each one needs its own deployment — there is no shared tenancy here, deliberately.

Questions people actually ask

Next step

Click through a working one.

The demo is loaded with invented leads, counsellors and enrolments. Ask and we will send you a login.