message

Message a customer (with the owner's approval) · Can change or delete · actions: request, status, list

For reading use message_read, which is read-only and needs no approval: "status", "list" here are deprecated (still works). Ask the project's owner to send an email to ONE customer from the project's own live address. You draft; nothing is sent until the owner approves the exact recipient and text in their portal (they can edit the text, tick that they know the address, or decline), then LazyFrog sends it once, word for word, through the owner's own email provider (connected in Account › Email), with a footer "Sent on behalf of <the project> via LazyFrog" and replies going to the owner. action "request" (recipient: one address that appears in the project's live data, a customer, order or contact row or a form submission, otherwise the owner has to confirm it; subject; text: plain text, no attachments; links only to the project's own live addresses, others need the owner's tick; repeat: true only when the user asks for a second message to the same person the same day): the answer is "waiting for the owner's approval" with a link; tell the user that, and read the outcome later with message_read status (message_id). Show the user the text in the chat before asking. Never for marketing, newsletters or more than one person (one recipient per request, a daily limit per project); never to move money (refunds, charges, payouts: the owner does those in their payment provider or the app's own admin; explain and link). For a request the user makes often, offer to build it into the app as an owner action instead. "status" (message_id) and "list" here are deprecated: use message_read.