requests.setLeadSettings

Change the shop's lead rules. Owner or office. auto_reply sends one first reply per new request: a text only where the customer already agreed to texts or texted the shop and the shop's number is approved, else an email, else nothing.


Who	Agents can call this
REST	`POST /v1/requests/lead-settings`
MCP tool	`requests_setLeadSettings`
Writes	yes, send an Idempotency-Key
Area	Customer hub, requests and customer emails

When to use it

Lead rules (requests.setLeadSettings, owner or office) decide what happens to a new request. With auto_reply on, Doing Work sends one first reply within a minute: a text only where the customer already agreed to texts or texted the shop, and the shop's own number is approved for business texting; otherwise an email; otherwise nothing.

What to tell the owner

Say what you did in plain words and what happens next.

Input

Field	Type	Required
`shop_id`	string (uuid)	yes
`auto_reply`	boolean	no
`after_hours`	string (one of offer, hold)	no
`skip`	array	no
`flag`	array	no

Example

POST https://doingwork.work/v1/requests/lead-settings
content-type: application/json
Idempotency-Key: 3f1c...

{
  "shop_id": "00000000-0000-4000-8000-000000000000"
}

Output

JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are {code, message, status}.

Errors

Code	Status	What to do
`invalid_input`, `invalid_token`, `rate_limited`		Can happen on any call. See errors.