Internal agents are live: Conduit agents that run your operation

Conduit agents started out doing one thing: answering guests. That hasn't changed. What changed this week is that your agents now come in two kinds, and the second one handles the parts of your operation that have nothing to do with a live conversation.

Customer agents and internal agents

Your customer agent is the one you already know. It runs the guest-facing conversation: the inbox, the questions, the back-and-forth. It's still doing exactly that.

Internal agents are the new half. They work in the background and take on the operational jobs, the analysis and the follow-ups that used to sit on someone's list. You set one going and it handles itself.

How internal agents wake up

An internal agent doesn't wait for a guest to write in. You can trigger it:

• On a schedule, so a nightly or hourly job runs without anyone pressing a button.
• From a webhook, when another system has something for it to pick up.
• From any channel, where a message, a review, or a booking event can set it going.

You can also @-mention an internal agent in Slack, or hand it a task from the Operator, the way you'd pass work to a teammate. These are the same events that already fire your workflows, so your agents slot into the automation you've built.

What's live on the marketplace

There are three things you can switch on today. Two are internal agents. The third is a skill you add to your customer agent.

Upsell Opportunity Analysis is an internal agent that reads every guest conversation and flags the upsells you let slip. For most operators that's a few hundred dollars a reservation, over and over.

Review Analysis is an internal agent that turns the pile of guest reviews into clear themes and the fixes worth making, so you're working off patterns instead of one-off complaints.

Inquiry Win-back is the one worth slowing down on. It's a skill, not its own agent. You add it to your customer agent, and the agent starts watching for the inquiries worth chasing, on whatever rule you set: a group of 20, a month-long stay, whatever matters to your business. When one matches, it follows up while you're still in the running. Early users saw inquiry-to-booking climb more than 15%, before anyone touched a setting.

Why a skill instead of a workflow

You could build inquiry win-back as a workflow. The problem is that a workflow makes you catch every edge case up front, and it never lets you tune the part that matters: who's actually worth winning back, and how hard to chase them. A skill on an agent flips that. You set the conditions, then change them next week, run a tighter cadence for big groups, or put a second agent on top to grade the results and improve them over time. A workflow automates a task. A skill hands the job to something that gets better at it.

Getting started

If you're already on Conduit, open the marketplace. The two internal agents are under Agents: add one and give it a trigger. Inquiry Win-back is under Skills: add it, then switch it on for your customer agent.

If you're not on Conduit yet and want to see this running across your portfolio, book a demo.