One list, not an inbox
Inquiries sit in a table you can sort, filter by stage and extend with your own columns. Above it a strip of numbers the database recalculates after every save.
All modules
People and contact
CRM
A receptionist fields dozens of inquiries a week: a company asking about a course for its staff, a parent asking about tutoring. CRM is the one list where each has a stage, a value and an owner.
In funnel 12
Pipeline 38 400 zł
Win rate 34%
LeadOwnerValueStage
Nord Logistics kurs dla działu M. Wróbel9 600 zł Offer
Dorota Malec korepetycje B1 K. Rybak1 200 zł Contact
auto lead funnel · today
CRM
What this module does
5
starting stages, from new to lost
10 min
window in which a repeat adds no second row
12 mths
win-rate window: it measures today's school
500
leads on Pro, 1500 on the School plan
Stages and channels you set
A stage carries a name, a tone and a kind: open, won, lost. A channel carries a key that appends to the link, so you can see where an inquiry came from.
Inquiries from outside
A form on your own site posts an inquiry with an API key, and a school without a site gets our form at /f/ plus a QR code for a Google business listing.
Next step and history
Each row carries a next step with a date, and the marker's color says whether it has passed. Behind it a drawer with the timeline: system trail plus notes, calls, meetings, offers.
A win creates a student
A won inquiry creates a student or a company from one dialog, the same way their own screens do. A loss asks for a reason, and rows sharing a contact can be merged.
Who sees what
A module is a permission, and which records may be touched is settled on write, not in the menu.
| Role | Sees | Changes |
|---|---|---|
| Owner | The whole funnel, every lead's history, the API keys and the sign-up form. | Everything: stages, channels, reasons, merging, creating a student or company. |
| Methodologist | The same as the owner: the module comes by default, with no grant. | The same as the owner, including the catalogs saved as a whole set. |
| Teacher | Nothing by default. The funnel carries data on people who are nobody's students yet. | Once granted, runs enquiries like the front desk. Deleting stays with management. |
| Student | No access to this screen. It is a list they could be standing on. | Nothing. |
The details nobody asks about during a demo
The things that only surface in the third week of working with the module.
What this module does not do
- several forms at once - channels are told apart by “?skad=”, not by a second copy of the texts
- a route that would hand the lead list back out - a key only adds, nothing more
- a captcha - there is a bot trap, a call budget and a “Revoke” button instead
- a hand-made card order on the board - dragging changes the STAGE, not the place in a column
From the CHANNEL, which is a catalog entry with a key you append to the link: add “?skad=facebook” to the form address. A string that matches nothing stays a string and does NOT create a channel - nothing is created out of someone else's input. Next to it stands “Source”, a system fact: panel, API key or form, read only, because a row has to tell the truth about itself.
For ten minutes the same name and contact come back with the same identifier instead of creating a second row. The window counts archived leads too, because a receptionist who has already dismissed an inquiry should not get a copy a minute later. New text is not lost: a message that is not in the note yet is appended to it as a paragraph.
Moving it into a stage of the “won” kind asks what to do about it: create a student or a company, or put the lead into the archive. The record is created by the same route and under the same cap as from its own screen, in a half-and-half dialog - fields on the left, the rest of the lead to read on the right. The lead then GOES TO THE ARCHIVE rather than disappearing, so a win stands in two places.
The next step with its date sits on the row, and the colour of the pinned marker says whether the date has passed. Tiles count how many are overdue and how many are due today, and the Dashboard picks up the same items. No message or alert comes out of it, and that is a boundary rather than a gap: a reminder in an inbox belongs to Messages, not to an add-on here.
By two routes. With an API key from someone else's site or from their backend: a key with a list of origins works ONLY from a browser and only from those pages, a key without a list only from a backend. The second route is our own form at /f/ with a QR code, for a school that has nothing but a Google listing. Ten working keys per school, and one key posts 200 inquiries an hour.
By default they do not have the module and see not a single zloty of the funnel. Once granted, they run enquiries on equal terms with the front desk: create, edit and move them through stages, but not delete - that stays with management. And this is exactly the case grants were made for: two people in the same role, one doing sales, one not.
Five tiles (new this month against last month, in the funnel with their value, win rate, the average road from inquiry to win, no reply for seven days), the funnel by stage - clicking a bar filters the table - twelve weeks and the channels. The database counts it and recounts after every save, while the win rate and the road take a twelve-month window.
Only around the sign-up form, and only where the school turns it on: a copy of the submission goes to at most three addresses, and the person who filled the form can get a short confirmation with the school name in the subject. A lead added by hand or through an API key sends nothing at all. Talking to a client is not this module: correspondence belongs to Messages.
See Cerium from the inside.
14 days on your groups and instalments. No card, no strings.