Business Email for Security Companies: Tenders, Control Room
Business email for security companies: controlroom@, tenders@ and compliance@ as groups, client confidentiality, alarm alerts and licensing mail.
Part of the collection Business email, industry by industry
A security company sells trust, and its email is where clients, procurement officers and regulators first test it. Guarding and alarm firms win work through tenders that expect a company address, hold client information that criminals would pay for, and run a control room that has to answer at 3 am whoever is on shift. This guide sets out the addresses a guarding or alarm business needs, how to keep client details out of the wrong hands, and how to stop licensing and tender mail getting lost when staff change.
Quick answer
Put the company on its own domain and create controlroom@, tenders@, compliance@ and accounts@ as groups, so each address reaches everyone on that duty and survives staff turnover. Give a mailbox to each manager, supervisor and controller who writes to clients; most guards do not need one. Never send alarm codes, keyholder lists or site access details by email. Publish SPF, DKIM and DMARC so nobody can send as your domain. OquMail does this free for up to 15 mailboxes and 10 groups.
The addresses a security company needs
- controlroom@yourcompany.com: a group with the controllers and the duty manager. Clients send site changes, extra-guard requests and non-urgent reports here. Change the members when the rota changes, never a shared password.
- tenders@yourcompany.com: a group with the owner, the operations manager and whoever writes bids. Register procurement portal accounts with this address, so clarifications and addenda reach the bid team even if one person leaves mid-tender.
- compliance@yourcompany.com: a group for regulator correspondence, licence and registration renewals, insurance certificates and audits.
- accounts@yourcompany.com: invoices, statements and payment queries, with finance and the owner as members.
- careers@yourcompany.com: guarding recruits in volume, so keep applications out of managers' personal inboxes. A group with the HR or admin lead.
- sales@ or hello@: the public address for enquiries and quotes.
- name@yourcompany.com: a mailbox for each person who writes to clients or regulators.
Each group delivers a copy to every member's own mailbox, and members reply from their own address, so a client always knows which controller confirmed an instruction. Our guide to email groups for a team shows the steps.
Email is not the emergency channel
Make it clear to clients, in contracts and on the website, that alarms and incidents in progress go by phone or radio, not email. An email can sit unread for minutes even in a well-run control room. What controlroom@ is for is written instructions that need a record: a change of keyholders, a site closure over a holiday, extra patrols for an event, or a request for an incident report. Ask clients to put the site name in the subject so controllers can sort quickly, and reply to confirm every instruction, so there is a written trail if something goes wrong later.
Client confidentiality
A guarding or alarm company holds exactly what a burglar wants: when a building is empty, where the cameras point, who holds the keys and how to switch the alarm off. Treat email as something that could be read by the wrong person, and keep the most sensitive details out of it.
- Never email alarm codes, safe codes, gate codes or passwords. Give them by phone to a verified person, or in person.
- Send keyholder lists, site plans and guard rosters for sensitive sites as password-protected files, with the password sent another way, such as a phone call. Our guide to sending confidential email explains the options.
- Be wary of anyone asking for patrol times or staffing levels by email, even from an address that looks like a client's. Call the client contact on a number you already hold.
- Incident reports with CCTV stills or the names of people involved are personal data. Send them only to the named client contact, and keep them only as long as your contract and the law require.
Licensing and regulator correspondence
Private security is licensed in most countries, and a missed renewal can stop you trading. In the UK, the Security Industry Authority licenses individual officers and runs the Approved Contractor Scheme for companies. In South Africa, PSIRA registers both security businesses and officers. In Kenya, the Private Security Regulatory Authority licenses firms and guards. In the US, licensing is by state, such as California's Bureau of Security and Investigative Services. Each one sends reminders, renewal notices and audit requests to the address on file.
- Register compliance@ with the regulator, not the owner's personal email or the address of an administrator who might leave.
- Keep a list of licence numbers and expiry dates outside the mailbox, and check it every month.
- Store licence certificates, insurance and tax clearance in one place, so a tender submission does not depend on searching old emails.
Free business email on your own domain
OquMail gives you up to 15 mailboxes on your domain — free — with guided SPF/DKIM/DMARC, webmail, IMAP/SMTP for any mail app, and a send API. Setup is a few DNS records; changes usually take effect within minutes, occasionally up to 48 hours. Start at oqumail.com.
Tenders
Corporate and government security contracts are usually awarded by tender, and the email side is where small firms lose points. Procurement teams send clarifications and addenda by email, or through a portal that emails a notice, often with only a few days to respond before the closing date.
- Submit from tenders@ or a named manager's mailbox on your domain. A bid from a free webmail address looks like a one-person operation.
- Read every addendum. A changed site list or new guard hours can make your original price wrong.
- Ask clarifying questions in writing before the deadline the tender sets for questions, and keep the answers with the bid.
- Put the company registration number and your regulator registration number in the signature of everyone on the bid team.
Alarm panels and monitoring software
Many alarm panels, IP communicators and monitoring systems can send email for events such as low battery, failure to arm or a daily test. If you point them at an OquMail mailbox, use SMTP on mail.oqumail.com, port 587 with STARTTLS, and the mailbox's full address as the username. Older devices that only support port 25 or outdated SSL settings may not connect, so check the device manual first. Each mailbox can send 250 messages a day, which covers routine notifications for a small monitoring business. Give the system its own mailbox, such as alerts@, so a faulty panel that floods messages cannot bury a manager's inbox. Event emails are a convenience, not a substitute for your alarm receiving equipment.
Staff turnover
Guarding has high staff turnover, and email is where it shows. Supervisors and controllers come and go, and each one may hold client threads.
- Give mailboxes to roles that write to clients, not to every guard. The free plan's 15 mailboxes usually cover managers, supervisors, controllers and admin in a small firm.
- When someone leaves, reset their password the same day, remove them from every group, and keep their mailbox until their client threads are handled. Our guide to removing a departed employee's mailbox shows how to keep the mail.
- Never share one login between shifts. Groups let each controller have their own mailbox while the shared address keeps working.
- Cover phishing at induction. Attackers target the people who hold keyholder lists and site details.
Setting it up
- Use the company domain, registered in the company's name, at any registrar.
- Create a free OquMail workspace, add the domain and paste the five DNS records it shows: an ownership TXT, then MX, SPF, DKIM and DMARC. Click Verify; the check names anything missing. Start DMARC at p=none and tighten it later; our DMARC guide for beginners explains how.
- Create mailboxes for the owner, managers, supervisors and controllers. The owner's account always signs in with a second step.
- Create controlroom@, tenders@, compliance@, accounts@ and careers@ as groups and add the right members. A subcontracted response partner can join a group as an external member, up to 10 per group.
- Set a signature on each mailbox in webmail with the company name, registration and licence numbers, and the control room phone number.
- Add the mailboxes to Outlook or phone mail apps over IMAP, then update the address with clients, the regulator, the bank and procurement portals.
Common questions
What email addresses should a security company have?
controlroom@ for client instructions, tenders@ for bids, compliance@ for the regulator and licences, accounts@ for invoices, careers@ for recruitment, and a mailbox for each person who writes to clients. Make the shared addresses groups.
Does every security guard need a company email?
Usually not. Guards on site rarely email clients. Give mailboxes to supervisors, controllers and managers, and let guards reach the control room by phone or radio.
Is it safe to send alarm codes by email?
No. Codes, keyholder details and access information should go by phone to a verified person, or be handed over in person. An email can be misdirected, passed on, or read by someone who has stolen a password.
Can a small security company get business email for free?
Yes. OquMail is free for up to 15 mailboxes on up to 3 domains with 5 GB each, and includes up to 10 groups for addresses like controlroom@ and tenders@. You only pay for the domain.
Want to see how your own domain is set up? Use the free SPF checker and DMARC checker: they run in your browser and store nothing.