Pipeline
Use tags and a practical follow-up routine
Keep prospect organization simple and make reminders reflect your own next actions.
Before you start#
- A genuine lead or submission in Pipeline.
Steps#
Step 1: Choose a small tagging system#
Open Pipeline and use its tag controls on the intended lead. Prefer useful labels such as a real interest or your next action. Too many overlapping labels make a list harder to work with.
Pipeline tags describe prospects. Team Command tags describe members in the team context; they are not interchangeable just because the names look similar.
Step 2: Check the correct person and saved state#
Review the lead before adding or removing a tag. Wait for the operation to finish and check the displayed result. If the app reports an error, do not assume it saved.
Avoid sensitive or speculative labels. A person's selected answer is not permission to categorize them by private characteristics.
Step 3: Make the next action specific#
When a follow-up tool or reminder is available, use it for an action you can actually take: respond to a question, share requested information, or check whether a conversation is still welcome.
If your reminder has a Done action, use it when you have completed the task. External automations or activity elsewhere should not be assumed to clear your own reminder.
Step 4: Review a manageable set regularly#
Review your follow-ups, read the submission, and use an appropriate contact channel only where you have a genuine basis to contact the person. Keep messages relevant and respect a request to stop.
Do not interpret a tracking event as proof that someone wants repeated outreach. A bounded request is not newsletter consent.
How you know it worked#
- Tags have a clear operational purpose.
- Saved tag changes are visible.
- Reminders represent a concrete next action.
Tips#
- Use fewer tags consistently rather than many tags once.
- When a tool is unavailable in your interface, do not assume an automation is running behind it.
Troubleshooting#
- A tag is not visible after saving.
- Check for a save error, confirm the intended lead, and refresh once if appropriate. Do not keep adding duplicate tags to work around a failed save.
Related questions#
Ready to do it? You may be asked to sign in.
Open PipelineRelated guides
Review submissions and recorded actions without confusing activity with identity or confirmed delivery.
Pipeline4 min readUnderstand Choice Auto TagsKnow when a Hook choice can organize Pipeline activity and when a Team tag can apply.
Account & privacy4 min readUnderstand announcements, email, and phone permissionsKeep communication channels separate and choose deliberately when a device asks for permission.