01 / WHY ATIENDEHuman in the loop when it matters
An agent must know when not to decide. We design each project with an explicit list of actions requiring a person’s approval —contract changes, eligibility decisions, money movements— and with a clear escalation path when information is missing or the situation is unprecedented. Whoever receives the case also receives the context, so the customer does not have to repeat their story.
This is not an abstract promise: it is a mandatory section of the proposal, stating who decides and what happens if that person is unavailable.
02 / WHY ATIENDERecorded, reviewable actions
To review a process you need to know which request arrived, which sources were consulted and which action was attempted. That is why the scope of logs, who can consult them and how long they are kept is agreed per project. An action is not reported as done until the evidence the process defined exists: a booking is not confirmed because the agent requested it, but because the system responded that it was recorded.
When something fails, the aim is to be able to reconstruct what happened, not to assign blame.
03 / WHY ATIENDEWe start with one case, not twenty
Projects that try to automate everything at once tend to stall. We prefer to choose a task for its frequency, impact or friction, measure it against a baseline and expand with evidence. That way each stage can be evaluated, corrected or stopped without having committed your whole operation.
This also protects your budget: the scope of the first stage can be small and still useful, and the decision to continue is made with data from your own operation.
04 / WHY ATIENDEBuilt for WhatsApp and voice in Mexico
Many companies in Mexico and Latin America serve customers through messaging and phone, not a portal. That is why we design flows for those channels: short messages, voice notes, confirmations a customer can answer with one word, and a voice that does not make people navigate a menu. Spanish and English are handled from the design stage, not as a later translation.
The availability of each channel and the conditions of its providers are confirmed in the proposal: the site describes categories and use cases, not a list of installed connectors.
05 / WHY ATIENDEWe tell you when an agent is not the answer
If your process is not defined, if volume is low or if the cost of a mistake is too high, we will say so in the first conversation. The comparison page explains those criteria. We prefer a long relationship with a customer who automated the right thing to a quick sale that unravels in three months.
We also avoid superlatives: we do not claim to be “the best”, nor that an agent never makes mistakes. We say what it does, what it does not do and how it is reviewed.
06 / WHY ATIENDEWhat they look like in practice
A principle is useful only if it changes concrete decisions. That is why each one translates into something you can ask for and review: in the proposal, a list of actions with human approval; in operation, a log of what the agent consulted and executed; in the schedule, a bounded first stage with its success measure; in the design, the channels your customers already use; and in the commercial relationship, a frank conversation about whether the project makes sense.
If a principle is not reflected in what you receive, it is reasonable to point it out. These are commitments of method, and you should be able to check them against the reality of your project.
