SaaS Trial Extension Request Response Builder

Write policy-safe SaaS trial extension responses with decision rules, customer context checks, and sales or success handoff notes.

Prompt Template

Act as a SaaS support lead. Build a response framework for customers requesting a trial extension for [product name].

Context:
- Trial policy: [standard trial length, extension rules, limits]
- Customer type: [individual, startup, SMB, enterprise, student, nonprofit]
- Request reason: [too busy, technical issue, procurement delay, needs more testing, missed onboarding, unclear value]
- Usage signals: [activation status, logins, features used, seats invited, support issues]
- Commercial context: [self-serve, sales-assisted, open opportunity, no sales involvement]
- Brand tone: [friendly, firm, consultative, premium, concise]
- Constraints: [no discounts, one extension max, manager approval required, billing rules]

Produce:
1. **Decision tree** for approve, conditional approve, decline, or route to sales/customer success
2. **Customer-facing response templates** for each decision path
3. **Internal note template** documenting reason, usage, risk, and next step
4. **Follow-up sequence** after extension approval to improve activation before the new deadline
5. **Abuse-prevention guidelines** that still feel customer-friendly
6. **Success handoff summary** for promising accounts that need guided onboarding
7. **Metrics to track**: extension approval rate, activation, conversion, churn risk, support volume

Keep responses empathetic, clear, and aligned with policy. Do not overpromise exceptions.

Example Output

Decision Tree

**Approve:** Customer had a verified technical blocker or invited teammates but could not complete setup.

**Conditional approve:** Customer has low usage but a clear evaluation plan. Offer 7 days plus onboarding checklist.

**Decline:** Multiple prior extensions or no fit/use case after qualification.

**Route to CS/Sales:** Enterprise evaluation, procurement delay, or high expansion potential.

Approved Response

Hi Sam,

Thanks for explaining the delay. I’ve extended your trial by 7 days so your team has time to complete the reporting setup.

To make the extra week useful, I’d suggest these three steps:

1. Invite your finance lead

2. Connect the Stripe integration

3. Run the sample MRR report

If you hit a blocker, reply here and we’ll help.

Internal Note

Extension approved: 7 days. Reason: integration issue. Usage: 3 logins, Stripe connected, 2 seats invited. Next step: send onboarding checklist.

Tips for Best Results

  • 💡Include usage signals so the prompt can distinguish serious evaluators from low-intent extension requests.
  • 💡Paste your real trial policy to avoid generating promises your team cannot honor.
  • 💡Ask for shorter macros if your support team works mostly in chat.
  • 💡Use the follow-up sequence to make extensions drive activation, not just delay decisions.

Frequently Asked Questions

What is the SaaS Trial Extension Request Response Builder prompt?

Write policy-safe SaaS trial extension responses with decision rules, customer context checks, and sales or success handoff notes. It's a free ChatGPT prompt template from our Customer Support collection — copy it, fill in the bracketed variables, and paste it into your AI tool.

Which AI tools work with this prompt?

It's written and tested for ChatGPT, Claude and Gemini. Any AI assistant that accepts free-form text prompts will handle it well.

How do I customize this ChatGPT prompt?

Replace the bracketed variables — such as [product name] — with your own details before running it. Include usage signals so the prompt can distinguish serious evaluators from low-intent extension requests.

Is this prompt free to use?

Yes. Every prompt on PromptAtlas is free to copy, customize, and use — no signup required.