Plan requirement
| Subscription | x-hoppers SuperHopper + AI |
How stores, zones and teams fit together in x-hoppers, and why getting the zones right decides whether alerts are useful.
The three levels
- Store. One physical location with its own broadcast channel. Staff in one store do not hear another.
- Zone. An area within the store, such as a department or a floor. Call points belong to a zone, which is how a request knows where to send people.
- Team. Who does what. Sales floor, back office, management.
Zones decide whether alerts are useful
A request that says "someone needs help in electronics" sends the right person. One that says "someone needs help in the store" sends everyone or nobody.
Zones that match how staff actually think about the space work; zones copied from a floor plan often do not. If your team says "up by the tills" and your zone is called "Zone 3", the announcement will not land.
Name zones the way staff already talk about the store. The announcement is spoken aloud into people's ears, so it has to sound like something a colleague would say.
How many zones
Too few and requests are vague. Too many and staff stop distinguishing them. A useful test: could someone hearing the zone name walk straight there without thinking? If not, the zone is too abstract or too large.
Multiple stores
Each store gets its own channel, so a busy Saturday in one branch does not fill the ears of staff in another. Head office can join any store's channel from the app when needed.
Setting it up
Stores, zones and call point assignments are configured when your system is set up. Changing the layout, adding a store or restructuring zones is something we arrange. Tell us what changed and we will update it.
Comments
0 comments
Article is closed for comments.