The Purpose field is your most powerful tool when creating Smartflows. It tells our AI system what your flow does and why users need it, directly impacting the quality of the generated content. It should be generic, encouraging, and action-oriented, resulting in a high-quality, reusable user experience for all of your customers.
.png)
What makes a great purpose statement?
A great purpose statement answers three simple questions:
What action? (creating, updating, inviting, finding)
What core feature? (project, billing settings, team member)
What goal/benefit? (get started, complete setup, customize view)
Formula for success
[Action] + [Feature] + [Goal/Benefit]
Example: "Guide users through creating their first dashboard so they can visualize their data."
Quick do's and don'ts
✅ DO | ❌ DON'T |
|---|---|
Keep it generic and reusable | Include specific names or data |
Focus on the actions users take | Describe UI elements or buttons |
Explain the outcome | Use passive labels like "This is an onboarding flow" |
Think about all users | Reference specific examples or IDs |
Common mistakes to avoid
❌ Being too specific
Wrong: "Help John Doe fix bug 404 in MyProject"
Right: "Help users create and track bug reports"
❌ Mentioning specific UI elements
Wrong: "Click the Settings gear icon, then the Integrations tab"
Right: "Guide users through account configuration and integration setup"
❌ Using specific IDs
Wrong: "Find ticket AB-893 in JIRA-123"
Right: "Help users locate their account-specific identifiers"
❌ Being passive
Wrong: "This is a feature overview"
Right: "Show users how to use the main features effectively"
Pro tips: Fine-tuning your flow
🎯 Set the right tone
Add the desired tone to your Purpose statement to influence how the AI writes:
Friendly: "...using an encouraging, friendly tone"
Professional: "...with clear, professional instructions"
Casual: "...in a relaxed, conversational style"
📏 Control flow length
Guide the complexity or simplicity of your flow:
Keep it brief: "...in under five steps"
Detailed process: "...with clear decision points at each stage"
Focused journey: "...highlighting the choice between basic and advanced options"
🎉 Design the perfect ending
Specify how users should feel when done. For example:
Celebrate achievements: “…end with celebrating their successful setup.”
Success messaging: “…finish with confirmation of what they’ve accomplished and what they can do, such as, 'You're all set! Time to create!’”
Continue learning: “…conclude by encouraging them to explore the new feature.”
Examples for optimal output
Example 1: Feature onboarding
Purpose: "Guide the user with a friendly, encouraging tone through the process of creating and publishing their first report in the Analytics dashboard. The final step must celebrate their successful publication and encourage immediate review."
Why it works:
Clear action (creating and publishing)
Specific feature (Analytics dashboard reports)
Defined outcome (successful publication)
Tone guidance (friendly, encouraging)
Strong ending (celebration and next steps)
Example 2: Configuration setup
Purpose: "Walk the user through the settings configuration, ensuring the copy highlights the choice between basic and advanced options using a professional tone. The goal is to successfully configure a new integration and link the account, keeping the process to six steps or fewer.
Why it works:
Clear process (settings configuration)
Important decision point highlighted
Length constraint (six steps or fewer)
Example 3: Quick start
Purpose: "Help new users set up their profile and workspace in under four steps with concise instructions. End with 'You're ready to go!'"
Why it works:
Specific goal (profile and workspace setup)
Clear constraint (under four steps)
Style guidance (concise)
Memorable ending
Checklist before you submit
Before finalizing your purpose statement, ask yourself:
Could this work for ANY user, not just one specific person?
Did I focus on what users DO rather than what they SEE?
Is the end goal clear?
Did I avoid mentioning specific buttons, tabs, or UI elements?
Would this make sense without any specific user data?
Remember: Think actions, not instructions
Your purpose should describe the journey, not give turn-by-turn directions. Let the AI handle the specific steps—you just need to tell it where users are going and why.
Need help? Start with this template:
"Help users [action] their [feature] to [achieve goal]"
Then add any tone, length, or ending preferences to make it perfect for your use case.