
A solution for service businesses
JediDesk for service businesses
Your specialists are on the job. JediDesk prepares the next enquiry.
Service · enquiry details · agreement with your team
A customer asks about pricing, wants to arrange a visit or needs service details while your team is busy working. JediDesk explains your terms, asks the right questions and prepares the enquiry for your administrator. The service, scope, city and preferred time stay together in one conversation. Your team starts by agreeing the details, and the customer understands the next step.
Hephaestus meets modern service. An artistic AI concept, not a photograph of a client company.
Communication in service businesses
“How much does it cost?” is only the start of an enquiry.
A short message leaves details to clarify: which service is needed, where the work will take place and what it involves. Gather those details before the conversation with your administrator so your team can agree the work with the customer more easily.
The service depends on the situation
For cleaning, the floor area and type of premises matter; for installation, the kind of work matters. Questions need to fit your service.
Your team is often working on site
A specialist is doing the job while new questions arrive in chat. Answers about arrangements can be prepared in your knowledge base beforehand.
Preferences need to be agreed
The city, service format and preferred time help your administrator check what is possible and suggest the next step.
Service continues after an order
Existing customers ask about service terms, enquiry progress or invoice details. These questions need their own information source and someone responsible for answering.
Before automation
What makes the path from message to order harder
The enquiry lacks details
“I need cleaning” or “I need a technician” does not yet explain the scope. Your administrator spends the start of the conversation on basic questions.
Routine answers distract your team
Service areas, what is included, working hours and how to place an order recur across different chats.
Pricing expectations do not match
The customer sees a starting price but does not know what affects the estimate for their job or which details need clarification.
Follow-up questions start from scratch
Without the earlier conversation, the operator has to establish which service is involved and what your team has already done to help.
Automation use cases
Five situations where JediDesk prepares the conversation for you
Let AI explain your services and gather the initial details. Your administrator receives context for an estimate, a visit arrangement or support for an existing customer.
Help customers choose the right service
“I need post-renovation cleaning. What does it include?”
The assistant explains what your services include and how they differ, using your materials. It clarifies the need and passes unusual questions to your administrator.
Advice from your knowledge baseThe customer understands which service to discuss and what information to provide for an enquiry.
Gather the details for an estimate
Someone asks about pricing but has not yet described the site or scope of work.
AI asks the agreed questions: type of work, city, floor area or other necessary parameters. It records the customer's own answers and passes them to your team. The responsible person agrees the final price.
An enquiry with the context you needYour administrator sees the initial information and can move on to a specific discussion.
Prepare a call-out request
“I'd like to book the service for Thursday afternoon.”
The assistant collects the preferred day, type of work and contact method. Your team checks the schedule, location and whether the job can be done. Rescheduling requests also need your administrator's confirmation.
Enquiry and handover workflowPreferences are recorded, and the customer knows who will agree the visit.
Support an existing customer
“Who can help me check my enquiry's progress or invoice details?”
AI explains how to get help. It can retrieve personal details or status only from a configured, current source after verifying the customer. If information is missing, ambiguous or outdated, it brings in an operator.
Data from your systemThe customer receives verified information or a conversation with the person responsible.
Pass a complex question to a specialist
The customer is unhappy with completed work or has a question your materials do not cover.
The assistant helps describe the situation and passes the conversation history to the responsible person. Your team agrees technical assessments, additional work and decisions about complaints.
Handover to a person with conversation historyThe specialist joins with the enquiry already explained, making it easier for the customer to continue.
How the solution works
Question → details → enquiry → agreement
The assistant prepares the enquiry; your team agrees how to carry out the work. The customer sees a clear path from their first message to the next step.
- 01

The customer describes their need
They explain which service they need or ask about terms and pricing.
- 02

AI asks for clarification
It gathers the necessary job details using your company's workflow.
- 03

It prepares the enquiry
It passes the service, scope and customer preferences to your administrator.
- 04

Your team agrees the next step
They check feasibility, the estimate and schedule, then confirm the next action.
Capability map
What a service company's assistant handles
From the first question to handover to your administrator: six areas of customer service. Each has defined materials, data or a responsible person.
The customer writes in a connected chat or messaging channel

Services and terms
Explains what the service includes and how to enquire.
Source: Current company materials
Job details
Clarifies the type of work and required parameters.
Source: Customer responses
Estimate preparation
Gathers context for a cost estimate.
Source: Price list + agreement with your team
Call-out request
Records the city and preferred time.
Source: Customer + administrator's confirmation
Ongoing service
Answers from a source or brings in an operator.
Source: Connected data after customer verification
Complex enquiries
Passes the situation and history to a specialist.
Source: Conversation + handover rules
The customer understands the next step. Your team has the details for an estimate, an arrangement or support.
Illustrative workflow. Schedules, personal enquiry statuses and invoice details require a separately configured source and access rules.
Channels and integrations
Meet customers where they already message you
Connect the channel you need and your company's materials. Enquiry, invoice or schedule data can be added once the sources and available actions have been defined.
Website chat
Questions alongside service descriptions, terms and examples of your work.
About the channelTelegram
Enquiries and service questions through your company's connected bot.
About the channelEnquiries prompted by work photos, recommendations and posts about your services.
About the channelYour service knowledge
Your services, scope of work, pricing rules, service area and contacts. The person responsible for these materials keeps them up to date.
How to connectCRM or business system
Enquiry creation, status retrieval and schedule access are configured for a specific system. Its API and access permissions are checked before launch.
How to connect
Example conversations
Your administrator sees the job, not just “How much?”
Illustrative conversations show the proposed workflows. These are hypothetical examples for a service company, not real messages or a deployment at a particular cleaning business.
- 01The customer's need
- 02Service details
- 03Agreement with your team
Prepare a cleaning enquiry
A service company's website chatThe floor area and description are provided by the customer. Your team agrees the final scope, price and visit.
Your administrator starts with a specific job and the customer's preferences.
Continue the conversation about an enquiry
The service's connected messaging channelS-124 is a fictional reference for this example. In this workflow, your team makes changes and verifies the customer.
The change request stays with the conversation history, and the responsible person confirms the arrangement.
Results and benefits
Prepare the next order while your team completes the current one
The assistant gathers the practical details of an enquiry. During a trial, check how complete enquiries are and which repeated questions your administrator no longer needs to ask manually.
Take repeated explanations off your team's hands
AI explains your service area, what is included and how to get help, using prepared materials.
Move on to discussing the job
The service, parameters and preferences are already in the conversation. Your administrator sees what needs checking for an estimate.
Set clear expectations
The customer knows what the service includes, which details need clarification and who will confirm the time and price.
Continue support with context
Complex questions are handed over with a description of the situation and conversation history.
Customer experience
How businesses use JediDesk

