Location messages webhook reference | Developer Documentation

Check incoming WhatsApp locations with ChatArchitect

Use this checklist when a customer shares a map point for a visit, collection or delivery. Confirm that the receiving system shows the intended point before turning it into an address or a business task.

The ChatArchitect API quick start documents an incoming text example. It does not specify incoming location payloads, map rendering or automatic address updates. Confirm these capabilities for the particular API application or CRM integration with support.

Confirm the destination with the customer

Meta's location-event reference describes coordinates and place details in a customer message. Its fields explain the platform event; obtain the ChatArchitect mapping before using those fields in a custom receiver.

• Keep the map point attached to the actual sender and the connected business number.
• Ask whether the point identifies the requested destination, an entrance or another meeting place.
• Check available coordinates even when a readable address is shown. Place labels and an operational delivery address can differ.
• Treat a shared map point as the information supplied in that message. It does not establish continuous tracking or the customer's current position.

Check receipt and map handling

1. Confirm the business connection and receiving route. For a ready-made CRM or help desk, check whether incoming locations appear as a map, link, text or unavailable message.
2. For a custom application, request a redacted location callback and confirmed coordinate fields from support. Verify the receiver setup before processing customer traffic.
3. Use a permitted test account and a non-sensitive public place. Send a normal text first, then share a fixed map point. Check the baseline using the incoming-text guide.
4. Compare the selected point on the test phone with the received chat item or supported event. Record the time with time zone and available message reference.
5. Open the received point in a map and verify the intended area and entrance. Check that any displayed name or address describes that same point.
6. Review the proposed CRM address or delivery task before saving it. If essential details are missing, ask for the street address, building and access instructions in text.

For an application that receives confirmed coordinate fields, validate them before constructing a map link. Latitude lies between -90 and 90; longitude lies between -180 and 180. Preserve signs and decimal values, and keep latitude/longitude order explicit. Zero is a valid coordinate value; use field presence and range checks to detect missing data.

When the received map is wrong or absent

If incoming locations are unavailable in that integration, ask for a clear address and a checked map link in text. Use the webhook overview for event routing and duplicate processing; confirm the connection before changing its callback.

For support, provide the receiving route, integration version, test time, available reference and the stage where the point changed or disappeared. Use non-sensitive test coordinates or redact customer location details according to the data-handling guide.

For sharing the business's own destination with a customer, use the outgoing-location guide. See Meta's incoming-location reference for platform details; it does not specify your CRM display or ChatArchitect callback mapping.