Plessisville
IT services in Plessisville: seeing what gets done on your IT
Many small businesses know nothing about their IT beyond the amount on the invoice. What was fixed, what is coming, where the passwords are kept: all of that sits with the provider. We work the other way round. Our office is in Trois-Rivières, about 90 km from Plessisville, with no address on site, and every request leaves a written record you can read.
A Plessisville SMB that hands its IT to OKTO Solutions follows it through four written records: a numbered ticket for every request, a client portal showing open files, a monthly report on the state of the fleet, and the documentation of its environment, which is handed over to it. OKTO’s office is in Trois-Rivières, about 90 km away.
What does a Plessisville SMB see of the work done on its IT?
A Plessisville business that pays a provider wants to know what was done, not just receive an invoice. OKTO Solutions offers its services to SMBs in Plessisville from its office in Trois-Rivières, about 90 km away, with no premises in the city, and leaves a written record of the work done. Each request gets a ticket number and a ranking by impact. When it closes, a note explains the cause and the fix. The client portal shows the person who coordinates IT the open requests, the history of past work and the documents handed over. A monthly report takes stock of the fleet: patches, incidents, verified backups, devices due for replacement. Automated on the Base plan, it is detailed from Standard up, which adds employee support and a quarterly review. The documentation of the environment is handed over to the business. Its administrator accounts, its domain name and its licences stay in its name. If it ever changes providers, it leaves with everything.
Day to day
What does the client portal show, and to whom?
It is aimed first at the person who coordinates IT at your end, often the same person who looks after administration. There they find the open tickets for the whole business, without chasing anyone to learn where a request stands.
They can open a request on behalf of a co-worker, add a screenshot to a ticket already sent and reread what was done on a closed file. That helps the day the same printer drops off for the third time: the history is there, dated, and the conversation starts from facts instead of memories.
The documents and reports our team hands over are filed in the same place. Nobody digs through a mailbox to find last spring’s report.
Employees do not need the portal. On every managed workstation, the OKTO button shows the state of their device: disk space, backup, protection. Request tracking and workstation status live in OKTO PSA and OKTO RMM, two tools our own team develops.
Client portalSample screen, with a fictional company, name and dates: an agreement, what it includes, then a monthly report landing among the documents. The wording shown is for illustration, not a commitment.
On paper
Which documents do you receive, and how often?
Four written records, each at its own time. Together they say what was done, what is holding and what is coming.
| What you receive | What it says | When |
|---|---|---|
| The closing note | The cause of the problem and the fix applied | When each ticket closes |
| The monthly report | Patches applied, incidents handled, backups verified, equipment to replace | Once a month: automated on the Base plan, detailed on Standard and Complet |
| The quarterly review | The quarter’s operations and the priorities for the next one | Every quarter, from the Standard plan up |
| The environment documentation | Network diagram, fleet inventory, list of licences, procedures | Written during onboarding, then handed over |
Employee tickets and their closing note assume user support, which is included from the Standard plan up. The Base plan monitors and protects the fleet without answering employees. An insurer or a customer asking for proof? Reports, logging and policies are available on request. The vCIO module is a paid add-on to a plan, from ten workstations or servers up. Its recommendations are documented at all three levels.
The test
Which questions tell you where you stand?
They apply to any provider, us included. How long the answer takes says as much as the answer.
- Can you send me our network diagram? If it is “in someone’s head”, it does not exist.
- Who holds our administrator accounts? They should be in your name, and one break-glass account should stay in your hands alone.
- In whose name is our domain registered? Yours, never the provider’s. It is the mistake that costs the most to undo afterwards.
- When was the last test restore? A green light does not answer the question. A date does.
- In which country are our data and our backups? You should be able to name it without looking it up.
- Why did the invoice move this month? Whoever cannot break down their invoice can rarely break down your fleet.
Sample screen, with a fictional company, durations and ratings: a restore test sheet, then the documentation ticked off line by line.
Ownership
Who owns the documentation of your environment?
You do. Network diagram, inventory, licences, procedures: those documents describe your business, not ours. They are written during onboarding, then handed over to you.
The same rule applies to whatever gives control. Your subscriptions, your domain name, your administrator accounts and your data stay in your name. On our side, access is named and traceable: it is known who did what, instead of a shared password nobody can attribute.
Why press the point? Because an SMB that does not own its documentation stays with its provider by default, not by choice. We would rather be kept for the work done. The day you leave, you leave with everything.
Backups follow the same logic of proof. Starting with the Standard plan, a restore is attempted two times a year, and the month’s report says which backups were verified. That report is the place to look, not a verbal assurance.
The ground
Plessisville, about 90 km from our office
Plessisville is the seat of the L’Érable regional county municipality, in Centre-du-Québec. Route 116 links it to Princeville and Victoriaville.
We have neither premises nor a stationed technician in Plessisville, and trips start from Trois-Rivières. Centre-du-Québec is among the regions our team travels to regularly. Conditions are agreed in the contract, and no on-site arrival time is published. The great majority of requests are settled remotely in any case.
That is exactly why the written record matters. When the technician is not in the next room, what you see of the work comes through the ticket, the portal and the report. What each service level includes is detailed in our plans, and the other towns covered are listed among the service areas. To tell us what you receive in writing today, use the contact page.
Questions and answers
Your questions about following your IT in Plessisville
Do you have an office in Plessisville?
Who on our side can follow open requests?
Do we get a report even in months when nothing broke?
What happens to our documentation if we change providers?
How do we know our backups really work?
Who answers outside office hours?
Want a clear view of your IT in Plessisville?
Tell us who looks after your fleet and what you receive in writing. We tell you what you should be able to read, and what to ask for first.
Reviewed by Antonio Pazzi, president of OKTO Solutions · updated