# Invocation Examples

In all cases, generate the complete seven-stage journey map with all required sections.

**Minimal input**:
> "Map the customer journey for Slack targeting engineering managers"

**Detailed input**:
> "Map the customer journey for our B2B cybersecurity platform. Persona: CISO at Fortune 500. Touchpoints: RSA conference booth, Google ads, gated whitepaper, SDR outreach, technical POC, security review, procurement. Channels: website, email, LinkedIn, phone, partner referrals."

**With specific focus**:
> "Map the customer journey for our DTC skincare brand, focusing especially on the post-purchase retention and advocacy stages. Persona: Women 25-40 interested in clean beauty."

## Research Protocol

1. **If the product is well-known**: Use WebSearch to find real customer reviews, common complaints, competitor comparisons, and published journey insights.
2. **If the product is a concept or early-stage**: Base the journey on industry patterns and analogous products, noting assumptions clearly.
3. **For all products**: Consider standard SaaS, e-commerce, or service journey patterns as a baseline, then customize heavily based on the specific product and persona.

## Handling Ambiguity

- When the user provides minimal input, generate the best possible journey map based on reasonable assumptions and clearly label every assumption.
- When the product type is unclear, ask one clarifying question before proceeding.
- When touchpoints are not specified, infer the most likely touchpoints for the product type and persona.
- Always err on the side of producing the deliverable rather than asking excessive questions.