Skip to content
Algoryq Learn

Admissions & Growth

Every enquiry, on one board

Enquiries from your website, a phone call or a walk-in land on one admissions board with an owner, a timeline and a follow-up date.

crm · 32 API routes
A prospective student reading an enquiry notice board while a staff member works at the reception desk behind it.

What it does

A pipeline whose names are yours

Call the first column Enquiry or Qualified. Nothing in the code reads the label — open, won and lost are the facts every funnel counts, so your conversion rate survives your vocabulary.

Duplicates suggested, never swallowed

The same person really does enquire twice — a form on Monday, a call on Thursday. Matching is deliberately loose, and its only output is a suggestion to merge.

Assignment that cannot collide

Round-robin runs off a cursor incremented in the database, so two enquiries a second apart cannot land on the same counsellor. A rule naming someone who has left leaves the enquiry unassigned.

A timeline written by the system

Stage moves, assignments and calls are appended by the software. A history assembled from what somebody remembered is not a history.

Applications, and two honest outcomes

Already a member? Enrolled. Not yet? Invited, and the application says so until they accept. Press it twice and nothing doubles.

Web-to-lead, hardened

A public endpoint your own site posts to. It forces the source, has no field for stage or owner, returns a fixed acknowledgement, and answers identically for an unknown institute so it cannot enumerate them.

How it actually works

Why a lost enquiry needs a reason and a won one refuses to have one

“Why did we not get this?” is the most useful field in an admissions system, and a reason recorded against a win means nothing. The close date is stamped entering a closed stage and cleared on the way out — a reopened enquiry still reporting one lies to every cycle-time report. Conversion is won ÷ closed, never won ÷ everything, or it falls every time marketing does its job.

The permission keys it adds

A sample. Each is a real key in the catalogue, described for a school administrator rather than an engineer.

  • crm.lead.view
  • crm.lead.assign
  • crm.lead.merge
  • crm.application.decide
  • crm.pipeline.manage

All 272 keys, filterable

Who holds it

  • Admissions Counsellor
  • Institute Admin

The shipped role templates that hold it by default. Each is a copy you own and can edit — nothing in the code reads a role's name.

And what it does not

Naming these here is cheaper for both of us than discovering them in week six of a pilot.

What this does not do yet

Naming these is cheaper for both of us than discovering them in week six.

  • Campaign attribution
  • Email sequences
  • SMS and WhatsApp channels
  • Lead scoring

The whole list, with percentages

Start on the free tier. Bring your spreadsheet.

A hundred seats, twenty-five courses and no conversation. If you would rather see it driven by someone who knows it, that takes twenty minutes.

Or open the sandbox (opens in a new tab) and click around first. No form.