The deal starts in the conversation, so the record should too.
A couple messages about a ten-day trip to Portugal. Over a week of WhatsApp they settle dates, budget and hotels. In most CRMs, none of that exists until someone copies it over. inChat is being built so the deal is created from the thread and updated as the chat moves.
inChat is in early access. Features shown are in development.
- 1Create the deal from the thread
- 2Capture details as fields while you chat
- 3Let the conversation drive the stage
- 4Keep the history on the record
- 5Review the pipeline, not the inbox
Your pipeline is only as current as the last time someone copied a chat
When most of the selling happens in messages, the CRM becomes a second job. Reps answer the customer, then retype the details somewhere else, or don’t. Within a few weeks the pipeline shows deals that closed, died or changed scope long ago.
- 01
Deals live in two places
The real negotiation happens in WhatsApp; the official record is in a spreadsheet or CRM. They drift apart the first busy week.
- 02
Details get lost in the scroll
Dates, party size, budget and preferences are spread across dozens of messages. Finding “what did they say about hotels?” means scrolling back through the whole thread.
- 03
Stage changes happen silently
The customer says “let’s book it” at 9 PM. The deal still reads Proposal sent the next week, and the forecast is wrong.
From first message to an accurate deal
This is the flow inChat is designed around. The conversation stays the place you work; the deal is the structured summary of it.
Create the deal from the thread
When a conversation becomes a real opportunity, create a deal from inside it. The contact, channel and conversation link are filled in already, so the deal and the chat stay connected.
Capture details as fields while you chat
Use custom fields for what matters in your business: dates, budget, party size, scope. Update them as the customer shares details. The AI assistant (in development) can propose field updates from the latest messages for you to approve.
Let the conversation drive the stage
When you send a proposal, move the deal to Proposal sent. When the customer agrees, move it to Won. Stage suggestions from the assistant are in development; a person confirms each one.
Keep the history on the record
The full thread, notes and field changes appear on the contact’s timeline, so anyone who opens the deal can see how it got here.
Review the pipeline, not the inbox
Managers look at deals by stage and open the conversation only when something needs attention. No weekly “update your CRM” chase.
A Portugal trip at a boutique travel agency
Inés never left the conversation, yet the deal has dates, budget, preferences and the right stage. Anyone on the team can pick it up from the record.
Fictional business and sample messages.
The parts of inChat that matter here.
Deals linked to conversations
Create a deal from a thread and keep the two connected on a visual pipeline.
See the sales pipelineFields that match your business
Define the details your deals need, from travel dates to project scope.
Set up custom fieldsSuggested updates you approve
The assistant reads the thread and proposes field and stage changes; nothing is saved until a person approves it (in development).
Meet the AI assistantOne timeline per customer
Messages, notes and changes in one history on the contact record.
See customer historyChat to deal: your questions.
What inChat is designed to do for chat to deal, and what’s still being decided.
Ask us something elseNot without a person. The AI assistant, in development, suggests field and stage updates from the conversation, and you approve, edit or dismiss each one. You can also update fields by hand.
The design ties the deal to the contact, so conversations on different channels with the same person show on one timeline. Exact multi-contact deal behavior is still being finalized during early access.
There’s no one-click importer to promise. If you plan to move, start by cleaning up your current list in a spreadsheet; the CRM migration checklist covers how. We’ll confirm import options with early access teams.
No. Third-party integrations and a public API aren’t available or scheduled. Teams have requested them, and we’re listening.
Contacts, deals, pipeline and custom fields are in development as launch scope. inChat is offered through early access, and pricing isn’t published yet.
Other ways teams use inChat.
Lead response
Answer new inquiries while they’re still warm, including after hours.
ExploreLead qualification
Ask the right questions in chat, record the answers, and hand off cleanly.
ExploreSales follow-up
Follow up over SMS and WhatsApp, and stop the moment the customer replies.
ExploreCustomer communication
Reminders, updates and service questions after the sale, in one history.
ExploreMake every conversation count.
Join the early-access list to see inChat in action, help shape what we build next, and be first to know when your team can start.
- A walkthrough built around your channels
- Early look at pricing and plans
- A direct line to the product team