WhatsApp in VentasxMayor

WhatsApp inside the platform works as a manual communication channel: https://wa.me/... links that open WhatsApp Web/App with a pre-filled message ready to send. There is no WhatsApp Business API integration, no automated sending, and no Meta-approved templates. Every message is fired by the manager (or the buyer) clicking.

How it works

The platform uses the business's WhatsApp number for three things:

1. "Send via WhatsApp" buttons in the manager panel (orders, payment, invoice): open WhatsApp with the message text and the buyer's number pre-filled; the manager just hits send in their own app.
2. Editable abandoned-cart message: every row in the abandoned carts list has a button that opens WhatsApp with editable text and the recovery link included.
3. Chat widget in the wholesale storefront: with one or several WhatsApp channels so the buyer can start the conversation from the store.

Configuration

Data is loaded in General settings and in Settings → Chat.

Main business WhatsApp number

• Field: :negocio/whatsapp (General settings → Contact data).
• Usage: default number the system uses for "Send via WhatsApp" buttons in the admin panel and for the chat widget fallback button when there are no channels configured.

Chat widget service channels

• Field: :negocio/chat-canales (Settings → Chat → Channels).
• In-platform help text: "Add one or more WhatsApp numbers so your customers can contact you. If you have several channels (sales, support, etc.), add one per area."
• Lets you add multiple WhatsApp buttons in the chat widget — one per area (Sales, Support, Collections, etc.). Each channel has:
• Channel name (canal/nombre): label of the button shown in the widget (for example, "Sales", "Customer service").
• WhatsApp number (canal/whatsapp): the specific number the buyer is redirected to on click.
• Default message (canal/mensaje): pre-filled text that appears in the buyer's WhatsApp input when the chat opens.
• When channels are configured, the widget shows the channel buttons instead of the single WhatsApp button.

Default abandoned-cart message

• Field: :negocio/whatsapp-cart (Settings → Communication → Other → WhatsApp abandoned cart).
• Usage: base text the platform pre-fills when the manager triggers a manual send from the abandoned carts list. The platform automatically appends the cart link at the end of the message.

Manager actions

• "Send via WhatsApp" from an order: opens WhatsApp with the buyer's number and a contextual pre-filled message (order data). Useful to manually confirm, notify shipping, request payment confirmation, or resolve questions. It's manual: the manager clicks, reviews the message, and sends it from their own WhatsApp account.
• Manual abandoned-cart recovery: from the abandoned carts list, the WhatsApp button opens the chat with the buyer and the default message plus the cart link.
• Invoice / payment-request send via WhatsApp: the invoice (VXM subscription) detail has buttons to record that the manual resend was done via WhatsApp on different occasions — this is only for VXM's internal collections, not for catalog orders.

What the buyer sees in the storefront

• Floating chat button: pop-up panel with FAQs (:negocio/chat-preguntas), contact form, and the configured WhatsApp channels (one or several buttons per chat-canales).
• If only the main number is configured and there are no channels, the widget shows a single WhatsApp button with the welcome message (chat-bienvenida).

What does NOT exist

• ❌ No automatic sending: no WhatsApps are sent automatically when an order is confirmed, shipped, an invoice is generated, or an abandoned cart is detected. Every action requires a manual click from the manager.
• ❌ No WhatsApp Business API: no Meta-approved templates, no number verification, no bulk sending to non-opted-in contacts. It's only the wa.me protocol that opens the user's app.
• ❌ No "templates per message type": there's only one editable message (abandoned cart). Other messages are pre-filled dynamically per button with the matching order/customer context, without the manager configuring them.
• ❌ No read/response tracking: the platform doesn't know whether the message was sent, read, or replied to — that's WhatsApp on the user's side.

Tips

• Set up separate channels (Sales, Support, Collections) when your team is small but buyers get attention from different people — one channel per area prevents commercial inquiries from landing in support and vice versa.
• Define clear default messages for each channel — the buyer arrives with context ("Hi, I have a question about an order…") and you start the conversation faster.
• For real "automated sending" (abandoned cart, repurchase nudges, recovery) use automatic emails and Auto-seller, not WhatsApp. Here WhatsApp is always manual.
• If you need massive WhatsApp reach, use WhatsApp Business or an external provider connected to Meta's API — the platform doesn't replace those tools, it just makes one-to-one clicks easy from the panel.
• Make sure the configured number has WhatsApp Business active on the matching device — the manager's send goes out of their own account, not a virtual number.