Skip to content
ContractSpec
Start here

reference

SupportOS website inquiries

Idempotent public website inquiry intake that opens a SupportOS case.

field.key.label
docs.customer-support.website-inquiry
field.version.label
field.type.label
field.title.label
SupportOS website inquiries
field.tags.label
supportos,website,inquiry,intake,idempotency
field.owners.label
field.stability.label
public

A website inquiry is untrusted public input, never an execution instruction. The host binds a server-owned site identity (site, tenant, workspace, privacy notice version, retention, locales and kinds); clients never choose them.

  • The body is a closed object: idempotencyKey (UUID), kind, locale, email, name, organization, message and an empty honeypot field. Unknown fields, a client-selected notice version, or a filled honeypot are refused.
  • The idempotency key identifies one normalized intent per site and kind. The same intent replays the original reference; the same key with changed content is an idempotency conflict and is never echoed.
  • Durable custody (protected payload, case, pending notice intent) commits in one transaction before received. A storage failure stores nothing.
  • Each accepted inquiry opens exactly one SupportOS case. Operators read the inquiry by reference behind existing SupportOS authority with support.case.read in the bound tenant and workspace.
  • Acceptance never sends mail or calls a provider. A pending notice intent is drained only by an explicitly supplied, approved notifier.
  • Source quotas (5 per minute, 20 per day per opaque source signal) apply only to new intents; accepted replays bypass them. Retention removes payload, idempotency and pending notice custody; the case follows SupportOS data lifecycle.