It surfaces the problem before it pitches, tells a prospect from an existing customer, and books the call rather than leaving somebody parked on your pricing page.
"Our booking system is garbage." "Our site keeps going down." "The app is stuck again." Every one of those is a problem somebody wants solved, which is the thing you sell. The agent treats them as leads. It treats them as support only when the broken thing is something your business already built, sold or runs for that customer, because getting this backwards is expensive in both directions: file a ticket for a prospect and the deal dies, pitch an existing customer whose system is down and you lose the customer.
It also reads who it is talking to. A solo founder and a two-hundred-person firm land in the same inbox, and enterprise discovery questions asked of a small job read as a waste of somebody's time. Someone gathering information wants educating. Someone comparing vendors wants a straight answer on what you do well. Someone who has already decided wants to move, and the fastest way to lose them is to ask about their budget. If a buyer hands over contact details and names an action, the agent fires the close on that turn and backfills only what the tool cannot go without.
That matters most on the comparison conversation, which in this category is where deals are actually won. A prospect weighing you against another vendor is asking a real question, and the answer that converts is a clear statement of what your business does well rather than a deflection into a demo request. The agent answers from your own material, then moves to the scoping call or the proposal, with what they need and who they are already attached.
A broken thing on their side is a lead. A broken thing you already delivered is support. The agent decides which before it does anything else.
It matches the depth of its questions to the scale of what is being asked for, so a small job does not get an enterprise interrogation.
Educating, comparing, or ready to move. Someone in buying mode gets the close on that turn, not a discovery script.
Answered from your own documents. Capability you have not documented is not something the agent will promise on your behalf.
Website chat, WhatsApp, Instagram, Messenger, Telegram and LINE, so an enquiry that starts on a founder's phone finishes in the same thread your sales team reads.
Every channel we supportIt books the scoping call into your Google Calendar and pushes the contact and deal into HubSpot with the problem description attached.
What it connects toEvery plan comes with a pool of credits, and one reply costs one credit at the level most businesses run on. The conversation above, where the agent reads your material, checks the calendar and writes back, is a single credit. You choose how deep each inbox thinks; nothing else in the product meters.
How credits workBy separating a problem in something you already built, sold or run for that customer from a problem in something they want built. The first goes to support, the second is treated as a lead. That distinction is the first thing it resolves.
From your own documents. Where a number is not in your material it says so and moves to the call, rather than inventing a figure you then have to walk back.
It answers with what your business does well, from what you have documented, and then moves toward the next step. It does not deflect the question, because in this category that is the conversation that decides the deal.
On Growth, yes. The support agent works service conversations and opens tickets that route into Jira or HubSpot and stay linked to the thread they came from.
Upload what you already have, connect a channel, and run real conversations through it before you pay for anything. Seven days, card saved, not charged.