Owner Problems · Enquiries · Pre-admission operations
How to Manage Study Library Enquiries and Leads
Capture prospective-member context, assign the next action, follow up responsibly and hand off to admission without turning interest into an entitlement too early.
Quick answer
Manage an enquiry as a pre-admission record. Capture the channel and the prospect context, check for duplicates, record needs and preferences, assign an owner, qualify operational fit, set a controlled status, schedule a concrete next action, preserve communication history, close or defer with a reason, and convert through an explicit admission handoff. Keep source, status, ownership, follow-up and conversion evidence separate.
Enquiry ≠ admission · interest ≠ commitment · preferred seat ≠ allocated seat · follow-up due ≠ completed · no response ≠ not interested.
Enquiry, lead, prospect, applicant and member
An enquiry is an interaction or request for information. A lead or prospect is the person/context that may contain one or more enquiry episodes. An applicant has entered the formal admission process. A member is recognized by the operating system, while a membership is the time-bound or rule-bound access relationship.
| Record | Purpose | Boundary |
|---|---|---|
| Enquiry | Preserve an interaction and request. | Does not grant entitlement. |
| Lead / prospect | Group context and future possibility. | Does not equal a member. |
| Applicant | Formal admission review. | Requires revalidation. |
| Member | Recognized person relationship. | Not the same as one enquiry. |
| Membership | Access/commercial entitlement. | Not created by interest alone. |
Capture channels with minimum useful information
Walk-ins, phone calls, websites, messages, social channels, referrals and local activity can all create enquiries. Use a controlled source vocabulary and preserve the observed attribution rule. Source is not proof of causation, and a channel should not be treated as universally better without evidence.
Identity
Name or contact context sufficient for safe follow-up.
Need
Branch, timing, plan or seating preference where relevant.
Action
Owner, status, next action and due context.
Do not turn every enquiry into a full admission or identity-document collection. Gather more information when the formal workflow requires it and when the purpose is clear.
Check duplicates before creating another prospect
Search by permitted, normalized contact patterns and existing enquiry references. A possible match should create a review prompt, not an automatic merge. A family contact, shared number or spelling variation can produce a weak match. Preserve repeat interactions without fragmenting one person into unnecessary identities.
Record needs and preferences without promising capacity
Ask what the prospect is looking for: branch, expected start period, preferred shift, fixed or flexible seating, quiet zone or other offered service. These are preferences or requirements. They are not confirmed shifts, reservations or allocations. Availability should come from the canonical capacity workflow, not from an enquiry note copied forward indefinitely.
Preference
Morning shift
Availability
Currently shown
Confirmation
During admission
Allocation
After approved workflow
Assign responsibility and preserve handoffs
An owner answers who is responsible for the next action. Ownership can change when staff move, take leave or hand over a branch. Preserve prior ownership, new ownership, timing and reason where the operating policy requires it. Cross-branch visibility and reassignment must remain permission-aware.
Keep status different from next action
Status describes where the enquiry is. Next action describes what should happen next, who owns it and when it is due. Contacting a prospect may complete one task but should not silently erase the outcome or create a new status without an explicit rule.
New
Next action: Review and assign
Contacted
Next action: Record outcome and next step
Follow-up
Next action: Due action remains visible
Deferred
Next action: Respect the future context
Converted
Next action: Preserve handoff linkage
Closed
Next action: Keep reason and history
Interactive enquiry lab
Keep status, ownership and next action visible
A conceptual review aid for pre-admission operations. It demonstrates the distinctions the live Libix implementation must preserve; it is not a claim about current product screens or integrations.
Prospect context
ClearNo possible duplicate is flagged.
Ownership
ClearNext action is owned by Front desk.
Next action
ClearConfirm branch and shift
Status interpretation
ClearCurrent status: New.
Make follow-up a traceable activity
A follow-up task should identify its owner, purpose, due context and outcome. A due date passing makes an action overdue; it does not complete the action. Do not hard-code a universal response time, contact count or stale threshold. Use context and approved policy. Communication events and follow-up tasks are related but not automatically identical.
Handle no response, deferment and closure carefully
No response is not automatically not interested. A deferred prospect should preserve the requested future context and should not be reminded before that point without a justified action. Lost, not suitable, abandoned and cancelled can be distinct outcomes. Preserve history; closing is not deletion. Reopening should create a new active episode or explicit transition while retaining the old record.
Record the known outcome and preserve prior activity.
Record the known outcome and preserve prior activity.
Record the known outcome and preserve prior activity.
Record the known outcome and preserve prior activity.
Convert to admission safely
Conversion is an explicit, permission-aware handoff. Reuse or link prospect identity safely, recheck duplicates and required admission data, preserve source and enquiry history, record actor and timestamp, and make the operation idempotent so retries or double-clicks do not create duplicate admissions. Conversion does not automatically allocate a seat, create a payment obligation or activate membership unless the approved admission workflow explicitly does so.
Consent, privacy and lead scoring
Marketing consent and service communication preference are not casually interchangeable. Collect only what the pre-admission purpose needs, protect contact details and notes by role, retain audit evidence where required, and follow the applicable retention and deletion policy. Treat lead scoring as a configurable interpretation, not objective truth; do not fabricate scores, predictions or protected inferences.
Reports owners can trust
Define the date basis, branch basis, status basis and denominator before reporting. New enquiry count is not necessarily unique prospects. Source attribution is not causation, and staff should not be ranked solely on conversions without context. Useful views include active enquiries without a next action, overdue tasks, duplicate-review queue, branch handoffs, deferred prospects, known lost reasons and conversion linkage for the specialist analytics page.
Where Libix fits
Libix — Library OS, from CodePex Technologies Private Limited
Libix is positioned for connected study-library operations. The exact enquiry module, source taxonomy, assignments, reminders, communication linkage, duplicate handling, reporting and conversion capabilities must be verified against approved product documentation and the live implementation.
Enquiry-management checklist
Frequently asked questions
What is a study-library enquiry?
It is a recorded expression of interest or request for information before formal admission. It does not create membership, a seat reservation or a payment obligation by itself.
Is a lead the same as an admission?
No. A lead or prospect represents a possible future member; admission is a separate controlled workflow that rechecks identity, eligibility, plan, dates and other required information.
Does no response mean the prospect is not interested?
No. No response records an incomplete contact attempt. The next action, policy and context should determine whether the enquiry remains open, is deferred or is closed.
Should duplicate enquiries be merged automatically?
No. Duplicate detection should flag candidates for safe review. Weak matches can represent different people, and a repeat interaction may need to remain as a separate episode linked to the same prospect.
What should happen when an enquiry converts?
Use an explicit, permission-aware and idempotent handoff that preserves enquiry history, rechecks member identity and creates or links the formal admission without silently activating access.