“We want custom software; can we get a quote?”
Asks project type, platform, budget range and timing; creates a brief. Books a discovery call; gives no price.
—INDUSTRY · Other
Collects the brief, routes the support request to the right team.
Qualifies custom software, mobile and SaaS quote requests by project type, platform, budget range, timing and integration needs; books a discovery call. Triages an existing customer’s support request by version, priority and affected users. It gives no price, delivery or warranty commitment.
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 discovery call without project type, platform and integration needs is inefficient; the right team cannot be chosen.
A bug report without version, priority and affected users does not reach the right team.
An agent inventing a technical fix outside the product documentation and release notes loses trust.
02THE AGENT’S ROLE
The boundary is deliberate: the agent says what it does not know and leaves expertise to a human.
DOES
For a quote request, collects project type, platform, budget range, timing and integration needs.
Triages an existing customer’s support request by version, priority and affected users.
Creates an appointment for a discovery call or support callback; leaves the summary to the team.
DOES NOT · HANDS OVER
Does not commit to a firm price, delivery time or warranty.
Does not offer a technical fix or code suggestion outside the product documentation.
Does not open a record in a ticket/PM tool; Jira/Linear integration is not available today.
03THREE SCENARIOS
The dialogues below are fictional; they contain no real customer name, phone or conversation.
“We want custom software; can we get a quote?”
Asks project type, platform, budget range and timing; creates a brief. Books a discovery call; gives no price.
“Can it integrate with our existing API?”
Asks about the current system and integration need; gives the general answer in your knowledge base. Refers to a discovery call for technical feasibility.
“We have a critical bug; how fast do you respond?”
Collects version, priority and affected users; shares the SLA copy in your knowledge base. It makes no commitment and hands over to the team.
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”.
New prospect (quote/discovery) and existing customer (support) records flow separately; the agent does not mix them.
Version, priority and affected users are collected; the summary and suggestion reach the team ready. No technical fix is invented.
Opening records in Jira, Linear and similar ticket/PM tools is not available today; it is on the roadmap. Today leads, support triage and appointments work.
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/support 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. Software company posts.
AI support plans count messages in some places and conversations in others. Five questions to ask and how the two models compare.
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.
Try free for 14 days, no credit card. The industry template is a starting point; we build your knowledge base and handover rules together.