Skip to main content
RoutMe

Eight industries, one very repetitive problem

A hospital, a warehouse, and a lending app look nothing alike, and their highest volume conversation is structurally identical: a customer asks something whose answer already exists in a system, and a person ends up fetching it by hand. Every example below is the same mechanism pointed at different data.

Industries walked through
8
Ready-made flows to start from
6
Systems the agent can read
34
Steps in every build
4

What every one of these builds looks like

The interesting differences are in what must stay deterministic, and where a human still has to enter the conversation.

  1. Connect the system that has the answer

    An order table, a CRM, a scheduling database, a CMS. Whatever a support agent would open a tab to check is what the AI agent needs to reach.

  2. Draw the parts that must not vary

    Refund windows, escalation thresholds, quiet hours, and who gets notified. These are logic nodes on the canvas, not sentences in a prompt.

  3. Let the agent take the open turn

    The customer phrases it however they like. The agent works out what they mean, looks it up, and answers from the record.

  4. Hand off cleanly when it should

    Low confidence, an explicit request for a person, or anything outside policy stops the run and passes the conversation on with everything already gathered.

Healthcare

A patient forgets a booked appointment because the only reminder was a call they missed.

The problem

No-shows are expensive, and the fix is not a louder reminder. It is making rescheduling take fifteen seconds on a channel the patient already has open, without a receptionist in the loop.

How RoutMe resolves it

The agent offers slots that are genuinely free in your scheduling system and writes the chosen one back before confirming. Anything requiring clinical judgement is handed to staff with the details already collected.

Ends without a human

  • Rescheduling and cancellation against live availability
  • Appointment details, location, and preparation instructions
  • Prescription readiness and collection windows

Typically connects to

  • PostgreSQL
  • Salesforce

One turn, resolved

can't make tuesday 3pm, anything later that week?
I can move you to Thursday 28 Aug at 4:30pm or Friday 29 Aug at 11am, both with Dr Rao. Which suits? Your Tuesday slot stays held until you confirm.

Illustrative. Every value in the reply would come from a live lookup against the systems listed alongside.

Example flows

Appointment bookedReminderReschedule or confirm
Prescription readyPickup notificationConfirmation
Post-visitFollow-up surveyNext appointment

Travel & Hospitality

A delay changes everything about a guest's trip, and they hear it from the airport screen rather than from you.

The problem

Disruption is when service actually matters, and it is exactly when phone lines are saturated. Every one of those calls is a question with an answer in a booking system.

How RoutMe resolves it

The agent reads the booking and answers the disruption question directly, including what the alternatives are. Rebookings that need commercial judgement go to a person with the itinerary already attached.

Ends without a human

  • Booking details, check-in windows, and cancellation terms
  • Disruption questions answered from the live itinerary
  • Amenity, policy, and location questions from your content

Typically connects to

  • PostgreSQL
  • Salesforce
  • Contentful

One turn, resolved

my connection is cancelled, what happens to my hotel booking?
Your room at the Grand Marina is held under booking BK-7741 with a 4pm check-in and free cancellation until 10pm tonight. If you would like it moved to tomorrow, I can request that now and a coordinator will confirm within the hour.

Illustrative. Every value in the reply would come from a live lookup against the systems listed alongside.

Example flows

Booking confirmedCheck-in instructionsRoom ready alert
Disruption detectedAgent explains optionsCoordinator handoff
Post-stayFeedback requestLoyalty offer

Real Estate

A hot lead asks about a listing, and by the time someone follows up they have already toured somewhere else.

The problem

Property enquiries arrive at every hour and decay within them. Qualification is also genuinely conversational, since budget, timeline, and location come out in whatever order the person feels like saying them.

How RoutMe resolves it

The agent answers the listing question immediately from live inventory, qualifies against criteria you defined in the flow rather than in a prompt, and writes the lead into your CRM with the transcript attached.

Ends without a human

  • Availability, pricing, and specification questions from live inventory
  • Viewing slots booked directly into the calendar
  • Qualification captured and written to the CRM

Typically connects to

  • HubSpot
  • Salesforce
  • PostgreSQL

One turn, resolved

is the 2-bedroom on Harbour Street still available? and what's the actual floor area
Yes, unit B-1204 is available. Floor area is 90 m², with a covered parking space included, and it is currently listed at $640,000. There is a viewing slot on Saturday at 11am if you want it.

Illustrative. Every value in the reply would come from a live lookup against the systems listed alongside.

Example flows

Inquiry receivedAgent answersViewing scheduled
Viewing reminderFeedback requestOffer follow-up
Document requestedReminderReceived

SaaS

A trial signs up, opens the product once, and the onboarding email sits unread in a crowded inbox.

The problem

Activation depends on a user getting past one specific blocker, and which blocker it is differs per account. A broadcast sequence cannot know that, so it sends step three to someone stuck on step one.

How RoutMe resolves it

The agent reads the account's actual usage state before it says anything, so the nudge matches where the user genuinely is. Support questions get answered against your docs and their plan rather than a generic FAQ.

Ends without a human

  • Plan, seat, and billing questions from the account record
  • Setup blockers identified from real usage state
  • Feature questions answered from your own documentation

Typically connects to

  • PostgreSQL
  • HubSpot
  • Contentful

