Visitor Pipeline

Visitor Pipeline is your team’s follow-up board for new guests and first-time connections.

What Visitor Pipeline Handles

• Collects new guest entries from your intake channels.
• Places each person into a visible follow-up stage.
• Helps staff move people forward as conversations happen.
• Connects guests back to Invite Campaigns when available.
• Tracks follow-up tasks so next steps are not missed.

Pipeline Workspace View

The Visitors page presents a column-based board:

• Columns represent stages.
• Cards represent people.
• Stage counters show current workload.
• Search helps find people quickly by contact details.

Each card can be reassigned to a new stage directly from its stage selector.

Intake to Pipeline Flow

Stage Progression

Teams can move a visitor card from one stage to another in real time. Stage changes are reflected immediately on the board, helping teams coordinate during services and weekday follow-up.

Typical progression example:

1. New
2. Contacted
3. Engaged
4. Ongoing Care

• Immediately reflect in board column placement. Your exact stage names can follow your ministry style. This supports live team triage during services or weekday follow-up blocks.

Attribution Connection with Invite Campaigns

When invite context is available: When an intake submission includes invite token context:

• The visitor can be linked back to the campaign and invite source.
• Teams can see which invites are producing real guest responses.
• Follow-up priorities can be adjusted based on what is working best.
• Invite Campaign stats can report conversion from click to submit.

This ties front-door invitation efforts directly to actual guest responses.

Contact and Source Data Rules

Visitor entries typically include:

• Full name
• Email and/or phone
• Preferred contact channel
• Optional message
• Source labels (for example kiosk, web, import, unknown)

This gives teams enough context to contact guests in the right way.

Duplicate Protection (Important)

The intake flow helps avoid duplicate cards when someone submits multiple times in a short period.

Later, legitimate new submissions can still be captured as expected.

Follow-Up Task Support

Visitor follow-up tasks are supported at the pipeline-item level:

• Create task with title, due date, and assignee.
• Update task status (open, done, canceled).
• List tasks per pipeline item in prioritized order.
• Delete task when no longer needed.

This gives teams an accountable checklist connected to each person.

Submissions Listing and Review

You can review submissions and current stage placement to support:

• Reporting exports
• Follow-up audits
• Queue balancing

Automation Integration

Visitor activity can trigger Automations, so follow-up messages can start quickly without manual handoff.

This is especially useful for welcome journeys and invite-response sequences.

Security and Access Model

• View access allows teams to read board details.
• Write access allows teams to move stages and update tasks.
• Delete access allows removal of tasks and related items where permitted.
• Communication features remain subject to your paid-feature access setup.

Suggested Team Workflow

1. Monitor new submissions in the first stage.
2. Assign and complete immediate contact tasks.
3. Move cards as follow-up milestones are completed.
4. Use campaign attribution to prioritize effective channels.
5. Review stale cards regularly and reset action dates.