Governed customer evidence, not testimonial theater
Every public fact traceable to an approved record, every customer asset rights-controlled, and every material outcome showing its evidence class, time period and limitations.
What are ZoikoSuite Customer Stories?
Customer Stories is governed customer evidence: accounts of how organizations use ZoikoSuite, published only where an approved source, evidence and rights record supports every public fact. Stories may be narrative and human, but each material outcome exposes its evidence class, measured period and limitations. A story describes one organization's experience under its own conditions; it does not establish a guaranteed or equivalent outcome for anyone else.
The status bar every story displays
Shown here with the values it can take. On a published story these reflect that story's live record.
Controlled taxonomy, user-controlled filters
These are the dimensions stories will be browsable by. All filters are chosen by you — nothing is inferred from role, identity or browsing.
Canonical inventory
This section renders exactly what the Story Registry reports as publishable — currently nothing.
Ten fields, and what each may not say
Published in advance so the rules are inspectable before any story exists.
Customer identity
Named, or approved anonymized. Identity is never implied through context, logo shape or descriptive hints.
Logo or image
Renders only with an active right. The fallback preserves layout rather than collapsing it.
Story title
No unsupported outcome claim in the title. A title cannot assert what the evidence record does not support.
Context
Challenge plus organization context. Implementation scope appears only where separately approved.
Outcome or lesson
Qualitative is allowed. Quantitative appears only via an approved Metric Record with full disclosure.
Evidence class
An adjacent text label, never colour or icon alone.
Period
The exact approved period, or the explicit words "not publicly disclosed". Never omitted silently.
Last verified
A date, or a review-due state. A story with no verification date cannot render as current.
Limitations
Accessible without opening a modal where the limitation is material.
Call to action
"Read story" only. Language such as "get results like this" is prohibited, because it converts evidence into a promise.
Twelve fields around every number
A number without its definition, period, method, scope and exclusions is not evidence. This is the block that will wrap any quantitative claim.
Eight events, each with an automatic behaviour
Customer control is operational. Suppression happens on the event, not after someone notices and files a request.
Quote right expires
Quote suppressed everywhere it appears, by quote ID.
Story owner reviews replacement or removal.
Logo or media right expires
Asset suppressed: an accessible neutral fallback preserves layout.
Reapprove or remove.
Metric permission withdrawn
Metric and result suppressed; the narrative reflows around the gap.
Revalidate the story's outcome copy.
Full story withdrawn
Hub, detail, featured, search, schema and social all suppressed; redirect or 410 per policy.
Confirm caches, syndication and internal archival.
Customer correction
Affected block paused if the correction is material.
Source check, customer review, then republish.
Evidence challenged
Claim or metric fails closed — it comes down rather than carrying a caveat.
Evidence owner investigates.
Product reference stale
Historical label applied, or the reference is suppressed.
Product owner validates current authority.
Re-identification risk rises
Affected story paused where an anonymized customer could become identifiable.
Privacy and legal re-review the granularity.
Eleven blocks, in fixed order
Limitations sit before the commercial route, never after it. Evidence sits immediately after the outcomes it supports.
Header
Approved identity or anonymity, title, summary, publication and update and verification dates, and the proof-status bar.
Customer context
Organization pattern, approved region and scale descriptors, operating scope and starting condition.
Challenge
The specific bounded challenge, and why it mattered to that organization.
Implementation
ZoikoSuite scope, source-of-record and coexistence position, migration and integration, governance, human roles, and rollout only as evidenced.
Outcomes
Approved qualitative and quantitative outcomes, each traced internally to a claim record.
Evidence
Evidence class, period, source description, method and limitations — adjacent to the outcomes above.
Customer voice
Approved quote or media, with active rights and an accessible alternative.
Lessons
What the customer and implementation team learned — never framed as a universal prescription.
Limitations
Explicit non-generalization, excluded scope, and the professional and product boundaries that apply.
Current authority
Links to current product, Trust, Documentation, Platform and solution pages — which supersede the story's history.
Continue
Related stories and resources, then existing-customer routes, and only then a commercial call to action. One contextual CTA after substantive proof or at the end — never repeated after every section.
Eight domains a story cannot speak for
One organization's experience is not a professional conclusion in any of these areas. Each boundary appears at the point where a story could otherwise be over-read.
Finance and accounting
Customer finance outcomes do not establish accounting correctness, financial statement accuracy or appropriate accounting treatment.
Legal and contracts
A story does not provide legal advice, determine enforceability or create legal authority.
Regulatory and compliance
A story does not prove regulatory approval or universal compliance. Jurisdiction, source and effective-date context controls.
Security and privacy
Customer experience does not independently certify platform security or privacy, or guarantee the absence of incidents.
Tax
A story does not provide tax advice, determine tax liability or prove jurisdiction-wide tax compliance.
Audit
Audit-readiness evidence does not constitute an audit opinion, certification, auditor acceptance or assurance conclusion.
Workforce and employment
No employment-law conclusion, employee surveillance or productivity-policing inference.
AI
Any AI-assisted workflow remains governed by source, limitation and human-authority rules. A story does not expand AI authority.
Where current truth actually lives
A story is historical by nature. These destinations carry the current product, architecture and trust position.
Not currently open
A customer advocacy path publishes only with an approved programme, and stays separate from sales, renewal and support. No programme is currently approved, so no invitation is shown.
Individual results vary. A story describes one organization's experience under its own conditions, over a stated period, with stated limitations. It is not a guarantee, a benchmark or a projection for any other organization.
Ask for the evidence you would need to believe a story
Since no story is published yet, the more useful conversation is about what would convince your evaluation team — which outcome, measured how, over what period, with which exclusions. That specification is worth more than a case study written to a template.
No customer outcome, benchmark, timeline or equivalent result is promised. Availability, coverage and implementation scope depend on approved architecture and readiness.
Book enterprise demo
Nothing on this page was gated behind this form.
Rights, evidence, metrics, anonymity and currency
Direct first sentences, then qualified detail. Every answer is present in the page source.
Because no story currently has all three approvals — source record, evidence record and rights record — that publication requires.
Any one of those failing blocks publication. Placeholder logos, illustrative company names or representative outcomes would be fabricated proof, which is the specific thing this page exists to prevent. See the inventory state