The CRM fills itself, from the conversation

The conversation is the form

The WhatsApp number is answered by a shared inbox, and on top of it an AI assistant that understands the case. What the person says is recorded as they speak: what they need, when, with whom. There is no second moment where somebody has to copy the conversation into a record.

• One inbox for the whole team, with full history per contact.
• The assistant replies instantly at any hour and leaves the case logged.
• When a human is needed, the conversation is handed over with all the context already written down.

Every conversation knows which ad brought it

This is where almost everyone loses the trail. Someone sees an ad, lands on the site, taps the WhatsApp button — and in that jump, where they came from is gone. The conversation shows up in the inbox as if it fell from the sky. We solve it with a short code that travels in the first message and that the database ties back to the visit that started it.

• The WhatsApp link carries a four-character reference the visitor sees and never has to understand.
• When the message arrives, the database links the conversation to the campaign, the ad and the search that brought it.
• If the person writes days later from another device, it still works: the reference travels in the text, not in a cookie.

The assistant books against the real calendar

A bot that promises an appointment that does not exist costs more than having no bot. Before answering, the assistant checks real availability and writes against it, under the same rules as any other process.

• It cannot book with a professional who does not exist, nor take the same slot twice: the database prevents it, not the prompt.
• It can record the appointment and cannot read conversations already stored. A permission per column, not per assumption of good behaviour.
• If free availability drops below thirty days ahead, it raises an alert. Without it, a bot answers “no availability” forever and that reads as an answer rather than a fault.

Who sees what, and who does not

A CRM holds data about people and about money, and not everyone on the team needs to see both. Permissions are enforced at every address, not by hiding a menu link.

• Someone who should not see costs gets a 403 even typing the address directly.
• Reaching any panel requires cryptographically verified identity, not a shared password.
• Who came in, what they looked at and the real address they used are all recorded.

You can test it right now

Cauce’s own WhatsApp is answered by that same system. Message it, ask about availability and watch what it does — it is the implementation, not a rehearsed demo.