Alchemer Iris: Boost Advocacy 5% by 2026

Transforming raw customer feedback into actionable insights that cultivate loyalty and drive growth is a primary challenge for modern marketing teams. With Alchemer Iris, organizations gain a powerful analytical layer to decipher customer sentiment, moving beyond simple data collection to strategic implementation. This tutorial details how to configure Alchemer Iris to convert customer feedback into brand advocacy, a process that can increase customer retention by up to 5% according to a 2025 Nielsen report on CX ROI.

Step 1: Initial Setup and Data Integration in Alchemer Iris

The foundation of effective customer feedback analysis rests on precise data integration. Without a unified view of customer interactions, any subsequent analysis will be fragmented. This initial step focuses on connecting your customer data sources to Alchemer Iris, ensuring all relevant information flows into the system for complete analysis.

1.1 Connecting Your Survey Platforms

First, log into your Alchemer Iris account. On the main dashboard, navigate to the left-hand menu and click on “Data Sources.” You’ll see a list of pre-built connectors. For most organizations, this means linking your primary survey tool. If you use Alchemer Surveys, the integration is native. Simply select “Alchemer Surveys” and authenticate your account. For other platforms, such as Qualtrics or SurveyMonkey, click “Add New Integration,” choose your platform from the dropdown, and follow the on-screen prompts to input your API key and secret. This usually involves generating these credentials within your survey platform’s administrative settings.

A common mistake here is not granting sufficient permissions during the API key setup. Always ensure Iris has read access to all relevant survey responses, including open-ended text fields. Without these, the sentiment analysis capabilities will be severely limited.

1.2 Importing CRM and Support Data

Beyond surveys, integrating data from your CRM (Customer Relationship Management) and customer support systems provides important context. This data often contains interaction history, purchase records, and support tickets, which enrich feedback analysis. In the “Data Sources” menu, select “CRM Integrations.” You’ll find direct connectors for platforms like Salesforce, HubSpot, and Zendesk. Click on the relevant icon, then “Connect Account,” and authorize the connection using your CRM administrator credentials. For custom or less common systems, select “API & Webhooks” and consult your development team to configure data pushes to the provided Iris API endpoint. I’ve found that integrating historical support ticket data for the past 12 months offers a solid baseline for understanding recurring customer pain points.

1.3 Configuring Data Mapping and Field Selection

Once connected, Iris requires you to map the incoming data fields to its internal structure. This ensures consistency and proper analysis. Go to “Data Sources” and click on the newly connected source. Select “Field Mapping.” Here, you’ll see a list of fields detected from your source on the left and Iris’s standard fields on the right. Drag and drop to match fields like “Customer ID,” “Survey Response Text,” “NPS Score,” “Purchase Date,” and “Support Ticket Subject.” For open-ended text, ensure it’s mapped to a field designated for “Customer Comments” or “Feedback Text.” It’s essential to map customer identifiers accurately. This allows Iris to create a unified customer profile, linking survey responses to their historical interactions and purchase behavior.

Step 2: Configuring Sentiment and Topic Analysis Models

The core of Iris’s power lies in its ability to understand the nuances of human language. This step involves fine-tuning the AI models to accurately interpret customer sentiment and identify prevalent topics within your feedback, moving beyond keyword matching to true understanding.

2.1 Customizing Sentiment Analysis Models

Navigate to “AI Settings” from the main menu, then select “Sentiment Analysis.” Iris provides a default sentiment model, which is a good starting point, but customization is key for industry-specific language. Click “Create New Model” or “Edit Default Model.” Here, you can upload a CSV file containing examples of your company’s specific positive, negative, and neutral phrases. For example, if “The app crashed” is a common negative comment, you’d list it under “Negative.” If “Fast delivery” is consistently positive, classify it as such. Aim for at least 50 examples per sentiment category to achieve meaningful accuracy. The model will retrain and provide an accuracy score. Strive for 85% or higher. I typically spend a few hours refining these models, especially for nuanced feedback where terms might be ambiguous without context.

2.2 Defining Custom Topic Categories

Beyond sentiment, understanding what customers are talking about is critical. In “AI Settings,” click “Topic Analysis.” Iris offers pre-built topics like “Product Features,” “Customer Service,” and “Pricing,” but you’ll likely need to create custom categories relevant to your business. Click “Add New Topic Category.” For a software company, this might include “User Interface,” “Bug Reports,” or “Integration Capabilities.” For each custom topic, provide a list of keywords and phrases that typically appear when customers discuss that subject. For instance, under “User Interface,” you might list “UX,” “layout,” “navigation,” “design,” or “ease of use.” Iris uses these seed terms to identify broader patterns in your feedback. After defining your categories, click “Train Model.”

It’s important to review the model’s performance regularly. I recommend checking the “Topic Distribution” report weekly to see if any significant feedback volume falls into an “Uncategorized” topic. This indicates a gap in your defined categories or keywords.

2.3 Setting Up Intent Recognition (Optional but Recommended)

