> ## Documentation Index > Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Internal Agent Use Cases > A gallery of internal agents teams have built, organized by what they automate. Internal agents run behind the scenes on your workspace's own data. They don't own a customer inbox, but they can trigger customer-facing actions through configured workflows, tools, or channels. See [Agents](/agent-hub/agents) for how to create one and how triggers work. This page is a gallery of specific internal agents teams have built or scoped, so you can see the pattern before building your own. Most need workspace-specific configuration (property rules, PMS fields, escalation contacts) to do the right thing out of the box. ## Workflow Or Agent? Not sure which to build? See [Agents → Triggers](/agent-hub/agents#triggers) for the rule of thumb. The cleaning status agent below is the clearest example of it in practice: a workflow can receive a "listing status changed" event, but figuring out *which* reservation to notify — is there a guest checking in within the next two days, and should they be messaged at all — is exactly the kind of judgment call a workflow can't make. An agent can just be told what "check in soon" means and reason about it per property. ## Property Readiness & Housekeeping Reacts to a PMS cleaning-status webhook and messages the guest once their unit flips from dirty to clean, if it's a same-day turnover. Guesty is currently the only PMS wired up to send this signal. Cross-references each property's trash schedule with active reservations and reminds current guests the night before or morning of pickup. The same broadcast pattern also covers ad hoc alerts, like a hurricane warning to guests in an affected region. Dispatches the day's properties to cleaners over SMS/WhatsApp and collects completion confirmations. A dedicated WhatsApp line lets a cleaner text a status update that syncs back into your scheduling system and can trigger a backfill notification. Picks up a "not clean" complaint from the guest-facing agent, contacts the assigned cleaner, and falls back to a backup cleaner list if there's no response in time. ## Revenue & Pricing Scans bookings 7–14 days out and offers guests in a cheaper room tier a discounted upgrade, freeing that room for last-minute bookers. Tested at a 1.55% revenue uplift. Scans guest messages to surface upsell opportunities that aren't configured yet — for example, several guests asking for a pack-n-play that isn't a paid add-on. Adjusts minimum length-of-stay and room pricing against configured floor rules. A competitor price-scraping variant is planned. Scans for properties with sparse upcoming availability and fans out a sub-agent per property to re-target past guests with a rebooking offer. ## Finance & Reporting Pulls the folio, generates a PDF invoice, and sends it automatically — useful on PMS platforms like Cloudbeds that don't do this natively. Sends each homeowner a monthly report and separately flags high-risk owners internally — for example a 30%+ booking drop — for proactive outreach. ## Guest Experience & Maintenance Drafts the host's review *of* the guest based on message sentiment and star rating — the reverse direction of the review response agent below. Reads guest messages for a mentioned honeymoon or anniversary and gives the assigned cleaner a heads-up to leave a small celebratory touch. Surfaces recurring issues across a portfolio that a human would otherwise lose track of — the same AC unit ticketed 8 times — and flags it for replacement. Reviews conversations for threads where someone was told "someone will follow up" and nobody did, and pings Slack with who still needs one. Checks the past week's reviews, thanks the positive ones, and deliberately holds off on negative ones. Reach depends on which PMS exposes a review API. Reasons over the actual conversation to decide whether asking for a review makes sense, instead of a rigid CX-score cutoff. Messages the guest directly to check in when a noise-monitoring integration reports a threshold breach, before it becomes a neighbor complaint. ## Hotel Staffing Sends a one-time WhatsApp nudge 14 days before arrival if a reservation is missing an arrival time. Pulls arrival times and concierge notes into a personalized WhatsApp briefing for each staff member. Generates monthly schedules from configured rules — full-time, flex, overtime — and emails each employee their own version. Checks the PMS each morning and sizes the pastry/amenity order to the current guest count. Fans a single guest request out to multiple vendors at once — chef, transfer, restaurant — and tracks state until every vendor replies. The most complex agent here. ## Operations Intelligence These don't act on a single guest or property — they analyze across the whole portfolio and surface findings for a human to act on. Reviews negative feedback across all conversations for recurring patterns rather than one-off complaints — like guests repeatedly getting the wrong door code, pointing at a Knowledge Base gap. Cross-references negative-sentiment conversations against inventory data — tracing a toiletries complaint back to a specific shampoo brand and flagging it for replacement. Clusters the past week's escalations by topic and emails the workspace admin a summary, alongside relevant automation features they haven't turned on. Reviews other agents' performance — diagnosing why an upsell agent's conversion rate is low, for example — and suggests a specific instruction change. ## Devices & Access (Roadmap) Both of these depend on the "Devices" feature, which is still in progress. Listed here so the pattern isn't lost, not because either is buildable today. Issues a temporary access code through a smart lock integration when a cleaner or guest reports being locked out, instead of a human relaying a code manually. Compares a cleaner's submitted photo against a checklist for that task, flags mismatches, and auto-approves the ones that match. ## Maintenance This gallery is maintained by the Conduit team and will be updated as internal-agent patterns evolve.