Managing Customer Communication Workflow

How to get there: This is a workflow guide. Start from All Posts in the sidebar to manage customer communication across posts.

Learn how to keep customers informed and engaged throughout the feedback lifecycle using ProductLift's email notification system, status updates, announcements, and interactive features.

What is Customer Communication in ProductLift?

Customer communication in ProductLift goes beyond simple notifications. It's a comprehensive system that keeps customers in the loop about features they care about, builds trust through transparency, and creates an engaged community around your product development process.

This guide shows you how to set up and manage all customer communication touchpoints in ProductLift, from automatic status change notifications to targeted announcements and engagement features.

The Complete Communication Journey

Status Changes → Email Notifications → Announcements → Engagement → Follow-Up

Step 1: Set Up Email Notification System

Configure Email Settings:

Before customers can receive updates, configure your email system.

  • Navigate to Settings → Email Notifications
  • Configure SMTP settings (or use ProductLift's default email service)
  • Set "From" name and email address
  • Customize email branding (logo, colors, footer)
  • Test email delivery

[Screenshot: Email settings page showing SMTP configuration, from address, branding options, and test email button]

Email Notification Types:

ProductLift sends several types of automated emails:

  1. Submission Confirmation - Customer submits feedback
  2. Moderation Result - Post approved or rejected
  3. Status Change - Feature moves through workflow (Planned, In Progress, Released)
  4. Comment Notifications - Someone comments on followed post
  5. Changelog Announcements - New release published
  6. Mention Notifications - Customer mentioned in comment (@username)

[Screenshot: Email notification settings showing toggles for each notification type with send frequency options]

Customize Email Templates:

Personalize notification emails to match your brand:

  • Navigate to Settings → Email Templates
  • Edit templates for each notification type
  • Variables available: {post_title}, {status}, {comment}, {user_name}
  • Add your tone and voice
  • Include helpful links (roadmap, changelog, support)

[Screenshot: Email template editor showing HTML/text editor with available variables sidebar and preview panel]

See Email Notifications for detailed email configuration.

Step 2: Configure Status Change Notifications

How Status Change Notifications Work:

When a post's status changes, all voters and followers automatically receive an email update.

Key Status Changes That Trigger Notifications:

  • Under Review → Planned: "We're building this!"
  • Planned → In Progress: "We've started development!"
  • In Progress → Testing: "Almost ready - now testing!"
  • Testing → Released: "We shipped it!"
  • Any Status → Won't Build: "Here's why we're not building this"

[Screenshot: Status transition diagram showing workflow from Under Review through Released with email icons at each transition]

Customize Status Change Emails:

Each status can have a custom email template:

  • Navigate to Settings → Statuses
  • Click on a status (e.g., "Planned")
  • Edit "Email Template for This Status"
  • Customize subject line and body
  • Add context specific to that status

Example "Planned" Status Email Template:

Subject: Good news! We're building {post_title}

Hi {user_name},

Great news! The feature you voted for is now on our roadmap.

**{post_title}** has moved to Planned

{admin_comment}

We'll keep you updated as we make progress. View our full roadmap to see what else we're working on.

[View Roadmap →]

Thanks for being part of our product development!

- The {company_name} Team

[Screenshot: Status-specific email template editor with subject and body fields, showing template variables]

Add Personal Comments:

When changing status, add a personal comment that appears in the email:

  • Change post status
  • Add comment: "Thanks for the suggestion! We're targeting Q3 for this feature. We'll implement the automatic switching you mentioned in the comments."
  • This comment appears in {admin_comment} variable in email
  • Makes notifications feel personal, not automated

[Screenshot: Status change modal showing status dropdown, comment field with personal message, and "Notify followers" checkbox]

See Follower Notifications for advanced email customization.

Step 3: Manage Follower Preferences

Understanding Follower System:

Customers automatically follow posts when they:

  • Submit the post themselves
  • Vote on a post
  • Comment on a post
  • Manually click "Follow" button

Per-Post Notification Preferences:

Customers can control notifications for each post individually using radio buttons:

  • All Updates - Receive all comments and status changes (default)
  • Replies Only - Only receive replies to their comments
  • None - Unfollow, no notifications

[Screenshot: Post page showing notification preference radio buttons under "Follow" section: All Updates (selected), Replies Only, None]

Simplified Follow Button:

Recent updates simplified the follow system:

  • Single "Follow" button with notification icon
  • Click to open preference dropdown
  • Select notification level
  • Preference saved automatically

[Screenshot: Follow button with dropdown menu showing three preference options with radio buttons]

Notification History:

Customers can view all notifications they've received:

  • My Profile → Notification History
  • See all past notifications for all posts
  • Click to view original post
  • Useful for finding posts they engaged with

[Screenshot: Notification history page showing chronological list of notifications with post titles, notification types, and timestamps]

See Comment Notification Emails for detailed notification preferences.

Step 4: Use Admin Notification Filters

Set Up Selective Notifications for Team:

Admins can filter which submissions trigger notifications to avoid noise.

Configure Admin Filters:

  • Navigate to Settings → Admin Notification Filter
  • Set up filters to receive notifications only for:
    • Specific categories (e.g., "Billing", "Enterprise Features")
    • Specific tags (e.g., "urgent", "security")
    • High-value customers (MRR > $5,000)
    • Specific user segments (Enterprise plan, Trial users)
    • Posts with many votes (threshold: 10+ votes)

[Screenshot: Admin notification filter settings showing category checkboxes, tag input, MRR threshold slider, and segment filters]

Team Member-Specific Filters:

Different team members can have different filters:

  • Product Manager: All feature requests, high-vote posts
  • Support Lead: Bug reports, urgent tags
  • Sales Team: Enterprise customer feedback (MRR > $10k)
  • Engineering: Technical features, integration requests

Benefits:

  • Reduce notification overload
  • Ensure right person sees right feedback
  • Respond faster to high-priority submissions
  • Scale feedback management as volume grows

See Admin Notification Filter.

Step 5: Publish Changelog Announcements

Create Changelog Entries:

When you ship features, announce them via changelog.

Create Changelog Entry:

  • Navigate to Changelog → Create Entry
  • Title: Feature name (e.g., "Dark Mode Support")
  • Description: What shipped, why it matters, how to use it
  • Release Date: Ship date
  • Category: Enhancement, Bug Fix, New Feature
  • Linked Post: Link to original feedback request

[Screenshot: Changelog entry editor showing title, rich text description, date picker, category dropdown, and linked post selector]

Publish Changelog:

  • Click "Publish"
  • Entry appears on Changelog board (yourcompany.productlift.com/changelog)
  • Optionally send announcement email to all customers

Changelog Email Options:

Choose announcement strategy:

  • No Email - Just publish to changelog board (customers visit to see updates)
  • Email Voters Only - Only notify customers who voted for linked posts
  • Email All Customers - Send changelog announcement to entire customer base

[Screenshot: Publish changelog modal with three email options as radio buttons: No email, Voters only, All customers]

Changelog Email Template:

Customize announcement email:

Subject: New Update: {release_title}

Hi there,

We just shipped a new update to {product_name}!

**{release_title}**

{release_description}

[View Full Changelog →]

This release includes features you requested. Thanks for your feedback!

- The {company_name} Team

See Changelog for detailed changelog management.

Step 6: Use Polls to Gather Quick Feedback

Create Polls on Posts:

Polls help you gather structured feedback quickly.

When to Use Polls:

  • Gauge interest in a feature variation ("Which design do you prefer?")
  • Validate assumptions ("How often would you use this?")
  • Prioritize between options ("Which integration is most important?")
  • Measure satisfaction ("Are you using the new feature?")

Create a Poll:

  • Open a post (or create new post)
  • Click "Add Poll" (admin-only feature)
  • Enter poll question
  • Add 2-6 poll options
  • Allow users to add their own options (optional)
  • Publish poll

[Screenshot: Poll creation interface showing question input, option inputs (Add option button), and "Allow users to add options" checkbox]

Poll Example:

Post Title: "Slack Integration Implementation"

Poll Question: "Which Slack notifications are most important to you?"

Options:

  • Status changes on posts I follow
  • Daily digest of new feedback
  • Mentions in comments
  • Weekly roadmap updates

Allow users to add options: Yes

[Screenshot: Published poll showing question, four options with vote counts and percentages, voter avatars, and "Add your option" button]

View Poll Results:

  • See vote count and percentage for each option
  • View voter avatars (know who voted for what)
  • Identify patterns by user segment
  • Use results to inform implementation decisions

Pin Important Polls:

  • Pin poll to top of feedback board
  • Ensures maximum visibility and participation
  • Unpin when you have enough responses

See Polls and Voting.

Step 7: Respond to Comments and Discussions

Engage in Post Comments:

Comments create dialogue and build community.

Best Practices for Comment Responses:

Acknowledge Quickly:

  • Respond to new comments within 24-48 hours
  • Even if you don't have updates, acknowledge you saw their input
  • "Thanks for the additional context! This helps us understand the use case better."

Ask Clarifying Questions:

  • Use comments to gather requirements
  • "Great idea! Quick question: would this apply to mobile app too, or just web?"
  • Customers appreciate being consulted

Provide Updates:

  • Share progress even if small
  • "We're researching this option. We'll have a decision by end of month."
  • Keeps customers engaged and informed

Set Expectations:

  • Be honest about timelines and feasibility
  • "This is a great idea but quite complex. We're considering it for our 2027 roadmap."
  • Honesty builds trust

[Screenshot: Post comments section showing admin response with team badge, addressing customer question with helpful context]

Use @Mentions:

Tag specific users in comments:

  • "@sarah Thanks for the mockup! Our designer will review this."
  • User receives mention notification email
  • Creates direct dialogue

Mark Helpful Comments:

  • Upvote particularly insightful comments
  • Highlights valuable contributions
  • Encourages quality discussion

Step 8: Bulk Status Updates with Notifications

Communicate at Scale:

When you need to update multiple posts simultaneously.

Use Cases:

  • End of quarter: Move planned features that didn't ship back to "Under Review"
  • Sprint planning: Move selected features to "In Progress"
  • Release day: Move tested features to "Released"

Bulk Status Update:

  • On Feedback Board, select multiple posts (checkboxes)
  • Click "Bulk Actions" → "Change Status"
  • Choose new status
  • Add comment (appears on all selected posts)
  • Check "Notify followers"
  • Apply

[Screenshot: Bulk actions panel showing 12 posts selected, status dropdown selecting "Released", comment field, and "Notify followers" checkbox]

Notification Sent:

All followers of all 12 posts receive status change email.

Example:

You ship 8 features in a major release:

  • Select all 8 posts
  • Change status to "Released"
  • Comment: "We just shipped our Q2 release! This feature is now live. Check out the changelog for all the details."
  • 347 total followers across 8 posts receive notification
  • Massive engagement spike

See Bulk Post Operations.

Step 9: Leverage Notification Analytics

Track Communication Effectiveness:

Measure how customers engage with your communications.

Email Metrics:

Monitor email performance:

  • Open rates for each notification type
  • Click-through rates to posts, roadmap, changelog
  • Unsubscribe rates (monitor for email fatigue)
  • Bounce rates (keep email list clean)

[Screenshot: Email analytics dashboard showing open rate (64%), click rate (23%), unsubscribe rate (0.8%) for each notification type]

Engagement Metrics:

Track post-notification engagement:

  • Comments added after status change notifications
  • Votes cast after changelog announcements
  • Profile views after release emails
  • Adoption rates for shipped features

Optimize Based on Data:

  • Low open rates? Test different subject lines
  • High unsubscribes? Reduce notification frequency
  • Low click-through? Improve email copy and CTAs
  • Low adoption? Better feature education in announcements

Step 10: Build Communication Cadence

Establish Regular Touchpoints:

Create predictable communication rhythm:

Weekly:

  • Moderate and respond to new feedback
  • Update status on active development items
  • Respond to comments

Bi-Weekly:

  • Share development progress on roadmap items
  • Sprint retrospective updates

Monthly:

  • Publish changelog for shipped features
  • Send product newsletter highlighting top feedback and roadmap
  • Review and respond to high-vote posts not yet prioritized

Quarterly:

  • Major roadmap refresh and announcement
  • Retrospective on shipped features
  • Roadmap planning transparency

[Screenshot: Content calendar showing weekly/monthly communication schedule with different notification types color-coded]

Avoid Notification Fatigue:

  • Don't over-communicate (quality over quantity)
  • Batch updates when possible (one email with 3 updates vs. 3 separate emails)
  • Respect customer preferences (honor "Replies Only" and "None" settings)
  • Provide easy unsubscribe option

Real-World Example: Customer Communication Success

Scenario: A B2B SaaS company uses ProductLift communication features to keep 2,500 customers engaged.

Month 1 - Setup:

  • Configure email templates with branding
  • Set up status-specific email messaging
  • Train team on comment response best practices
  • Create admin notification filters for team

Month 2-4 - Execution:

Feedback Collection (42 new posts):

  • Confirmation emails: 100% delivery rate
  • 24-hour moderation SLA: approval/rejection with personal notes
  • Average response time to comments: 18 hours

Roadmap Update (Q2 Planning):

  • 15 posts moved to "Planned" status
  • 687 voters received "We're building this!" emails
  • Email open rate: 68%
  • 142 customers clicked through to roadmap
  • Support tickets asking "When will you build X?" decreased 45%

Development Progress (8 features in progress):

  • Bi-weekly progress comments on all in-progress posts
  • 16 total update emails sent over 2 months
  • Average open rate: 61%
  • Customers reply with encouragement and additional context

Feature Releases (6 features shipped):

  • Bulk status update: 6 posts → "Released"
  • 423 total voters across 6 posts notified
  • Changelog published with announcement email to all 2,500 customers
  • Announcement email open rate: 54%, click rate: 31%
  • 187 customers adopted new features within first week

Community Engagement:

  • 3 polls created for implementation decisions
  • Average poll participation: 73 votes per poll
  • Comments increased 35% due to team responsiveness
  • Customers feel heard and engaged

Results:

  • Customer engagement score: +18 points
  • NPS increase: +14 points
  • Feature adoption rate: 67% within 30 days
  • Support ticket volume: -32%
  • Churn rate: -8% (customers cite "feeling heard" in exit surveys)
  • Community trust and transparency: measurably increased

Tips and Best Practices

Email Notifications:

  • Personalize subject lines with feature names customers recognize
  • Keep emails concise (1-2 paragraphs max)
  • Include clear call-to-action (View Roadmap, Try Feature, Read Changelog)
  • Test emails before sending to all customers
  • Monitor unsubscribe rates and adjust frequency

Status Updates:

  • Always add personal comment when changing status
  • Explain the "why" behind status changes
  • Be honest about delays or changes in plans
  • Update status within 24 hours of actual changes (keep it current)

Comment Responses:

  • Respond quickly (24-48 hour SLA)
  • Be genuine and conversational
  • Ask follow-up questions to deepen understanding
  • Thank customers for detailed feedback
  • Set realistic expectations

Announcements:

  • Coordinate changelog with release timing
  • Send announcement emails during business hours (better open rates)
  • Include screenshots or demo videos in changelog
  • Link to documentation for new features
  • Celebrate customer contributions

Community Building:

  • Recognize active contributors publicly
  • Feature customer quotes in announcements
  • Create polls to involve customers in decisions
  • Respond to every comment (even short acknowledgments)
  • Build relationships, not just transactions

Common Challenges and Solutions

Challenge: Email Fatigue - Too Many Notifications

  • Solution: Implement "digest" mode for weekly summaries. Let customers set notification preferences per-post.

Challenge: Low Email Open Rates

  • Solution: Test subject lines, send at optimal times (Tuesday-Thursday, 10am-2pm), personalize sender name.

Challenge: Customers Don't See Changelog

  • Solution: Send email announcements, add in-app "What's New" widget, link changelog in app navigation.

Challenge: Comment Response Workload Too High

  • Solution: Set up admin notification filters, delegate comment responses to team, create FAQ for common questions.

Challenge: Customers Unsubscribing from Notifications

  • Solution: Review notification frequency, improve email content quality, offer granular notification controls.

Challenge: Status Updates Not Reflecting Reality

  • Solution: Create process to update ProductLift as part of sprint ceremonies, assign DRI for ProductLift updates.

Use Case Workflows:

Email and Notifications:

Engagement Features:

Announcements: