How WhatsApp conversations land on the CRM customer card

Example scenario: Picture a kitchen showroom in Eskişehir. One evening a customer asks on WhatsApp for the price of a worktop. If the customer is registered, the conversation sits on the card that holds last month's measuring visit and the first quote that was sent; the next morning the salesperson sees on one screen who wrote, what they asked, and whether there was any earlier contact.

The keys to matching are the phone number and the e-mail address. If the same person writes on WhatsApp one day and by e-mail the next, and both details are on the same card, the conversations come together on that card. The technical side, how a business number connects to software, is covered in what the WhatsApp Business API is.

For matching to work well, the cards need to be clean. If the same customer has been opened twice, the conversation lands on one of them and does not show on the other. We move your existing customer records into Corex360 together with you.

The salesperson goes on leave or leaves the company. The customer keeps writing to the same number, but that number is now in someone else's pocket, or in nobody's. The new salesperson has to ask the customer what they discussed before. For the customer, that means explaining everything from the start.

Selling from a personal phone also has a visibility problem. The manager does not know which customer is waiting for an answer and finds out only when the customer complains. Once the conversation is on the record, an unanswered message lands on a list everyone can see.

The point of putting the conversation on the record is to look after the customer; the record also safeguards the salesperson's work. Customers believe they are talking to the company, not to one person; the information they give, the photos they send, and the promises they receive should stay with the company. It makes a difference for the salesperson too: when they go on leave, they know their customers will not be left unanswered.

Most price questions that arrive on WhatsApp never make it onto a list. Some get an answer, some are forgotten in the evening rush. At month end there is no answer to 'which quotes did we hear back on', because the price question was never recorded. On the card, the flow runs in this order:

• The price question becomes an opportunity; its stage and owner sit on the card.
• The quote is prepared on the card and sits in the card's Quotes tab.
• If no reply comes, a reminder rises to the top of the list; it is sent on approval.
• If the customer approves by phone, the call record lands on the same card.
• The contract sits on the same customer card as the quote; its start and end dates show on the contract card too.

WhatsApp stops being a chat window and becomes the first step of the sales process. The manager can also see from the cards which question became a quote and which is still waiting, without asking the salesperson for a report. Because the quote is prepared on the same card, sent once approved, and followed up with a reminder if no reply comes, no step of the flow moves into a separate file.

The same customer asks for a catalogue on Instagram in the morning, sends a photo on WhatsApp at noon, and rings the switchboard in the evening. Three channels often mean three different people and three half-stories. Nobody sees the whole picture, and the customer tells the same thing three times. When the channels are gathered in one inbox, the team looks at one list. Every conversation is assigned to an owner, and anything unanswered comes to the top. How several people write from one number, and how assignment and manager visibility are set up, is covered in detail in WhatsApp for teams.

Knowing the latest contact looks like a small detail, but it sets the direction of a sale. If the customer called last night, the note on that call is read before a price reminder goes out on WhatsApp in the morning. The card does not tell the salesperson what to say; it shows what has already been said.

In Corex360, WhatsApp, Instagram, and website messages are gathered in one inbox. Company email and phone calls link to the same person. You can see step by step how the channels come together on Messaging module page. The current rules for businesses using WhatsApp through software are in Meta's WhatsApp Business Platform developer documentation.

The conversation is assigned to an owner, and the Assigned to me filter above the list lets everyone pick out their own conversations. A thread converted into an opportunity carries the opportunity number badge in the list and in its header; if a quote that came out of it gets no reply, X AI follows the quote up. It does not send a reply or a quote to a customer on its own; it prepares a draft, and sending happens with your approval. Because the story sits on the card, whoever takes over the conversation carries on from where it stopped.

Messages are stored in the Corex360 core, on the customer card, either on Corex360 Cloud or on your own server. Access is role-based and logged, and personal data is processed under KVKK (the Turkish Personal Data Protection Law).

For someone running a neighbourhood shop on their own, tying WhatsApp to a record can be extra work; the conversation already sits with the owner, and the owner does not change. The need for a record arises as the sales team grows, when several people start writing from the same number, or when the quote and contract process gets longer.

Before tying WhatsApp to the record, agree one rule with the team: which number will business conversations run on? If salespeople keep messaging customers from personal numbers, no system can see the whole picture. Moving conversations to the company number is a decision to make before the software.

Let us also state a limit plainly: we do not promise bulk messaging, campaign sending, or an automatic reply bot for Corex360 Messaging. In the demo we open a conversation with your own WhatsApp number and watch together how the card is created and how the price question turns into a quote.