Remote Support

Remote Support · Your IT partner since 2016

You call, an engineer answers. Not a ticket number.

Remote helpdesk and support for staff and systems, with a real person on the phone, an engineer on site when the problem needs hands, and no queue to argue with.

Engineering offices in Egypt, delivering on site across Egypt and Saudi Arabia, and supporting clients remotely across the Gulf, Africa, Europe and the United States.

Most people call. It is faster, and you speak to an engineer, not a form.

What a support review looks at

How long people wait nowNot the SLA in the contract, the actual time between raising a problem and getting help.

What keeps coming backThe same five issues every month, which are a fix waiting to happen rather than tickets.

Who people really callWhether staff use the process, or ring the one colleague who is good with computers.

What is documentedWhether support depends on one person’s memory of how your systems fit together.
2016
Operating since
50+
IT specialists
40+
Projects delivered
25+
Clients
5.0
Rated on Google
What we deploy and supportMicrosoftKasperskySophosDellHPEVeeam
What we see in the field

Why IT support frustrates people

Rarely because the engineers are bad. Usually because of how the service around them is arranged.

A queue instead of a person

A portal, an auto-reply and a reference number. Meanwhile somebody cannot work, and the clock the SLA measures is not the clock the business feels.

The same problem, every month

Tickets closed quickly and never analysed. The printer, the mailbox and the shared drive break on a schedule because nobody is paid to fix the cause.

A shadow IT person

One helpful colleague who fixes things unofficially. It works until they are on leave, and none of what they know is written down.

No documentation, so every call starts from zero

Each engineer rediscovers your environment. The same questions, the same delay, every time.

What we actually build

How our support actually works

Designed around the two things people care about: how fast somebody picks up, and whether the problem stops happening.

1

Getting help, the part that matters most

Phone first. Most issues are resolved in the call rather than scheduled for later.

  • A phone number answered by an engineer, not a switchboard
  • Secure remote session started in seconds once you agree
  • Email and ticket routes for anything not urgent
  • Priorities agreed with you, so ‘urgent’ means the same to both sides
  • Arabic and English support for your staff
  • On-site attendance when the problem needs hands

We would rather fix it while you are on the phone than log it and call back.

2

Day-to-day support scope

The routine work that consumes an internal team’s week.

  • Desktops, laptops, printers, mobiles and peripherals
  • Microsoft 365, mail, files and collaboration
  • Servers, shares, permissions and line-of-business applications
  • Network, Wi-Fi and connectivity faults
  • New starters and leavers, set up and closed down properly
  • Vendor liaison so you are not the one chasing a supplier

Wider infrastructure work sits in Managed IT.

3

Fixing causes, not just tickets

The measure of good support is that the volume of it goes down.

  • Recurring issues identified from the ticket history
  • Root cause addressed as a small project rather than re-fixed
  • Preventable failures pushed into monitoring and maintenance
  • Common requests turned into a documented self-serve step
  • Trends reported so you can see what is improving
  • Honest advice when the real fix is replacing something

See Monitoring & Auditing for early warning.

4

Security inside support

The helpdesk is a target. Attackers phone helpdesks and ask for password resets.

  • Caller verification before any credential or access change
  • Remote sessions require the user to approve, and are logged
  • Least-privilege admin accounts for our engineers
  • Phishing and suspicious-mail reports treated as incidents
  • Leaver access removed on the day, not the month
  • Actions auditable, so you can see what we did and when

Wider controls are in Cyber Security.

5

Knowing your environment

Support is only fast if the engineer already knows how your systems fit together.

  • Documented estate: systems, accounts, dependencies, contacts
  • Runbooks for the tasks that recur
  • A named engineer who knows you, with a briefed backup
  • Handover notes so cover is not a downgrade
  • Asset and licence records kept current
  • Regular review of what changed and what it means

Asset records tie into IT Asset Management.

Where we have done it

How we support clients

Real Stark work. Client identifiers are withheld under confidentiality. Sector and scope only.

Multi-site enterprise

One helpdesk across sites

Staff in several locations supported by one team with one documented estate, instead of each site solving the same problem separately.

Fintech · 24/7

Support against an agreed response commitment

Cover specified around what an hour of downtime actually costs, rather than a generic service level.

SMB and mid-market

Support without an internal IT department

Full helpdesk for businesses whose alternative was one overloaded person and a shortlist of phone numbers.

Alongside internal teams

Second line and overflow

Covering holidays, peaks and the specialisms a small internal team cannot reasonably hold.

References can be provided directly, on request, with the client’s agreement.

How we advise

Three things we will tell you not to do

Do not judge support by the SLA on paperA four-hour response target means little if the first response is an acknowledgement email. Ask how long until somebody is actually working on it, and ask the current clients.
Do not close tickets without asking why they keep openingFast closure with a high repeat rate is a service that looks efficient and costs you every month. The number worth watching is repeat issues, not tickets closed.
Do not rely on one person who knows everythingWhether that person is inside your company or inside ours, it is the same risk. Insist on documentation, and on a named backup who has actually read it.
Before you call

The questions we get asked most

Do we get a real person, or a ticket system?

A real person. Phone is the primary route and it is answered by an engineer. Most issues are resolved during that call. Tickets exist for tracking and for anything that is not urgent, not as a barrier between you and help.

Do you come on site, or is it only remote?

Both. Remote first because it is faster, on site when the problem needs hands: hardware, cabling, a machine that will not boot, or a new office. Our engineers work on site across Egypt and Saudi Arabia, and support clients remotely well beyond that.

Can you work alongside our internal IT person?

Yes, and it is a common arrangement. We take the volume and the specialisms, they keep the business knowledge and the relationships. We agree the split in writing so nothing falls between us.

What are your support hours?

Standard cover is Sunday to Thursday, 9am to 6pm, with extended and out-of-hours cover where a client needs it and it is specified in the agreement. We would rather agree honest hours than advertise 24/7 and disappoint you at midnight.

How do you charge. Per ticket or a fixed fee?

Normally a fixed monthly fee based on users and systems, because per-ticket pricing rewards the wrong behaviour: it pays us more when your IT works badly. A fixed fee means the incentive is to fix causes, which is the same thing you want.

Talk to an engineer · no obligation

Call and see who answers.

That is the most useful test of a support company, and it costs you nothing. Try the number below and judge for yourself.

02 3537 5791

Sunday to Thursday, 9am to 6pm · Egypt, and remote worldwide