One turn, resolved

why can't I invite my team?
Your workspace is on the Starter plan, which includes two seats and both are in use. Upgrading to Team lifts that to twenty. I can send the upgrade link, or flag this to sales if you want annual pricing first.

Illustrative. Every value in the reply would come from a live lookup against the systems listed alongside.

Example flows

SignupSetup checkTargeted nudge
Usage limit hitExplain limitUpgrade link
Support questionAgent resolvesTicket if unresolved

Fintech

A login attempt is waiting on an OTP, and every extra second of delivery lag is a user abandoning the flow.

The problem

Verification and transaction messaging have to be fast and provably delivered. The conversations around them, a disputed charge, a stalled KYC, a statement request, are exactly the ones customers will not accept a canned answer for.

How RoutMe resolves it

Authentication messages go out on the authentication category with delivery tracking on each one. Around them, the agent answers account questions from your own systems, with anything consequential held behind flow logic rather than model judgement.

Ends without a human

  • Statement, balance, and transaction lookups
  • KYC progress and which document is still outstanding
  • First-line dispute triage before a specialist takes over

Typically connects to

  • PostgreSQL
  • Salesforce
  • MongoDB

One turn, resolved

there's a charge on my account I don't recognise, $420 yesterday
I can see a $420.00 debit on 25 Aug to a merchant listed as SPL RETAIL. That is the trading name for a store you have paid twice before. If it still looks wrong, I will open a dispute and a specialist will call you within one business day.

Illustrative. Every value in the reply would come from a live lookup against the systems listed alongside.

Example flows

OTP deliveryVerificationConfirmation
Transaction queryAgent explainsDispute if unresolved
KYC reminderDocument uploadApproval

D2C & eCommerce

A customer places an order, goes quiet on your app, and then checks WhatsApp a dozen times a day.

The problem

The single highest-volume question in retail support is some version of where is my order. It has a definitive answer sitting in a database, and it still reaches a human because the messaging channel cannot see that database.

How RoutMe resolves it

The agent matches the customer to their order, reads the live shipment state, and answers with the actual tracking position. Returns are checked against the real purchase date rather than a guess at the policy window.

Ends without a human

  • Order and delivery status, answered from the live record
  • Return eligibility, evaluated against the real purchase date
  • Product and stock questions, read from the catalogue

Typically connects to

  • Shopify
  • PostgreSQL
  • Zendesk

One turn, resolved

hey, any update on my order? it was supposed to be here friday
Your order ORD-48210 left the regional hub yesterday and is out for delivery today before 7pm. Friday's slot was missed because of a courier delay at the hub. Want me to send the live tracking link?

Illustrative. Every value in the reply would come from a live lookup against the systems listed alongside.

Example flows

Order confirmedShipping updateDelivery notification
Cart abandonedReminderDiscount offer
Product inquiryAgent resolvesHuman handoff

EdTech

An assignment deadline passes because the in-app notification was never opened.

The problem

Engagement nudges only work if they are specific. A reminder that names the assignment, the deadline, and where the learner actually stopped is a different message from a generic prompt to log in.

How RoutMe resolves it

The agent reads progress before it writes, so a nudge references the real module and the real due date. Questions about deadlines, fees, or certificates get answered rather than routed to a form.

Ends without a human

  • Deadlines and progress, read from the learner record
  • Fee, enrolment, and certificate status questions
  • Content and schedule queries answered from your CMS

Typically connects to

  • PostgreSQL
  • MongoDB
  • Contentful

One turn, resolved

did I miss the deadline for module 4?
Module 4 is due Sunday 31 Aug at 11:59pm, so you have four days. You are through 6 of 9 lessons. The last submission slot is the quiz, which usually takes about twenty minutes.

Illustrative. Every value in the reply would come from a live lookup against the systems listed alongside.

Example flows

EnrollmentWelcomeCourse schedule
Assignment dueProgress-aware reminderSubmission link
Course completeCertificateNext course

Logistics & Delivery

A customer refreshes a tracking page instead of being told the moment something changes.

The problem

A failed delivery attempt costs more than the entire conversation that would have prevented it. The information needed to prevent it, a working time window, a gate code, a neighbour, only exists in the customer's head.

How RoutMe resolves it

Exceptions open a conversation rather than a notification. The agent offers real reschedule slots, captures delivery instructions, and writes both back to your system before confirming anything.

Ends without a human

  • Reschedules booked against genuine route availability
  • Delivery instructions captured and written back
  • Address and exception queries handled without a call

Typically connects to

  • PostgreSQL
  • MongoDB
  • Salesforce

One turn, resolved

nobody was home, can you try tomorrow evening?
Rescheduled for Wednesday 27 Aug between 6pm and 9pm, same address. I have added a note that the parcel can be left with the building security desk if you are out. Reference stays SHP-99120.

Illustrative. Every value in the reply would come from a live lookup against the systems listed alongside.

Example flows

Pickup scheduledIn transitOut for delivery
Delivery exceptionReschedule optionsConfirmed
DeliveredProof of deliveryFeedback

Use case questions

Something missing? Talk to us and a person will answer.

Don't see your industry?

If your most common inbound message has an answer sitting in a system somewhere, this works, and the build is the same four steps.