Feedback
Confirm FirstSend docs gaps, product questions, sensitive operational details, and navigation issues through the approved path so support can act without exposing private source links, customer data, or unapproved support promises.
Issue-first intake
Use your assigned support or feedback channel when a page is missing, unclear, stale, hard to find, or inconsistent with product behavior.
Share the public route, product, content type, observed problem, expected outcome, and impact.
Open support guidanceAssigned support channel
Use the support path from your private beta invitation for account-specific behavior, tenant context, pilot blockers, or product-support questions.
Start with the docs route and sanitized details, then keep product or account specifics in the assigned support channel.
Open support guidanceRedaction required
Use the support bundle privacy guidance before sharing logs, traces, diagnostics, configuration, screenshots, or troubleshooting output.
Remove credentials, customer identifiers, raw payloads, proprietary logs, and private topology before handoff.
Open redaction guidanceReport the query
Report a search term, route, or navigation path that fails to reach the product documentation you expected.
Include the search query, current route, expected destination, product, and whether a status, limits, compatibility, or reference page would help.
Open searchUse the canonical docs URL or route path where the gap appears. Do not include repository paths, branch names, or local development paths.
Name ObjectDB, Message Broker, LogDB, or cross-product, plus whether the page is a quickstart, guide, reference, limit, operation, concept, or status page.
Describe what the reader needed to do or understand, and whether the gap affects a claim, example, limit, support flow, or release note.
Prefer status codes, route names, counters, timestamps, and shape-only examples before logs, payloads, screenshots, or customer-specific values.
This route does not submit or store feedback by itself. It routes readers to approved support, redaction, and customer-safe diagnostic paths.
Retention, visibility, and acknowledgement follow the approved destination used for the report, such as the issue template process or assigned support channel.
The public docs site does not add third-party analytics tags, analytics cookies, or remote page-feedback telemetry for this intake.
Customer identifiers, credentials, secrets, raw payloads, proprietary logs, private topology, and support bundles stay out of public reports.
The destination where you submit the report provides the safe acknowledgement path. Include enough sanitized context for the receiving team to reproduce the docs gap, answer the product question, or confirm whether the current public docs already cover the boundary.
Inline page rating controls stay hidden until support, privacy, analytics, acknowledgement, retention, triage ownership, and browser automation coverage are approved for that separate control surface.