CiteLoop logo

CiteLoop

Feature

Participant matching by relevance

Participant matching connects a POV to the people most likely to contribute useful responses, using reusable profiles instead of ad hoc contact lists.

Book product demoSee comparison

Features/Participant matching by relevance

What it is

Each participant in CiteLoop is a profile with contact details, language preference, tags, interests, expertise, and workflow state. When you prepare outreach from the POV panel, you target recipients through send lists or individual selection. Matching uses that profile data so each POV reaches relevant voices.

  • Participant profiles persist across stories and campaigns
  • Tags, interests, and expertise fields support filtering
  • Send lists group participants for repeat outreach
  • Individual selection for one-off or mixed recipient sets

Who uses it

Newsroom desks use matching to reach experts, citizens, and underused sources per POV. Community teams use it to target audience segments without rebuilding lists for every callout.

  • Newsroom: reduce repeated-source drift by targeting per angle
  • Community: route callouts to the right segment profiles
  • Both: reuse participant context instead of spreadsheet contact hunting

What you control

Matching happens at send time in the POV panel. You choose lists or individuals, and the UI surfaces language and channel constraints before messages go out.

  • Which send lists are included for a send
  • Which individual participants are added
  • Language priority relative to story and template languages
  • Per-send channel rules (email, SMS, Slack) and preferred platforms

How it differs from a contact spreadsheet

A spreadsheet stores names. CiteLoop stores operational context: approval state, language, platform preference, and linkage to POVs and stories. The same profile can be matched again in the next cycle without re-entering data.

  • Profiles stay tied to outreach history and reply intake
  • Send lists reflect language composition with mismatch warnings in the panel
  • Approved, pending, and rejected states apply to intake workflows
  • Section scoping limits which participants appear for a desk or team

Workflow steps

What happens from link creation to a reply in the inbox.

  1. Step 1

    Build or maintain participant profiles

    Operators add contributors with tags, interests, and expertise. Profiles can come from direct entry, imports, or approved open invitation registrations.

  2. Step 2

    Group participants into send lists

    Send lists bundle participants for recurring outreach. Lists show participant counts and language hints when selected in the POV panel.

  3. Step 3

    Select recipients for a POV send

    In the POV panel, choose send lists and/or individual participants before previewing or sending messages for the active question set.

  4. Step 4

    Review language and channel fit

    The panel warns when list languages do not align with story or template languages, and when a participant's preferred platform cannot be used for the send.

  5. Step 5

    Send and reuse profiles on the next POV

    After replies arrive, the same profiles remain available for the next story angle or campaign cycle without rebuilding contact context from scratch.

Product screenshots

Match POVs to relevant participants.

Audience operations with editorial structure.

Common questions

Does CiteLoop automatically verify someone is an expert?

No. Matching uses profile fields such as tags, interests, and expertise that your team maintains. The product helps you target relevant profiles; it does not independently verify credentials unless your workflow defines that separately.

Can one participant receive outreach for multiple POVs?

Yes. Profiles are reusable. Send composition is per POV and per send action, so operators still control when and how someone is contacted.

What are send lists used for?

Send lists are saved participant groups for repeat outreach. They appear in the POV panel with counts and language metadata so desks can select them quickly.

How does section scoping affect matching?

When section filtering is active, stories, send lists, and related records can be limited to the operator's current section. That keeps participant pools scoped in multi-team deployments.

What happens if a participant cannot be reached on their preferred channel?

Bulk send preview and send results report skipped recipients when platform or channel rules block delivery. Operators see what was queued versus skipped before assuming outreach completed.

Related terms

Definitions used on this page.

POV (Point of View)

A specific angle inside one story or campaign, with its own question set, audience, and outreach message.

Read in glossary

Story

The higher-level container that groups one or more POVs around a shared editorial or campaign objective.

Read in glossary

Participant

A contributor profile that can represent an expert, citizen, audience member, or campaign respondent.

Read in glossary

See this workflow on your desk or campaign

We can walk through setup, approval, and reply handling using your story format.

Book product demoSee comparison
Email usBook demo