The quality of what Alex AI generates depends entirely on what you provide. Think of Alex as a highly skilled colleague who knows the mechanics of journey mapping but needs you to provide the "story." Vague prompts produce generic journeys; specific, detailed prompts produce robust, actionable maps.
1. The Power of the Prompt + Document Combo
When you start a project in Alex AI, you aren't just limited to a text box. You can attach documents (PDFs, Word docs, etc.) to give Alex deeper context.
The Prompt is the Journey’s Map: Use the prompt to describe the "narrative"—the scope, the location, and the specific stages you have in mind.
Documents are the Journey’s Fuel: Use attachments to provide the data that enriches the map.
💡Avoid saying, "Create a journey with the information in the file." This forces Alex to guess the structure. Instead, describe the phases in the prompt and let the documents fill in the granular details.
💡Avoid adding PowerPoints with large images and little text. Alex thrives on descriptive, text-heavy documents that provide actual journey content.
2. Guide the Structure with Lanes and Templates
Alex AI is designed to be flexible, but he works best when he knows your "guardrails."
If you tell Alex you want lanes for Touchpoints, Pain Points, Gains, and Opportunities, he will prioritize those. Alex is proactive. If he detects extra information in your attached files—like "Regulatory Requirements" or "System Actions"—he will automatically add those lanes to ensure no data is lost.
👉 If you have a specific structure you must follow, use a template. When a template is active, Alex embeds the detected content directly into that predefined structure, keeping your map consistent with your organization's standards.
The 6 Core Practices
Be specific. Vague prompts produce generic output. Name the persona, the channel, the touchpoints, every detail you add sharpens the result.
Use plain language. Write how you'd explain the scenario to a colleague. Simple, direct sentences work better than formal or technical phrasing.
Name the journey type. Tell Alex whether you want a master journey, a stage journey, or a specific touchpoint map. This changes how the output is structured.
Set the context. Include persona characteristics, industry, brand, business line, and channel. Alex uses this to generate relevant, contextualized outputs.
Give examples. If you have a preferred structure or tone in mind, describe it or point to an existing journey as a reference.
Test and refine. Your first prompt is a draft. Run it, review the output, adjust the wording, and run again. Iteration is normal.
Master Journey vs. Stage Journey
Master Journey - covers the full end-to-end experience across all stages. Use this for a high-level overview from first touch to resolution.
Stage Journey - zooms in on a specific stage. Use this when you want detailed steps, emotions, and touchpoints for a single part of the experience, such as onboarding or renewal.
👉 Practical rule: if your prompt covers more than two or three stages, you likely need a master journey. If you are focused on one moment, go with a stage journey.
Context of a Good Prompt
Every good prompt answers four questions:
Who — the persona, their role, background, and relevant characteristics. Example: "a first-time SME owner with no prior insurance experience."
What — the action or process they are going through. Example: "applying for business insurance through a web form."
Context — channel, brand, business line, location, or any constraints. Example: "via the insurer's public website, South Africa, omnichannel."
Goal — what you want Alex to produce. Example: "create a master journey map" or "map a stage journey for the broker consultation phase."
Sample Prompts
Journey maps
Weak prompt (avoid this): "Create a journey map for a customer getting business insurance."
What goes wrong: no persona, no channel, no entry point, no outcome. Alex will generate something generic that fits no real scenario.
Strong prompt — web form scenario: "Create a master journey map for an SME business owner seeking Business Insurance in South Africa. The journey starts when the customer visits the insurer's website and selects the Business Insurance quote option. The customer fills in a contact form including name, surname, contact number, email, ID number, business type, annual turnover, number of employees, current premium, and required cover options. Based on their profile, the customer is funneled either to a general Business Insurance call center or to a specialized internal brokerage. If funneled to the call center, the agent qualifies the lead before deciding to quote or transfer. Once in the brokerage, a lead agent confirms details and schedules a face-to-face appointment with a broker. After the meeting, the broker sets a follow-up session to present the quote. The journey ends with the customer accepting or rejecting the quote."
Why it works: names the persona, the channel, the touchpoints, the branching logic, and the journey endpoint.
Strong prompt — outbound call scenario: "Map a customer journey for a business owner who is contacted by the insurer's Business Insurance contact center based on a lead referral. The contact center agent calls the customer and asks qualifying questions. Based on the customer's needs, the agent recommends an in-person consultation with a broker. The customer may prefer to complete the process by phone — in that case, the consultant proceeds with a telephonic quote. If the customer agrees to a broker meeting, the consultant sets expectations on timing. The broker then calls the customer, confirms their details, and schedules a face-to-face appointment. A follow-up meeting is set to present the final quote. End the journey at the accept or reject decision."
Why it works: specifies the entry channel, names both decision paths, and defines the exact endpoint.
Personas
Weak prompt (avoid this): "Create a persona for a business insurance customer."
What goes wrong: no demographics, no pain points, no goals. The output will be a generic placeholder that won't reflect a real segment.
Strong prompt: "Create a persona for an SME owner aged 35–50, running a business with 10–50 employees and an annual turnover between R2M and R20M. The persona is seeking business insurance for the first time and is unfamiliar with insurance terminology. They value speed, clear pricing, and personal guidance. They are risk-aware but time-poor. Include their goals, pain points, preferred channels, and typical objections during the insurance quoting process."
Why it works: gives demographics, business profile, behavioral context, and explicitly requests the output structure.
Stage journeys
Strong prompt: "Create a stage journey map for the broker consultation phase of a Business Insurance master journey. The stage starts when the broker calls the customer to confirm details and schedule a face-to-face meeting. It includes the initial meeting where the customer shares their business needs and the broker gathers information, followed by the broker setting a follow-up appointment. The stage ends when the broker presents the final quote and the customer makes an accept or reject decision. Map the customer's emotions, key touchpoints, and potential friction points at each step."
Why it works: clearly scopes the stage with a defined start and end, names the actions, and requests specific outputs.
Omnichannel journeys
Strong prompt: "Create an omnichannel master journey map for an existing business insurance customer who previously declined a quote. The insurer re-engages the customer via an outbound call. The journey covers the outbound call and re-engagement conversation, the customer's decision to proceed telephonically or via broker, the broker consultation path, including call, face-to-face meeting, and follow-up, and the final quote decision. The channels involved are outbound phone, in-person broker meeting, and email confirmation. Map the customer's experience across all three channels."
Why it works: names the segment, lists all channels, maps the branching paths, and specifies omnichannel as the lens.
Quick checklist before you prompt
Have you named who the customer is — their role, profile, or segment?
Have you specified where the journey starts and where it ends?
Have you listed the key touchpoints, channels, or steps in between?
Have you told Alex whether this is a master journey or a stage journey?
Have you mentioned the business line, brand, or market context?
Have you specified what you want in the output — emotions, friction points, touchpoints?
What makes these prompts work
They name the customer type and their situation upfront
They specify where the journey begins
They describe the path, not just the destination
They include decision points where relevant
They end at a clear resolution
Before submitting, ask yourself: if someone who knows nothing about this customer read your prompt, would they understand exactly what journey you are trying to map? If not, add the missing detail.
👉 Learn more about creating Journey Maps with Alex AI in Cemantica