Login
Start free trial

CRM pipelines in your support platform.

Deals and renewals keep moving, with the conversation beside them.

Book a demo Start free trial

Your team sees what blocks each deal, onboarding or renewal and clears it from the same record. Boards run on the companies and contacts already in Gleap, with per-stage totals, automations on stage change and the ticket one click away.

★ 4.6/5 on G2 Trusted by 4,500+ teams worldwide

7 days free. Cancel anytime. Card required. First charge on day 8 unless you cancel.

Trusted by 4,500+ teams
Customer conversations beside every deal. A deal waits on a technical answer, an onboarding stalls on SSO, a renewal is at risk after an incident. The pipeline and the conversation sit in the same record.

Deal details, tickets and automation.

See deal context and trigger work as it progresses.
The entry opens as a drawer: stage, due date, entry fields, linked tickets and activity. Fields sum per stage.
A ticket's sidebar shows the customer's pipeline and stage. Link an existing entry or create a ticket from the deal.
Workflows trigger on entry added or stage changed: create a ticket, email the contact, notify a teammate, set a due date.

Records from your product.

Billing or signup moves the deal.
The Admin SDK for Node.js and the REST API add companies or contacts to a pipeline, set entry values and move stages, so a signed contract or a paid invoice updates the board without a sync.
See the pipeline API

A deal blocker becomes a ticket.

Investigated with full context.
Create the ticket from the entry. Kai Support investigates the technical blocker with the logs and your code, and a confirmed bug becomes a coding task for Kai Code.
Meet Kai Support
Everything is in the same place.
Tridonic brought customer interactions, ticket routing, surveys, AI support and product guidance into one Gleap dashboard.
Elif Kavas
Digital Customer Experience Platforms Specialist, Tridonic
About CRM pipelines
What is a CRM pipeline in Gleap?
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.
Which pipelines can we start from?
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.
What is the difference between entry fields and record fields?
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.
Can we see totals per stage?
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.
Is there a table view?
Yes. Each pipeline switches between the board and a table with the same fields as columns, inline editing and sorting.
Can support tickets be linked to pipeline entries?
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.
What can pipeline automations do?
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.
Can our product or billing system add records?
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.
Does a card show when a deal is overdue?
Yes. Set a due date on the entry and the card shows it as a chip that turns red once the date has passed.
Can Gleap replace our existing CRM?
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.
How do pipelines connect to the rest of Gleap?
Through the customer record. A blocker on a deal becomes a ticket. From Team, Kai Support 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, the platform overview and AI customer support for SaaS.
Which plan includes CRM pipelines?
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.
Every deal keeps moving.
The conversation sits beside it.
Start free trial
See pricing

7 days free. Cancel anytime. Card required. First charge on day 8 unless you cancel.

4.6/5
on G2