DocsPoints of interest
Points of interest
Rooms, restrooms, elevators and exits as locations; display names, aliases and keywords; detected text from signs; and how a visitor’s request resolves.
On this page
Visitors ask for places in their own words: “the toilets”, “Dr. Lee”, “where do I pay”. Points of interest are how an organization makes those requests resolve to the right location without renaming the location itself.
Locations and points of interest
A location is a node on the map with a name, a type and a floor; routes start and end at locations. A point of interest is a searchable name attached to a location: a display name, optional aliases and keywords, a category and a description. One location can carry several points of interest (a reception desk that is also the lost-and-found), and a point of interest can be hidden from visitors until it is ready.
Rooms, restrooms, elevators and exits
| Place | How to map it |
|---|---|
| Rooms and offices | A Room location named as it is signed (“Room 210”). Add a point of interest for the occupant or the service (“Dr. Lee”, “Payroll”). |
| Restrooms | A Room location named “Restrooms” or as signed, with aliases such as “toilets”, “WC”, “bathroom”, “ladies”, “gents”. Map each restroom; visitors are routed to the one they ask for or that the resolver picks. |
| Elevators and stairs | An Elevator or Stair location on each floor they serve, connected across floors. Visitors can ask for them directly and floor-change instructions use them. |
| Entrances and exits | Entrance and Exit locations. Entrances are offered first among suggestions and are the usual place for a location QR code. |
| Landmarks | A Landmark location for atriums, information desks and fountains: easy to recognise, useful to say “Head toward the atrium”. |
| Outdoor | An Outdoor location for a courtyard or a car park, joined with Outdoor or Outdoor path connections. |
Managing points of interest
Open the map’s Reference images tab and switch to Detected text. Owners and administrators can add a point of interest with these fields.
| Field | Notes |
|---|---|
| Display name | Required, up to 160 characters. What visitors see when it matches. |
| Destination location | Required. The location the visitor is routed to. |
| Category | Free text, up to 120 characters, for example “Restroom” or “Café”. |
| Approved OCR source | Optionally link the detected text this point of interest came from. |
| Description | Up to 1200 characters, shown to your team. |
| Aliases | Up to 20, comma-separated. Other names visitors use: “Cafe, Coffee shop”. |
| Keywords / services | Up to 30, comma-separated. What visitors come for: “coffee, breakfast, takeaway”. |
| Published and searchable by visitors | Off keeps it as a draft only your team sees. |
Detected text from signs
Run Run / retry OCR on a reference image to read printed text such as room numbers and door signs. Each detection appears in the Detected text view with the status Detected, where owners and administrators can Approve it, Reject it or Reassign it to another location, and turn an approved detection into a point of interest. Detection never publishes a destination automatically.
How a request resolves
When a visitor sends a request, Veeee matches it against the building’s location names and its published points of interest, including display names, aliases and keywords, and answers in one of three ways.
- Matched: one place clearly fits. The visitor sees “Your destination is {name}.” and the destination card.
- Needs clarification: several places could fit. The visitor is asked Did you mean with a short list and can pick one or say None of these.
- No match: the visitor is asked to try the room name or describe what they are looking for.
Testing the words visitors actually use, and adding the ones that fail as aliases or keywords, is the single most effective way to improve a building’s navigation. See Testing navigation.