Enterprise
Eva for large operations
Eva's three public plans are bought off a table: they change by volume and take ten seconds to understand. That works until the operation stops being one operation — dozens of locations with separate inventories, a corporate group with thousands of conversations a month, or an integration that has to be built against the system already in use.
That is where Enterprise starts. It is the same product — the complete agent and the CRM — under a contract shaped around the operation: what gets quoted is the scope, not a package from the table.
When the public plans stop fitting
Any one of these three signals usually means the conversation belongs to Enterprise rather than to the public table.
- Several locations or brands with their own inventory, team and calendar, where each site needs its own agent and its own rules.
- A volume of conversations or users the published plans do not contemplate, or a season that multiplies it for a few weeks.
- Systems that have to be connected — commercial, invoicing, scheduling, or the one you built yourselves — and an implementation that needs support at every site.
What Enterprise includes
Only what we can hold up under contract.
Named account executive
A person who knows your operation and answers for it, rather than a shared support queue.
Service level agreement
Response times and scope of support are agreed in the contract, written where they apply to your operation rather than on a marketing page.
Multi-location
One agent per site or per brand, each with its own catalog, calendar, team and rules, without one configuration overwriting another.
Custom integrations
The connections your operation needs are built during implementation, against your system's endpoints and its contract.
Negotiated limits
Conversation volume, users and agents are sized against your real operation rather than against the public table's brackets.
Mexican tax invoicing
Eva issues and stores Mexican CFDI invoices for eligible charges through its stamping provider, given a valid tax profile and configuration.
How it is quoted
Enterprise carries no public price, and the reason is an honest one: two operations of the same size can need very different things, and publishing a number would mean inventing an average that serves neither of them.
When the operation is many locations running the same process, the natural unit is the site: a base platform plus a price per location, with volume tiers. That unit makes expansion obvious — start with three, they work, add ten — and it is the unit you already budget with.
When it is a single operation carrying heavy volume, the quote is built against what has to be sustained: conversations, users, integrations and the agreed service level. In both cases the quote arrives in writing, with the scope spelled out, after a conversation about the operation.
Implementation, built to fit
Implementation is bought separately from the plan, and on Enterprise it is the custom level: complex flows, multiple locations, deep integrations and support site by site.
It is quoted alongside the contract, because its scope depends on how many catalogs have to be loaded, how many systems have to be connected, and how many teams have to be supported through go-live.
Security and privacy
- Data is encrypted in transit and at rest.
- Your data is not used to train models.
- We sign a data processing agreement as part of the contract.
Tell us about your operation
Leave us a picture of how your operation runs and we will get in touch to build the scope and the quote. If you would rather talk now, message us on WhatsApp.
Message us on WhatsApp