CiteLoop logo

CiteLoop

Feature

Controlled open invitations

Open invitations let teams publish a managed link for a specific POV so new contributors can register, get reviewed, and record a response without treating the callout as an uncontrolled public form.

Book product demoSee comparison

Features/Controlled open invitations

What it is

An open invitation is a shareable access link tied to a POV and story context. The link starts without a fixed participant record. Someone who opens it can register with contact details and consent, after which the workflow can attach them as a participant and continue with the normal invitation and recording flow.

  • Created from the POV outreach panel in Engage
  • Scoped to one POV and its question set
  • Supports expiry on the link
  • Registration can require GDPR consent and language preference

Who uses it

Newsroom teams use open invitations when they need broader sourcing around one angle without manually adding every contact first. Community and engagement teams use them for campaign callouts where participation should stay reviewable instead of landing in a generic form inbox.

  • Newsroom: widen sourcing for a defined POV under editorial control
  • Community: run callouts with registration and approval before responses enter production
  • Both: reuse the same participant and inbox workflow after intake

What you control

The product treats open intake as part of the workflow, not a separate endpoint.

  • Which POV the link belongs to
  • Link expiry
  • Registration fields and consent step
  • Participant state after registration: pending, approved, or rejected
  • Whether the contributor continues into the standard recording flow

How it differs from a generic form

A standalone form collects submissions. CiteLoop links registration to a POV, participant records, approval states, and the same inbox and creation pipeline used for direct outreach.

  • Responses stay tied to story and POV context
  • Contributors become reusable participant profiles when approved
  • Editors review intake before replies enter triage and production
  • Recording links follow the same access-link model as direct invitations

Workflow steps

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

  1. Step 1

    Create the link in Engage

    An editor selects a POV, sets expiry, and generates an open invitation link from the outreach panel.

  2. Step 2

    Publish the link

    The link is shared on site, email, social, or embed surfaces. Each visitor hits the managed registration flow instead of an anonymous upload endpoint.

  3. Step 3

    Register and consent

    The visitor submits contact details, language preference, and required consent. The system can check whether the email already exists as a participant.

  4. Step 4

    Review participant state

    New registrations can enter a pending state until a desk or campaign operator approves or rejects them. Approved participants continue in the normal workflow.

  5. Step 5

    Record and triage the reply

    After approval, the contributor receives the recording path used for POV responses. Replies arrive in the same inbox used for direct outreach and move into clip assembly when selected.

Product screenshots

Create controlled open callouts with expiry and section scope.

Launch controlled community callouts in minutes.

Common questions

Is an open invitation the same as a public upload form?

No. It is a managed access link tied to a POV, with registration, consent, optional approval, and participant records. Submissions stay inside the CiteLoop workflow instead of a detached form bucket.

Can anyone with the link respond immediately?

Only after they complete registration and any approval step your team uses. Pending, approved, and rejected states are part of the participant model.

Does the link work without selecting a POV?

No. Open invitations are created for a specific POV so questions, story context, and downstream inbox handling stay aligned.

What happens if the same email registers twice?

The registration flow can detect an existing participant email so operators can route repeat contributors through the normal participant workflow instead of creating duplicates.

Where do replies go after recording?

Into the same media-rich inbox as other POV responses. From there, editors triage text, image, audio, and video replies and can move selected items into clip assembly and render jobs.

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

Open invitation

A managed access-link flow used for public or semi-public registrations and callouts.

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