CRM pipelines in your support platform.

A CRM pipeline is a board of stages that tracks companies or contacts through a process such as Lead, Qualified, Proposal, Won and Lost. In Gleap it runs on the customer records support already uses, so each entry links to the company or contact, its attributes and its tickets.

Four templates: Sales pipeline (Lead, Qualified, Proposal, Won, Lost with a Deal value), Customer onboarding (Kickoff, In setup, Training, Live with a Contract value), Renewals (Upcoming, At risk, Renewed, Churned with a Renewal value) and Simple (New, In progress, Done). Rename, add or archive stages afterwards.

Entry fields are stored on the pipeline entry and differ per deal, for example Deal value. Record fields read and write the company or contact attribute itself, for example Plan, so a change in the pipeline shows everywhere else the record appears. Both can be edited inline on the card or in the table.

Yes. A numeric field can carry a sum, average, minimum or maximum per stage, formatted in the currency or unit you set. The totals come from a server-side aggregation over the whole stage, not only the loaded cards.

Yes. Each pipeline switches between the board and a table with the same fields as columns, inline editing and sorting.

Yes. The ticket sidebar shows the customer's pipeline entries and stage, lets you link an existing entry, and unlink it. From the entry drawer you see linked tickets and can create a new ticket for that deal or onboarding.

Automations are workflows that trigger when an entry is added or its stage changes, filtered by pipeline and stage. Actions include moving the stage, setting an entry field or due date, adding the record to another pipeline, creating a ticket, emailing the contact and notifying a teammate.

Yes. The REST API and the Admin SDK for Node.js expose getPipelines, addPipelineEntry, updatePipelineEntry and removePipelineEntry for identified companies and contacts. See the pipeline API examples.

Yes. Set a due date on the entry and the card shows it as a chip that turns red once the date has passed.

It depends on the work. Gleap pipelines fit teams that want sales, onboarding or renewal stages next to support conversations and product feedback. Compare forecasting, reporting and integration needs before replacing an established CRM. A trial lets you run one real process with your team. Coming from HubSpot? See Gleap vs HubSpot.

Through the customer record. A blocker on a deal becomes a ticket. From Team, Kai Resolve investigates it with the logs and your code, a confirmed bug becomes a coding task for Kai Code, and the contact hears back once a teammate confirms the fix is live. See how Gleap closes the loop and the platform overview.

Pipelines are in Beta and available on every plan. See pricing for plan details, or book a demo to review your pipeline requirements. Company names and values on this page illustrate the interface; they are not customer results.