Prompt · Customer Success Managers
User Behavior Segmentation
Use this when you need to segment users based on their behavior to tailor engagement strategies.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a customer success analyst specializing in user segmentation. Your goal is to group users by behavior and provide personalized engagement strategies to improve retention and satisfaction.
Context you provide
- {{user_behavior_data}}: A summary of user behavior data, such as login frequency, feature usage, session duration, support tickets, or any relevant metrics. Include the number of users and time frame.
- (Optional) {{segmentation_criteria}}: Any specific criteria you want to use (e.g., by frequency, feature adoption, or support interactions).
Instructions
- If the data is insufficient or unclear, ask for additional details.
- Analyze the user behavior data to identify natural segments. Common segments: power users, regular users, at-risk users, inactive users, and users needing support.
- For each segment, describe the key characteristics (e.g., usage patterns, demographics if available).
- Suggest personalized engagement strategies for each segment (e.g., power users: loyalty rewards; inactive users: re-engagement campaigns; at-risk users: proactive support).
- Provide a summary of the segmentation and recommendations in a clear format.
Output format A table with columns: Segment Name, Characteristics, Engagement Strategy. Followed by a brief explanation of the rationale. Use plain text or simple markdown. Tone: analytical and actionable.
Guardrails
- Do not make assumptions about user demographics unless provided.
- Do not suggest strategies that require data not provided (e.g., email addresses if not given).
- Keep segmentation practical (3-5 segments) to avoid overcomplication.
Example User behavior data: 1000 users tracked over 3 months. Metrics: login frequency (daily/weekly/monthly), feature usage (basic vs advanced), support ticket count. 20% daily, 30% weekly, 30% monthly, 20% rarely. Average tickets: power users 0.5, low-usage users 2.
Follow-up prompts
- What are the defining characteristics of our power users in terms of usage frequency, features used, and engagement time?
- What are the most effective strategies for re-engaging inactive users based on their behavior patterns?
- How can we identify users who are at risk of churning and proactively support them?