Your reps sell in the chat. Your CRM should know what they said.
Reps live in text and WhatsApp threads; managers live in the pipeline. inChat is being built to connect the two, so every conversation has an owner, deals come straight from chats, and a manager can see which customers are waiting on a reply.
inChat is in early access. Features shown are in development.
Sales happens in messages, and management happens in the dark
Once customers prefer texting, the real sales activity moves to phones. Reps are responsive, but the manager can’t see who’s talking to whom, which quotes are outstanding or which leads have been waiting since yesterday. The weekly pipeline review becomes a round of “let me check my phone.”
- 01
Ownership is assumed, not recorded
A lead texts the main number and two reps reply. Another lead goes to a rep who’s on vacation. There’s no single place that says who owns which conversation.
- 02
The pipeline lags the chats
Reps update the CRM on Friday, if at all. By then, deals have moved, stalled or closed in WhatsApp, and the forecast is built on last week’s memory.
- 03
Managers can’t see who’s waiting
The costly problem isn’t the lost deal you hear about; it’s the customer who asked a question at 3 PM and never got an answer. Without a waiting view, managers only find out when it’s too late.
How a sales team runs its day in inChat
This is the working rhythm inChat is designed for, from a rep picking up a new lead to a manager reviewing the pipeline.
New leads are routed to an owner
Inbound SMS and WhatsApp conversations are claimed or assigned by rule, such as round-robin or territory. Every thread shows its owner, so there’s no double reply and no orphan.
Reps work from “my waiting” first
Each rep starts with their own list of conversations where the customer spoke last, sorted by how long they’ve waited. That’s the to-do list.
Deals are created from the conversation
When a lead becomes an opportunity, the rep creates a deal from the thread. Details captured in chat become fields; the AI assistant (in development) can suggest updates that the rep approves.
Follow-ups are attached to threads
After sending a quote, the rep sets “no reply in 2 days.” The reminder clears if the customer answers first.
Managers watch the waiting view and the pipeline
A manager checks one view of conversations past the response target and one pipeline by stage. When something’s stuck, they open the thread or leave an internal note, without asking for a status update.
A solar installer’s sales team on a Tuesday afternoon. The waiting view caught a 45-minute gap, the manager covered without stepping on the rep’s deal, and the pipeline reflects the real stage before the end of the day.
The parts of inChat that matter here.
Ownership on every thread
Claim, assign or round-robin conversations so every lead has exactly one owner.
How assignment worksPipeline built from conversations
Create deals from threads and keep stages current from what customers say.
See the sales pipelineResponse time and conversion reporting
Response time by rep, volume by channel and stage conversion (analytics, in development).
Explore analyticsNotes and @mentions for coaching
Managers can step in with an internal note the customer never sees.
See team collaboration- Assignment, response timers, deals and pipeline are in development as launch scope. Analytics is in development.
- There are no integrations with dialers, email or other CRMs today, and none are scheduled. If your team relies on email sequences, inChat would sit alongside them, not replace them.
- Outbound prospecting over SMS has stricter consent rules than replying to inbound leads. Check with your provider or counsel; rules change.
Sales teams: your questions.
What inChat is designed to do for sales teams, and what’s still being decided.
Ask us something elseFor teams whose selling happens mostly in SMS and WhatsApp, it’s designed to be the CRM: contacts, deals, pipeline and the conversations in one place. If you depend on email sequences or integrations, it may not fit yet, since those aren’t available.
Yes, that’s the point of a shared inbox on business numbers. Managers can see every thread, its owner and how long the customer has been waiting.
No. The AI assistant, in development, summarizes threads, suggests next steps and drafts replies for a rep to review. A person approves everything that’s sent or saved.
inChat is designed around inbound conversations: leads who message you. Teams that do outbound texting need to handle consent and 10DLC rules carefully, and inChat isn’t a bulk-sending tool.
inChat is pre-launch and offered through early access. Pricing isn’t published yet; you can request details.
Other ways teams use inChat.
Make 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