Use cases

A separate WhatsApp line for each client, building, or agent

Agencies and property managers get into trouble when several clients share one WhatsApp thread, or when each client has a phone that lives in a different bag. The useful model is the opposite of a shop floor. Lines must stay separate. One person, or a small office, still has to see all of them. Chato is a sidebar of those numbers, not a blended inbox.

A shared pot is the wrong default

A tenant asking about a leak, a buyer asking about a viewing, and a landlord asking about rent should not be three chats on one number if those relationships are supposed to stay distinct. People forward the wrong screenshot, reply from habit in the wrong thread, and eventually text from a personal phone because the shared one feels unsafe. Separate numbers avoid that class of mistake.

Give the client, the building, or the agent their own WhatsApp number, then connect each one as a session. The sidebar shows the list. Opening a session shows only that number's chats. There is no step that merges them, and there is no department that scoops a message from one session into another. If a coordinator works across clients, they use an account that holds the sessions. They do not get a single mixed feed.

This is the same QR connection as WhatsApp Web. The phone for that client or that building scans the code and stays online. You are not registering each line as an official API number. You are putting the numbers you already operate into one browser.

One person watching many lines

The other half of the job is attention. A property manager with eight buildings cannot honestly watch eight handsets. They can watch eight sessions. A quiet building is still in the list. Reports show, per number, whether it is online, how many messages it has handled, when it was last active, and how slow replies have been. A building that has gone dark is visible next to one that is busy, instead of being averaged away.

Contacts from every connected number land in one searchable list. That helps when you remember a person and not which building they wrote to. The chat you then open is still the session they used. The contact list is not a deal pipeline. Stages, offers, and owners of a sale belong in whatever system you already use for that. Chato is the place the WhatsApp conversation lives.

Billing follows the numbers. Eight buildings are eight WhatsApp accounts at €5 each per month, or €48 each per year, with the chatbot included if you want it on a particular line. The trial lets you connect one session for seven days before you add the rest. You are not charged per colleague.

When an assistant should see one building and not the others

Share only the session they should touch. An assistant covering one building gets that building's session, with view-and-send if they reply, or view-only if they are checking what was promised. They do not automatically see the other seven. The owner still sees all of them. Revoke the share when the cover ends.

There is no finer switch than that. You cannot assign one tenant's chat to the assistant and hide the rest of that building's chats. If a building's number contains conversations that an assistant must not see, do not share that session. Use a different number for the conversations they are allowed to handle, and connect it separately.

An agent who should have their own leads uses their own number and their own session. You might still hold that session on the office login so a colleague can cover leave. The agent's contacts are not poured into a pool unless you choose to share the session. That is a deliberate step, not the default.

What you still handle outside Chato

Viewings, offers, maintenance tickets, and keys do not become structured records because the chat moved into a browser. The External API can place a note from another system into its own thread beside WhatsApp, so a form submission is visible without being sent on WhatsApp. It does not push a WhatsApp message out, and it does not replace your agency software.

Chato also will not run a template campaign to a database of old leads. That requires the official WhatsApp Business API and Meta's template rules. If a portal demands that kind of sending, Chato is not the tool for that channel. It is the tool for the many one-to-one numbers you already answer by hand.

The day-to-day gain is narrower and more useful: each client or building keeps a clean line, one login shows every line, and a colleague can be invited to exactly the sessions they cover. Start with the busiest number on the trial. Add the rest when the sidebar is the place you actually work.

Many sessions, one login · Scan each number in · Price per client or building number · A different problem: one number on each shop door