How to Send a Location on WhatsApp Business API (Store Locations, Delivery, Appointments)

A store address typed out as plain text ("123 Main St, next to the pharmacy") asks a customer to do the work of finding the place themselves - copy it, open a maps app, paste it in, hope the address resolves correctly. A WhatsApp location message skips all of that: it sends an actual pin, with latitude and longitude, that opens directly in the customer's map app with one tap.

The format itself is simple - a location message (or a template with a LOCATION-format header) carries a latitude, a longitude, and optionally a name and address string shown alongside the pin. Unlike an image or document header, there's nothing to upload in advance for a location template - the actual coordinates are supplied at send time, since a location is inherently a live value, not a fixed sample.

The clearest use case is a physical store or branch: instead of a support agent typing an address and hoping it's copy-pasted correctly into a map app, a single template send drops the exact pin for the nearest branch, with the store's name and hours in the address field. For any business with more than one location, this alone measurably cuts down on customers going to the wrong branch or getting lost en route.

Delivery and field service is the other strong fit - a driver's current stop, a technician's next appointment address, or a pickup point can all be sent as a live location the customer can tap straight into navigation, rather than a support agent describing where to meet in a paragraph of text that has to be re-read and manually entered.

Appointment-based businesses (clinics, salons, repair shops) benefit from combining a location message with a booking confirmation template - the same message that confirms the date and time can carry the exact location pin for where to actually show up, cutting down on a specific, common support question ("wait, where is this again?") before it's even asked.

One thing worth getting right: the location's name and address fields are for humans, not for parsing - keep them short and exactly matching what a customer would see on a sign or a map listing, since a location message's whole value is instant recognition, not another string to interpret. If your CRM or booking system already stores coordinates for stores or appointments, this is a genuinely low-effort feature to wire in once, that keeps paying off on every relevant send afterward.