Stop drowning in support requests. Tickets opened by your AI chatbot, your AI receptionist, and your public ticket form all land in one queue, so your team can assign, track, and resolve every issue in one place.
Cannot access billing portal
Source: Public form
Feature request: Dark mode
Source: Chatbot
Integration setup help
Source: AI receptionist
From chatbot intake to resolution, handle every customer issue with speed and precision.
Built for support teams that want to deliver exceptional customer experiences at scale.
Tickets from the chatbot and AI receptionist arrive with a priority and type already set, so your team spends less time sorting and more time solving.
Faster responses and consistent follow-up lead to more satisfied customers and better retention.
Assignees get an email when a ticket is assigned to them, changes status, or gets a new comment. Status tiles and saved views keep every open ticket in sight.
See every customer interaction in one place. No more searching through emails or chat logs.
Bring chatbot, phone, and form tickets into one queue your whole team can work from. Start with a 7-day free trial for qualified businesses.
A ticket in PipeCrush is one customer issue tracked from the moment it is raised until it is resolved: a numbered record with a subject, description, status, priority, type, source, assignee and any custom fields you add, plus a thread of comments and attachments.
Ticketing is built for small B2B teams where support is a person or a handful of people, often the same people who sell. Tickets live in the same workspace as your customers, contacts and deals, so the person answering a ticket can see who the customer is, what they bought and what else is open before replying.
Tickets come in from several places at once. Your team creates them by hand, your website chatbot and AI receptionist open them during conversations, customers submit them through your public ticket form, and other systems create them through the API.
Each new ticket gets the next ticket number for your account and a source: manual, chatbot, voice (raised by the AI receptionist on a call), external form, or API. Chatbot tickets link back to the chat session that produced them. Public form submissions can include image attachments and any custom fields you mark to show on the form.
Open Service > Tickets. Status tiles across the top show how many tickets are Open, In Progress, Waiting, Resolved and Closed, and clicking one filters the list. Filter further by priority (Low, Medium, High, Urgent), type (Bug, Feature Request, Question, Technical Issue, Billing, Account, Other) and assignee.
Set an assignee, who gets an email when the ticket is assigned to them. Link the ticket to a customer record so it appears in that account's history. Select several tickets to change status, reassign or delete them in one action.
Open a ticket to edit its fields and add comments. Mark a comment Internal for notes that should not go out in notifications. The first non-internal comment stamps the ticket's first response time. The creator and assignee are emailed about new comments and status changes.
Moving a ticket to Resolved records when it was resolved. Save filter combinations as named views, such as urgent tickets or everything assigned to you, and export the list to CSV. Custom dashboards can chart tickets by status and the open ticket count.
Chatbot and receptionist tickets land in one queue instead of scattered across chat logs and voicemails. A saved view of open Urgent tickets is the first thing checked each morning.
The support lead assigns incoming tickets by type: billing tickets to one person, technical issues to the other. Internal comments hold the back-and-forth on tricky cases so it stays off the notification emails.
Because tickets link to customer records, an account manager preparing a renewal call opens the customer and sees every ticket raised this quarter alongside the open deals.
A team leaving a spreadsheet or another tool imports its existing tickets from CSV, sets up custom fields for product version and plan, and turns on the public form for new requests.
Ticket number, subject, description, status, priority, type, source, assignee, creator, linked customer, contact and lead, the originating chatbot session, custom fields, comments (public or internal), file attachments, and created, first response, resolved and closed timestamps.
Manual entry, the website chatbot, the AI receptionist, the public ticket form, CSV import, the dashboard assistant, the public API and the MCP server. Webhooks fire when a ticket is created and when a comment is added.
Notifications go to your team: the ticket's creator and assignee. PipeCrush does not automatically email the person who raised the ticket; reply to them from your inbox or from their customer record.
There is no SLA management or breach alerting, no CSAT surveys, no automatic AI categorization or routing of tickets, and no automation triggers on ticket events. There is no native Slack or Zapier integration; use webhooks or the API.
Yes. Your account has a public ticket form where customers enter their email and issue, attach images, and fill in any custom fields you choose to show. Submissions are rate-limited to protect you from spam.
When a visitor wants to report a problem, the chatbot can open a ticket with a subject, description, priority and type, linked to that chat session.
Yes. Mark a comment Internal. Internal comments are labeled in the thread and never trigger comment notification emails.
No. Tickets record first response and resolution timestamps, but there are no SLA targets, breach alerts or CSAT surveys.
Yes. Import a CSV from the Tickets page. You can also export the current list to CSV at any time.
Ticketing has no separate plan limit. Your plan sets the number of users who can work tickets: 1 on Solo, 5 on Growth, 10 on Pro and 20 on Business.