---
name: selge-new-survey
description: Interviews the user about their goal, recommends the best expert template, fills in targeting, and creates a survey as a draft. Use when the user wants to create, build, or set up a new survey - whether they know what to ask or just have a problem they're trying to solve.
---

# Create a Selge survey

You help the user create a new on-site survey by interviewing them about their goal, picking the right expert template, and landing the survey as a draft in their dashboard. Surveys always come out as drafts - the user activates them from the dashboard once they've reviewed.

## Core principle: pick a template, don't write from scratch

Selge has 13 expert templates. They're battle-tested and outperform custom questions in almost every case. Only write custom questions if the user explicitly insists on it, or if no template fits.

## Workflow

### 1. Understand the goal

Ask one short question first:

> "What are you trying to learn? A few examples: why visitors aren't signing up, what's confusing on a specific page, what feature to build next, why customers churn."

Don't dump the full template list yet. Let them say it in their own words.

### 2. Pick the template

Use the MCP prompt `pick-template` with the goal description, OR call `list_templates` and reason about which fits best. A good fit beats a perfect goal description.

Show the user one recommended template plus one alternative. Don't list all 13.

Example:
> Based on your goal, I'd recommend the **why-didnt-you-sign-up** template. It's designed for exit-intent on pricing or signup pages and tends to surface the top 3 objections fast.
>
> Alternative: **pricing-page-clarity-check** if you specifically want to test whether the pricing page itself is the problem.
>
> Want me to go with the first one?

### 3. Pick the project

If the user has multiple projects, ask which domain this survey is for. Use `list_projects` to show options. If they have one project, skip this step.

### 4. Targeting

Ask two short questions:

1. **Where on the site?** (e.g. `/pricing`, all pages, only `/blog/*`)
2. **When should it appear?** Default suggestion: exit intent on the targeted pages. Other options: time delay (15-30s), scroll depth (50%), immediate.

Don't over-explain. The defaults are good - "exit intent on /pricing" is a complete answer.

### 5. Adapt the wording (optional)

If the user mentioned an ICP, product, or company name in step 1, lightly tailor the template's wording to match. Don't rewrite questions wholesale - the template's structure is what makes it work. Only adjust references to product names, audience labels, or pricing tiers.

### 6. Create the survey

1. Call `create_survey` with the chosen template slug and the user's project (if multiple).
2. Call `update_targeting` with the page rules and trigger from step 4.
3. If the user wanted custom wording from step 5, call `update_survey` with the adjusted questions.

### 7. Confirm and hand off

Output:

```
Survey created as draft: <name>
Template: <slug>
Where: <page rules>
When: <trigger>

Preview: <preview_url>

The survey is a draft. Activate it from the dashboard when you're ready - that way nothing goes live by accident.
```

Suggest `selge-review-results` once they have data flowing.

## Don'ts

- Don't activate the survey. Drafts only. The user activates from the dashboard.
- Don't write custom questions unless the user explicitly asks for them.
- Don't ask for widget style or colors - the project's defaults apply.
- Don't ask the user about more than two things at once.