Location messages

The important part first: doTask does not track anybody, and cannot. A location only ever arrives because something sends it — your own app, POS or kiosk calling POST /v1/api/location with a contact and a latitude and longitude, or a customer who pressed a button and granted their browser’s permission. There is no background collection, nothing runs on a customer’s phone, and a fence with nothing reporting to it never fires. That is a design choice, not a limitation: a messaging tool that quietly followed people around would deserve everything it got.

A fence is a point and a radius, whether it fires on arriving or on leaving, and what goes out — a browser notification (free) or a text message (your provider bills you). Keep the radius at 150 metres or more: ordinary GPS drift will otherwise set it off across the street. There is no map on the page because a map means a third party watching your customers; instead, “use where I am now” reads this device’s position and a link opens the circle in a real map to check it.

Three manners, all enforced. A message goes on a crossing, not for every reading — someone standing in your shop for an hour is messaged once. It never goes twice inside the cooldown, however often their phone reports in. And it never goes during quiet hours, in your workspace’s own clock: a crossing at 2 a.m. sends nothing and is not held for the morning, because an offer that arrives eight hours late is a mystery. On top of that, anyone who replied STOP to an SMS is never messaged by an SMS location message.

1. Flows → Location messages → New location message.
2. Set the place and the radius; check it on the map.
3. Write the message, set the cooldown and the quiet hours.
4. Switch it on, and have your app or your kiosk post locations to /v1/api/location.