Feature

Media-rich inbox triage

The inbox is where POV responses land after outreach. Editors review mixed media formats in one place instead of splitting triage across email, chat, and file shares.

Features/Media-rich inbox triage

What it is

When participants respond to a POV, replies enter CiteLoop's inbox as structured records linked to story and POV context. The inbox supports text, image, audio, and video responses and can be browsed in grouped or classic layouts.

  • Replies retain POV and participant context
  • Multiple media types in one operational view
  • Grouped views for story- or thread-oriented review
  • Response activity visible at POV level (reply counts on POV cards)

Who uses it

Newsroom editors use inbox triage under deadline to decide which responses are usable for air or digital. Community operators use it to review campaign submissions before they become public-facing assets.

  • Newsroom: fast review of incoming expert and citizen replies
  • Community: filter usable voices from broader callouts
  • Both: one handoff point into the Create page for selected clips

What you control

Triage is an editorial decision layer. Operators decide which replies move forward; the inbox keeps format and context visible while they decide.

  • Which view mode fits the desk (grouped vs classic)
  • Which replies are selected for clip assembly on Create
  • Section-filtered clip browsing when assembling outputs
  • Thread and metadata context while reviewing

How it differs from a shared email inbox

Email scatters attachments and loses POV structure. CiteLoop inbox replies are tied to the POV they answered, the participant profile, and downstream creation slots. Selected items flow into trim, transcript edit, and render without re-uploading files.

  • Media types are first-class, not buried in attachments
  • Story and POV linkage stays intact through production
  • No separate export step to get video into an editing tool
  • Same participant record connects outreach to reply to output

Workflow steps

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

  1. Step 1

    Responses arrive after outreach

    Participants submit text, image, audio, or video through the invitation or recording flow tied to a POV.

  2. Step 2

    Open the inbox for review

    Editors browse replies in grouped or classic inbox views, with media-type and thread context available during review.

  3. Step 3

    Assess usability per POV

    POV cards show reply counts so desks can see which angles are getting traction before opening individual threads.

  4. Step 4

    Select replies for production

    Usable replies are carried into the Create page clip browser, still linked to their source context.

  5. Step 5

    Continue into clip assembly

    Selected inbox items become timeline slots where editors trim, edit transcript segments, and start render jobs.

Product screenshots

Triage text, image, audio, and video replies fast.

Collect broader voices and curate them into one insight view.

Common questions

Which reply formats does the inbox support?

Text, image, audio, and video replies can be handled in the same workflow. Create page clip loading uses media-rich replies from the API.

Can I see replies per POV without opening every thread?

Yes. POV inventory views expose reply counts so operators can prioritize angles with incoming activity.

Does triage happen in a separate product from outreach?

No. Outreach from the POV panel and triage in the inbox share the same participant and POV model. There is no manual re-linking step between send and review.

What happens after I mark a reply as usable?

Usable replies are available in Create for slot assembly, trim, transcript edits, graphics templates, and render jobs.

Does the inbox replace editorial judgment?

No. It consolidates intake and context. Editors still decide which voices meet story standards before production.

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

Participant

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

Read in glossary

Render job

An asynchronous background job that turns prepared clips and settings into a deliverable output.

Read in glossary

See this workflow on your desk or campaign

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