How to turn inbound messages into booked meetings

If people are messaging you on WhatsApp, LinkedIn, Instagram, or your website chat, you already have inbound demand. The problem is almost never generating interest. It's responding to it fast enough, consistently enough, across enough channels, that the interest doesn't go cold before someone gets back to it.

Usetta is built around one specific idea: every inbound message carries an intent, and the fastest path to a booked meeting is reading that intent correctly and acting on it immediately, not routing the message to a queue and hoping someone checks it within the hour.

Every message gets classified before anyone replies

When a message lands in your unified inbox (from WhatsApp, LinkedIn DM, Instagram, Facebook Messenger, or your website's chat widget), Usetta reads it and classifies it into one of six intent types before generating a response:

• Interested: genuine curiosity about what you offer
• Question: a specific ask (pricing, features, availability)
• Objecting: hesitation or a stated concern
• Booking: ready to schedule a call or meeting
• Unsubscribe: wants to stop hearing from you
• Not relevant: spam, misdirected messages, noise

This matters because "someone messaged you" isn't a single event that deserves a single kind of reply. A pricing question and a booking-ready lead need completely different responses, and reading that difference correctly, on every message, at whatever hour it arrives, is exactly the part that doesn't scale with a human inbox.

Leads move through a funnel, not a list

Every contact who messages you gets tracked through a lead state that updates automatically as the conversation develops:

A first-touch message starts a lead at cold. Once they've replied and there's a real back-and-forth, they move to engaged. This is the state where most of the actual qualifying work happens, and where Usetta's replies are doing the most: answering questions, handling objections with your objection playbook, and steering the conversation toward a natural next step. Strong buying signals push a lead to hot. Booking intent moves them to booked, which is also the trigger for auto-scheduling (more on that below). This isn't a label you set manually: it's inferred from the conversation itself, every time a new message comes in.

The practical value here is visibility: you can see at a glance which conversations are genuinely warming up versus which are still cold first-touches, across every channel, in one inbox, instead of that context living in five different app notifications.

Autopilot or Draft: you choose how much control to keep

Not every team wants AI sending messages under their name with zero review, and Usetta doesn't assume you do. Every channel can run in one of two modes, independently:

• Autopilot: Usetta replies directly, typically within 30 seconds, around the clock. No human in the loop.
• Draft: Usetta writes the reply and queues it for review. You read it, edit if needed, and send with one click.

A common pattern: run high-volume, lower-stakes channels like Instagram or website chat on Autopilot, and keep something like LinkedIn (where the tone matters more, or the accounts are higher-value) on Draft until you trust the pattern of replies it's generating. You can switch either at any time.

Replies are shaped by what you actually tell it

None of this works off a generic prompt. Usetta replies are generated from a 12-field knowledge base you fill in once: your company description, ideal customer profile, tone of voice, primary goal, objection playbook, how you want pricing questions handled, social proof you want referenced, and, just as importantly, a set of do-not-say rules that are enforced as hard constraints on every single reply, not just suggestions. If there's something Usetta should never claim, promise, or discuss, that rule holds on every message, on every channel, without exception.

When a lead is ready, the calendar link sends itself

The moment a message expresses booking intent, like "can we do a call Tuesday," "I'd like to book a demo," or "what times are open this week," Usetta detects it and sends your calendar link automatically, at the moment the intent was expressed, not whenever someone next checks the inbox. That's the gap that actually costs meetings: a lead ready to book right now, met with silence for six hours, cools off. Usetta closes that gap by design.

Getting started

The fastest path to seeing this work on your own inbound: connect one channel (website chat is usually the quickest, live in under 10 minutes), fill in your knowledge base honestly (vague inputs produce vague replies), and start that channel in Draft mode for the first few days so you can see exactly what it would have sent before switching it to Autopilot. Most teams add a second channel once the first is producing replies they'd have written themselves.