Customer Stories & Reference Requests

Evaluate results with evidence you can verify

Evaluate ZARIS customer references, workflow evidence, pilot measurements and permissioned case studies for AI, CRM and business automation projects.

Illustrative case study folios examined through a verification lens
Evaluation evidence

Evidence policy: named customer accounts, quotations and results are published or discussed only when permission allows.

Evidence before claims

A credible story shows what changed—and how it was checked.

Comparable context

Industry alone is not enough. Compare the workflow, systems, team roles, request volume and operating constraints.

Confirmed scope

Identify what reached production, what remained a pilot and which decisions or actions stayed with staff.

Traceable outcome

Connect every result to a baseline, measurement period, source and review method—with limitations visible.

Representative journeys

See the workflow. Test the fit.

These scenarios explain possible handoffs. They are illustrative workflow examples—not customer case studies, testimonials or measured outcome claims.

Open interactive demos →
01

Workflow example · Not a customer claim

Healthcare workflow

Patient enquiry to appointment request

An illustrative path for capturing an enquiry, checking the request context and routing it to an authorised clinic team member.

Explore healthcare solutions
02

Workflow example · Not a customer claim

Property workflow

Buyer enquiry to agent follow-up

A representative handoff from property interest and buyer requirements to the right sales or leasing owner.

Explore real estate solutions
03

Workflow example · Not a customer claim

Education workflow

Programme enquiry to admissions owner

An example of collecting programme context, preserving the conversation and routing the next step to admissions staff.

Explore education solutions
Anatomy of publishable evidence

From baseline to a permissioned customer story.

A demo can explain a workflow. A customer story needs a stronger chain: approved context, actual scope, a defined observation period, reviewed evidence and publication permission.

  1. 01

    Baseline

    Describe the original workflow, volume, constraints and source of the starting measure.

  2. 02

    Delivered scope

    Separate implemented actions from proposals, demonstrations and work left outside scope.

  3. 03

    Observation window

    State the period, task population, exceptions and people involved in reviewing the result.

  4. 04

    Evidence review

    Check quality, staff effort and failure cases alongside speed, volume or completion.

  5. 05

    Publication permission

    Approve the identity, wording, quotations, visuals and supporting detail before release.

Pilot measurement scorecard

Measure the workflow that your team will use.

Before a pilot begins, agree what will be measured, where the source record lives and who decides whether the result is acceptable.

Define the sourceInclude exceptionsName the reviewer

Response handling

How long it takes a valid request to reach its next owned step.

Assignment quality

Whether requests reach the correct person, queue or system with usable context.

Exception rate

How often the workflow needs recovery, correction or an unplanned manual handoff.

Staff review effort

The time and judgement still required from an authorised team member.

Successful action

Whether the intended action completed and left an auditable record.

Visual indicators are illustrative categories—not published performance results.

Reference request

Ask for evidence relevant to your decision.

Tell us the workflow and result you need to assess. Where customer permission and confidentiality allow, we will explain what reference material can be shared and what should be validated in your own pilot.

Ask about customer references

Include in your request

  • Industry and operating context
  • Workflow and connected systems
  • Outcome you need to assess
  • Decision stage and stakeholders

Possible next evidence

  • Permissioned reference discussion
  • Relevant workflow demonstration
  • Scope and risk review
  • Pilot with agreed acceptance criteria
BUILD THE NEXT STEP

Validate a workflow with your own operating context

Bring a process, representative requests and success criteria. We can map a focused pilot and the evidence needed for a rollout decision.

ScopeSystemsSafeguards
Request a conversation

How to evaluate customer evidence

What a useful case study includes

Look for the initial workflow, implementation scope, timeframe and who measured the result. Check whether the example reflects a similar team, tool set and request volume.

What to request during evaluation

Tell us your industry, systems and the type of result you want to assess. Where permission allows, ask what evidence is available and what would require an evaluation with your own workflow.

How to use a demonstration

A demo helps you understand the steps and handoffs. Use representative requests and acceptance criteria in a pilot to test whether the approach works for your team.

Frequently asked questions

Can I request a customer reference in my industry?

Ask the team what approved references or evidence can be shared for a comparable workflow. Availability depends on customer permission.

Does an interactive demo show measured customer results?

Interactive demos show example workflows. Evaluate performance with agreed metrics and representative data in your own pilot.

Are the workflow examples on this page customer case studies?

No. They are clearly labelled representative workflows designed to explain possible steps and handoffs. They are not testimonials or measured customer outcome claims.

What evidence can be shared during an evaluation?

Depending on permission and confidentiality, evidence may include an approved reference discussion, workflow demonstration, scope explanation or pilot measurement plan.

How should we validate whether a workflow fits our team?

Use representative inputs, known exceptions and agreed acceptance criteria in a focused pilot. Review quality, staff effort, permissions, recovery and successful actions before rollout.

Can a customer story be anonymised?

Anonymisation may be possible when customer permission and evidence integrity allow it. The description should still provide enough context to understand scope, measurement and limitations.