Route support, billing, sales, and policy work without ambiguity.
Use the channels below for product support, commercial onboarding, and legal documentation. For operational questions, include endpoint URL, event type, timestamp, and delivery status.
Routing matrix
Public beta contact paths by request type
support
Delivery troubleshooting and account help
billing
Invoices, taxes, payment issues
sales
Limits, procurement, rollout planning
privacy
Data access, deletion, policy questions
product
Support triage
Endpoint, event, timestamp, and status make delivery issues actionable.
sales
Commercial review
Use sales for higher beta limits, procurement, and production rollout planning.
legal
Policy separation
Privacy and security requests route to dedicated mailboxes outside general support.
ops
Public references
Docs, status, and reliability pages stay available before opening a ticket.
Product support
Technical questions, delivery troubleshooting, endpoint behavior, and general account help.
[email protected]Billing
Subscription, invoices, tax documents, payment issues, and plan changes.
[email protected]Privacy
Data access, deletion requests, privacy questions, and policy inquiries.
[email protected]Sales
Higher beta limits, procurement, custom SLA discussions, and commercial onboarding.
[email protected]Include this in support requests
- Organization or application name.
- Endpoint URL and event type involved.
- Approximate time of the failed or delayed delivery.
- Observed HTTP status, error text, or retry state.
- Sanitized payload sample if the issue depends on body shape.
Commercial onboarding
Teams evaluating Nestarc before public launch can use the sales channel for rollout planning, procurement coordination, and early limit review.
- Higher beta limits or launch-readiness review
- Procurement and security questionnaire requests
- Migration planning from an existing webhook flow
- Commercial onboarding for post-beta rollout
Security and legal
Security disclosures should be sent to the dedicated security mailbox. Privacy and policy questions should go to the privacy mailbox so they can be handled separately from general support.
For public bug reports or non-sensitive issues, GitHub issues remain available as an additional channel.
Open GitHub issues (opens in new tab)Operational references
If you are validating rollout risk before adoption, these public references are the fastest way to review current operating posture.