Conduit is the coordination layer for hospitality. It's an agent that works every channel an operator does, from a guest's late-night WhatsApp to the phone ringing at the front desk, and it acts on the business's behalf instead of just shuttling messages between people. It answers the guest directly. When a job needs someone on the ground, it dispatches the contractor and keeps the owner in the loop. It can close a booking or push a refund through without anyone stepping in. All of that works out of the box, because general intelligence is already good enough for the routine work that fills most of a day. The part that makes it yours is everything underneath: how your operation actually runs, and the exceptions only someone inside it would know. The agent picks that up by working alongside your team. Give it long enough and it stops feeling like software and starts to mirror the place itself.
Five thousand years of routing information through people
In 3300 BCE, the temple administrators of Uruk, the first city in recorded history, ran into a problem we'd still recognize: how do you coordinate complex work across people who can't all be in the same room? Their answer was clay tablets. The scribe who kept them became the world's first knowledge worker, someone whose entire job was to hold and relay information too important to leave to memory.
The Romans faced a harder version of it. A Greek phalanx moved as one rigid block, dependent on line of sight and shouted orders, which was fine at small scale and useless the moment things got complex. Rome's answer was hierarchy: eight men under a decanus, those under a centurion, and so on up the chain, so an order never had to travel more than one level to reach anyone. It was a routing protocol built out of people.
Then the telegraph let information move faster than any person could carry it, and that created a new problem. A company now needed some way to act on all of it at scale. Rockefeller's answer was the modern corporation, vertically integrated and run from the top down. Everything since has been a variation on the same theme, whether it's a rigid matrix org or a flat startup that swears off managers entirely. Each one is another attempt to push information and decisions through people more efficiently. None of them touched the real constraint. Information still had to pass through people, and people have limited bandwidth.
AI is the first thing to break the pattern. Strip away the centuries between them and the scribe in Uruk and the manager in a modern org chart turn out to have the same job: hold the context, and carry the decision from whoever has the authority to whoever does the work. Now that job can run on its own. The agent holds the context and routes the decision, and the judgment at the edges stays where it always was, with the people who were always going to make it.
The bottleneck was never speed
Almost everything a hospitality business does runs through a conversation. Revenue gets made in one, whether it's a question about availability or a booking that closes over WhatsApp at midnight. The problems land in the same place. Pick almost any operational function and you'll find it starts with someone sending a message, the refund that needs approving, the guest who's quietly about to walk.
The last thirty years solved the speed problem. Anyone can reach anyone now, instantly, around the clock, and they do. So the bottleneck moved. It's no longer how fast information travels. It's how fast a person can absorb it and act, and there's a hard ceiling on that.
And the channels don't talk to each other. A guest's question sits for hours while a contractor waits on a reply that landed in the wrong inbox. In one Conduit customer's data, median human response time across a single team ranged from 26 minutes to 46 hours. The agent answers in 93 seconds. It gets worse after hours, which is when most guest messages actually arrive, and when the booking tends to go to whoever replies first.
The usual fix is to throw people at it, a VA or a small offshore team parked across all those inboxes, relaying messages between everyone who needs to talk. It doesn't scale. The shifts grind people down, and context leaks out every time a conversation hops from one app to the next. Worse, the business keeps changing under them, so they're never quite trained for the version of it that exists today. The overhead grows in lockstep with the operator. Hiring has never actually solved orchestration. It just adds more people to it.
What Conduit does
Conduit puts a single agent across every channel an operator uses, and it keeps the full context no matter who's on the other end of the thread, a guest one minute, a contractor the next. It acts in real time. Picture a guest messaging at 1am about a leak. The agent answers on the spot and pings the on-call plumber on WhatsApp. It books the visit for 7am, then emails the owner a summary with a comp already drafted for sign-off. The operator wakes up to a six-line digest and one button to press. The night shift ran itself.
The role that disappears is the one in the middle, the person who shuttles information between tools and decides which specialist needs to see what. The specialist at the edge doesn't go anywhere. The plumber still fixes the leak, the front-desk manager still reads the room; their judgment was never the bottleneck. That middle role only existed because information had to pass through a person, and the moment it doesn't, there's nothing left for it to do.
General intelligence handles the routine out of the box. What it can't know on day one is the part specific to you: how you escalate, and the unwritten rules your team falls back on when a call is genuinely hard. That layer gets built over time. You teach some of it directly, and the agent absorbs the rest by watching how your people handle the cases that don't fit the mold. Either way, the result tracks the operator. Tight instincts and clean process give you a system that holds that standard at scale. A sloppy operation gives you a sloppy agent. The agent reflects how the business already runs; it won't fix it for you.
The same capability runs outbound. A booking confirmation kicks off a pre-arrival flow. A guest who went quiet on a quote gets a nudge two days later. None of this is a separate automation bolted on the side; it's the same agent as everything else, now working toward a goal instead of waiting for a message. The conversation stays open as long as it needs to and closes when it's done, and nobody on the operator's side has to track it by hand.
The early signs
We're still early. The clearest evidence isn't in the metrics, it's in what an operator can pull off now that was flatly impossible a year ago. The metrics are real, though. Conduit has handled more than 50M conversations and influenced over $3B in reservation value. The customer base runs past 1,000 hospitality brands. They operate in more than 120 countries and 140 languages. The agents resolve 87% of guest communications on their own. CSAT sits at 95%, and a first reply lands in under a minute. Industry-wide, the AI automation rate has roughly doubled in nine months, and the operators who moved early are already pulling away from the ones who waited.
We start in hospitality because it's the sharpest version of the problem anywhere. The conversation volume is brutal and the operations are genuinely messy, which is exactly why the payback shows up in weeks instead of quarters. But hospitality is only the entry point. The coordination layer underneath it, an agent sitting at the center of how a business talks and acts for itself, is where every industry eventually lands. Run it forward: no guest left waiting, no contractor sitting on a message nobody saw. Get there, and coordination stops being the quiet tax that every growing business has simply learned to pay.
-Punn and Cole