A system for several teams sharing one case
In an organization the problem is usually not a lack of software. Reception, handling, and finance each keep a different version of the same person, request, or vendor.
Who it is for
For an organization or institution with more than one department on the same process. A poor fit for a single team that keeps the whole case from open to close.
Problems this page addresses
The case moves by email
No screen says who owns it now. The question comes back at every handoff between departments.
Permissions are all or nothing
Either everyone sees everything, or work stops because only the system admin can open the next step.
The old system cannot be switched off
Nobody wrote down what happens to the working week if it is turned off, so it stays beside every replacement attempt.
What you get
An owner for each step
Who opens, who approves, and who closes is written on the path, not in the email thread.
Permission by department and role
Finance sees a charge without editing the case notes. Handling sees the charge status without changing it.
A move that does not stop the week
A list of what goes live first, what stays on the old system on purpose, and who checks the first week.
Common questions
We already have an enterprise CRM. Why another page?
If every department works in it and there is no parallel copy in email, there is nothing to build. This page matters when the CRM covers one department and the others still pass cases by hand.
Who needs to be on the first call?
Someone from each department that touches the case, not only IT. Without the person who actually closes the step, you cannot see where the case gets stuck.
Do all departments go live together?
No. We go live on one handoff between two departments, for example reception to handling. A third department joins after ownership of that handoff is clear.
Related pages
A CRM shaped around how you already work
An off-the-shelf CRM asks the team to adopt someone else’s stages and fields. We build the record around the approvals, statuses, and fields that already decide who the customer is and what happens next.
Rollout and training the team actually uses
A system without practice slides back to WhatsApp in the second week. We hand it over with drills on real routines, a short page per role, and a clear order for permissions and backup so work continues if the person who knew the system leaves.
A core system instead of a pile of tools
When the central process - enrollment, handling, scheduling, follow-up - fits no product without bending it, the team becomes the glue. We build the core of that process and leave outside the tools that already do one narrow job well.