Talk to the people who build it
We are a small team and we answer our own support. Every message below reaches someone who works on the product.
Support and sales
Questions about how Operator works, help with a venture that is not behaving, plan changes, and anything before you buy.
hello@launchsurface.aiPrivacy and data requests
Access, correction, and deletion requests, questions about the Privacy Policy, and data-processing enquiries.
privacy@launchsurface.aiSecurity reports
Vulnerability reports and anything that looks like a security problem. Mark the subject line so it is routed straight through.
hello@launchsurface.aiBilling
Invoices, receipts, refunds, wallet top-ups, and subscription questions.
hello@launchsurface.aiWhat to include
If you are writing about something the Operator did or did not do, include the product URL or venture slug and roughly when it happened. That is enough for us to pull the trace for that cycle and see the same thing you saw. If you hit an API error, quote the correlation ID from the response body or the X-Correlation-ID header and we can find the exact request.
For billing questions, tell us the account email you subscribed with. For anything involving a message that was sent to one of your prospects, include the prospect domain rather than the individual address.
When we reply
We aim to answer support email within one business day. Deliverability incidents, anything where sending has stopped or a domain is at risk, jump the queue. Security reports are acknowledged as soon as we read them and we will tell you what we intend to do before we do it.
Customers with an active subscription can also open a ticket from inside the platform, which attaches the account and venture context automatically and is usually the fastest route.
Where we are
LaunchSurface is operated from the United States and serves customers worldwide. We work asynchronously and handle everything over email rather than scheduled calls, which keeps the response time short regardless of where you are.
Building against the API?
The developer documentation covers authentication, endpoints, errors, and rate limiting.