dove-schedulelisted

# /dove-schedule — schedule a send / campaign Engine: `dove.py` in this skill's folder. Config: shared `~/.dove/config.json` (run `/dove-setup` if missing). Scheduling uses Dove's `time` parameter (`YYYY-MM-DD HH:MM:SS`, account timezone). ## Single / few numbers ``` python3 ~/.claude/skills/dove-schedule/dove.py send-template --name <template> \ --mobile <number> --schedule "2026-06-06 10:00:00" ``` ## Bulk campaign ``` # preview first python3 ~/.claude/skills/dove-schedule/dove.py bulk --name <template> \ --file <numbers> --schedule "2026-06-06 10:00:00" --dry-run # then schedule for real python3 ~/.claude/skills/dove-schedule/dove.py bulk --name <template> \ --file <numbers> --schedule "2026-06-06 10:00:00" --yes ``` ## Confirming later A scheduled send is accepted now but delivered at the scheduled time, so there's no immediate DLR. After the scheduled time, confirm with `/dove-report`: ``` python3 ~/.claude/skills/dove-schedule/dove.py report --date <send-date> ``` ## Notes - Use the account's timezone for the schedule time; confirm it with the user. - Same DLT rules apply at delivery time (template match, route, DND, CTAs). - To cancel a scheduled campaign, use the Dove portal (no cancel API here).