safe-draft-and-send

Safe draft and send

Use this workflow for one deliberate message to one phone number. A request to draft, rewrite, summarize, or prepare is not permission to send.

Non-negotiable send boundary

• Before calling send_message, show the connected workspace, exact E.164 phone destination, chosen device when applicable, exact final text, every media URL, and any message effect.
• Ask for explicit confirmation of that exact preview. Stop before the tool call until the user confirms. Provider confirmation UI is an additional approval boundary, not a replacement for the preview.
• If any destination, workspace, device, attachment, effect, or text changes after confirmation, show a new preview and obtain new confirmation.
• Call send_message once. Never retry an ambiguous timeout or transport failure; first check the returned message identifier or status so a retry cannot create a duplicate.
• Never split one request into multiple recipients, loop over contacts, or present this workflow as bulk messaging.
• Public OAuth sends are 1:1 only. If the requested destination is a group, multiple recipients, or a group_chat_id, stop and explain that this connection cannot send there.
• Never call send_message with group_chat_id.

Stop and cancellation control

• The newest user instruction is authoritative. If, before a write tool starts, the user says stop, cancel, hold, pause, do not send, changes the request, or otherwise withdraws approval, cancel the pending action immediately.
• Cancellation invalidates every earlier preview and confirmation.
• Do not call send_message for the cancelled action, even if an earlier message approved it.
• If the provider or host rejects or closes its confirmation, treat that as cancellation too.
• Silence, elapsed time, or approval for a different payload never restores authorization.
• To resume or act on a changed request, rebuild the exact preview from current state and obtain fresh explicit confirmation in a later user turn.
• After a pre-call cancellation, acknowledge that no write ran and stop this workflow unless the newest instruction explicitly replaces it with read-only work.
• If a write tool may already have started, do not claim that it was cancelled. Check status or current state, report the facts, and never retry the write automatically.