Pipeline

This guide explains how the Pipeline screen works so anyone using the product can follow it without a technical background. Read it in order the first time, or jump to a section when you need a reminder—many ideas are repeated on purpose so you do not have to hunt for them.

​

🛠️ What Pipeline is for

Pipeline is a workspace where you see your workflow as columns. Each column is a stage. Contacts show up as cards in the stage where they belong. What you can do here

• See contacts grouped by stage in a Kanban-style board.
• Move cards from one stage to another by dragging and dropping.
• Open a contact from a card to review or edit details, add Notes, manage Appointments, and use the Log tab to send texts and see the conversation thread.
• Set up your process under Pipeline Management: create pipelines, name stages, and put stages in the order you want.

Think of a pipeline as a named process (for example a sales funnel or onboarding flow). Think of stages as the steps along that process. The board is simply that process drawn as columns left to right.

​

⬆️ Top of the page

These controls sit at the top of the Pipeline screen. Each one is explained again in the sections below where it matters most. 🧭 Breadcrumb Pages → Pipeline shows where you are in the app. It is a simple location marker.

​

🛠️ Pipeline Management

Open Pipeline Management from the top of the Pipeline page. This is the only place to add pipelines, edit names and stages, and delete pipelines (aside from shortcuts like Create Pipeline when the board is empty).

​

📋 List

The list shows each pipeline with information such as:

• Name
• Number of stages
• Created date (or similar metadata)
• Actions to edit or delete

​

➕ Add or edit

Add: From the management window, use Add Pipeline (or + Add Pipeline) to open the form. Edit: Pick a pipeline in the list and use Edit to open the same style of form for that pipeline. Pipeline name

• Required. Use a clear name (for example a funnel name or process name like “Sales” or “Onboarding”).

Pipeline stages

• At least one stage is always required. You cannot save a pipeline with zero stages.
• Add Stage adds a new row. Enter a stage name in each row before you rely on the save.
• Delete (trash) removes a stage. You cannot remove the last stage—the product will warn you.
• Drag the handle on the left of each row to reorder stages. Order here is the same order as columns left to right on the board.

Saving behavior (said twice on purpose):

• For a pipeline that already exists, reordering stages may store automatically when you drag—still use Save Pipeline whenever you change names or add/remove stages so nothing is left half-saved.
• Save Pipeline (bottom of the form) stores the full configuration and refreshes the page so the Pipeline dropdown and the board stay in sync.

New pipelines often start with default stage names (for example “New Lead”, “Contacted”, “Proposal Sent”, “Closed”). You can rename, delete, or add stages to match your process before or after the first save.

​

🗑️ Delete

1. Open Pipeline Management.
2. Find the pipeline.
3. Choose Delete and confirm when asked.

Deleting a pipeline cannot be undone. Stages and configuration for that pipeline go away. Check with your team before removing a pipeline others rely on.

​

📨 Messages and confirmations

Small notices or toasts may appear when you:

• Save a pipeline or contact
• Move a card between stages
• Assign a contact
• Send a text from the Log
• Hit an error (network, permissions, validation)

Read them—they usually tell you whether the action finished or failed.

​

🔽 Pipeline (dropdown)

The Pipeline dropdown chooses which pipeline you are viewing. The board always shows one pipeline at a time: its name and its stages as columns.

• When the page first loads, one pipeline is selected for you—typically the newest in the list (unless your product behaves differently; if in doubt, check what is highlighted in the dropdown i.e; “Noah Testing”).
• When you pick another pipeline, the board reloads so the columns match that pipeline’s stages and order.

​

📄 SOPs

SOPs opens Standard Operating Procedures built into the product: formal, step-by-step language for creating pipelines, editing stages, selecting a pipeline, and related rules. Use SOPs when your organization wants written procedures; use this guide for a plain-language tour. A screenshot and short summary appear in SOPs (Standard Operating Procedures).

​

👥 All assigned users (team-wide filter)

