Start Here: What Plenix Is and How It Fits Together
A plain-English tour of the whole platform β what each part does, how they connect, and where to begin on your first day.
Read this one first
Plenix is one system that runs your whole business, instead of five or six separate tools that do not talk to each other.
Most companies end up with a CRM for sales, a helpdesk for support, a spreadsheet for stock, an accounting package for invoices, and something else for HR. The work is the same work β but the information is scattered, so people re-type the same details over and over, and nobody can see the full picture.
In Plenix, those are all modules of one platform. A customer you add in one place is the same customer everywhere. Work done in one module flows into the next automatically.
You will not use all of it. Nobody does. Most people live in two or three modules and never open the rest. This page is here so you know what exists and can ignore the parts that are not yours.
The seven things Plenix does
| # | What you want to do | Where it happens |
|---|---|---|
| 1 | Find and win customers | CRM & Sales |
| 2 | Handle requests and problems | Service Desk |
| 3 | Send people out to site | Field Service |
| 4 | Deliver bigger pieces of work | Projects |
| 5 | Get paid | Billing & Accounting |
| 6 | Look after IT equipment | Monitoring & Remote Management |
| 7 | Look after your staff | HR & Payroll |
Everything else in Plenix supports one of those seven.
How the parts connect
This is the bit that makes Plenix different from a folder full of separate apps. The modules hand work to each other:
- A lead becomes a deal. When you win the deal, it can open a project and raise an invoice β see How a Lead Becomes Cash.
- An email from a customer becomes a ticket. Time logged against that ticket can end up on an invoice β see How a Request Becomes a Resolved, Billed Ticket.
- A computer that stops responding raises an alert, which raises a ticket, which sends an engineer β see How a Device Problem Becomes a Fix.
- A new hire becomes an employee record, which feeds payroll β see How a New Hire Becomes a Paid Employee.
- A purchase request becomes an order, then stock, then a supplier bill β see How Procure-to-Pay Works.
You do not have to set any of that up. It is how the platform already behaves.
Why you cannot see everything
If a module in this documentation does not appear in your Plenix menu, it is almost always one of two reasons:
- Your plan does not include it. Plans unlock different modules. See What Your Plan Includes.
- Your role does not allow it. Payroll and admin settings are usually limited to a few people.
Neither is a fault. Ask whoever administers your Plenix account if you think something is missing.
Your first day
- Log in and look at your dashboard. It is empty at first β that is normal.
- Find the one module your job lives in. If you answer customer emails, that is Service Desk. If you sell, that is CRM.
- Do one real piece of work in it. Raise one real ticket, or add one real customer. Reading about it teaches you less than five minutes of doing it.
- Make it yours. Pin the pages you use to the top of your menu β see Personalising Your Menu.
Come back to this page in a week. The map will make far more sense once you have used a corner of it.
Where to go next
- New to the whole platform β How a Lead Becomes Cash is the best single flow to read.
- Wondering what you are allowed to see β What Your Plan Includes
- Want the menu to suit you β Personalising Your Menu
Was this article helpful?