Written permission
Permission must cover the identity, materials, statements, channels, scope of use, and any limits or expiration.
Customer stories
Customer proof should be specific, permitted, and verifiable.
Heritage uses customer names, logos, workflows, screenshots, quotations, architectures, and results only with the facts and written permission needed for public use.
A useful story standard
Every proof element needs its own support.
A customer’s permission to discuss one fact does not automatically authorize every name, asset, workflow, result, or future use.
Verified context
The initial problem, constraints, relevant environment, design, migration context, and products used must be accurate.
Defensible result
A result needs its measurement method, period, baseline, and limitations. Heritage does not convert an anecdote into a metric.
Permission-safe collateral
Each logo, portrait, photograph, screenshot, call record, workflow, or architecture diagram needs appropriate rights and sanitization.
How to read customer proof
Context and limitations belong beside the outcome.
A useful story shows what was learned without implying that the same design or result applies to another organization.
- Context
- Industry, organization shape, locations, roles, and the relevant starting environment.
- Problem and constraints
- The operating issue, dependencies, policies, timing considerations, and boundaries that shaped the work.
- Design and migration
- The workflow, products used, responsibilities, transition, testing, and important exceptions.
- Result and method
- The outcome, how it was assessed, the relevant period, limitations, and what should not be generalized.
- Customer voice
- An exact permitted quotation with speaker identity and context; no reconstructed or composite endorsement.
- Permission scope
- Written authorization must cover every customer name, mark, statement, asset, architecture, and result used.
Evidence before analogy
A category does not prove expertise or fit.
Industry, problem, solution family, organization size, and multi-location context can help compare situations. They do not make one customer’s architecture, result, or product fit transferable to another.
Evidence without customer proof
Use sanitized planning artifacts for the method—not as a substitute endorsement.
The Our Approach page links the deterministic System Planner, synthetic call-flow demonstration, Migration Guide, and Business Phone Buyer’s Guide worksheet. They explain process boundaries without presenting fictional customer results.
Your requirements are still specific
Start with the current environment—not an unverified analogy.
Heritage can review the workflow, constraints, dependencies, and desired result without claiming another organization proves the answer.