Argentina in River Plate Spanish; the rest in neutral Spanish; English for everyone else.
An assistant with your brand answers 24 hours a day, every day, on WhatsApp and your website's chat. It already knows who's writing: it sees their record, their balance, their orders and what they talked about last time. It resolves what it can resolve, and whatever needs a person goes to a person — with the case labeled and your team notified.
* This is the base. Collections, sales and campaigns are added on top.
Look at the order. First it answers what it knows —the balance, with the real data from the record— and sends them the link to their account instead of typing a list in the chat.
Then they ask something it doesn't have loaded. It doesn't improvise: it says so and hands it over. That's the part we care most about, because it's where almost every assistant makes something up and burns a customer.
And at the end a complaint appears. There it neither negotiates nor over-apologizes: it acknowledges it, says someone on your team is already looking at it, and at that instant the card opens on the board and the email goes out.
Service inbox
Conversations · 23:00 to 23:20
Marina Ferraro
Asked their balance · answered with the record's data
Damián Ocampo
Asked for details · link to their account
Rocío Baigorria
Asked something that isn't loaded · handed to a person
Tomás Iriarte
Sent a voice note · understood and answered
Alejandra Puig
Sent a receipt · saved for validation
Ignacio Bordón
Complaint · escalated, with the history attached
Verónica Sandoval
Asked about payment methods · answered
Hernán Vidal
Wanted to talk to someone · handed over and notified
With every message the assistant receives that customer's real data. There's no "press 1 for balance": they ask in plain language and it answers with what's in the record.
How much they owe, what they bought, when the last delivery was, how their order is going. The assistant already has the record in front of it when they write: it doesn't ask for a customer number or make them wait.
When they ask for the fine details, it doesn't type them in the message: it sends them the link to their account summary, with your brand, no username or password. There they see balance, installments, invoices and movements.
If you have products or services loaded, it answers with your prices, already adjusted to the group that customer belongs to. If a product has no price, it says "to be confirmed" — never "US$0".
Your bank details, the ones you loaded in the panel. If they aren't loaded, it doesn't make them up: it hands the case to your team.
The delivery day for their area, calculated with your routes, your holidays and your cut-off time. If the contact has no area assigned, it says so as tentative and notes that your team will confirm.
If someone asks to meet and you have the CRM, it offers them three free time slots from your team —leaving out what's already booked and what's busy on each person's calendar—, books the one they choose and sends them the video call link.
If someone who isn't in your database writes, it serves them anyway, takes their details and leaves them loaded as a new contact, labeled for you to review.
It doesn't reply line by line, and it doesn't sell to someone who's angry.
Many people write in pieces. The assistant waits for the person to finish and answers once, with everything, instead of replying to each line separately.
It gets to the point, without filler or excess pleasantries, and if needed it hands the case to a person on your team.
To someone who's upset or asked not to receive messages, it offers no promotions or invitations to anything else. Their issue gets solved first.
They aren't three different bots with three memories. It's the same one, and that's why whoever wrote to you on one channel and continues on another doesn't have to start over.
Running from day one, with your number. It's where almost everything comes in, and where your customer already is.
Also from onboarding, with your logo and your colors. Whoever lands on your site asks right there, without looking for a phone number.
When you ask for it, we connect it. Useful where your customer already uses it for everything else.
And email we use for what goes out: reminders, payment notices, summaries and receipts, with your brand and from your own mailbox.
How far it resolves on its own and from where a person steps in is your call, case by case. What matters is that this line isn't decided by the model in the moment: it's configured and always enforced the same way.
| When this happens | What it does |
|---|---|
| An ordinary complaint | A delivery that didn't arrive, a question about a charge, a date change: if you leave it in its hands, it resolves it right there and notes it down. |
| A complaint that heats up | Here almost everyone prefers a person to step in. It's handed over instantly, with the case labeled and your team notified. |
| Mention of a lawyer or a threat | Immediate handover, no matter how confident the assistant is. This is the only one we recommend not touching. |
| Debt dispute | If the customer says they don't owe that, most prefer a model not to argue. You choose. |
| When this happens | What it does |
|---|---|
| Payment plan request | Special terms can be negotiated on its own within the limits you set, or go straight to a person. |
| Opt-out request | It's recorded and no rule ever contacts them again, through any channel. This isn't configurable: it's the law. |
You don't set this up alone: we define it with you at the start, and we adjust it as the operation changes. One detail that usually surprises people: handing over doesn't switch the assistant off. The label is visibility for your team, not an off switch — while nobody takes that case, it keeps serving everyone else. Real silence comes when someone on your team assigns themselves the conversation: then it goes quiet instantly, in that chat and only that one.
The problem with serving over WhatsApp isn't answering: it's that a week later nobody knows what's left pending, and the only way to find out is to open chat after chat.
Here every case that needs someone comes out as a card on the board, in its stage's column, at that moment. A new account already comes with nine labels and the board set up: you don't start with an empty screen.
And everything leaves a trace. Every label writes a note in the contact's record with what was marked, who marked it and why. If there's an argument tomorrow, it's written down.
Everyone starts the same way: the assistant answering what comes in. Then you ask it to also go out and look, or to work with another part of Cobratia, and the corresponding module switches on. This is what the assistant does with each of the other seven.
It takes the order in the conversation, with your catalog, and confirms with the customer before creating it.
Every incoming message lands in Leads according to what was asked, and meetings get booked in your team's free slots.
Have it go after whoever hasn't bought from you in a while, and serve them when they answer.
Announce or offer something to the audience you define. Whoever answers talks with the assistant, which knows what campaign they came from.
Chase what you're owed with your rules: whom, when, in what tone and how far to insist. If they reply, it gives them the payment details and records the promise.
It gives their alias to whoever asks how to pay, reads the receipt and knows who already paid: it doesn't ask them for money again.
The app's chat is the same assistant, with the same history as on WhatsApp.
How the modules connect with each other, and how your plan is put together.
They aren't separate systems: it's the same assistant, the same customer record and the same board. That's why the one who writes about a complaint and the one who owes you money are the same person on screen, not two records nobody ever cross-references.
Real platform numbers, totaled and without naming any customer. They update on their own.
What people ask us most before getting started. If something's missing, write to us and we'll answer it.
Yes, and I say it with the code in hand: the path of an incoming message never checks the time. The time window Cobratia respects is for messages that go out —collections won't message you at eleven at night—, but as for answering, it always answers.
WhatsApp and your website chat, which have been running since day one, and Telegram when you ask for it. All three are served by the same assistant, with the same customer record: if someone messaged you on WhatsApp and later comes in through the web, it arrives knowing what was being discussed. Email we use for outgoing notices —reminders, receipts, summaries— under your brand.
Yes. You send us your material —the manual, the questions you get most, your policies, your hours— and we load it so the assistant uses it. You don't need to format it or paste it anywhere: send it to us however you have it and we take care of it. On top of that come the live data from your account: your catalog, your prices, your routes and each customer's record.
It answers that it's passing the case on and flags it for a person. There's a system rule, above any configuration, that forbids it from asserting hours, areas or data it doesn't have. It isn't infallible —it's still a language model— but it's built to stay quiet rather than guess.
As far as you say, and you draw that line. Some complaints get resolved in the conversation —a delivery that didn't arrive, a question about a charge, a date change— and others you'd rather a person take, no exceptions. We define together which is which, and the assistant respects that line: what you let it resolve, it resolves; what you don't, it hands over instantly with the case labeled and your team notified. What will never happen is an angry person going in circles with a bot.
The assistant goes quiet in that chat, instantly. You can also stop it with a label, or mark a contact so it never serves them. You'll never have two voices talking to the same customer.
We don't hand you an editor and leave you to it. The assistant's script is written and tuned by us, with you, and we stay on it afterwards: if something answers differently than you wanted, you write to us and we fix it — usually the same day. It's a person from the Cobratia team alongside you, not a ticket. What you do manage on your own from your panel is what feeds the answers: your catalog, your prices, your routes and drivers, your payment details, your holidays and which events you want to be alerted about.
Nobody is left without an answer. If the assistant can't reason, it still replies acknowledging receipt and hands the case to your team. We'd rather a "we're on it" than silence.
Tell us what reaches your WhatsApp today and who answers it. With that we build the assistant's script, load what it needs to know and define which cases go straight to a person. That part we do: we don't hand you an editor and leave you to it.
Service is the base. These are the modules that get added.