Your request form
Last updated August 21, 2026
Customers ask you for service without anyone typing it in: a link for an email or a Facebook post, a QR code for the truck and the invoice, or the form inside your own website.
Every shop has one public form. Anyone who opens it can ask you for service: their name, a way to reach them, the address, which of your lakes it is on, and what they need. Nothing goes into your book until you accept it.
Three ways to hand it out
Under Settings → Account, the Requests for service panel shows all three. The address never changes and never expires, so print it once.
- The link — for an email signature, a Facebook post, a text reply.
- The QR code — for the truck, the barge, the invoice, a sign at the landing. Save the image from that page or print the page.
- The embed — a few lines to paste into your own website where the form should appear. It takes your site's width and shows nothing of LakeOps around it.
What happens when someone sends one
It lands under Requests in the office, the bell rings, and your admins get an email with what they wrote. Open it and press Accept: that creates the customer and the property on the lake they chose and opens the property so you can add the pieces. Decline files it under Decided and creates nothing. Either way the request stays on the record, and it leaves with your data in an export.
The form is public, so it is guarded like one: a hidden field that only a script would fill, and a limit on how many requests one address can send in an hour. A household sends one; a property manager sends a handful; a script gets nowhere.
How a request knows it is yours
The address carries a signed code for your shop. A request sent through it can only land on your account, and it can only name one of your lakes — a form for another shop's lakes is refused outright.
Still stuck? Ask us — or go back to the help center.