Sales + product support
Talk to the people
who run the API.
Weighing a plan, moving another email path, or stuck mid-integration? Send the context once. A NoticeAPI operator reads the note and takes it from there.
- A human reads every note
- Sales and support stay distinct
- Usually one business day
Start in the right place
One front door. Three clear paths.
Pick the route that matches the work. The form keeps sales and support separate; security reports have their own published review path.
Talk through plans, projected volume, multiple projects, or a migration from another email API.
Start a sales noteProduct supportUnblock the integrationShare the request, error, project context, or product behavior you need help understanding.
Start a support noteSecurityReview the security controlsRead the shipped controls first, then email support with SECURITY in the subject line if you need to report an issue.
Review securityAfter you press send
A short path to the right operator.
The contact flow uses NoticeAPI's own inbound and operator tooling, so the context stays attached from form to reply.
- 01POSTThe form validates the note
Required fields, request size, rate limits, bot checks, and the selected sales or support topic are checked first.
- 02ROUTEIt enters operator triage
The same inbound workflow used for the public mailboxes routes the message into the operator queue and sends an alert.
- 03REPLYA person answers your email
The reply goes to the work email on the form, usually within one business day.
Send the context
Tell us what you're working on.
A useful note includes what you are sending, the rough volume or request that is blocked, and the outcome you need.
Prefer the self-serve path?
Start with the shortest useful answer.
Use the quickstart for the first send or compare the published limits before you open a sales conversation.