Research Agent in Communities

The Research Agent is a conversational panel beside your community that helps you complete everyday panel management tasks. Ask in plain English to check panel health, find members, build audiences, send surveys, track responses, follow up with non-responders, and review pending rewards.

Use it as a working assistant: review the community, identify what needs attention, and prepare your next action. The agent never sends messages or makes changes without you clicking Approve.

1. Open the Research Agent from any Communities screen.
2. Tell it which community to work in. For example: Open Shopper Insight.
3. Check the panel header to confirm the community and current page. For example: Now in: Members.
4. Ask What can you help me with? to see the tasks available on that page.
5. Describe the task you want to complete. Review the answer or proposed action before proceeding.

The agent works inside one community at a time. Its available tasks depend on the current page. If you ask about survey sends while on Members, it may direct you to the Send tab. You can change pages during the conversation; the agent picks up from your current page.

Start your weekly review with a health check. Ask the agent to explain the findings and their impact, so you can decide what to address first.

Example: Run a health check on Shopper Insight. Review member statuses, signup sources, recent sends, and pending rewards. Tell me what needs attention first and why. Do not make changes.

For a focused review, ask:

• How many members are verified, bounced, inactive, and unsubscribed?
• How many members can actually receive a survey right now?
• Check my latest send and explain any delivery or completion issues.
• What rewards are pending approval?

Expand What I checked to see which reports the agent read. If part of the review could not be checked, ask it to retry before relying on that finding.

1. Go to the Members page and provide the member's email address.
2. Ask to view their profile, status, or points balance.
3. If a change is needed, describe the specific action and member.
4. Review the approval card to confirm the correct member and action, then click Approve.

Example: Find the member with email [member email]. Show their profile, current status, and points balance.

Example: Unsubscribe the member with email [member email].

Ask the agent to list the profile fields in your community, including each field's type and whether it is required. You can also ask for the answer options for a specific field.

Example: List all profile fields with their types and required status. Show the answer options for Department.

To create a field, describe its name, type, required status, and answer options where applicable. The agent will ask for missing details and prepare an approval card.

Example: Create an optional single-select profile field named Shopping Frequency with options Weekly, Monthly, and Less often.

Review the proposed field before clicking Approve.

Describe the profile answers that define your audience. Use clear field names and specify whether members must match all conditions or any condition.

Example: How many members have Department 1 and State 2? Members must match both conditions. Show their names.

Before sending, ask the agent to preview the reachable recipients. A matching member count may be larger than the number eligible to receive a survey.

1. Go to the Send tab.
2. Provide the survey name or keyword, saved audience filter, invitation template, and completion points.
3. Resolve any questions about matching surveys, templates, or missing details.
4. Review the recipient preview and approval card. Confirm the survey, audience, recipient count, template, and completion points.
5. Click Approve to send, Request changes to revise the proposal, or Discard to cancel it.
6. Review the result to confirm whether the send completed or failed.

Example: Prepare a send for the CSAT survey using the saved filter Verified Members and the default invitation template, with 10 points on completion. Preview the recipients before asking for approval.

1. Ask the agent to check the latest send or identify a specific send.
2. Review delivery, opens, bounces, and completions. Ask which email domains are bouncing if delivery needs investigation.
3. Ask whether a reminder is appropriate for the send.
4. Ask the agent to prepare a reminder for non-responders and preview the recipients.
5. Check the original send and proposed reminder audience, then click Approve when ready.

Example: Check my latest CSAT send. Show delivery, opens, bounces, and completions. Should I remind the non-responders now?

Example: Prepare a reminder for non-responders to that send. Show who it will reach before asking for approval.

Ask the agent to show the pending approval queue and check reward stock and eligibility. Review these details before deciding which redemptions to approve or reject.

Example: Show pending reward redemptions and check stock and eligibility. Do not approve or reject anything yet.

Once you have reviewed the queue, specify the redemption and decision. The agent prepares an approval card and waits for you to click Approve before applying the decision.

Every action that changes something requires you to click Approve. This includes sends, reminders, member status changes, unsubscribes, reward decisions, and any supported creation or deletion action.

The approval card describes what will happen and whether the action can be undone. For sends, check the recipient count, survey, and template. For a deletion, review both what the agent checked and what it could not check, and inspect any unchecked dependencies yourself.

• Name the community: Confirm the agent is working in the intended community.
• State the task: Say whether you want a review, a preview, or an action prepared for approval.
• Identify the target: Provide a member email, survey keyword, saved filter name, or specific send.
• Include send details: Specify the survey, audience, invitation template, and completion points together.
• Use clear criteria: Replace phrases such as "my members" with a named saved filter or explicit profile conditions.

You do not need exact survey names; a keyword is enough to start. If several items match or details are missing, the agent asks you to clarify instead of guessing.

The following tasks are outside the current release. Complete them on the relevant Communities page.

Expand What I checked on an answer to see which reports the agent read. If it says part of this could not be checked, treat the answer as incomplete and ask it to retry.

To review the work completed during your conversation, ask What did you do for me in this session? The agent returns the actions it took.

If a report fails to load or an action does not go through, the agent reports the failure. Check the result after an approved action rather than assuming approval means it succeeded.

• Wrong community or page: Check the panel header, name the intended community, and move to the page the agent requests.
• More than one match: Give a more specific survey name, keyword, or other identifying detail.
• No saved audience filter: Create the filter in Analytics » Sampling and provide its name.
• Fewer reachable members than expected: Ask for a recipient preview and check member statuses. Only verified members receive sends.
• Incomplete report or failed action: Ask the agent to explain the failure and retry. Check whether an action completed before requesting it again.
• Unsupported task: Follow the agent's guidance to complete it on the relevant Communities page.

If the answer differs from what the platform shows, record your request, the agent's response, the community and page, and the result shown in the platform. Share these details when reporting the issue.