Closed beta: Conversations is available only on selected portals. The workflow and interface may still change while we learn from beta customers. Contact support@productlift.dev if you want access.
How to get there: Click Inbox → Conversations in the sidebar. The item appears only when Conversations is enabled for your portal.
Conversations reads a sales call or other customer transcript, finds explicit feature requests, checks whether matching posts already exist, and prepares decisions for an admin. Nothing is added to your board until an admin approves it.
ProductLift keeps requests where a customer clearly asks for a capability they do not have. It intentionally leaves out:
ProductLift uses your configured Product Vision as context when deciding whether a call and its requests belong to your product. A Fireflies call classified as another product is kept under the Not this product filter so you can inspect or re-process it.
If you leave the title empty, ProductLift generates a short title from the conversation. When the transcript contains a clear meeting date, ProductLift uses that date instead of the import date. You can edit the title, meeting date, customer name, and customer email later from the conversation's ... menu.
For automatic imports, see Connect Fireflies to Conversations.
The Inbox is the default Conversations view. It contains conversations that are being processed, failed to process, or still need a decision. Use Done for completed reviews and Not this product for calls classified as another product.
Open a conversation to review each proposed request:
Use the checkboxes to approve several safe decisions together. Bulk approval uses the prepared post details without reopening the editor for every request.
For Fireflies calls, ProductLift lists the external attendees it can identify. All are selected by default. Before approving, you can decide exactly which people the feedback represents.
If no external attendee is recognized, click Add customer, add a name and email, save, and then select that customer for the review.
The admin who approves a new post is its default author, but does not automatically receive a vote. You can choose another author in the full post editor. Only the selected customers vote. Approving a match never changes the author of the existing post.
The public post description is a neutral summary of the need. ProductLift does not copy the customer's transcript quote, name, email address, or company name into that description.
Admins can find the originating conversation in the post's Sources tab. When several conversations support the same post, each source appears separately. Customer votes remain visible through the normal voter information.
For an automatic Fireflies import, ProductLift emails the admin who owned the call when feature requests are ready for review:
The email is sent only when requests need review. A manually pasted conversation does not email the admin who is already reviewing it. Creating a post through Conversations also suppresses the usual "new post created" email noise for the reviewing admin.
Every processed conversation uses at least one AI credit for extraction. A call classified as another product still uses that credit because ProductLift must read it before it can classify it. Calls with feature requests can use additional credits when ProductLift compares those requests with existing posts.
Re-processing a conversation runs the AI steps again and can therefore use more credits.
ProductLift always skips a Fireflies meeting ID that was already imported. It can also link a Fireflies import to a manually pasted copy when the meeting date, participants, and transcript strongly indicate that they are the same call.
This matching is deliberately conservative. Two separate calls with the same person or company should remain separate conversations.
Use the conversation's ... menu to:
The transcript remains private to portal admins. Only approved post content and selected customer votes reach the product board.