Contact SayHex

Talk to SayHex before you share details

Use the public contact form for website questions, planning requests, and approved access inquiries. Share enough context for safe routing, but do not include passwords, secrets, private records, or raw logs.

Public contact form

Send a clear, safe message

Tell SayHex who you are, how to reply, and what you want to discuss. Required fields are checked before submission, and the server verifies anti-abuse tokens before accepting the message.

Use an address where SayHex can send the confirmation and reply.

Add this only if a call would help the follow-up.

Helps SayHex understand the business context.

Use a short topic such as website question, demo planning, or access inquiry.

Describe the question or next step. Do not include passwords, secrets, private records, payment details, or raw logs.

The first-party challenge service will populate this field before production submissions are accepted.

Messages are accepted only after CSRF, signed nonce, first-party challenge, and idempotency checks are present.

Before protected access

Share context, not sensitive data

Contact messages are for public website and business questions. Account work, Customer Admin provisioning, license actions, and private support records remain behind approved protected processes.