Domain and DNS
MX, SPF, DKIM and DMARC records set at your registrar, with a check that every tool writing on your behalf, invoicing, newsletter, website form, is properly declared.
While the business has five people, the mailbox that came free with the domain name holds up fine. At fifteen the symptoms start showing. A salesperson answers from a personal address and the customer keeps that contact. The contact@ mailbox is read by one person, who goes on holiday. Quotes land in junk folders because the domain was never configured properly. And when somebody leaves, two years of correspondence walks out with them. Email run on your own domain, on a serious platform and with clean DNS, settles all four of those at once.
We usually build on Microsoft 365 or Google Workspace, after checking the data location options the chosen plan actually offers. The decision follows the software already in use at your end, not our preferences.
MX, SPF, DKIM and DMARC records set at your registrar, with a check that every tool writing on your behalf, invoicing, newsletter, website form, is properly declared.
contact@, accounts@ or support@ read by several people, with the history visible to all of them and a record of who answered what. Nobody waits for a colleague to come back from leave.
Team calendars, a look at who is free before offering a slot, and booking for meeting rooms, company vehicles and shared equipment.
Old messages are transferred with their folders, attachments and dates from the previous server, without interrupting delivery of new ones.
Retention rules applied to your policy, including when a user empties their deleted items. That is what saves a file in a commercial dispute or an inspection.
Mail and calendar on handsets managed through Intune, with screen lock and encryption enforced, and remote wiping of company data only if a phone goes missing.
Joiner and leaver accounts tied to Entra ID or the Google directory, two-factor authentication for everyone, and a periodic review of which access is still open.
How long it takes depends on the number of mailboxes and the volume to carry over. A short walkthrough is arranged for the team before the switch.
An inventory of existing mailboxes, domains and aliases, the licences required and the retention obligations specific to your line of work.
The Microsoft 365 or Google Workspace tenancy, domains, accounts, groups, retention rules, second factor and DNS records.
The history moves in the background while everyone carries on working. The MX change then happens in the evening, and nothing is lost in the transition.
We configure Outlook and phones remotely, then the team gets a session over video and a one-page sheet to keep at hand.
A fake invoice sent from your own domain is nothing like a theoretical risk. Without DMARC, anyone can write to your customers pretending to be your accounts department and give them fresh bank details. The customer pays, in perfectly good faith, and you spend the following quarter explaining. We roll DMARC out in stages: first in monitoring mode, to find everything that legitimately sends on your behalf, then quarantine, then reject. None of your own legitimate mail gets blocked along the way.
If your teams live in Word and Excel, use Teams and run Windows business software, Microsoft 365 more or less picks itself. Google Workspace suits organisations already settled in the browser, agencies, and teams that share everything online. Data location options vary by plan, so we check them before recommending either, and we administer both.
No, and it is the first thing we protect. The whole history is transferred, folders and attachments included, and the MX records only change once that transfer has finished. For a few days after the switch we keep collecting anything still arriving at the old server, until every correspondent has been redirected.
The account is disabled on the day of departure, which cuts off outside access immediately. The mailbox then becomes a shared one handed to the manager or the successor, with all of the history. Messages to the old address keep arriving, so no customer is left without a reply. The person concerned must be told this is happening; the GDPR requires it.
It is, provided the access is framed. With Intune we require a screen lock and encryption, we keep company data separate from the employee data, and we block copying into private apps. If the phone is lost, only the work container is wiped: the family photographs stay exactly where they are.
One licence per person who writes, yes. Service addresses such as contact@ or quotes@ consume none: those are shared mailboxes or aliases, and they are the first place to save money when a subscription invoice looks high. We also clear out accounts belonging to people who left long ago, which a surprising number of businesses go on paying for.
Tell us how many people need mailboxes and where your mail sits today. We propose a platform, a migration plan and the licence cost.
Message received
An answer follows inside one working day. Report an outage that is stopping people working and it moves ahead of everything else.
Nothing here under that name. Check the spelling, or simply choose the nearest large city instead. Since every engagement runs remotely, whichever you pick changes nothing about what we do for you.