| Signal137 | Is this place, route, or event under real pressure, or only busy-looking? | Aggregated dwell time and flow by zone and time band, not device-level trails | Management action aimed at the zones and hours where pressure and dissatisfaction coincide |
| Signal137 | Which visitor segment is worth marketing to? | Segment-level behaviour and sentiment linked to spend pattern, not individual profiles | Marketing spend redirected toward the segments correlated with value, not only footfall |
| Signal137 | Where and when should we intervene on visitor experience? | Near-current aggregated flow and sentiment by location, on a defined refresh schedule | Signage, staffing, or dispersal placed where the evidence shows friction |
| Signal137 | Is that complaint a demand problem or an operational one? | Sentiment concentrated on wait time and signage at an interchange, separated from crowding in the core | A low-cost fix identified as such, and a capacity problem as such |
| Signal137 | Does this track individual visitors? | No. Aggregated before an analyst sees it, with small cells suppressed | The data-protection officer can see exactly what the figures represent |
| Signal137 | How is sentiment measured? | Review and social text aggregated by place and period, beside dwell and return-visit patterns | The two together, more reliable than either alone |
| Signal137 | Is this real time? | Refreshed on each source's documented schedule, stated in the brief | The refresh cycle is known, not assumed |
| Demand137 | What would a new event or campaign do to the pattern? | The same vectors run forward under the scenario | The intervention tested before it is placed |
| Both | Can we use our own survey or CRM data alongside yours? | Yes, where governance terms allow | An existing dataset strengthens the aggregated pattern rather than duplicating it |
| Both | Who holds this, and where? | Model, data, and a trained team inside your jurisdiction | The evidence survives the change of officer or agency |