Frequently asked questions

It means taking a task someone currently does by hand and having it run on its own: answering a message, recording a lead, booking an appointment, sending a reminder, or moving data between systems. It is not software you install — it is one of your business processes translated into rules a machine can execute the same way every time.

A chatbot follows a fixed script — ask something outside it and the thing breaks. An agent understands natural language and, more importantly, has access to tools. A chatbot tells you which slots are open. An agent checks your calendar, books the appointment, writes it to the CRM and sends the confirmation.

Yes. Agent-based solutions include a CRM that centralizes leads, customers, conversations, appointments and history. We do not sell it separately because without somewhere to record what happened, the agent resolves the conversation and loses the information — which is exactly the problem we are trying to solve.

Yes, and it is usually the better choice if your team already works there daily. We connect via API and write into your CRM. We only stand up a new one if you do not have one, or if the one you have has no usable API.

Yes — it is what we get asked for most. We build exclusively on Meta’s official WhatsApp Business Cloud API, never on tools that simulate a phone: those violate the terms and end with the number banned. On the official API the agent answers, qualifies, books, and everything is recorded.

Yes. CRM, WhatsApp, email, calendars, payment platforms, spreadsheets and custom APIs. If a system has an API or supports webhooks, it can almost always be connected. The hard case is legacy software with no API, and we verify that during the initial analysis before promising anything.

Yes, and we treat it as part of the product rather than an add-on. You can see which processes ran, which conversations happened, which leads came in, what actions the agent took, what failed, and what needs a human. Automating without visibility is the fastest way to let a problem go undetected for weeks.

It is planned for. Retries handle transient failures, duplicate control keeps a retry from creating two records, and everything that goes wrong is logged. What we do not accept is silent failure: if something needs intervention, it appears on the dashboard. And with an ongoing agreement, we are the ones watching it.

No, and projects framed that way usually go badly. What gets automated is repetitive work that requires no judgment — which is most of the volume. Your team stops retyping data and answering the same question twenty times, and spends that time on what actually needs a person. In practice you serve more customers with the same headcount.

It depends on scope, and we do not quote a number before understanding the process because it would be made up. One tightly scoped flow is a small project; a full system with CRM, several integrations and monitoring is a different scale. During the free initial analysis we give you a realistic range before you commit anything.

A specific flow is usually live in two to three weeks. A full system runs four to eight. What stretches projects is rarely the technical work — it is how long the business takes to decide exactly how the process should work.

No. Cancún is our base and where we take in-person meetings, but we work remotely with businesses across Mexico and the United States. The work is identical; the only difference is whether we meet face to face.

Yes. Cancún shares a time zone with the U.S. East Coast for most of the year, so overlap is complete and nobody takes calls at odd hours. We work and invoice in USD, and meetings happen in English or Spanish, whichever you prefer.