Domain-pretrained understanding
Knows the common intents, edge cases and vocabulary of its vertical from day one. “Size swap”, “wrong fit” and “change this” all land on the same exchange flow.
Support agents that already know your domain
An exchange in e-commerce. A prorated downgrade in SaaS. A new slot at a clinic. Huematte agents are pre-trained on each domain's patterns, then grounded in your policies, so answers fit your business instead of a generic guess.
Open conversations
4I want to change this.
ExchangeIt said Tuesday. Where is it?
TrackingThe zip broke on day two
Damaged itemRefund for a ₹7,800 order
Handoff: Over limitPriya S.
Web chat
Returns policy, section 2.1. Unworn items can be exchanged within 30 days of delivery.
Exchange drafted
Linen overshirt, size M to size L. Pickup booked on confirmation.
The problem
General-purpose chatbots are fluent, but fluency isn't knowing that a return window, a proration rule and a reschedule policy are three different problems.
A generic assistant treats “change this” the same way everywhere, so it asks clarifying questions an experienced agent in your industry would never need to ask.
Teaching a general model your domain's edge cases means writing prompts, scripts and exceptions one ticket at a time, and repeating it every time a policy changes.
When the bot can't act, the customer gets a vague reply, a ticket number and a queue. The person who picks it up starts from zero.
The domain lens
Customers don't describe their problem in your team's vocabulary. Each Huematte agent reads the same short message through what its domain usually means by it.
“I want to change this.”
E-commerce
Exchange for another size, inside the 30-day window
SaaS
Downgrade to Starter with a prorated ₹1,240 credit
Healthcare
Move the Thursday slot, within the 12-hour rule
“Where is it?”
E-commerce
Live courier status and the promised delivery date
SaaS
The latest GST invoice, sent to the billing contact
Healthcare
Clinic location and room for the booked visit
“I was charged twice.”
E-commerce
Duplicate UPI payment matched to one order, refund started
SaaS
Two card charges found, handed to billing with IDs
Healthcare
Booking deposit checked, passed to the front desk
“Cancel it.”
E-commerce
Cancel free before dispatch, or book a return after
SaaS
Cancel at term end, with access kept until then
Healthcare
Cancel the visit and offer the slot to the waitlist
How it works
You don't build a bot. You pick the agent for your domain, point it at your rules, and check its work on your own history.
Start from an agent that already knows your vertical's intents, vocabulary and edge cases, not a blank prompt.
Connect your real return windows, plan rules, catalog and clinic calendars. The agent answers from these, and only these.
Replay your own resolved conversations. Compare each agent answer with what your team actually said before anything goes live.
Turn it on for web chat and email. It resolves what it can, and hands off what it shouldn't, with the full context attached.
Web chat, Email
Handoff: over limit, unclear, or asked for a person
What the agent actually does
Four things every Huematte agent does on every conversation, in this order.
Knows the common intents, edge cases and vocabulary of its vertical from day one. “Size swap”, “wrong fit” and “change this” all land on the same exchange flow.
Answers cite your own return, billing or scheduling rules. If no rule covers the question, the agent says so and hands off instead of inventing one.
Your ₹1,240 credit will be applied to the 25 Oct invoice.
billing-policy.pdf, section 4.3Mid-cycle plan changes are prorated to the day as account credit.
Starts an exchange, applies a credit or moves a slot, but only inside the boundaries you set. Anything over a limit is prepared, then passed to a person to approve.
When a case needs a person, your teammate receives the conversation, the detected intent, the records checked and the reason for handoff. Nobody asks the customer to repeat themselves.
Handoff note to Billing team
The domain agents
Every agent ships with the intents and edge cases of its domain already mapped. Pick the one that matches the questions your team answers most.
Returns, exchanges, order status, refund eligibility and address edits, checked against your own windows and conditions.
Plan changes, proration, invoices and failed payments, answered with the exact figures from your billing rules.
Booking, rescheduling, reminders and waitlists. Scheduling and admin only. Clinical questions go straight to your staff.
For verticals not covered yet: insurance claims, travel changes, education admissions and more.
Scope boundaries
Each agent has hard edges that you can tighten but never loosen past. These are written into the agent, not left to a prompt.
Never
Never
Never
Support analytics
Resolution by intent, the exact reasons for each handoff, and which questions are growing week to week, split by domain.
Handoff reasons
Sample viewOver action limit
No matching policy
Outside scope
Customer asked for a person
Illustrative layout. Your dashboard shows your own conversations.
Try the lens
A demonstration on sample data. Connect your own policies to see your real answers.
Returns & Orders agent reads this as: Exchange request
Returns policy 2.1: exchanges within 30 days of delivery
Outcome
Resolved within limits
Exchange drafted, pickup booked on confirmation