customers.winBackQueue
Send the win-back note to customers from customers.winBack: adds one service due date each (title, due in the shop's lead days), so the service_due_reminders job emails them once by the usual rules. Customers who can't be emailed, or who are no longer on the win-back list, are skipped and counted. Owner only. Needs service due emails on and the shop's mailing address. No texts.
| Who | Agents can call this |
| REST | POST /v1/customers/win-back/queue |
| MCP tool | customers_winBackQueue |
| Writes | yes, send an Idempotency-Key |
| Area | Shop |
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 |
customer_ids | array | yes |
months | integer | no |
title | string | no |
Example
POST https://doingwork.work/v1/customers/win-back/queue
content-type: application/json
Idempotency-Key: 3f1c...
{
"shop_id": "00000000-0000-4000-8000-000000000000",
"customer_ids": [
"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. |