An AI chatbot for a service business helps visitors find out whether you can help, understand the process, and send a useful enquiry. Chirps can answer from your business information and collect project details in a configured form. Your team still decides the scope, confirms any quotation, and handles the work.
Imagine someone reading your renovation website after work. They have a small kitchen project, live near the edge of your service area, and do not know whether you handle design as well as installation. Your contact page asks them to “Get in touch,” but it does not answer the questions that would make contacting you feel worthwhile.
A helpful assistant makes that first step easier. It can explain the relevant service, check the published coverage information, and offer a short enquiry once the visitor knows you may be a fit. This guide uses an illustrative service-business example and applies the same approach to consultants, installers, repair companies, and other businesses that sell work rather than a standard shopping-cart item.
- Find the questions people ask before they contact you
- Answer first, then ask for details
- Prepare business information your assistant can explain confidently
- Build a service enquiry assistant from a prompt
- Collect the information your team will actually use
- Handle quote requests without inventing prices
- Make follow-up part of the design
- Add appointments when a real scheduling process is ready
- Test the conversation as a potential customer
- Measure enquiry quality and response, not just totals
- Questions about service-business chatbots
- Give interested visitors a reason to take the next step
Find the questions people ask before they contact you
Your best starting point is the work your team already does on the phone or by email. Do customers ask whether you cover a certain town? Whether a visit is needed before a quote? Whether a service includes materials? These are buying questions. Clear answers can help a visitor decide to enquire without forcing them to wait for a staff member just to understand the basics.
Choose a small set of services to explain well. An assistant that accurately describes your installation service is more useful than one that vaguely promises to handle anything. Prepare the eligibility conditions, exclusions, typical process, and the customer’s next step. If you cannot offer a particular service, say so and give the most relevant supported alternative.
| Before the enquiry | What the visitor needs | What you should prepare |
|---|---|---|
| Can you help with this project? | A clear explanation of the relevant service and exclusions. | Current service pages and examples of accepted work. |
| Do you work in my area? | A reliable coverage answer or a way to confirm an exception. | Maintained locations and any travel conditions. |
| How does the process work? | What happens after contacting the business. | The enquiry, assessment, quotation, and booking process. |
| What will it cost? | Published pricing conditions or the information needed for a quote. | Approved price information and a clear distinction between an estimate and a confirmed offer. |
Answer first, then ask for details
A visitor asking whether you install a particular product should not have to submit a phone number before receiving a basic answer. Start with the approved service information. If your business can help, offer the next step and explain its purpose: “If you send the project location and a short description, our team can review it and follow up.”
This sequence respects the visitor’s effort. It also improves the meaning of an enquiry. The person has learned what you offer and chosen to continue, rather than completing a form simply to find out whether they were on the right website. Do not confuse this with a guarantee of lead quality. Your team still needs to review the request.
Ask one useful clarification at a time. If coverage depends on location, ask for the town or postcode. If the project type is unclear, ask which service they need. Do not insist on an entire questionnaire before explaining what you can do. A conversation should reduce uncertainty, not reproduce a long contact form as a series of chat messages.
Prepare business information your assistant can explain confidently
Give Chirps the public website and relevant business files, then review what it learns. The most useful sources are often service descriptions, coverage information, common questions, pricing conditions, and a document explaining your normal process. Include the details a knowledgeable team member would use to answer the visitor’s first question.
Make exceptions visible. “We provide commercial cleaning” may hide restrictions on building size, access hours, or specialist work. A consultant’s fixed-price package may exclude implementation. A repair company may not support every brand. These conditions protect both the customer’s expectations and your team’s time when they are explained early.
Do not let outdated material compete with current information. A brochure can describe last year’s service area or an old introductory price. Choose one authoritative version, update the website, and remove or clearly label superseded files. The assistant should explain your business; it should not have to decide which of two contradictory sales promises you still intend to honour.
Private staff notes need a separate decision. Your team may hold supplier costs, internal margins, or customer-specific exceptions that do not belong in a visitor-facing answer. If you connect a supported knowledge source, approve the exact pages or folder intended for customers. A useful service assistant does not require unrestricted access to every business document.
Build a service enquiry assistant from a prompt
- Describe the business, its website, and the services customers ask about. State the outcome you want: a useful enquiry, a callback request, or a configured consultation.
- Review Chirps’s business summary and sources. Correct the service area, exclusions, contact information, and any pricing conditions.
- Choose a conversation style that fits your customers. Tell the assistant to clarify relevant project needs and avoid promises that require staff approval.
- Configure a short lead form with the details your team needs to reply. Explain the expected response and who receives the enquiry.
- Test common questions, a project outside your scope, an unknown price, and an unsupported location.
- Install the widget, check the mobile experience, and assign responsibility for reviewing the first real leads.
The Agentic Builder can guide preparation and supported connections. You can refine the assistant in the dashboard afterwards, including its knowledge, appearance, and business actions. For a WordPress site, use the WordPress installation guide. For other platforms, follow the integration instructions for the site that will display the widget.
Keep the first release understandable. A service explanation and a useful enquiry form are a complete starting point. Add scheduling or a connector when the corresponding business process is ready. Turning on more tools before someone owns the follow-up creates a more complicated interface without necessarily creating a better experience for the customer.
Collect the information your team will actually use
The right fields depend on the work. For a renovation enquiry, the team might need project type, location, a short description, and one contact method. For a consultant, the business goal and company context may matter more. Ask the people who handle enquiries which missing details usually force a second email. Use that answer to design the form.
Separate essential details from helpful extras. Name and a reply address may be required. A preferred callback window can be optional. Budget may help for some projects, but an early-stage visitor might not know it yet. Allow a useful enquiry to proceed without making the customer invent information just to satisfy a required field.
Be careful with attachments and sensitive information. If a project needs a document, explain what to share and avoid collecting unrelated personal records. Keep the conversation focused on what is necessary for the service enquiry. Your staff should handle any later exchange that needs a different level of access or a formal review process.
| Field | Why it may help | A sensible treatment |
|---|---|---|
| Project type | Routes the enquiry to the relevant service. | Use clear choices with an “other” or short-description path where appropriate. |
| Location | Checks coverage or travel needs. | Ask for the level of detail needed now, not automatically a full address. |
| Contact method | Lets your team reply. | Explain how the business will follow up. |
| Preferred timing | Helps staff understand urgency and availability. | Do not interpret it as a confirmed appointment. |
| Additional context | Reduces repetitive questions during follow-up. | Keep the prompt short and relevant to the work. |
Handle quote requests without inventing prices
A question about cost is a reasonable buying question. If you publish a fixed price for a clearly defined service, the assistant can explain that information and its conditions. If the price depends on inspection, size, materials, or a bespoke scope, it should explain the dependency and collect the information your team needs to assess it.
Avoid turning a broad question into an invented number. “What would a new kitchen cost?” does not contain enough information for a reliable quotation in many businesses. A useful response describes the quotation process and offers to send the project details for review. It can mention an approved published range if one exists, while making clear what that range does and does not include.
Keep the terms consistent. An enquiry is a request for contact. An estimate is indicative information. A quote is an offer made under your business’s process. A booking is an agreed time. The assistant should not move between those meanings simply because a confident answer feels more persuasive. Honest expectations make the subsequent human conversation easier.
Make follow-up part of the design
Decide who receives each type of enquiry and how they review it. A saved lead in Chirps is useful only if somebody acts on it. Your team can inspect the conversation, read the submitted details, and follow up with the customer’s original goal in view. Assign a backup for periods when the primary person is unavailable.
Where configured and supported by the plan, business-event notifications can reach Slack, Teams, or an automation destination such as Zapier or n8n. Select the events that matter and explicitly test the destination. A workflow accepting a request is not proof that the staff member has seen it or that the downstream process completed.
Tell customers what they can expect. If your team normally replies during business hours, say that instead of promising a call within minutes. If you offer human takeover in the inbox, define the circumstances and staffing hours. A clear callback expectation is better than an apparently immediate support option that nobody monitors.
Add appointments when a real scheduling process is ready
Some service businesses benefit from letting visitors arrange a consultation directly. Configure the service, duration, availability, timezone, and calendar connection before offering it. A requested time should not become a confirmation until the actual booking flow succeeds. If a slot is unavailable, offer another valid time or collect an enquiry for the team.
The appointment booking guide covers this in more detail. Keep the distinction between an initial consultation and the delivery of the full service. Booking a discussion about a building project, for example, does not reserve an installation crew or commit the business to a final price.
Test the conversation as a potential customer
- Ask whether the business covers a supported area and an unsupported one.
- Describe an ambiguous project. Check whether the assistant asks a relevant clarification.
- Request a price that requires assessment. It should explain the process without inventing a quote.
- Submit a test enquiry and confirm the saved lead, context, and notification destination.
- Ask to speak to someone outside staffing hours. The response should set a realistic expectation.
- Use the widget on a phone, including the keyboard, form validation, and closing the conversation.
Read the experience for tone as well as factual accuracy. A reply can be technically correct but sound like an internal procedure. Use the customer’s terms, explain the useful next step, and avoid jargon that assumes they already understand your service. Keep your most important conditions readable rather than burying them in a long answer.
Measure enquiry quality and response, not just totals
Look at how many enquiries contain usable details, how quickly the team follows up, and whether the projects fit your service scope. Review questions that caused confusion and requests that should have reached a person earlier. A higher lead count is not automatically better if staff spend more time sorting unrelated projects.
Connect outcomes to your normal sales process. Distinguish a submitted enquiry, a completed consultation, an accepted quotation, and paid work. They are different stages. If you compare performance over time, account for changes in advertising, traffic, seasonality, and service availability. Do not attribute every new job to the assistant simply because the customer once used chat.
Use the findings to improve the site too. Repeated service-area questions can justify a clearer coverage page. Repeated confusion about what a package includes can lead to a better service description. Update the source and check the next conversations. The strongest experience combines a useful assistant with a website that explains the business clearly.
Questions about service-business chatbots
Can I start without an online booking system?
Yes. Start with service answers and a short enquiry form. Scheduling is a separate configured capability. A good callback or quote-request flow can be useful before you offer appointment times inside the conversation.
Will Chirps automatically quote every project?
No. It can explain approved pricing information and collect the context needed for assessment. Bespoke scope, commercial exceptions, and a confirmed quotation should follow your business’s actual approval process.
Can an assistant serve several locations?
It can explain maintained location and coverage information. Make any differences clear, including services, hours, or contact routes. Do not assume every branch has the same availability or that training alone connects separate scheduling systems.
How do I choose a plan?
Review assistant capacity, monthly AI credits, team access, and the tools you need on the current pricing page. Begin with the customer workflow and expected usage. Visitor messages are free; completed replies and additional AI work consume the appropriate credits.
Give interested visitors a reason to take the next step
Choose the questions your customers need answered before they trust you with a project. Prepare accurate sources, make the enquiry short, and put a real person behind the follow-up. The purpose is a better first conversation: the visitor understands what you can do, and your team receives enough context to respond usefully.