Check what the number includes.
If the question is how long customers wait, start with response-time measurement. Define the response being counted, then examine recorded times alongside unanswered inquiries and missing evidence. The guide includes calculation tools; a result is only as complete as the records entered.
If the question is whether activity became business, use the attribution guide. Keep inquiries, bookings, attendance and settled payment separate. A visit source can describe where a record came from without proving what caused the outcome.
Ask the person who experienced the step.
Use staff feedback questions when you need to understand the work behind the screen. Ask about a task the person actually attempted, then distinguish an observed obstacle from a preference.
Use customer feedback when you need to understand the experience outside the business. Keep comments separate from possible explanations and note whose experience is missing. These are different viewpoints; neither automatically proves the cause or represents everyone.
Make the review end somewhere useful.
The customer-path review guide brings observations, limits and a proposed next action together. Choose a small check that could resolve the uncertainty, an owner and a review point your team has agreed.
You can stop with a clear question when the evidence cannot support a change yet. When a change is justified, use a change brief so a proposed fix does not become an assumed approval. If you want to discuss ongoing stewardship of an agreed customer path, read the BusinessOS scope and responsibilities.
Put the guidance to work.
Use the instructions before filling in a worksheet. These downloads are blank and do not submit information to JetSynapse.