SHERIFF · customer support
Customer answers and handoff to the team
Explore the SHERIFF case studyAI-generated case illustration, not a photograph of SHERIFF employees. Process description based on the public case study.

NarsCars · car rental
Advice before booking
View a related case studyOriginal NarsCars photo from the case materials

Shop For Cars · car accessories
Help choosing car accessories
View a related case studyProduct visual from the Shop For Cars case study


TANOYA · cosmetics
Cosmetics recommendations from the catalog
View a related case studyIllustrative visual from the TANOYA case study. Process description based on the case materials.
About SHERIFF
Customer support after a service is connected
AI-generated case illustration, not a photograph of SHERIFF employees. Process description based on the public case study.
Security group SHERIFF uses JediDesk AI for customers' information requests. The public case study describes retrieving an account balance through the company's API and passing complex questions to an operator with context. This is an example of support for existing customers of a service company. The cleaning and technician call-out requests above are separate illustrative workflows.
- The balance response relies on an integration with the company's system.
- A person continues complex enquiries with the context preserved.
Built around your process
Your services, your rules, your next step
Advice based on your company's knowledge
You define the services, terms and questions to ask. The assistant uses those materials in the context of the enquiry.
AI assistant capabilitiesAI and your team in one conversation
An administrator or specialist joins the enquiry with the conversation history preserved. Handover is configured according to your rules.
Chat for AI and peopleA gradual launch
Start with advice and enquiry preparation. Add business system data for a specific task after checking the connection.
Integrations for your processLaunching the solution
Choose a service and test the first enquiries
To get started, you need clear materials and someone responsible for enquiries. Setup time depends on data readiness and the connections you need.
- 1
Describe one service
Prepare the scope of work, terms, service area, pricing rules and contacts. Assign someone to keep the information up to date.
- 2
Choose the questions you need
Agree which details help your administrator: job type, city, scope, preferred time and contact method.
- 3
Configure handover
Define who handles new enquiries, existing customers and complex questions. Agree who confirms arrangements.
- 4
Test real situations
Walk through an incomplete enquiry, a pricing question, rescheduling and an unknown service. Make sure your team receives the details it needs.
Before you start
Frequently asked questions
About pricing, visits, enquiries and support for existing customers.
Which service companies is this workflow suitable for?
This page describes enquiry handling for businesses that need to clarify a job before providing a service: cleaning, installation, workshops and maintenance. Questions and the knowledge base depend on your work. Support for existing customers can be configured separately. The SHERIFF case study shows information requests at a security company; it does not demonstrate automatic technician dispatch or deployment across every sector listed here.
Can the bot confirm a visit or appointment on its own?
In the proposed basic workflow, AI collects an enquiry and time preferences, while your administrator checks feasibility and confirms the arrangement. A submitted request does not mean a specialist has been assigned. Automatic booking requires separately configured access to the current schedule and confirmation that the action succeeded. These conditions are agreed for your system before that workflow is launched.
How does the assistant answer pricing questions?
It explains the current price list and pricing rules you have prepared. If the price depends on floor area, type of work or other parameters, the assistant clarifies them and passes the details to your team. A starting price needs to be clearly identified as such. The responsible person agrees the final estimate and additional work. If information is missing, AI does not invent a price or promise that the service scope is already final.
What information should an enquiry collect?
Agree the minimum information with your administrator: the required service, city, job description, necessary parameters, preferred time and contact method. Questions will differ for different jobs. The customer's own information helps prepare the conversation but does not replace an inspection or professional assessment. Ask for an exact address and additional details only at the stage where the agreed process requires them.
Can AI see enquiry status and invoice details?
Only if a current information source has been defined and connected. Personal information is provided after the customer has been verified under your company's rules; an enquiry reference alone is not a universal access permission. If a record cannot be found or the information is outdated or ambiguous, hand over to an operator. The public SHERIFF case study demonstrates an integration, not default access to any system.
What happens with a complaint or a complex technical question?
The assistant helps collect a description of the situation and passes the conversation to the responsible specialist. It can explain your process for getting help from the materials you provide. Your team agrees technical assessments, changes to the scope of work, repeat visits and compensation decisions. Define the limits of advice and handover rules before launch so an unfamiliar question does not turn into an unverified recommendation or a promise to the customer.
The next step — your service business
Test how JediDesk prepares an enquiry for your team
Choose one service. Add its terms and the questions you need to ask, configure handover to your administrator and walk through common enquiries. See whether your team receives enough detail for the next conversation.
The free trial lasts 14 days. Advice, handover and integrations are configured for your process.
- One service to start with
- Enquiries with the details you need
- Your team agrees the arrangements




