Testimonial Request Email

Complete **testimonial request email** from the source material, constraints, and desired outcome below. For “testimonial request email prompt”, accuracy and usability matter more than impressive-sounding breadth.

## Starting point — Testimonial Request Email
- [KEY_DETAIL] — for Testimonial Request Email, supply the relevant key detail. If unavailable, label [KEY_DETAIL] `unknown`; never infer it.
- [SIGN_OFF] — for Testimonial Request Email, supply the relevant sign off. If unavailable, label [SIGN_OFF] `unknown`; never infer it.
- [RELATIONSHIP] — for Testimonial Request Email, supply the relevant relationship. If unavailable, label [RELATIONSHIP] `unknown`; never infer it.
- [TONE] — for Testimonial Request Email, supply the relevant tone. If unavailable, label [TONE] `unknown`; never infer it.
- [DEADLINE] — for Testimonial Request Email, supply the relevant deadline. If unavailable, label [DEADLINE] `unknown`; never infer it.
- [RECIPIENT] — for Testimonial Request Email, supply the relevant recipient. If unavailable, label [RECIPIENT] `unknown`; never infer it.
- [MESSAGE_HISTORY] — for Testimonial Request Email, supply the relevant message history. If unavailable, label [MESSAGE_HISTORY] `unknown`; never infer it.
- [REPOSITORY_CONTEXT] — for Testimonial Request Email, supply the relevant repository context. If unavailable, label [REPOSITORY_CONTEXT] `unknown`; never infer it.

## Execution sequence — Testimonial Request Email
1. Account for what has already been communicated and what response is realistically needed now.
2. Include a direct version and a softer alternative without changing the underlying facts.
3. Trace observable behavior through the relevant code path before editing anything.
4. Provide the smallest defensible patch, regression tests, and exact verification steps.
5. Include only details that help the recipient act.
6. Make the requested next step easy to understand.
7. Calibrate warmth and directness to the situation.
8. Remove pressure, filler, and invented familiarity.
9. Boundary for Testimonial Request Email: Do not invent a relationship, urgency, prior conversation, offer, result, or personal detail.

## Deliverable — Testimonial Request Email
- **Subject line for Testimonial Request Email** — material inputs for Testimonial Request Email, each connected to testimonial request email prompt.
- **Email draft for Testimonial Request Email** — ready-to-use Testimonial Request Email, formatted for testimonial request email prompt.
- **Short alternative for Testimonial Request Email** — Testimonial Request Email weak points, unknowns, and testimonial request email prompt limits.
- **Tone note for Testimonial Request Email** — testimonial request email prompt → verify Testimonial Request Email before use.
- **Send check for Testimonial Request Email** — testimonial request email prompt evidence → Testimonial Request Email; omit preamble.

## Last review — Testimonial Request Email
Confirm that the finished Testimonial Request Email answers the stated query, uses no unsupported facts, and can be acted on without guessing what comes next.