This show for users who can view all contacts within their company.

• All assigned users means: show every contact in each stage for users, but not limited to one assignee.
• Choosing a specific person limits cards to contacts assigned to that person.
• Changing this filter refreshes every column so counts and cards stay accurate.

🆕 When nothing is set up yet If no pipeline exists yet, you see a short message instead of a full board. You will typically see Create Pipeline (or similar), which opens Pipeline Management so you can add your first pipeline and stages. Until at least one pipeline exists with at least one stage, there is nothing to show as columns. After you save a pipeline, return to the main Pipeline page and pick it from the Pipeline dropdown if needed.

​

🗂️ The board (columns and cards)

Once a pipeline exists and has stages, the main area shows one column per stage, in the order defined for that pipeline (left to right matches the order in Pipeline Management). 🏷️ Column header Each column header usually includes:

• Stage name — the label you gave that step (for example “New lead” or “Proposal sent”).
• Count — how many contacts are in that stage for your access level and for the assigned-user filter when you use it. If you filter to one person, counts reflect that person’s contacts only.
• Dial — opens the dialer for this pipeline and this stage so outbound calling matches the column you are working in. Use Dial when you want calls to line up with that stage’s queue.

📦 Inside a column

• Cards may load in small groups. Scroll down inside a column to load more when there are many contacts.
• If a stage has no contacts, you see a simple empty message.

🧑‍💼 Each contact card Each card is a contact in that stage. You will usually see:

• Name (first and last when the system has them).
• Phone and email, or a short “not available” style label when something is missing.
• Call — quick way to start a call to this contact, consistent with calling elsewhere in the product.
• Message — takes you to Conversations for that contact.

🔀 Moving contacts between stages

1. Drag a card from one column.
2. Drop it on another column (another stage).

The contact’s stage updates to match the column you dropped on. Counts in the headers refresh. If something fails, a short message may appear so you know to try again or ask an admin.

​

📋 Contact Details

Click the card (the main body of the contact tile) to open Contact Details. This panel or window is where you work on one contact without leaving Pipeline. The following tabs and areas are described in order. Screenshots match the older walkthrough where helpful.

​

📝 Contact Information

• Common contact information fields include: First Name, Last Name, Phone Number, Email Address, ZipCode,City, and Country .

​

🗒️ Notes

• Lists notes for this contact.
• Add Note opens a form: enter text, save, and the note stays on the contact.
• When edit actions are available, you can adjust an existing note the same way you would elsewhere.

Notes are for context, follow-ups, and handoffs between teammates as the contact moves through stages.

​

📅 Appointments

• Shows a table of appointments (for example date, time, duration, calendar, status, location, notes, and actions—exact columns depend on your product).

​

💬 Log

Select the Log tab to load the conversation-style thread and messaging controls.

• SMS / iMessage — switches context; From and To lines match SMS use when SMS is active.
• From — choose which of your approved numbers to send from.
• To — the contact’s number (usually read-only).
• Assign — set Company, a team member, or for Company accounts Unassign, to control who owns the contact.
• Type in the message box and press Send or Enter to send when a valid From number and the contact’s number are present.
• An optional emoji control may let you insert symbols into the message.

Use the Log when you need to text from Pipeline while seeing the same thread you would care about for follow-up.

​

📑 SOPs (Standard Operating Procedures)

The SOPs button opens an in-product reference written in more formal language than this guide. It covers ideas such as:

• Purpose and scope of the Pipeline module
• Definitions (pipeline, stage, Kanban board, stage order)
• Who needs access and prerequisites
• Procedures for creating, modifying, and deleting pipelines; selecting a pipeline; managing stages; and using the Kanban interface
• Rules (for example at least one stage per pipeline, independence of multiple pipelines, irreversible deletion)
• Best practices (clear naming, reviewing configuration, documenting purpose, testing before wide rollout)

How the SOPs window behaves: Sections are often collapsible—click a header to expand or collapse so you can focus on one topic.