Author: admin

  • Five phishing red flags your team should know

    Five phishing red flags your team should know

    News & Insights

    Five phishing red flags your team should know

    Security 12 August 2026 4 min read
    Working at a laptop in the New Solutions office

    Overview

    Nearly every security incident our team is called into begins the same way: one person, in a hurry, opens an email that looks exactly like the ones they get every day. The technology behind these attacks has improved, and the spelling mistakes we used to rely on as a warning sign have largely disappeared.

    Good filtering stops most of it. What matters is what happens to the small number of messages that get through. Below are the five checks we teach client teams to make, in the order they are quickest to apply.

    1. The request creates urgency

    Payment must be made today. The account will be closed within the hour. The manager is in a meeting and cannot take a call. Urgency is the one feature almost every phishing email shares, because it discourages the pause in which someone would normally check. Treat a deadline in an email as a reason to slow down, not speed up.

    2. The reply address is not the display name

    A display name is free text and can say anything. Expand the sender field and read the full address, then read it again from the right: the domain at the end is the part that cannot be faked. Lookalike domains that swap a letter or add a hyphen are common, and they are much easier to spot when you know to check the last part first.

    3. The link text and the link destination disagree

    Hover over a link before clicking and compare what it says with where it goes. On a phone, press and hold to preview the address. Attachments deserve the same treatment: a document that asks you to click through to a second site to view it is worth a phone call.

    If an email asks you to change bank details, confirm it by phone on a number you already have. Not the number in the email.

    4. It asks for credentials or a code

    No supplier, bank or IT provider needs your password, and none of them will ask for the six-digit code from your authenticator app. If a login page appears after clicking an emailed link, close it and reach the service through a bookmark or by typing the address yourself.

    5. Something about it is slightly off

    A supplier who has never emailed an invoice suddenly does. A colleague writes in a tone they do not usually use. A thread appears to continue a conversation you do not remember having. Staff instincts are accurate more often than they are given credit for, and the cost of asking is a two-minute interruption.

    Make reporting easy

    The single most useful change most businesses can make is giving people one obvious place to send a suspicious email, and thanking them when they do. If reporting feels like admitting a mistake, people delete instead, and you lose the chance to check whether anyone else received the same message.

    If you would like us to review your email security settings or run a short awareness session with your team, get in touch and we will talk through the options.

    What our clients say

    “We have found them to be very flexible – they work nights and weekends to fix problems and install upgrades to minimise disruption. They are also proactive and offer solutions to simplify our IT, whilst being mindful of our budget.”

    Elaine Hogg, Reproflex3

    Looking for an IT partner that just gets it?

    No silly questions, just straight up answers.

  • Building a hardware replacement plan you can budget for

    Building a hardware replacement plan you can budget for

    News & Insights

    Building a hardware replacement plan you can budget for

    Hardware 28 July 2026 5 min read
    Planning for the long term

    Overview

    Hardware rarely fails at a convenient moment. The laptop that dies is almost always the one belonging to the person mid-way through a deadline, and the replacement then has to be bought at whatever price and specification is available that week.

    A replacement plan removes most of that cost and nearly all of the disruption. It does not need to be complicated. Three pieces of information are enough to build one.

    Start with an accurate list

    Before anything else, you need to know what you own, how old it is and who uses it. Most businesses are surprised by this list. Machines that were retired years ago are still on the network, and a handful of devices turn out to be well past the point where a warranty claim is possible.

    We maintain this list for clients as part of hardware management, but a spreadsheet updated twice a year is far better than nothing.

    Set a replacement age, not a replacement date

    Four years is a reasonable working life for a laptop in most offices, and five for a desktop. Rather than replacing everything at once, decide the age at which a device gets replaced and let the list tell you how many fall due each year. The spend levels out, and the annual number stops being a surprise.

    Emergency replacements cost more than planned ones, and the difference is rarely just the price of the device.

    Standardise where you can

    Two or three standard models covering most roles makes everything after purchase easier: spares are interchangeable, setup is repeatable, and support calls are faster because the environment is familiar. Specialist roles still get specialist machines, but they become the exception rather than the norm.

    Keep one spare on the shelf

    A single configured spare device turns a failure from a lost day into a twenty-minute swap. For most teams it is the cheapest resilience available, and it pays for itself the first time it is used.

    Plan disposal at the same time

    Retired equipment still holds business data. Decide up front how devices will be wiped and where they will go, whether that is trade-in, redeployment for lighter tasks or certified recycling. Handling it as part of the plan avoids a cupboard filling with machines nobody wants to make a decision about.

    If you would like help building a device list and a three-year replacement schedule for your business, we are happy to put one together with you.

    What our clients say

    “We have found them to be very flexible – they work nights and weekends to fix problems and install upgrades to minimise disruption. They are also proactive and offer solutions to simplify our IT, whilst being mindful of our budget.”

    Elaine Hogg, Reproflex3

    Looking for an IT partner that just gets it?

    No silly questions, just straight up answers.

  • Moving to a cloud phone system without disrupting the business

    Moving to a cloud phone system without disrupting the business

    News & Insights

    Moving to a cloud phone system without disrupting the business

    Phone Systems 9 July 2026 4 min read
    A meeting room at New Solutions

    Overview

    The phone system is usually the last thing a business wants to touch. It works, everyone knows how to use it, and the risk of a bad changeover is obvious: missed calls are lost customers. In practice a cloud migration is one of the more predictable projects we run, provided a few decisions are made before any hardware arrives.

    Decide what happens to your existing numbers

    Numbers can almost always be ported, but porting takes time and has to be scheduled with the current provider. This is the item that sets the project timeline, so it is worth confirming early. Where a number is tied to an old contract, we look at whether it is simpler to port later and forward calls in the meantime.

    Map how calls should actually flow

    Most systems have grown by accident: a menu option added for a campaign that ended, an extension still ringing at a desk nobody sits at. A migration is the natural point to write down how a call should be answered during business hours, after hours and when the person is already on a call. It usually takes an hour and improves the caller experience more than the technology itself does.

    The technical work is rarely the hard part. Agreeing how calls should be handled is.

    Choose handsets, headsets or both

    Cloud systems work from a desk phone, a computer or a mobile app, and different roles want different things. Reception generally still wants a physical handset. People who spend the day in meetings often prefer a headset and the app. Deciding this per role avoids buying hardware that sits in a drawer.

    Check the network first

    Call quality depends on the connection and on how the network prioritises voice traffic. We test this before the changeover rather than after, because the fix is usually straightforward when it is found in advance and much more disruptive when it is discovered by a customer.

    Run both systems for a short period

    Where the connection allows, we keep the old system live while the new one is in use. Staff learn the new handsets with a safety net, and if anything is missing there is no rush to resolve it. Once a week has passed without issues, the old service is switched off.

    Add training on the day of the switch, keep a short written guide on hand for the first fortnight, and most teams stop thinking about the change within days. If you are weighing up a move, get in touch and we will talk through what it would involve for your setup.

    What our clients say

    “We have found them to be very flexible – they work nights and weekends to fix problems and install upgrades to minimise disruption. They are also proactive and offer solutions to simplify our IT, whilst being mindful of our budget.”

    Elaine Hogg, Reproflex3

    Looking for an IT partner that just gets it?

    No silly questions, just straight up answers.