Eva vs Kommo: which one fits your business?

Kommo does sales CRM well: it publishes sales-stage boards, tasks, records, analytics, per-user prices, AI credits and a 14-day trial with no card. For one or two people only organizing their process, Básico at $20 USD per user can cost less.

It does not publish final prices for 9-, 12- and 24-month terms, or Empresarial’s price and limits. It also does not publish quoting with price and stock verified against your catalog, photo identification, payment inside the thread or data export terms.

That message decides a sale: «how much for 22-gauge sheet, 4 by 8?». Eva searches the catalog you loaded by file or API, returns up to 25 candidates, and pulls the verified product record before answering. It only answers with fields you marked visible.

If the prospect sends a photo, Eva matches it against catalog images and returns candidates, a confidence level and the evidence used. Price, currency and availability are confirmed against the record; if verification is incomplete, it answers with medium confidence rather than asserting an unchecked fact.

Kommo has two possible answers. A Salesbot, which according to Kommo detects the customer's intent and replies with preset templates and flows built in a visual editor from Avanzado up; whatever does not fit the flow goes to your advisor. Or its AI agent, from Avanzado up, which answers in natural language from the sources you upload and can request information, update the prospect, start a Salesbot or transfer the chat.

From Avanzado up, its AI agent recommends products from the sources you upload and can read a Shopify, WooCommerce, Lazada or Tiendanube store in read-only mode. What its September 2026 documentation does not describe is checking price and stock against the product record before quoting. If your sale is booking an appointment or moving an opportunity between stages, that gap costs you nothing.

If your sale is «what does this part cost», that gap is the whole difference. Then comes follow-up: Kommo's agent reactivates inactive prospects up to 24 hours later, and for later on Kommo offers a Salesbot that sends a fixed message, for example after 3 days without a reply. Eva comes back on its own with sequences of up to five steps and delays of up to 180 days, each one a full agent turn, and when a value is missing it asks your advisor for help with the full history.

The honest limit is on our side: catalog sources on an API sync every 24 hours, and file sources refresh when uploaded again. A price that changed ten minutes ago is not in the catalog until the next sync.

Kommo bills $20 USD on Básico, $30 USD on Avanzado and $45 USD on Pro per paid user per month. One account shares one plan: five salespeople on Avanzado cost five times that monthly figure. The minimum is six months prepaid.

You cannot leave two people on Básico and lift only one to Pro.

Eva bills capacity: 5,000 credits and 5 users on Essential, 9,000 and 10 on Professional, 15,000 and 15 on Complete. Another person does not change the bill until included users run out; then it costs $17 USD per month.

Each agent reply spends one credit; messages from a prospect and your team spend none. A campaign spends one credit per ten sends.

Kommo’s AI has another meter: 750, 1,250 and 2,250 credits per paid user per month, multiplied by licenses and not rolled over. Its guide publishes roughly 15 credits for an agent reply and 100 to 200 for an analyst request.

On the Avanzado allowance, that arithmetic, ours on their published numbers, is a little over eighty agent replies per license per month before the allowance is gone. When credits run out, the agents stop replying until they renew or someone buys a package.

Published packages are Inicial at $29 USD per month for 5,000 credits ($10 USD on Pro), Crecimiento at $99 USD for 50,000 and Escala at $199 USD for 100,000. They require three months prepaid and reset every 30 days: unused credits are lost.

A new package cannot outlast the remainder of your subscription term.

With Eva a 1,000-credit top-up costs $49 USD and purchased credits never expire. If one or two people answer WhatsApp without catalog quoting, Básico at $20 USD per user per month costs less than any Eva plan.

Eva’s entry point assumes a team and volume. The arithmetic flips when the team grows and every new person bills again, or when the agent rather than people does the work.

Since 1 September 2026, Básico and Avanzado carry regional prices for new customers based on billing country; its Spanish-language card publishes the figures on this page, and existing customers keep their price while they stay on their plan. Kommo publishes 6-, 9-, 12- and 24-month selectors and standard discounts on 9-, 12- and 24-month terms. It does not publish discount rates or resulting per-seat totals. The published floor is no month-to-month option and six months prepaid.

That means the real cost of a long contract cannot be calculated from its site.

Direct payment is in US dollars by card or PayPal. An official partner may resell in local currency, but public material does not give a standard partner price, exchange-rate rule or bundled service. Ask a partner to put the total in writing.

WhatsApp usage sits outside both subscriptions. Kommo’s native integration is free to install on every plan, but Meta charges delivered templates by type and destination country, except those that fall inside a free window. On 28 July 2026 Kommo documented free-form messages and utility templates as free inside the 24-hour window a customer message opens. From 1 October 2026, under Meta’s official rate card, utility templates inside the 24-hour window cost USD 0.0085 per delivered message in Mexico and service messages are free up to 1,000 per phone number per month.

Marketing templates are always charged outside a qualifying free window. A click-to-WhatsApp ad answered within 24 hours opens a Meta free entry point window, with no delivery charge while it stays open. Kommo publishes a calculator for those rates, warns Meta can change them, and documents authentication templates as unsupported.

Kommo says the peso became available for WhatsApp Business accounts on 1 April 2026. That applies to Meta usage, not the CRM subscription.

Kommo’s plan comparison publishes scheduled backups on Empresarial, but no export format or retention window was found on the reviewed pages; its FAQ says cancellation takes effect at the end of the current billing cycle. That is not an accusation; it is a gap to resolve in the contract.

Setup is included: we configure everything Eva does today, at no extra cost. Eva goes live in up to 5 business days once access and catalog are ready.

Seven points remain open: the exact price for a Mexican billing address under its regional pricing; exact 9-, 12- and 24-month prices; Empresarial’s price and limits; local contracting terms; an official partner’s local resale price; the final WhatsApp bill; and extra-credit prices above Escala.

Empresarial publishes no seat minimum, credit allowance, storage cap or service metric. The final WhatsApp bill depends on message mix and Meta’s rates. Escala publishes a monthly ceiling and increment size, but not its cost.

Quoting with price and stock verified against your catalog, identifying a product from a photo and taking payment in the thread are not published. Neither are data export terms; on cancellation, its page says it takes effect at the end of the billing cycle. That does not prove they are impossible through an integration; they are absent from the material a buyer decides on.

That is why this page says «not published» rather than «no».

Kommo publishes more than 100,000 customers, a footprint in more than 100 countries and more than 3,000 partner agencies. Its Mexico, Peru and Chile cases report large response-time drops without linked methodology or audit; one calls a company Mexican while its header says Lima.

Eva has limits too: there is no public trial or self-serve signup; onboarding is assisted. The payment links Eva sends your customers are SPEI bank transfers, with no card option yet. Single sign-on and audit logs are built when Enterprise is signed, not published capabilities.

If any of that is required, say so in your first message and we will tell you no right there.

Ask in writing for the full-term total at your actual headcount, credit consumption, export and cancellation clauses, and a demonstration with your catalog and a real customer question. Those answers separate what is published from what is only promised.