AI Chatbots and Voice Agents
Short answer
An AI chatbot answers customer questions from your own documented knowledge rather than from general training data, and shows the source behind each answer. PHOENIX VERUS builds text and voice agents that can also act — booking, looking up an order, opening a ticket — with the access rules and logging that acting safely requires.
A useful assistant cites its sources. A confident one does not.
What the engagement covers
- Grounded answers
- Retrieval over your documents, with the source shown per answer so a wrong answer is traceable rather than mysterious.
- Scope control
- A defined boundary and an honest refusal outside it. A bot that guesses costs more trust than it saves time.
- Actions
- Booking, order lookup, ticket creation — each with its own permission model and audit trail.
- Languages
- Greek, English and German, each with its own evaluation set rather than one set translated.
How it runs
- Define the scope and collect the knowledge base.
- Build retrieval and answer evaluation before any interface work.
- Add actions and permissions.
- Launch behind a review period, then measure deflection and escalation.
Frequently asked
What does a chatbot cost?
Four variables move it: number of languages, size and volatility of the knowledge base, integrations, and whether it is text or voice. The pricing page sets out each of them.
How long does it take?
A scoped text assistant on a defined document set is measured in weeks. Voice, multiple languages and write access each extend that, and the knowledge base is usually the slowest part — not the software.
Will it hallucinate?
Grounded retrieval with per-answer sources makes hallucination visible and rare, not impossible. The design choice that matters is what the bot does when it does not know: ours say so and hand over.
Contact us
Send us the brief or book a short call. You get concrete next steps in reply.