One conversation, whichever door they come back through

The order they walked away from is still there

A customer builds a cart on your website and then something happens. A meeting starts, a child needs something, the train arrives. The tab closes. In almost every ordering system in existence, that cart is now gone, because it lived in a browser session that no longer exists.

Here it is held. Not for the length of a session, and not tied to the device it was built on. When that person comes back, the conversation continues from where it stopped and the cart is intact, with the modifiers they had already chosen still on it.

• An abandoned order is held rather than discarded with the browser session
• The cart comes back intact, with modifiers and variants preserved
• The customer resumes rather than restarting
• The cart belongs to the customer, not to a tab

Including when they come back by phone

This is the moment worth understanding, because it is the one that is genuinely hard to build and immediately obvious to a customer.

Somebody with an unfinished order calls your business. The call does not open with a blank greeting and a request for their name. It opens already knowing who they are and what they were in the middle of, so the conversation starts from the cart rather than from nothing.

From the customer side it reads as a business that was paying attention. From the technical side it is the hardest boundary in the whole stack to cross, because voice normally lives in a different system from web chat, on a different vendor, with a different idea of who the customer is. See how phone answering works.

• A call from a customer with an unfinished order opens already knowing about it
• No name to re-ask, no order to describe again from the start
• Web to voice is the boundary point tools drop customers at

Bookings continue across channels too

It is not only carts. A booking conversation that starts in one place and picks up in another runs on the same machinery. Somebody asks about Saturday on the website widget, thinks about it, and texts you that evening. That is one conversation with a gap in it, not two enquiries from two strangers.

It matters most for the bookings that need thinking about: the expensive service, the group, the job somebody wants to check with a partner before committing. Those are exactly the conversations that pause, and exactly the ones a channel boundary usually kills. See how booking works and how it runs over text.

• A booking conversation continues on a different channel without restarting
• The same machinery as an order resume, applied to appointments
• Works across WhatsApp, text, web chat, and the phone

The same person, not three half-records

None of the above is possible unless the system can tell that the caller and the texter are the same human being. That is what the identity graph does: the same person arriving by phone, by email, and by channel resolves to one record rather than three partial ones.

Behind the record sits one append-only event ledger. Nothing is overwritten, every visit and order and adjustment is an event, and the counters on the profile are reconstructed from those events. The history stays reconstructable and the numbers cannot quietly drift apart from reality. See the unified customer record.

• An identity graph merges phone, email, and channel into one person
• One history, one visit count, one no-show count, one balance
• An append-only event ledger behind the record, so counters never drift

This is why it is one platform and not four good tools

It is a fair question to ask why you would not just buy the best chat tool, the best booking tool, the best ordering tool, and the best CRM. They are all good products. Plenty of them are better at their one job than any single module of a platform.

The answer is this page. Four excellent tools cannot do continuity, and not because anybody built them badly. They cannot do it because they do not share a customer record. The chat tool has its own idea of who the customer is, the ordering tool has another, and the phone system has a third, and there is no join between them that survives a real conversation. An integration can copy data between them on a schedule; it cannot make a phone call open already knowing about a cart from forty minutes ago.

Here every module writes to the same record. Continuity is not a feature that was bolted on afterwards; it is what falls out of the architecture once that is true. That is the whole argument for one system, stated concretely rather than as a slogan about seamlessness.

• Every module writes to the same customer record
• Continuity is a consequence of the architecture, not a feature on top
• A stack of point tools cannot do this, however good each one is

Questions owners ask