A practical guide to selling on WhatsApp

Start with five steps in order: prepare a catalog that answers questions, define how replies work, make payment clear, assign every follow-up, and measure progress. Do not automate a confused process. First make it repeatable by a person; then use technology wherever the work is repetitive.

Write the journey on one page. What the buyer needs in order to choose, what you need in order to quote, how they accept, how they pay, and what happens if they do not decide yet. Once that journey is clear, WhatsApp becomes a visible process rather than a pile of messages.

Each step should produce something you can name in one line: a catalog ready to share, a reply with a next action, confirmed payment, a follow-up with an owner and date, and a recorded outcome. Miss one and a conversation can look busy without moving forward.

Build the catalog from the questions buyers ask, not from internal system labels. Each product needs a recognisable name, useful photos, variants, price with currency and unit, conditions, availability, and a next action. When price changes by customer or quantity, publish the rule and ask for the missing fact.

Review recent conversations and mark every question that forced you to open another file or ask somebody. Those questions are the missing columns. A polished catalog that does not clarify size, delivery, or compatibility still leaves the important work outside the conversation.

Do not send the entire inventory when somebody asked for one category. Ask a question that narrows the choice first and share only what fits. Explain why each option matches, then confirm variant, quantity, destination, and date before finalising the price.

You can begin with the WhatsApp Business catalog, a document, or your own site. Eva fits when you want to search a connected catalog and answer with verified fields; it cannot repair an incomplete file or decide which information should be customer-visible.

Answer the specific question first and end with one easy action. Keep messages short, confirm what you understood, and ask only for what moves the purchase forward. Avoid long welcomes, walls of text, and replies with no exit. A good answer reduces uncertainty and makes the next step obvious.

A useful structure has three parts: answer, condition, and next step. ‘Yes, it comes in black; price changes by size. Which size do you need?’ does more than a long introduction because it answers, avoids overpromising, and asks for the fact that advances the purchase.

When you do not have the answer, say what is missing and who will confirm it. Do not say ‘I will let you know’ without a date. If another person takes over, include the product, variant, quantity, objection, and prior agreement so the buyer does not start again.

Save frequent replies without turning them into a rigid script. Eva can interpret text, audio, and images and use configured business information; a person should step in when a condition is missing, an exception appears, or the buyer wants to negotiate.

Decide before selling which methods you accept, what identifies a payment, when stock is reserved, and who confirms receipt. Send amount, purpose, and reference together. Never treat a screenshot as automatic confirmation: validate the transaction in the payment source and record its status before fulfilling the order.

The conversation should distinguish quote, acceptance, payment pending, payment confirmed, and delivery. If all those moments are called an order, your team will reserve stock without funds or ask a buyer to pay twice.

Send complete instructions in one message and explain what happens after payment. For a bank transfer, use a reference that connects the transaction to the contact and order. For a payment link, confirm that the amount and description are correct before sending it.

Eva can create a Mexican-peso SPEI bank-transfer payment link when that tool is configured. Confirmation must come from the payment system, not from an image posted in the conversation, and your business still owns its cancellation and refund rules.

Follow up with a reason and a date rather than a vague reminder. Record what the buyer requested, which option they received, the objection, and the next agreement. The return message should add something useful: a pending answer, an alternative, current availability, or a clear request for a decision.

Before ending a conversation without a purchase, choose one of four outcomes: follow up on a date, wait for information from the buyer, hand it to somebody else, or close it as not proceeding. Simply leaving it unanswered makes a paused opportunity indistinguishable from an abandoned one.

Do not write out of habit. If the buyer asked to review on Friday, return on Friday with the context. If price stopped them, do not repeat the same offer; ask whether the condition changed or present an alternative that genuinely addresses the objection.

A CRM keeps memory from living on one person's phone. Eva can record contacts and opportunities, schedule follow-up, and decide each turn whether to retrieve information, update the record, reschedule, or hand the conversation to the team.

Measure the journey rather than messages sent. Record where each prospect came from, the product requested, whether a proposal was sent, whether payment arrived, and why progress stopped. Also review time to first reply and overdue follow-ups. The goal is to find the step that loses purchases.

Start with a small set of states nobody can confuse: new, information pending, proposal sent, payment pending, won, and closed. Define the fact that moves each state. A label assigned by instinct produces a polished report and an operation you cannot improve.

Review the process by source and product. If many people arrive from a campaign but none reaches a proposal, inspect the initial promise or first reply. If they reach payment and stop, inspect instructions, trust, and available methods.

Measurement exists to choose the next change, not fill a dashboard. Eva records the conversation in its CRM and can keep the opportunity current, but your team still has to agree on what each stage means and review why real cases are lost.

Avoid five mistakes: sending promotions without permission, replying before understanding the need, hiding price conditions, treating an unverified payment as confirmed, and leaving follow-up without an owner. Do not automate exceptions that require judgment. Trust disappears faster after a wrong promise than after a careful human reply.

Do not treat a contact list as automatic permission to write. Explain which messages a person will receive and let them stop those messages. Having a saved phone number does not make every promotion relevant.

Do not promise stock, delivery, final price, or a refund unless the fact comes from a current source. When something depends on validation, say so before asking for payment. Clarity may delay a purchase; a late correction may lose the customer.

Finally, do not change five things at once. Fix the step with the largest loss, observe the result, and continue. A clearer catalog can solve what looked like a speed problem; better payment instructions can solve what looked like a lack of interest.

• Map the current journey from first question through payment and delivery before buying a tool.
• Use real conversations to complete the catalog, replies, and objections instead of designing the process from assumptions.
• Define observable facts for each state and retain an owner, date, and reason for every follow-up.
• Automate repetitive work with a clear exit first; keep exceptions, negotiation, and sensitive decisions with the team.