Your team does the same sales and support work by hand every day: answering the same questions, checking orders and accounts, taking bookings, copying leads into a sheet. We build a custom AI chatbot that does this work for you, for any software or app, from your own information. It sells before people buy, supports them after, and hands the rest to your team.
See it work
Sales, support and the hand-off, in one chat.
Three example conversations: a demo booked, an order looked up in your system, and a refund passed to a person. No one on your team did any of it by hand.
Sales: book a demo
- Does your software work for a business with 3 branches?
- Yes. The Business plan covers several branches, each with its own staff and reports.Plans and pricing
- Would you like a 20-minute demo? I can book it now.
- Yes, Thursday afternoon.
- Demo booked for Thursday 3:00 pm and sent to your sales team
Support: order status
- Where is my order 10482?
- I can check that. What is the phone number on the order?
- +1 555 014 2236
- Checked in HolaReply, never sent to the AI
- Order 10482 left our warehouse on Monday and is with the courier.Your order system (read-only)
Hand-off: a refund
- I was charged twice. I want a refund.
- Refunds are handled by our billing team, so I have passed this on with our whole conversation. They will reply by email.
- Ticket opened for Billing, with the conversation
Manual work, automated
The work your team does by hand, done by the chat.
Sales and support tasks that take hours every week, and what happens to them.
| Today, by hand | With your AI chatbot |
|---|---|
| Answering the same questions all day | Prices, plans, how-tos and policies answered at once, with the source |
| Checking an order, booking or account by hand | Read from your system and told to the customer, for them only |
| Taking bookings and callbacks by phone | Booked in the chat, into your calendar or system |
| Copying leads from chats and emails into a sheet or CRM | Every lead saved with the whole conversation, sent where your team works |
| Reading every support email to decide who handles it | Simple ones answered; the rest a ticket for the right person |
| Following up people who asked and went quiet | Their question and contact kept, with a reminder for your team |
The workflow
How one question is automated.
From the customer’s question to your team, without anyone copying, checking or typing it in.
- 1Customer asksOn your website, in your app or your mobile app, any time, in any language.Where is my order 10482?
- 2HolaReply checks the rulesLocked topics go to a person. Names, emails and phone numbers are removed before the AI.Not a locked topic
- 3Reads your systemThrough a read-only door: orders, stock, bookings, accounts. Only what this answer needs.Order 10482: shipped Monday
- 4Answers or actsReplies with the source, or books, opens a ticket, asks for a callback.Answered in seconds
- 5Your team gets the restLeads and tickets with the whole conversation, in the Desk, by email or in your CRM.Nothing to copy by hand
One question, start to finish. The example is shown in grey under each step.
Sales and support
One chatbot that sells and supports.
The same assistant talks to people before they buy and helps them after, from your software’s own information.
Sales: before they buy
- Explains your plans, prices and features from your own pages and documents
- Answers “does it do X?” and “which plan is right for me?” with the source
- Books a demo, a visit or a call in the chat
- Collects the lead (name, email, phone) and sends it to your sales team or your CRM
- Sends price talks, discounts and big orders to a person, every time
Support: after they buy
- Answers “how do I…?” from your help articles, guides and manuals
- Explains error messages and what to do about them
- Tells a signed-in customer about their own order, booking, payment or account
- Opens a support ticket with the whole conversation when it can’t help
- Answers in the customer’s language, day and night
What changes
Less manual work, more leads kept.
What a team typically sees in the first months. Switch between the charts.
Manual work
Hours a week your team spends on repeated questions
Where 100 questions go
Out of 100 customer questions
Leads kept
Leads saved a month, with the whole conversation
Is this for you?
Do you need custom development?
Many businesses don’t. Here is the honest line.
You don’t need custom work if…
- Your answers are on the pages of your website: HolaReply reads them today, with one line of code
- You have a few PDF or Word files: upload them yourself in the Desk (Knowledge base › Files)
- You want your own colour, logo, chat button or greeting: that’s in the settings on every plan
You need custom work if…
- The answers are inside your software or app, not on public web pages
- Customers ask about their own order, booking, payment or account
- You want the chat to do things: book, open a ticket, ask for a callback
- Leads and tickets should go into your CRM or helpdesk
- You want the chat inside your mobile app, or on a private server
One example
What changes, in one question.
Today
After custom work
How it works: your software opens a small, safe door that answers one question, “what is the status of this order?”. The chat first asks for the phone number on the order, so only the buyer sees it, and that check happens in HolaReply, never in the AI. Nobody on your team had to look it up.
What we build
Custom AI chatbot solutions on HolaReply.
Each one runs on HolaReply, so you also get the Desk, reports, lead capture and the chat your visitors already know.
Answers from your software or app
Your software sends its help articles, guides, plans and error codes to HolaReply as they change. For example: a booking app’s “how do I reschedule?” is answered from its own guide.
Live answers from your system
Stock, free slots, prices, order and delivery status, read from your system the moment someone asks. For example: “Is size 42 in stock?” gets today’s answer, not last week’s.
Each customer’s own account
A signed-in customer asks about their own payment, plan or profile. For example: “Why is my account still pending?” Only they see it, and it never reaches the AI.
Actions in the chat
Book a demo or an appointment, open a support ticket, ask for a callback or a quote, without leaving the chat and without anyone typing it in by hand.
Your CRM and helpdesk
Leads and tickets go straight into HubSpot, Zoho, Salesforce, Odoo, Zendesk, Freshdesk or your own system, so nobody copies them over.
Chat inside your mobile app
Today: a page of your website inside your app (a web view). Custom: a chat built into your Android or iOS app.
Many or difficult documents
Hundreds of files, scanned papers, Excel price lists or catalogues, turned into answers with the document named as the source.
Private servers and data rules
A separate server or your own, for banks, hospitals and companies with strict data rules.
An assistant for your own team
Staff ask about your procedures, HR policies and internal guides, and get the answer with the document.
Examples
Sales and support for any kind of software.
Typical projects, described without names.
A software company (SaaS)
Sales: visitors ask which plan fits them and book a demo in the chat. Support: customers ask how to export a report or what an error means, and get the steps from the help center.
A booking or service business
Sales: “How much is a home visit?” answered from the price list. Support: “Can I move my booking to Friday?” answered from the customer’s own booking, with free slots.
A store on its own system
Sales: “Is this in stock in blue?” read live from the stock. Support: “Where is my parcel?” read from the courier status, and bulk orders handed to sales.
App and software support
An AI chatbot for your app’s users.
Help articles, guides and error codes from your app, answered in seconds, in your users’ language. How app support works
Working together
What you give us, and what you get.
What we need from you
- A few lines about your business, your software or app, and who uses it
- The work your team does by hand today, in your own words
- Twenty or so real questions your customers ask (copy them from your emails or chats)
- Where the answers live today: your website, files, the app, an Excel sheet, your software
- Who should get the leads and tickets, and how (email, the Desk, your CRM)
What you get
- A written proposal in plain words: what we build, how it connects, the price
- The chatbot connected to your software, tested on a copy first
- Your rules: which topics always go to a person, what it may never say
- The HolaReply Desk for your team: conversations, leads, tickets, reports
- Help after launch: we read the first conversations with you and improve the answers
How a project works
From your idea to a live chatbot.
1. Tell us
Fill in the form below. Plain words are enough: what your team does by hand, what customers ask, and where the answers are today. You don’t need to be technical.
2. A short talk
We reply by email and ask a few questions, or call you if that’s easier. If you have a developer, we talk to them about the technical part.
3. Proposal
You get a written proposal with a fixed scope and price. Nothing starts until you say yes.
4. Build and test
We build it on HolaReply and test it on a copy of your site or app. You try it yourself before customers see it.
5. Live, and looked after
It goes live. We watch the first conversations with you, fill the gaps and keep the connection working.
Price
How the price is made.
Every project is different, so we quote after we understand yours.
What you pay
- A HolaReply plan for the chat itself, the same plans as everyone
- A one-time fee for the custom part, fixed in the proposal before any work starts
- No hourly surprises: a change of scope gets its own price, agreed with you first
What makes the custom part bigger or smaller
- Smaller: importing many documents, or a design that matches your brand
- Medium: one live connection, such as order status or stock
- Larger: customer accounts, several systems, or a chat built into a mobile app
The rules we keep
Custom, but never careless.
Only your information
The chatbot answers from what you connect, shows where each answer came from, and says so when it doesn’t know. It never makes things up.
Personal details stay out of the AI
Names, emails, phone numbers and account details are removed before any text reaches the AI.
It looks, it doesn’t change
Connections read only what an answer needs. Anything that changes data, such as a booking, is agreed with you first.
Yours to keep
Your data, conversations and leads are yours, and are deleted when you ask.
Plain words
Words you may see in a proposal.
- API
- A safe door your software opens so another program can ask it one question, such as “what is the status of order 10482?”. It answers only what the door allows.
- Read-only
- HolaReply can look, never change. It can read a stock level; it can’t change it.
- Web view
- A page of your website shown inside your mobile app, like a small browser. The chat works there without building anything new.
- Signed-in check
- Proof from your app that the person chatting really is that customer, so the chat shows them their own details and nobody else’s.
- CRM / helpdesk
- The software where your team keeps customers and support tickets, such as HubSpot, Zoho or Zendesk.
- NDA
- A confidentiality agreement: we keep what you show us private.
Questions
Custom development, answered.
I’m not technical. Can I still ask?
Yes. Tell us in your own words what your team does by hand and what customers ask. We work out the technical part, with your developer if you have one.
Which manual work can it take over?
Sales and support work that happens in conversations: answering questions, looking things up for a customer, taking bookings and callbacks, saving leads, opening tickets and passing them to the right person. Work that needs a human decision, such as refunds or discounts, stays with your team.
Do I need my own developer?
Not always. Documents, design and many connections we do ourselves. When the answer is inside your software, someone who can change it opens a safe door (an API) for us; if you have nobody, tell us and we’ll suggest a way.
Which software or app does it work with?
Any software or app your customers use: on the web, Android or iOS, ready-made or built for you. If it can share information safely, the chatbot can answer from it.
Can it read my database?
Only through a door you control, read-only, and only the fields an answer needs. We never ask for direct access to your database.
Which HolaReply plan do I need?
Any website or Shopify plan, or WordPress Pro or Business. Most custom work uses Business features such as live chat and routing; the proposal says which.
Will it change my website or app?
Only what is agreed in the proposal. Everything is tested on a copy first.
Do you work under an NDA?
Yes. Tell us in the form and we sign yours or send ours before you share anything.
Which languages?
The chatbot answers in your visitor’s language, including Bangla, English and mixed messages, from your content in any language.
What happens after it goes live?
We watch the first conversations with you, fix answers and gaps, and keep the connection working when HolaReply updates.
Tell us about your software or app
We reply by email with a few questions, then a written proposal with the scope and the price. No obligation.