I Looked for a Support Email at 25 AI Companies. Five Have One.

TL;DR: Five of 25. On 2026-08-15 I read the public help-centre, contact and support pages of 25 AI vendors a solo operator depends on, and counted what a prospective buyer can see before paying. Five publish a support email address you could write to today: Cursor, Lovable, n8n, Clay and ElevenLabs. Twenty route you to a form or a chat widget instead, eleven name an AI assistant as the front line, seven state in writing that human support depends on your plan tier, twelve present a community forum or Discord as a channel, and exactly one publishes a first-response time in hours. This measures the pre-purchase surface only. A paying customer may see an in-app channel this audit cannot reach.

A solo operator has no CSM, no vendor manager and no procurement leverage. When something breaks at 11pm, the escalation path is whatever the vendor put on a public page. That is a question people ask constantly and nobody has counted, so I counted it. The scope matters and I am fixing it deliberately at the buyer's view: what you can verify before you hand over a card, which is the only moment you still have a choice.

Who publishes an email a stranger can write to?

Five of 25, and I mean a real address in the page markup, not a contact form that emails on your behalf.

Vendor	Address	Where
Cursor	hi@cursor.com	docs.cursor.com get-help
Lovable	support@lovable.dev	lovable.dev/support
n8n	help@n8n.io	community.n8n.io
Clay	support@clay.com	clay.com/contact
ElevenLabs	team@elevenlabs.io	elevenlabs.io/contact

Two more vendors publish an email, but not one for support. Runway's help centre carries press@runwayml.com and partnerships@runwayml.com and no customer address. Synthesia's contact page carries sales@synthesia.io. Both companies decided an inbox was worth publishing, then chose which inbound to accept.

What is behind the other twenty doors?

A form, a widget, or a bot. OpenAI's own article "How can I contact support?" resolves to a single instruction: "You can contact OpenAI Support by opening the chat bubble icon displayed at the bottom-right." There is no address, no queue, no alternative route on the page.

Eleven of the 25 name an AI assistant, agent or bot on the support surface itself: Anthropic, GitHub, Notion, Google Gemini, Make, n8n, Apollo, Clay, ElevenLabs, HeyGen and Synthesia. Anthropic's "How to get support" is the most explicit document in the sample, and worth reading precisely because it is honest. Every tier gets the AI: "Chat with Fin, our AI support bot." What differs is who gets past it. Pro, Max, Team owners and Enterprise owners get human specialist support. Team and Enterprise members who are not owners get Fin only, with the note that "Human specialist support is not directly available." Free users get documentation, Fin, and human help for exactly one thing: account deletion where self-serve is unavailable.

Seven vendors publish that human or priority support depends on your plan: Anthropic, GitHub, Zapier, Vercel, Notion, n8n and Supabase. Zapier's pricing page is the bluntest, listing support for the Free plan as none at all, with email support beginning at Professional and live chat gated further to the 2,000-task tier and above. GitHub's support docs send free users to community discussions and reserve direct contact for paid plans, and its first line is now an AI: the docs describe "Copilot in GitHub Support" as the thing that answers before a ticket exists. Vercel lists "email support with optional priority support upgrades" as a Pro feature; the free Hobby plan's entry does not mention support at all.

Twelve of 25 present a community forum or Discord as a support channel: Anthropic, Google Gemini, Microsoft Copilot, GitHub, Notion, Vercel, Supabase, n8n, Descript, Midjourney, HeyGen and Synthesia. Supabase puts it first on the page: "Our Discord community can help with code-related issues. Many questions are answered in minutes." n8n is admirably direct about the split, describing the forum as "Free for every n8n user" and reserving "Priority support" for enterprise.

Does anyone tell you how long you will wait?

One vendor in 25. GitHub publishes real numbers, and only inside the GitHub Premium Support document: initial response of 30 minutes for Urgent, 4 hours for High, 24 hours for Normal on the higher tier and 48 hours otherwise. That is a paid add-on, not the page a prospective buyer lands on.

Everyone else declines. Supabase gets closest and still stops short: "Response time for support tickets will vary depending on plan type and severity of the issue," with no figure attached to either variable. n8n publishes "63% Common issues resolved in minutes," which is a resolution statistic about a forum, not a commitment about a ticket. Twenty-three vendors publish nothing at all. If you are deciding which vendor to put in the critical path of a one-person company, the wait time is the number you want most and the number almost nobody prints.

Is anyone actually blocking the audit?

This is where my own premise broke, so here is the correction. Zero of 25 blocked automated fetching outright. Eight returned 403 to the markdown-converting fetcher: OpenAI, Perplexity, ElevenLabs, Runway, Descript, Apollo, Midjourney and Synthesia. Every one of those eight then returned HTTP 200 to curl with a browser user-agent. The 403 is a tooling artifact, not a policy.

The real obstacle is duller and more effective. help.openai.com served me 43,301 bytes that reduced to 32 lines of readable text, all of them category names. Perplexity's help centre gave 109 lines, all category names. These are JavaScript shells: the support content exists, and it is invisible to anything that does not run a browser. Nobody is locking the door. The building simply has no visible entrance for a machine, which is a strange design choice for companies whose products are machines that read the web. On this site's robots.txt audit the same pattern showed up on the marketing pages. It runs all the way through to support.

What does this not prove?

It does not prove these companies abandon paying customers. Anthropic, Notion, Zapier and the rest all run in-app messengers that a logged-in account reaches and I cannot, and the support quality behind them is not something a page audit can see. "No published email" is a statement about the shop window, not the back office.

What it does establish is what you can verify with your own eyes before money changes hands, and that answer is thin. Five addresses. One response-time commitment, sold separately. Eleven bots standing where a queue used to be. For a company of one, that is the actual risk profile of the stack, and it is worth weighing next to which of these tools will even sell to a single person before you build a business on top of it. The one-person AI company is a real thing now. Its support plan is a chat bubble.