Talk to us.

Three ways to reach the team. Pick the channel that fits — we answer all of them, but some are faster for some kinds of question.

No ticket queues, no AI triage, no "we'll route you to the right team". Both engineers read every email.

# response_times

discord● typically within 20 minutes (GMT hours)email● 24–48h business daysbooking● same-day confirmationincident● critical incidents prioritised

# channels

Pick the right channel.

We don't mind which one — but matching the channel to the question gets you a useful answer faster.

$ mail/

Email us

support@hsve.cc

The support email address. The main source of support, from the HSVE Helpdesk.

Best for

▸Order Help
▸Quotes & invoices
▸Proxmox Support Tickets

mailto:support@hsve.cc

FASTEST

$ discord/

Join the Discord

discord.gg/hsve

6200+ members including most of our past clients. Quickest place to get an answer to a Proxmox question, see how we work, or read the threads from people who hit your bug last month.

Best for

▸Technical questions
▸Template requests
▸Nerds lurking

discord.gg/hsve →

$ book/

Book a call

hsve.cc/contact

When email tag isn't cutting it. A 30-minute intake call is free and unobligated. After that, calls are billed as part of an Hourly or Standard engagement.

Best for

▸Intake calls (free)
▸Hourly consult slots
▸Live troubleshooting

./book_consultation.sh

# good_first_email

What makes a good first email.

We answer faster when these are in the first message. Skip whatever doesn't apply.

# checklist

✓
What you have today
Cluster size, Proxmox version, current hypervisor if migrating, rough VM count.
✓
What you want
Outcome in one sentence. "Migrate off ESXi by Q3" beats "we need help with virtualisation".
✓
Constraints
Budget range, deadline, downtime windows you can or can't use.
✓
Decision shape
Who signs off. Whether this is exploratory or you're ready to engage.
✓
Best contact mode
Email vs. Discord vs. call. We default to email replies unless you say otherwise.

To:      support@hsve.cc
Subject: Migration off ESXi — 14 VMs, ~Q3 cutover

Hi HSVE,

We're a 22-person manufacturing firm in Sheffield running 14
production VMs on a 3-host vSphere 7 cluster. Renewal is up in
August and the new licence quote roughly tripled.

What we want:
  - Move all 14 VMs to Proxmox on existing hardware
  - Keep ZFS-backed snapshots + offsite PBS
  - One day of training for our 2-person ops team

Constraints:
  - Cutover must happen across two weekends in July
  - Budget cap around £4–6k for the engagement
  - I'm the sign-off; my CTO sees the invoice

We've read your /consult page. The Standard package looks close
but I'm not sure if 14 VMs fits the 20–40h scope. Could you
quote, or suggest a different shape?

Best,
Mark T. — Head of IT
● expected reply: 24–48h

# office

Where we are.

Remote-first, UK-based. On-site work is available across the UK and Ireland, billed at the same hourly rate plus travel at cost.

location

Manchester UK

hours

Mon–Fri · 09:00–17:00 GMT

on-site

North West UK

incidents

Critical Incidents Only