Technical assistance
Help with the website, hosting questions we can act on, forms, and the tools Omnia Focus has delivered. You get a person who already understands the system instead of explaining it from zero.
IT & Customer Support
Systems need a person to call when something breaks, and customers need a clear reply when they write. Omnia Focus provides IT services and customer support for businesses that want that responsibility defined, not left as an informal favour. Coverage, hours, and the kinds of requests we take are agreed before the work starts.
Support is only reliable when both sides know what is included. A website error, a CRM question, a customer email, and a request for a new feature are different kinds of work. Omnia Focus sets the channels, the hours, and the boundary between a support task and a new project so requests do not disappear into a general inbox.
The service can cover technical assistance for the systems we built, helpdesk handling for your team, customer-facing replies, and routine maintenance. Some clients need all of that. Others need a single lane, such as keeping the website healthy or answering product questions by email.
We are based in Tunisia and work with companies that want a named way to ask for help. There is no universal package and no claim that every issue can be solved in a fixed number of minutes. Priority and response expectations are written into the agreement.
Choose the lanes that match the risk you want covered. We would rather define three clearly than imply that everything is included.
Help with the website, hosting questions we can act on, forms, and the tools Omnia Focus has delivered. You get a person who already understands the system instead of explaining it from zero.
A structured look at what failed, what changed, and what will restore the service. We record the cause when we can find it, so the same incident is easier to recognise next time.
A queue for internal requests: access, small fixes, how-to questions, and incidents. Each item has an owner and a status, which is more useful than a long chat thread.
Replies to your customers on the topics you define, in the tone you approve. We escalate anything commercial or sensitive back to your team rather than guessing.
Shared inboxes and contact forms that need a timely, consistent answer. Templates cover the common questions. Unusual cases are handed to a named person on your side.
Routine checks and updates for the website or system in scope: backups you can explain, certificate and form checks, and small corrections before they become an outage.
The point of an external support partner is coverage and a record, not a second company that invents its own process.
Coverage is written down. If you need extended hours, that is a scoped decision, not an assumption that someone is always awake.
Requests and resolutions are noted. When a similar issue returns, the history is there, and your team is not relying on memory.
Customer-facing support follows your guidance. We do not freelance policy on refunds, pricing, or complaints that belong to you.
A broken form is support. A new customer portal is a project. Naming that difference keeps the queue honest and the roadmap visible.
The shape of the retainer follows who is waiting on an answer: your staff, your customers, or both.
01
The site is live and the first real questions arrive: a form, a page, a small content change, or a hosting warning that should not wait for a new proposal.
02
Users need a place to ask why a record looks wrong or to request a field change that is still within the agreed system.
03
Customer email that deserves a consistent reply during the hours you publish, with a path to escalate what the support team should not decide.
04
Smaller companies that need checks and a named contact, without hiring staff for work that comes in bursts.
We agree the operating rules first. The queue works better when those rules are boring and clear.
01
Systems, channels, languages, and the request types we will accept. Anything outside that list is flagged as a separate piece of work.
02
You choose the coverage window and which incidents jump the queue, such as a site that is down versus a wording change.
03
Requests arrive by the path we agreed, with enough detail to act. A helpdesk or a shared mailbox is chosen for the volume you have, not for show.
04
On a rhythm we agree, we look at what came in, what was resolved, and what should become a project. The support service stays aligned with the work you actually send.
Support is easier when the same company knows the website or CRM already. Omnia Focus can take that continuity for systems we built, and we can also agree a narrower scope for a site or inbox that already exists. Either way, you get a written boundary and a record.
We do not describe support as unlimited, and we do not imply that every technical problem in a company is ours. The value is a professional response on the work we have accepted, with customer communication handled carefully when that lane is included.
If the same questions reveal that the customer records themselves are the problem, the next step may be custom CRM development rather than another month of workarounds.
Technical assistance, troubleshooting, a helpdesk for your team, customer email, and maintenance of the systems in scope. The exact list is agreed before the service starts.
Continuity is strongest there, but we can support an existing website or inbox when we have reviewed it and accepted the scope. We will say if a system is outside what we can responsibly take.
A single queue for requests, with a status and an owner. It replaces scattered messages so you can see what is open, what is waiting on you, and what was finished.
Yes, on topics and in a tone you approve. Pricing, complaints, and exceptions are escalated to your team. We do not invent policy during a reply.
Only if that window is part of the agreement. Many clients choose business hours. Extended coverage is a separate decision because it changes staffing, not a slogan.
Each accepted request is recorded with what was asked and what was done. That history helps the next incident and gives you something to review.
Yes, when the CRM is in scope. User questions, small configuration changes, and incident handling can sit in the support agreement. A new module is quoted as a project.
Through the channel we set with you, usually a helpdesk address or a shared form. A short description of what you expected and what happened is enough to begin.
Other ways Omnia Focus can support the same business.
Custom CRM systems that keep customers, tasks, and reporting in one place.
Learn MoreModern, fast, and scalable websites built around your business.
Learn MoreTechnical and on-page SEO that makes the website easier to find.
Learn MoreSearch campaigns aimed at qualified enquiries, with clear tracking.
Learn MoreTell us which systems and which customer messages you want covered. We will propose hours and a scope before calling it a support plan.