From Enterprise Inquiry to a White-Label VPN

The white-label page is for operators who already know they want a brand on our network. Enterprise leftovers often need a conversation: bulk seats, a private split, a dedicated exit, a DPA. Those are contact jobs. If you already know you want a consumer-style brand with your logo, you can still write that in the message. Do not skip the nouns.

Enterprise VPN is the org-facing product story. This article is the inbound hygiene. Use both. Do not paste the homepage into the message box and call it a brief.

Do not write that Klox is SOC 2 certified in your internal deck because it would help the cell turn green. We will not invent it here. If your buyer requires a named audit, put the requirement in the message so we can say yes, no, or 'here is what we can actually produce.' A fake logo in a slide is a future incident.

Invoices, seats, device lists, tickets — that pile is not the same as packet destinations. Say which pile you care about. 'No logs' without a noun is how white-label brands copy the wrong policy. The White-Label VPN and Privacy Policy Template Mistakes piece is the document. The inquiry just has to admit the piles exist.

If your company already uses a specific HRIS, IdP, or ticketing tool you want the VPN admin to talk to, name it. If you need LDAP/AD, say so. If you do not know, say you do not know. Inventing a connector in the first email wastes a week.

Say which platforms you actually need. A hospital that only needs Windows is a different build than a hotel that wants a QR to iOS. 'All platforms' is a sentence from someone who has not paid for screenshot production.

Some enterprises never want a public listing. MDM, internal testing, TestFlight, managed Play. Write the distribution path. If you wanted a public brand, say public. Mixing those in one sentence is how we quote the wrong thing.

Employees will email the address on the receipt and in the app. If that address is yours, you own the clock. If you want us on the clock for network incidents only, write the split. Silence becomes 'they never answered' in a QBR.

P1 that means 'CEO cannot join Zoom from a hotel' is different from P1 that means 'node in one city is sad.' Define two examples in the message. I would rather argue about examples than about a percentage I will not invent.

Shared is how consumer economics work. Dedicated is how allowlists work. If you need both, say both. If you need neither and you just heard the phrase on a competitor webinar, omit it.

Credits, exclusions, notice windows. If your legal team has a template, attach the shape in the message: 'we need credits after X hours, exclude customer LAN and captive portals.' I will not mint a 99.something number so your RFP cell fills. Packet networks have weather. RFC 8446 is about TLS on control planes, not cafe Wi-Fi.

'Hi we want to white label your VPN like Nord' with no company, no seat count, no stores. Competitor names are fine as context. They are not a brief. Rel nofollow exists on this page for a reason: we are not pretending we are them.

If you have an RFP PDF, say so and ask where to send it. Do not dump 40 pages into the message field. Do put the five nouns above even if the PDF exists, because nobody reads the PDF first.

The form asks for mobile. Use a number a human answers. A sales-dev number that goes to a bot trains us to email only, and then you complain nothing moved.

If you need one before a call, say so in the message. Do not send a 30-page NDA that treats a tunnel like source code to a weapons program unless you mean it. We can still talk at a high level without your customer list.

If you need a trial on two laptops, write the success test: connect, stay up on the office Wi-Fi, pass an allowlist, survive a hotel portal. 'Feels fast' is not a test. WireGuard is usually the weekday protocol. OpenVPN is still the hotel protocol. Say if you already know you need both, because the consumer apps ship both and a brand that drops OpenVPN will hear about it from travelers.

Store review, processor KYC, legal. If your board wants it 'this quarter' and Apple enrollment is not started, the board is not in the packet yet. Write the real longest queue.

If the humans are your staff, you have employment and device-management questions. If the humans are your customers, you have a product and a review page. Write which. Hotels and ISPs are the second kind. Internal IT is the first. Mixing them is how the privacy page lies.

Central invoice, payroll deduction, guest upsell, MSP pass-through. Money path changes tax, refunds, and who screams. One sentence.

If you have a 200-row spreadsheet, say so and ask where to send it. Do not paste row 1 through 200 into the contact message. Do still paste the five nouns. Questionnaires that ask for city counts will get 'confirm on a call,' not a made-up integer. Questionnaires that demand a certification we will not invent will get a straight no or a pointer to what exists. That is faster than a green cell you cannot defend in diligence.

You can name Nord or anyone else as the thing your buyer compared. Put rel-honest context in your own notes. In the message, tell us what you actually need that a consumer brand did not give you: your icon, your DPA, your allowlist, your hours. Bake-offs that are only price will bounce you to consumer pricing. That is not an insult. That is classification.

Legal name. Motion. Controller guess. Store status. Hours. Dedicated IP yes/no and why. Seat order of magnitude. Longest queue. If those are in the message, a commercial conversation is possible. If they are not, we are still in therapy. I would rather delay a quote than send a number that assumes a 24/7 NOC you do not have.

If five employees just need a tunnel this week, give them download on a consumer plan and stop pretending it is a rollout. You can still send the enterprise packet for the real brand. Mixing a five-device household SKU with an MSA is how finance and IT stop speaking.

Write three checks: connect on office Wi-Fi, connect on a phone on LTE, survive one captive portal or say you will not support portals. If dedicated IP is in scope, hit the allowlist. If those pass, you have a product conversation. If they fail, you have an ops conversation. Do not skip to logo colors.

No developer accounts. No one to own the inbox. No need for your name on the icon. That is consumer or reseller. Say it. The contact form can still be 'we picked wrong, send us to the right page.' That is a successful inquiry.

Who refunds. Who is on the card descriptor. Whether the app is public. Whether OpenVPN must stay in the client because you have travelers. Whether WireGuard-only is a hill you want to die on. Those answers change the quote. They also change whether a seven-day consumer money-back window is even in the conversation. Enterprise MSAs are not that window. Do not paste our consumer refund sentence into your SOW unless we agreed.

Send the packet. Book the call. Let legal read in parallel. Waiting for a perfect DPA before you admit you have no Apple account is how a quarter disappears. Stores and hours are ops. Controller language is legal. You need both tracks. One person who can say 'we do not have that yet' is more useful than a redline on a clause for a product you cannot publish.

Say so. 'They installed a five-device consumer VPN and now they want our logo.' That is a common path. The consumer product is from $2.83 a month with WireGuard, OpenVPN, OpenConnect, and Shadowsocks. The white-label path is a different invoice and a different inbox. Classification in the first message saves you from quoting the wrong one.