“Do you offer an IT support contract for our office?”
Asks device/user and branch counts and current infrastructure; creates a discovery call. It makes no price/SLA commitment.
—INDUSTRY · Other
Qualifies the IT request, puts the incident in the right queue.
Qualifies IT support, network/security, server/cloud and hardware requests by need type, device/user and branch count, current infrastructure and integration needs. Triages an existing customer’s incident by priority and impact. It gives no price, implementation time, SLA or hardware warranty; it never asks for a password or remote-access code.
Example monthly: Starter ₺2,750 + 2 extra channels ₺3,500 + Appointment Pro ₺1,990 = ₺8,240 + VAT
01WHAT DOES THE CUSTOMER ASK?
These three questions slow down daily work and keep coming back on every channel.
A proposal cannot be prepared until IT support, network/security, server/cloud, hardware and hosting requests are separated.
Without priority, impact and start time, the technical team cannot respond in the right order.
A remote-access code, password or licence key must not be shared in chat; the agent must not ask for them.
02THE AGENT’S ROLE
The boundary is deliberate: the agent says what it does not know and leaves expertise to a human.
DOES
Separates the need type (support, network, server/cloud, hardware, hosting); collects device/user and branch counts.
Asks about current infrastructure and integration needs; creates a discovery call.
Triages an existing customer’s incident by priority and impact; leaves the summary to the team.
DOES NOT · HANDS OVER
Does not commit to a price, implementation time, SLA or hardware warranty.
Never asks for a password, remote-access code or licence key; does not accept that information in chat.
Does not open a record in an RMM/ticketing tool or connect to a device.
03THREE SCENARIOS
The dialogues below are fictional; they contain no real customer name, phone or conversation.
“Do you offer an IT support contract for our office?”
Asks device/user and branch counts and current infrastructure; creates a discovery call. It makes no price/SLA commitment.
“We have a critical outage; how fast do you respond?”
Collects impact, start time and affected users; shares the SLA copy in your knowledge base. It makes no commitment and hands over to the team.
“Should I send the admin password so you can connect remotely?”
Does not ask for a password or access code; tells them not to share it. Says the team will direct them to a secure channel.
04THE DIFFERENCE IS IN THE DETAILS
Only behaviours the product supports today are labelled “Today”; anything it does not do is labelled “Coming soon” or “On request”.
Request type, device/user, branch and current infrastructure are collected in one record; the discovery call starts with a ready brief.
Priority, impact and start time are collected; a critical record reaches the team with a summary. Diagnosis and response belong to the technical team.
RMM/ticketing integration and remote device access are not available today; they are on the roadmap. A password/access code is never requested at any step.
05WHERE DOES IT CONNECT?
The links below go to the pages this industry actually uses; each row carries a status label.
06PLAN AND EXAMPLE MONTHLY
Amounts are calculated from the current list prices; plan, extra channels, voice and appointment are separate line items. All prices exclude VAT, which is a separate line.
WhatsApp + web; two paid channels and Appointment Pro fit discovery/incident calls.
14-day free trial; no credit card. Extra channels, voice and appointment packages are separate items; the prepay discount applies only to the plan fee.
In this example: 2 extra channels · Appointment Pro
The voice phone channel is not in this example; if you use it, a 250-minute voice package is added separately (₺3,750 + VAT).
07FAQ
08PROOF
If there is no customer case whose name, logo and metrics can be shared, we do not put an invented case here. The proof on this page is the product’s current behaviour, channel/integration status and written limits.
09RELATED INDUSTRIES
+RELATED POSTS
Posts from the same topic cluster that complete this page. IT infrastructure posts.
Five common multi-channel customer communication mistakes — tone, handover, stale knowledge, ownership and measurement — and how to fix them.
A plain guide to what an AI customer agent does, how it answers from a knowledge base and when it hands a conversation to a person.
Both appear in a message box, but they do different work. A guide to the difference between a rule-tree chatbot and an assistant that answers from a knowledge base.
Try free for 14 days, no credit card. The industry template is a starting point; we build your knowledge base and handover rules together.