Draft a short, careful reply that answers the request without overexplaining or inventing commitments.
The recommended model and prompt are filled in. Choose your own inputs and generation settings.
Preview
Chat Prompt
A partner asks if we can guarantee every Prompt template will use fully licensed media before launch.
Thanks for asking. We are treating reviewed examples as a launch gate, not a cosmetic task. The current plan is to keep draft assets separate, move final examples to approved URLs, and document any compatibility behavior that remains. I cannot frame that as a blanket guarantee until the final audit passes. Next step: I can share the current audit status and remaining replacement list.
Output
Acknowledgment / Direct answer / Useful detail / Boundary / Next step
Best for inbox replies, support follow-up, and calm operational communication.
Concise reply prompt for inbox, support, and partner messages.
You are a concise communications assistant. Draft a reply in under 120 words with: Acknowledgment, Direct answer, One useful detail, Next step, and Boundary. Preserve the user intent and tone. Do not add promises, timelines, discounts, or policy claims that were not provided.
Usage notes
Paste the original message, allowed facts, forbidden promises, and desired tone.
Prompt FAQ
Paste the original message, allowed facts, forbidden promises, and desired tone.
Replace the product, audience, constraints, output format, and any brand or safety rules so the result matches the actual job.
Thread preview
Output
Acknowledgment / Direct answer / Useful detail / Boundary / Next step
More prompts in this mode
Original reply: We cannot refund this. Try again later. Policy does not allow it.
Revised reply: I cannot approve a refund from this message alone, but I can help review the failed task. Please send the task ID and the time it ran so we can check the logs. Tone change: firm but helpful. Removed risk: no unsupported blanket policy claim. Remaining caveat: refund depends on task review.
Macro: Sorry this happened. We always investigate failed generations and will make it right once we know what went wrong.
Revised macro: Thanks for sending this in. Please share the task ID and approximate time of the failed generation so we can review the logs. Required placeholders: task ID, task time, account email if needed. Policy boundary: do not promise a credit adjustment before review. Agent note: use only when the customer reports a failed generation.
Clause says vendor may change AI subprocessors with notice on the website only. What should we ask?
Risk: notice may be easy to miss and may not give the team enough time to object. Business impact: privacy, procurement, and customer commitments could be affected. Question 1: can changes trigger email notice to the account owner? Question 2: is there an objection window for material subprocessor changes? Question 3: can regulated customer data be excluded from new subprocessors by default?
