VUST Custom Solutions · Conversational AI and Support Systems
Support and intake assistants that know when to hand off to a human.
For heads of support · Operations leads · Service companies · Agencies
VUST designs conversational systems for one bounded workflow: grounded answers from approved sources, structured qualification, and a clean escalation path into your team. Web or Telegram first; CRM and helpdesk delivery are scoped as custom integrations.
Approved answer sources · Explicit escalation · No unbounded sales bot
Conversation decision run
Illustrative — not a client case
Customer · web chat
Hi — my invoice from March shows the old company name. Can you reissue it?
- Intent & qualificationSystemRequest classified: billing / document reissue; account facts collected
- Knowledge & tool decisionSystemAnswer policy checked — reissue requires a person; no invented reply
- Human handoffYour teamStructured case with context lands with the billing operator
- Response & recordSystemCustomer gets status + expected time; case is written to the record
- MonitoringOwner + VUSTVolume, resolution, cost, and failure review
The assistant answers what policy allows — and only that.
01 · Fit
When is this the right fit?
Operators repeat the same 20 answers
Routine questions consume the team while policy-safe answers already exist in your docs.
Intake arrives unstructured
Email, chat, and forms produce half-complete requests someone has to chase.
First response is slow
The queue waits on one expert; customers wait on the queue.
Leads are answered late or not qualified
Sales-relevant requests hide inside the support stream.
Escalations lose context
Each handoff restarts the conversation from zero.
Nobody sees conversation outcomes
No record of what was asked, answered, escalated, or dropped.
02 · Process transformation
What changes in the process?
Today
- Requests scattered across inbox, chat, and personal messages
- Operators re-type answers and re-ask the same questions
- Escalation by forwarding; context is lost
- No shared view of volume, topics, or outcomes
With the system
- One entry per channel with structured qualification
- Routine answers drafted from approved sources only
- Escalation carries the full case to a named owner
- Volume, cost, resolution, and failures are logged and reviewed
Human boundary
The assistant never invents policy, never closes a deal, and never answers past its sources. Uncertain, sensitive, or high-impact requests always route to a person — this boundary is part of the acceptance matrix.
03 · Deliverables
What VUST delivers — and what is custom
Three honesty tiers: what VUST already operates in production, what is designed for your project, and what requires a discovery-stage audit before it can be promised.
Operating at VUST today
- Conversation state and safe callback patterns
- Durable support intake on VUST's own products
- Provider routing with fallback rules
- Structured logging and per-call cost accounting
- Scheduled follow-ups and notifications
Designed for your project
- Answer policy and approved source corpus
- Qualification schema and routing rules
- Escalation rules with a named owner
- Roles, identity, and retention
- Conversation reports and review cadence
Scoped after discovery
- CRM and helpdesk delivery
- WhatsApp, Slack, and email channels
- Multi-language answer policy
- Analytics destinations
A named integration is treated as custom work until an access and platform-policy audit verifies it.
04 · Example scopes
What a first release looks like
Three example scopes drawn from workflows VUST operates in its own products. They illustrate shape and boundary — not completed client cases.
Customer support intake assistant
Example scope — not a client case
Routine product and account questions consume operator time while complex cases wait.
- Buyer
- Head of support at a service business
- Inputs
- Approved help articles, answer policy, escalation rules
- Systems
- Web chat entry; helpdesk handoff scoped as custom integration
- VUST delivers
- One-channel assistant, qualification flow, escalation path, conversation log, weekly report
- Human gate
- Operator approves anything outside the approved answer set
- Measured target
- Median first-response time and escalation share, measured weekly against your baseline
- Excluded
- Auto-closing tickets, multi-language policy, channels beyond the first
- First engagement
- Discovery, then a one-channel focused MVP
Structured lead qualification flow
Example scope — not a client case
Inbound leads arrive half-described; sales spends the first call collecting basics.
- Buyer
- Agency or service company owner
- Inputs
- Qualification criteria, routing rules, consent text
- Systems
- Web form + chat entry; CRM delivery scoped as custom integration
- VUST delivers
- Qualification schema, structured intake, advisory scoring, routed case with full context
- Human gate
- A person owns every accept / decline decision — scoring is advisory
- Measured target
- Share of leads arriving complete, measured against your current intake
- Excluded
- Automatic pricing or contracting, cold outreach, purchased lead lists
- First engagement
- Discovery & architecture
Internal request assistant
Example scope — not a client case
IT and ops answer the same internal how-to questions in chat, one at a time.
- Buyer
- Operations or IT lead at a professional firm
- Inputs
- Internal knowledge sources with owners, access rules
- Systems
- Internal web surface; identity provider scoped at discovery
- VUST delivers
- Access-aware assistant, abstention policy, request routing, usage report
- Human gate
- Unanswerable or permission-blocked requests route to the owning team
- Measured target
- Deflection of routine internal requests, measured after a fixed pilot window
- Excluded
- HR or legal decisions, document editing, external users
- First engagement
- Discovery with a source-readiness audit
05 · System anatomy
What is a custom support assistant made of?
Six named parts. Each one has an owner and an acceptance check — this is what discovery maps for your workflow.
System
Channel surface
Web chat or Telegram entry — one primary channel first
You + VUST
Answer policy & corpus
Approved sources, tone rules, and what must never be answered
VUST
Qualification schema
Required facts, classification, and routing rules
Your team
Escalation & approval
Named owner; uncertain and sensitive cases go here
Custom scope
Integration layer
CRM / helpdesk delivery after an access audit
Owner + VUST
Observability
Logs, cost per conversation, failure review
Coral marks the human-authority component. Actor tags show who owns each part in operation.
06 · First engagement
How does a project begin?
A full production build is not VUST's default first step. The entry matches the state of your workflow.
Default
Paid discovery
Workflow map, answer-source audit, escalation design, architecture, MVP boundary, go/no-go.
Right when: You have the workflow and the sources, and want the boundary defined before building.
When prerequisites are finite
Focused MVP
One channel, one workflow, approved sources, human handoff, monitoring, acceptance matrix.
Right when: Discovery is done — or the owner, KPI, sources, and approval boundary are already written.
Existing bot
Audit & stabilization
Read-first audit of the assistant you already run: evidence, risks, stabilization plan.
Right when: A bot exists but answers badly, costs too much, or nobody can see why.
Discovery
Sources, policy, escalation, architecture
Architecture
Channel, schema, integration plan
Focused MVP
One channel, human handoff, acceptance
Production
Roles, data handling, rollback
Operations
Handoff or contracted monitoring
You can stop at any gate · MVP emphasis: this category usually ships as discovery → one-channel MVP
07 · Cost and timing
What affects cost and timing?
Exact pricing is stated in your proposal after discovery — never as a public number. These are the factors that move it.
Price and schedule drivers
- Channels
- Answer-source size and quality
- Integrations
- Roles and identity
- Languages
- Volume
- Approval design
- Reporting
- Support model
Always separate lines
- Provider and model usage
- Hosting
- Third-party services and licences
- Taxes, where applicable
Timing starts when access, decisions, and prerequisites are complete. Consumer VUST pricing does not apply to B2B delivery.
08 · Why VUST
Why VUST for conversational systems?
Operating evidence — 07·2026
- Focused AI tools operating across web and Telegram
- Durable support intake running on VUST's own products
- Conversation state, safe callbacks, structured logging
- Provider routing with per-call cost accounting
Facts refer to VUST's own products — not client cases.
After launch
Either an operational handoff — runbook, monitoring, a named owner on your side — or contracted managed operations with agreed coverage and reporting.
Answer sources drift. The operating agreement includes a review cadence for policy and corpus, so the assistant's boundary stays true as your product changes.
09 · FAQ
Clear before the contract.
Buying & scope
What is the smallest useful start?
Paid discovery: workflow map, answer-source audit, escalation design, architecture, and a go/no-go. If you already run a troubled bot, a read-first audit is the entry instead.
Can you take over our existing bot?
Via the audit path: evidence collection first, reproducible failures where feasible, risk-ranked findings, then a separately approved stabilization scope.
Implementation & data
Which channels are proven, which are custom?
Web and Telegram are evidenced by VUST's own production tools. WhatsApp, Slack, email, CRM, and helpdesk delivery are custom integrations, scoped after an access and platform-policy audit.
How do you prevent invented answers?
The assistant answers only from the approved source set under a written answer policy, with an abstention rule: uncertain requests escalate to a person. The policy is tested against an evaluation set before acceptance.
Operation & ownership
Who maintains the assistant after launch?
Your named owner with a runbook, or VUST under a contracted managed-operations agreement with agreed coverage. 24/7 is never implied by default.
What do we see in reports?
Conversation volume, topics, escalation share, resolution outcomes, provider cost per conversation, and failures — scoped to exclude personal data.
Next step
Describe your support or intake workflow.
The brief takes about five minutes: current process, channels, sources, volume, and the outcome you need. It ends with a concrete recommendation — discovery, a focused MVP, or an audit — prepared as guidance for the scoping conversation.
6 steps · Review before send · Nothing sent without your consent