> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getwhys.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Prompting tips

> How to write questions that get sharper answers.

The single biggest lever in GetWhys is how you ask. A vague question gets a vague answer. A specific question gets a specific answer with citations. These tips compress what GetWhys customers have learned about getting the most out of Chat.

## Be specific

Three flavors of specificity that consistently improve answers:

Three flavors of specificity that consistently improve answers:

* **Context.** Tell Chat why you're asking. "I'm about to launch a developer-focused observability product, and I'm trying to figure out which buyer persona pays for it" gives Chat something to reason about. "What do developers think about observability?" doesn't.

* **Format.** Tell Chat what you want the output to look like. "A bulleted list", "a table organized by company size", "a short summary followed by three sub-bullets per point". You'll spend less time reformatting if you ask up front.

* **Constraints.** Tell Chat what to ignore. If you're researching Atlassian Confluence Whiteboards, explicitly say "I'm not interested in general Confluence insights — only Whiteboards." Same for product categories with ambiguous names.

## Use the templates

The template library covers the workflows people run most often — building personas, drafting brand voice, testing positioning, planning content. Start with a template, then edit the prompt before sending. See [Templates](/features/templates).

## Ask follow-ups

Chat keeps context within a conversation. Follow-ups produce better answers than rerunning the same query with a small change. Useful follow-up patterns:

* "Can you elaborate on that?"
* "What else should I know about this?"
* "Can you break this down by company size, industry, or role?"
* "What questions am I not asking that I should be?"
* "What would a skeptic say about this?"
* "How has this changed over the past year?"

<Warning>
  If a conversation goes off track, start a fresh one. Chat will keep pulling context from prior messages even when they're misleading.
</Warning>

## Lean on Chat to comment, not just answer

Chat is good at reviewing content. Try prompts like:

> I'm attaching a draft below. Read through it and return the full draft back to me, with your commentary inline. Start each of your comments with "GetWhys Comment:" so I can see them clearly.

Or:

> Here's a persona I have. What in this persona looks out of date or incorrect based on what you're seeing in recent interviews? List the out-of-date points first with proof for each.

This is often more useful than asking Chat to write something from scratch.

## Prompt examples that consistently work well

<Tabs>
  <Tab title="Content creation">
    > I'm writing a blog post about \[topic] for \[target audience]. What are the biggest pain points and misconceptions this audience has about \[topic]? Format as a bulleted list with specific quotes where possible.

    > What questions do \[job title] at \[company size] companies ask most frequently when evaluating \[product category]? I want to create FAQ content that addresses real concerns.

    > I'm planning a webinar for \[audience]. Based on what you know about their challenges with \[topic], what would be the most compelling title and 3 key takeaways that would get them to register?
  </Tab>

  <Tab title="Competitive research">
    > When \[target audience] evaluates \[competitor name] vs other solutions in \[category], what do they say are the main pros and cons? I'm trying to understand our competitive positioning.

    > What feature gaps or complaints do customers mention most about \[competitor]? I work for \[your company] and want to understand opportunities in the market.
  </Tab>

  <Tab title="Messaging and positioning">
    > I'm revising our homepage messaging. Our product is \[brief description] for \[target audience]. Based on what this audience cares about most, what should be our primary value prop and what proof points would be most compelling?

    > We're launching \[new feature]. What language and benefits would resonate most with \[target persona] when announcing this? What objections should we proactively address?
  </Tab>

  <Tab title="Sales enablement">
    > What are the most common objections \[target audience] raises when considering \[product category], and what responses or evidence do they find most convincing?

    > When \[job title] at \[company type] companies are building the business case for \[product category], what ROI metrics and benefits do they focus on most?
  </Tab>
</Tabs>