slice icon Context Slice

Internal FAQ Template

# [Feature/Launch] FAQ

**For:** Sales and Support Teams
**Launch Date:** [Date]
**Last Updated:** [Date]

## Overview

### What is [Feature]?
[2-3 sentence explanation in plain language]

### Why are we launching this?
[Business rationale and customer need]

### When is it available?
[Date and rollout plan—all customers, beta, specific tiers]

## For Sales

### Who should I pitch this to?
[Target persona and use cases]

### What's the elevator pitch?
[30-second version they can use in calls]

### What problem does this solve?
[Customer pain point in their words]

### How is this different from [Competitor]?
[Differentiation points]

### What if they ask about [Common Objection]?
[Talk track for handling]

### Is there additional cost?
[Pricing impact if any]

## For Support

### How does a customer enable/access this?
[Step-by-step instructions]

### What are the known limitations?
- [Limitation 1]
- [Limitation 2]

### What are common issues and how do I troubleshoot?

**Issue:** [Description]
**Solution:** [Steps to resolve]

**Issue:** [Description]
**Solution:** [Steps to resolve]

### When should I escalate?
[Criteria for escalation and where to send]

## Resources

- [Link to help article]
- [Link to demo video]
- [Link to internal training]

Value Proposition Template

Generate value propositions for different audiences and contexts:

One-Liner (Tagline)

Formula: [Action verb] + [outcome] + [differentiator or qualifier]

Examples:

  • "Ship features faster with AI-powered code review"
  • "Turn customer feedback into product roadmap in minutes"
  • "The analytics platform that actually gets used"

Elevator Pitch (30 seconds)

Formula: [Problem] → [Solution] → [Differentiator] → [Proof point]

Template:

[Target user] struggle with [problem]. [Product] helps them [solution] by [how it works]. Unlike [alternative], we [key differentiator]. [Proof point: customers/metrics/awards].

Value Proposition by Audience

For End Users:
Focus on personal benefit and ease of use.

"[Product] lets you [action] without [pain point]. Just [simple action] and [outcome]."

For Decision Makers:
Focus on business outcomes and ROI.

"[Product] helps teams [business outcome] while reducing [cost/risk]. Companies like [customer] have seen [metric]."

For Technical Buyers:
Focus on capabilities and integration.

"[Product] provides [capability] with [technical differentiator]. It integrates with [tools] and supports [standards]."

Required Inputs

For FAQ

  1. Feature/launch name — What are we documenting?
  2. Target audience — Sales? Support? Both?
  3. Launch details — Date, rollout plan, pricing
  4. Known limitations — What can't it do?
  5. Anticipated questions — What will people ask?

For Value Props

  1. Product/feature — What are we positioning?
  2. Target audiences — Who needs to hear this?
  3. Key differentiators — What makes us different?
  4. Proof points — Customers, metrics, awards
  5. Competitive context — Who are we compared against?

Writing Tips

FAQs

  • Anticipate, don't just react — Include questions they'll ask before they ask
  • Use their language — "What if the customer asks..." not "Objection handling for..."
  • Be honest about limitations — Internal teams need the full picture
  • Make it scannable — Bold key terms, use bullet points

Value Props

  • Be specific — "Save 5 hours per week" beats "Save time"
  • Lead with benefit — What they get, then how it works
  • Test with real people — Does it resonate? Do they understand?
  • Vary by audience — Same product, different angles