For advanced users, Iris’s intent recognition can differentiate between a customer merely stating a fact and expressing an intent, such as “I want a refund” versus “My product broke.” Under “AI Settings,” select “Intent Recognition.” Click “Add New Intent.” Define intents like “Cancellation Request,” “Feature Suggestion,” or “Complaint.” Similar to sentiment analysis, you’ll provide example phrases for each intent. For “Feature Suggestion,” examples might be “It would be great if…” or “Consider adding a…” This capability is particularly useful for routing feedback to the correct internal teams automatically, which we’ll cover next.

Step 3: Building Automated Feedback Loops and Alerts

Collecting and analyzing feedback is only half the battle. The real value comes from acting on it. This step outlines how to configure automated workflows within Iris to ensure critical feedback triggers immediate action and positive feedback is leveraged for advocacy.

3.1 Configuring Real-time Alerts for Critical Feedback

Go to the “Notifications & Alerts” section in the main menu. Click “Create New Alert.” You’ll define the conditions that trigger an alert. For instance, to catch negative sentiment quickly, set a condition: “Sentiment Score is Negative” AND “NPS Score is less than 6.” Specify the recipients (e.g., your customer success team’s email address or a Slack channel). You can also integrate with project management tools. Select “Jira Integration” and map the alert to create a new ticket in your “Customer Issues” project, assigning it to the relevant team. This ensures that every highly dissatisfied customer receives a follow-up within 24 hours, mitigating churn risks.

One pro tip: don’t overwhelm your team with too many alerts. Start with high-priority conditions and refine them over time. A common pitfall is creating alerts for every “neutral” sentiment, which can lead to alert fatigue.

3.2 Automating Follow-ups for Positive Feedback

Positive feedback is a goldmine for brand advocacy. In “Notifications & Alerts,” create another alert. Set the condition: “Sentiment Score is Positive” AND “NPS Score is 9 or 10.” For the action, choose “Trigger Webhook.” Configure this webhook to send data to your marketing automation platform (e.g., Mailchimp, HubSpot Marketing Hub). The payload should include the customer’s email and their positive comment. Your marketing automation system can then send a personalized email, thanking them for their feedback and gently inviting them to leave a review on a third-party site or share their experience on social media. This turns satisfied customers into active promoters, a strategy that HubSpot’s 2025 marketing report shows can increase referral rates by 15%.

3.3 Integrating with CRM for Closed-Loop Feedback

To truly close the loop, feedback needs to be visible within your CRM. In the “Integrations” section, ensure your CRM (e.g., Salesforce Service Cloud) is connected. Then, navigate to “Workflow Automation.” Click “Add New Workflow.” Set a trigger: “New Feedback Received” AND “Topic Category is ‘Bug Report’.” For the action, choose “Create CRM Activity.” Map the feedback details (customer name, comment, sentiment) to a new “Task” or “Case” within Salesforce, associating it with the customer’s existing record. This allows your sales and support teams to see the full history of customer interactions and feedback directly in their workflow, preventing customers from having to repeat themselves.

Step 4: Using Insights for Brand Advocacy

With feedback flowing and analyses running, the final step is to translate these insights into tangible strategies that foster brand advocates. This involves identifying key trends, sharing positive stories, and addressing systemic issues.

4.1 Generating Advocacy Reports and Dashboards

From the main menu, select “Reporting & Dashboards.” Click “Create New Dashboard.” Focus on metrics that directly relate to advocacy. Add widgets for “NPS Trend Over Time,” “Sentiment Distribution by Topic,” and “Top Positive Keywords.” You can also add a “Customer Churn Prediction” widget if you’ve configured that advanced model in Iris. These dashboards provide a quick, visual overview for marketing and executive teams. I often create a dedicated “Advocacy Dashboard” that highlights customers who have given repeat positive feedback or have been identified as high NPS promoters. This makes it easier to identify potential brand ambassadors.

4.2 Identifying and Engaging Brand Advocates

Within the “Customer Profiles” section, use the filtering options. Filter by “NPS Score = 10” and “Sentiment Score = Positive (last 90 days).” This will give you a list of your most satisfied customers. Iris allows you to export this list. Use this data to initiate personalized outreach campaigns. This could be a direct email from a senior executive, a special invitation to an exclusive beta program, or a gift. The goal is to deepen their connection with your brand and encourage them to share their positive experiences. A personal touch goes a long way in converting a satisfied customer into an enthusiastic advocate.

4.3 Addressing Systemic Issues Identified in Feedback

Advocacy isn’t just about celebrating wins. It’s also about proactively eliminating detractors. In the “Topic Analysis Report,” look for recurring negative topics. For example, if “Shipping Delays” consistently appears with negative sentiment, this indicates a systemic operational issue. Use the drill-down feature to view specific comments related to this topic. Share these insights with your operations or logistics team. By resolving these core issues, you not only prevent future negative feedback but also demonstrate to customers that their voices are heard and valued, which builds long-term trust. Remember, every resolved issue can turn a frustrated customer into a loyal one, and sometimes even an advocate.

The journey from raw customer feedback to a strong network of brand advocates is a continuous process, not a one-time setup. Regularly reviewing your Alchemer Iris configurations, refining your AI models, and consistently acting on the insights generated ensures that your customer experience efforts translate directly into measurable business growth and enduring loyalty.