Eight routes, each with a clear purpose
Each route states what it is for and what it is not for. A route marked pending has no verified
destination yet, so it does not link anywhere.
Sales
Evaluating Zoiko iD for your
organization.Not for
Booking demos or quoting
prices here.Talk to Sales · pending
Help & Support
Existing customers with an
account or service issue.Not for
Security incidents or general
enquiries.Route pending
Developers
Integration questions and
documentation.Not for
Public ticketing, which is not
assumed to exist.Developer Overview · pending
Security
Security concerns and
account-security questions.Not for
Vulnerability reports, which go
to Responsible Disclosure.Security Contact · pending
Privacy
Questions about privacy
practices and data handling.Not for
Data-rights requests, which
need the approved process.Privacy Notice · pending
Press
Press enquiries, if a verified
route exists.Not for
Customer support or sales.
No mailbox published
Partnerships
Partnership enquiries, if a
verified route exists.Not for
Sales of the platform.
No mailbox published
General
Corporate questions that fit
none of the routes above.Not for
Sensitive data, secrets or
incidents.Form not yet approved
Security and privacy are handled
separately
Vulnerability reports and data-rights requests never travel through a general inbox or a general
form.
Report a suspected vulnerability Request
Use Responsible Disclosure. Do not send exploit material, passwords
or secret keys through this page.
Vulnerabilities: Responsible Disclosure.- Other security questions: Security Contact.
- Live service events: Availability / Status.
Route pending verificationPrivacy questions and rights requests
Sending a message here does not verify your identity or fulfil a rights
request.- Privacy practices: Privacy Notice.
- Data-rights requests: the approved rights process.
- Legal terms: the legal notice.
Route pending verification
Do not include secrets
Passwords, tokens, API keys, private keys, government identification numbers and confidential security configurations must never be included in a message. We will not ask for them.
Keep messages to the facts needed to route your request.- Attachments are not accepted by default.
The general form is
gated
The general enquiry form is not shown on this page. It can be
published only once every item below is verified.
Publication gate
- A verified recipient and owner for each category
- An approved route and privacy notice
- Security review of the processing
- Consent, retention and monitoring in place
- Accessibility testing and failure handling signed off
- Enquiry type
- Required. Error: Choose a
reason for contacting us. - Full name
- Required; 1–120 characters;
international characters allowed. - Reply email
- Required; checked on the
server; never echoed in
analytics. - Organization
- Optional; length-bound.
Individuals are not asked for
one. - Subject
- Required; 5–160 characters.
- Message
- Required; 20–4000 characters.
Warns against passwords and
tokens. - Consent
- Only if Legal requires it. Never a
default marketing opt-in. - Marketing opt-in
- Optional and unchecked.
Cannot block an enquiry.
No state claims success it has not
earned
A receipt is shown only after the server confirms durable acceptance. A timeout is never shown
as success.
Pristine
Empty fields and no errors shown.
Field error
Error beside the field and in a
summary. Focus moves to the
summary.Transmitting
Submit disabled, with progress
announced.Accepted
Shown only after durable server
receipt, with a safe reference.Failed or unknown
No success message. Status is
checked before any retry; the
draft is kept.Rate limited
Neutral message. No internal
defence detail.Route unavailable
Hidden, or an approved alternate
is shown. Never a broken link.Backend offline
Safe error with the approved
alternative route.
Your enquiry has been received.
Thank you. The details you submitted have been received for
review. A response or meeting is not confirmed by this receipt.
What a receipt means, and what it does not
A receipt confirms that your details were received for review. It is not a confirmed meeting, a sales response, a quote or an accepted offer. Any reference shown is opaque and contains none of your details.
Where each intent goes
Each intent has a destination and a forbidden fallback. A general
inbox is never a fallback for a security or privacy matter.
Zoiko iD is a Zoiko Tech Inc. platform.
Headquarters details are published on the Zoiko Tech Inc.
page once approved. A listed address does not mean a staffed
reception, local support or business hours.
Zoiko Tech Inc. page · route pending
| Intent | Destination precedence | Forbidden fallback |
|---|---|---|
| Sales and evaluation | Talk to Sales, then Enterprise | General contact used as a demo booking |
| Live technical fault | Help & Support or authorized account support | Public generic contact |
| Security vulnerability | Responsible Disclosure | General form |
| Security account issue | Security Contact or authorized support | Press or commercial route |
| Privacy or rights | Privacy Notice or approved rights process | General contact without rights verification |
| Developer integration | Developer Overview, documentation or supported help | Unverified public support email |
| Press and partners | Approved route, if verified | Invented mailbox or unapproved channel |
Where should I report a security issue?
Vulnerabilities go to Responsible Disclosure. Other security questions go to Security Contact. Neither uses the general form.
How do I get developer help?
Start with the developer documentation. Support routes are shown only where they are verified.
Can I send confidential information?
No. Do not send passwords, tokens, keys, identification numbers or
confidential configurations through any route here.How do I contact sales?
Choose Sales in the routes above. It is the route for evaluating Zoiko iD
for your organization.Does the page offer urgent support?
No. This page is not an emergency channel. For a live service event,
check Availability / Status and follow your own escalation process.
WCAG 2.2 AA is a
release blocker
The layout adapts at each breakpoint without horizontal scroll,
clipping or hover-only information.
- Desktop 1200px and up: four-column route grid.
- Tablet 768–1199px: two columns, no clipped menus.
- Mobile 320px: single column, no horizontal scroll.
- 200% zoom and 400% reflow with content preserved.
- Visible focus, linked error summary, colour never the only signal.
Access by role, and specialist queues stay private
Nothing on this page grants account privileges. Specialist submissions remain with their
owners.
Anonymous visitors
Access approved public
routing and submit an
approved general enquiry.
No account privileges.
Routing
administrators
Update only approved
registry records, with change audit, publisher review and rollback.
Specialist queues
Security, Privacy, Sales and
Support own their data.
General users cannot inspect it.
Abuse prevention
Privacy-respecting,
accessible rate limiting and
bot protection, with a manual alternative.
No user-provided content in URLs, browser analytics, log labels or third-party telemetry.- No claims of end-to-end encryption, exact retention days or 24/7 response unless approved controls exist.
Metadata that matches real availability
Structured data is added only for verified operational channels, and every FAQ matches the
routes that exist.
| Suggested title | Contact Zoiko iD | Corporate Enquiries and Support Routes (confirm against the content registry) |
|---|---|
| Meta description | Find the right Zoiko iD contact route for enterprise, developer, security, privacy and corporate enquiries. |
| Indexing | Index only if the page offers useful, current contact routing. No thin pages or false FAQ schema. |
| Structured data | Organization or ContactPoint, only for verified operational channels. No invented telephone numbers. |
| Canonical | Taken from the route registry, with one H1 and descriptive H2 groups. |
Ten journeys, including the failure
paths
Each journey ends at a real destination or a safe fallback. None ends at a broken link or a false
confirmation.
J01
Enterprise evaluator
Sales card → Talk to Sales.
No false booking
confirmation.
J02
Existing customer
Help & Support. Status
context kept, no secrets.
J03
Developer
API docs or developer help.
No assumed public ticketing.
J04
Vulnerability reporter
Responsible Disclosure with
a safe report path.
J05
Privacy requester
Verified rights instructions,
not a rights request.
J06
General enquirer
Minimal form, validated
receipt, accessible
confirmation.
J07
Keyboard visitor
Route selector to link, focus
preserved, no trap.
J08
Route disabled
Hidden, or a clear
maintained alternative.
J09
Backend unavailable
Safe error. No fabricated
success.
J10
Route update
Owner update, review,
staging QA, release,
rollback.
Measure qualified handoffs, not form volume
Events record intent categories and outcomes only, never message content or personal values.
| Event | Safe properties | Never recorded |
|---|---|---|
| contact_view | page version, locale | IP address, email, name |
| contact_intent_select | intent category, origin page | message content |
| contact_route_click | destination type, link ID | private URL parameters |
| corporate_form_validation | field key, error category | entered values |
| corporate_form_submit_result | success or failure class | full receipt token |
| contact_route_unavailable | route type, page version | personal details |
Primary measure
Successful qualified handoff to the right destination.
Secondary measure
Self-service deflection and fewer misrouted requests.
Guardrails
Assistive-technology abandonment, error rates and reports of
misrouted sensitive submissions.
Forty normative checks
Each check is verified by QA with owner sign-off before publication. A sample is shown here; the full register is held by the content registry.
- CT-01Registry keys
drive links - CT-04General form
publish-gated - CT-05No credential
collection - CT-06One visible H1
- CT-10Descriptive
link names - CT-12Errors tied to
fields - CT-15CSRF and
abuse
protection - CT-16No input in
analytics - CT-17Backend-
confirmed
receipts - CT-18Duplicates
avoided - CT-24Owner-verified
mailboxes - CT-26No walk-in
hours inferred - CT-27No SLA claims
- CT-28Security
routed
separately - CT-29Privacy rights
separate - CT-40Specialist
sign-off
Failing one test holds publication
Twenty acceptance tests must pass before release. A sample is shown below.
- AT-02A security reporter reaches Responsible Disclosure without seeing a
general form. - AT-03A privacy requester reaches approved rights instructions. The form is not
described as fulfilling a legal request. - AT-04An unknown route disables safe publication. No 404 and no invented
mailbox. - AT-06A server rejection is never reported as a successful submission.
- AT-07A duplicate retry does not create multiple submissions.
- AT-09No personal values appear in analytics, unauthorised logs or URLs.
- AT-10Mobile 320px and 400% reflow show no clipping.
- AT-15The corporate route is not an implied emergency-support channel.
- AT-18Consent is unbundled and defaults to the safe choice.
- AT-19Screen readers announce errors and success based on real outcomes.
Release blocker. Do not publish the corporate contact form or operational details until recipient ownership, approved route or URL, legal notice,
security processing, accessibility testing, consent, retention policy, monitoring and failure handling are verified and signed off.
Each function approves its own facts
Unconfirmed items stay as placeholders, and the page fails closed
until they are verified.
Decision log. Actual email addresses, telephone numbers, current
hours, ticket capabilities and canonical paths remain unresolved.
The page may be built with placeholders, but publication must fail
closed until each is verified.
Corporate and
ProductNarrative, brand
and route
taxonomy
Sales,
Support,
DevRelDestination
ownership and
capacity
Security
Disclosure routing
and form threat
review
Privacy and
LegalCollection,
retention, notices
and rights
Engineering
Form contract,
route registry,
deployment
Accessibility
and QAWCAG 2.2 AA and
acceptance matrix
Start with the route that
matches your question.
Specialist routes come first, so each enquiry reaches the team that
can act on it. No response time is promised.
Company / Contact
Reach the right
Zoiko iD team.
Choose the reason you are contacting us so
your request reaches the appropriate team.
For identity-platform evaluation, technical
help, security matters and privacy enquiries,
use the dedicated routes listed below. We will
not ask you to include passwords, secret keys
or unnecessary personal data.
Your enquiry type decides the next route.
Specialist routes come first. No response
time is promised on this page.
A general enquiry form appears only once it is approved
and verified.
How your enquiry is routed
Choose the reason
Select the category that matches
your question.
Follow the specialist route
Each category opens a
destination owned by the team
that handles it.
Security and privacy never
use the general form
High-risk requests go to their own
routes.
Receipt only after the
server confirms
A confirmation appears only when
the request is durably accepted.
Eight routes, each with a
clear purpose
Each route states what it is for and what it is
not for. A route marked pending has no
verified destination yet, so it does not link
anywhere.
Sales
Evaluating Zoiko iD for your organization.
Not for
Booking demos or quoting prices here.
Talk to Sales · pending
Help & Support
Existing customers with an account or
service issue.Not for
Security incidents or general enquiries.
Route pending
Developers
Integration questions and documentation.
Not for
Public ticketing, which is not assumed to exist.
Developer Overview · pending
Security
Security concerns and account-security
questions.Not for
Vulnerability reports, which go to Responsible
Disclosure.Security Contact · pending
Privacy
Questions about privacy practices and data
handling.Not for
Data-rights requests, which need the approved
process.Privacy Notice · pending
Press
Press enquiries, if a verified route exists.
Not for
Customer support or sales.
No mailbox published
Partnerships
Partnership enquiries, if a verified route
exists.Not for
Sales of the platform.
No mailbox published
General
Corporate questions that fit none of the
routes above.Not for
Sensitive data, secrets or incidents.
Form not yet approved
Security and privacy are
handled separately
Vulnerability reports and data-rights requests
never travel through a general inbox or a
general form.
Report a suspected
vulnerability
Use Responsible Disclosure. Do not send
exploit material, passwords or secret keys
through this page.
Vulnerabilities: Responsible
Disclosure.- Other security questions: Security
Contact. - Live service events: Availability /
Status.
Route pending verificationPrivacy questions and
rights requests
Sending a message here does not verify
your identity or fulfil a rights request.
- Privacy practices: Privacy Notice.
- Data-rights requests: the approved
rights process. - Legal terms: the legal notice.
Route pending verification
Do not include secrets
Passwords, tokens, API keys, private keys,
government identification numbers and
confidential security configurations must
never be included in a message. We will not
ask for them.
Keep messages to the facts needed to route
your request.- Attachments are not accepted by default.
The general form is gated
The general enquiry form is not shown on this
page. It can be published only once every
item below is verified.
Publication gate
- A verified recipient and owner for each
category - An approved route and privacy notice
- Security review of the processing
- Consent, retention and monitoring in place
- Accessibility testing and failure handling
signed off
Field specification only. No submit control is
shown.
- Enquiry type
- Required. Error: Choose a reason for
contacting us. - Full name
- Required; 1–120 characters; international
characters allowed. - Reply email
- Required; checked on the server; never
echoed in analytics. - Organization
- Optional; length-bound. Individuals are not
asked for one. - Subject
- Required; 5–160 characters.
- Message
- Required; 20–4000 characters. Warns
against passwords and tokens. - Consent
- Only if Legal requires it. Never a default
marketing opt-in. - Marketing opt-in
- Optional and unchecked. Cannot block an
enquiry.
No state claims success it
has not earned
A receipt is shown only after the server
confirms durable acceptance. A timeout is
never shown as success.
Pristine
Empty fields and no errors shown.
Field error
Error beside the field and in a summary. Focus
moves to the summary.Transmitting
Submit disabled, with progress announced.
Accepted
Shown only after durable server receipt, with a
safe reference.Failed or unknown
No success message. Status is checked before
any retry; the draft is kept.Rate limited
Neutral message. No internal defence detail.
Route unavailable
Hidden, or an approved alternate is shown.
Never a broken link.Backend offline
Safe error with the approved alternative route.
Your enquiry has been
received.
Thank you. The details you submitted
have been received for review. A
response or meeting is not confirmed
by this receipt.
What a receipt means, and
what it does not
A receipt confirms that your details were
received for review. It is not a confirmed
meeting, a sales response, a quote or an
accepted offer. Any reference shown is
opaque and contains none of your details.
information
Where each intent goes
Each intent has a destination and a forbidden
fallback. A general inbox is never a fallback
for a security or privacy matter.
Zoiko iD is a Zoiko Tech
Inc. platform.
Headquarters details are published on
the Zoiko Tech Inc. page once approved.
A listed address does not mean a staffed
reception, local support or business
hours.
| Intent | Destination precedence | Forbidden fallback |
|---|---|---|
| Sales and evaluation | Talk to Sales, then Enterprise | General contact used as a demo booking |
| Live technical fault | Help & Support or authorized account support | Public generic contact |
| Security vulnerability | Responsible Disclosure | General form |
| Security account issue | Security Contact or authorized support | Press or commercial route |
| Privacy or rights | Privacy Notice or approved rights process | General contact without rights verification |
| Developer integration | Developer Overview, documentation or supported help | Unverified public support |
| Press and partners | Approved route, if verified | Invented mailbox or unapproved channel |
Where should I report a security
issue?Vulnerabilities go to Responsible
Disclosure. Other security questions go to
Security Contact. Neither uses the general
form.How do I get developer help?
Start with the developer documentation.
Support routes are shown only where they
are verified.Can I send confidential
information?No. Do not send passwords, tokens, keys,
identification numbers or confidential
configurations through any route here.How do I contact sales?
Choose Sales in the routes above. It is the
route for evaluating Zoiko iD for your
organization.Does the page offer urgent
support?No. This page is not an emergency
channel. For a live service event, check
Availability / Status and follow your own
escalation process.
resilience
Access by role, and
specialist queues stay
private
Nothing on this page grants account
privileges. Specialist submissions remain with
their owners.
Anonymous visitors
Access approved public routing and submit
an approved general enquiry. No account
privileges.
Routing administrators
Update only approved registry records, with
change audit, publisher review and rollback.
Specialist queues
Security, Privacy, Sales and Support own
their data. General users cannot inspect it.
Abuse prevention
Privacy-respecting, accessible rate limiting
and bot protection, with a manual
alternative.
No user-provided content in URLs, browser
analytics, log labels or third-party telemetry.- No claims of end-to-end encryption, exact
retention days or 24/7 response unless
approved controls exist.
WCAG 2.2 AA is a release
blocker
The layout adapts at each breakpoint without
horizontal scroll, clipping or hover-only
information.
- Desktop 1200px and up: four-column route
grid. - Tablet 768–1199px: two columns, no clipped
menus. - Mobile 320px: single column, no horizontal
scroll. - 200% zoom and 400% reflow with content
preserved. - Visible focus, linked error summary, colour
never the only signal.
governance
Metadata that matches real
availability
Structured data is added only for verified
operational channels, and every FAQ
matches the routes that exist.
| Suggested title | Contact Zoiko iD | Corporate Enquiries and Support Routes (confirm against the content registry) |
|---|---|
| Meta description | Find the right Zoiko iD contact route for enterprise, developer, security, privacy and corporate enquiries. |
| Indexing | Index only if the page offers useful, current contact routing. No thin pages or false FAQ schema. |
| Structured data | Organization or ContactPoint, only for verified operational channels. No invented telephone numbers. |
| Canonical | Taken from the route registry, with one H1 and descriptive H2 groups. |
Analytics, conversion and
retention
Measure qualified
handoffs, not form volume
Events record intent categories and outcomes
only, never message content or personal
values.
| Event | Safe properties | Never recorded |
|---|---|---|
| contact_view | page version, locale | IP address, email, name |
| contact_intent_select | intent category, origin page | message content |
| contact_route_click | destination type, link ID | private URL parameters |
| corporate_form_validation | field key, error category | entered values |
| corporate_form_submit_result | success or failure class | full receipt token |
| contact_route_unavailable | route type, page version | personal details |
Primary measure
Successful qualified handoff to the right
destination.Secondary measure
Self-service deflection and fewer misrouted
requests.Guardrails
Assistive-technology abandonment, error
rates and reports of misrouted sensitive
submissions.
Critical user journeys
Ten journeys, including
the failure paths
Each journey ends at a real destination or a
safe fallback. None ends at a broken link or a
false confirmation.
J01
Enterprise evaluator
Sales card → Talk to Sales. No false booking
confirmation.
J02
Existing customer
Help & Support. Status context kept, no secrets.
J03
Developer
API docs or developer help. No assumed public
ticketing.
J04
Vulnerability reporter
Responsible Disclosure with a safe report path.
J05
Privacy requester
Verified rights instructions, not a rights request.
J06
General enquirer
Minimal form, validated receipt, accessible
confirmation.
J07
Keyboard visitor
Route selector to link, focus preserved, no trap.
J08
Route disabled
Hidden, or a clear maintained alternative.
J09
Backend unavailable
Safe error. No fabricated success.
J10
Route update
Owner update, review, staging QA, release, rollback.
Forty normative checks
Each check is verified by QA with owner sign-
off before publication. A sample is shown
here; the full register is held by the content
registry.
- CT-01Registry keys drive links
- CT-04General form publish-gated
- CT-05No credential collection
- CT-06One visible H1
- CT-10Descriptive link names
- CT-12Errors tied to fields
- CT-15CSRF and abuse protection
- CT-16No input in analytics
- CT-17Backend-confirmed receipts
- CT-18Duplicates avoided
- CT-24Owner-verified mailboxes
- CT-26No walk-in hours inferred
- CT-27No SLA claims
- CT-28Security routed separately
- CT-29Privacy rights separate
- CT-40Specialist sign-off
publication blockers
Failing one test holds
publication
Twenty acceptance tests must pass before
release. A sample is shown below.
- AT-02A security reporter reaches Responsible
Disclosure without seeing a general form. - AT-03A privacy requester reaches approved
rights instructions. The form is not
described as fulfilling a legal request. - AT-04An unknown route disables safe
publication. No 404 and no invented
mailbox. - AT-06A server rejection is never reported as a
successful submission. - AT-07A duplicate retry does not create multiple
submissions. - AT-09No personal values appear in analytics,
unauthorised logs or URLs. - AT-10Mobile 320px and 400% reflow show no
clipping. - AT-15The corporate route is not an implied
emergency-support channel. - AT-18Consent is unbundled and defaults to the
safe choice. - AT-19Screen readers announce errors and
success based on real outcomes.
Release blocker. Do not publish
the corporate contact form or
operational details until recipient
ownership, approved route or
URL, legal notice, security
processing, accessibility testing,
consent, retention policy,
monitoring and failure handling
are verified and signed off.
Cross-functional sign-off and
handoff
Each function approves its
own facts
Unconfirmed items stay as placeholders, and
the page fails closed until they are verified.
Decision log. Actual email addresses,
telephone numbers, current hours, ticket
capabilities and canonical paths remain
unresolved. The page may be built with
placeholders, but publication must fail closed
until each is verified.
Corporate and Product
Narrative, brand and route taxonomy
Sales, Support, DevRel
Destination ownership and capacity
Security
Disclosure routing and form threat review
Privacy and Legal
Collection, retention, notices and rights
Engineering
Form contract, route registry, deployment
Accessibility and QA
WCAG 2.2 AA and acceptance matrix
Start with the route that
matches your question.
Specialist routes come first, so each enquiry
reaches the team that can act on it. No
response time is promised.
