# Vatoo > Vatoo is an AI chatbot for websites. It answers from a company’s own content, captures enquiry details, and guides booking or support workflows through configured integrations. This file lists every published industry, use case, integration, comparison, and guide, with the same limits as the public pages. Vatoo is for sales, support, and lead capture. NIVA is the previous name. The product site is https://vatoo.ai. Contact sales@vatoo.ai or book a 30-minute demo at https://calendly.com/vatoo/30min. Bring one task, such as qualifying an enquiry or collecting a booking request. ## Product Vatoo is an AI chatbot for a business website. It answers from the company’s own pages and documents, captures enquiry details, and can guide a booking or support request when a flow and a connected system are configured. A team starts from a role, adds approved content, tests answers and handoffs, and adds the website embed. The AI Agents page describes ready specialist roles (it states 250+ personas across 25 industry domains) that you then ground in your own documents, tone, and tools. Role templates do not already know a customer’s policies or prices. A request is not a confirmed booking unless the connected system confirms it. ### Pages - [AI Chatbot for Your Website — Support & Leads](https://vatoo.ai/): Add Vatoo to your website to answer customer questions, capture leads, and collect booking requests. No-code setup. Try free with 1,000 messages to use within 3 months. - [AI Chatbot Features for Sales & Support](https://vatoo.ai/features): Answer from your content, qualify enquiries, and guide bookings. Explore Vatoo AI agents, no-code flows, smart forms, analytics, and human handoff. - [AI Agents for Sales, Support & Bookings](https://vatoo.ai/ai-agents): Help customers with sales, support, and bookings using AI agents grounded in your business knowledge, all in one conversation. - [No-Code Chatbot Workflow Builder](https://vatoo.ai/flow-engine): Build chatbot workflows for bookings, quotes, and intake. Use visual steps, conditional branches, forms, and webhooks to connect the next action. - [Conversational Forms for Lead Capture](https://vatoo.ai/smart-form-engine): Capture and qualify leads with forms inside AI chat. Collect relevant details, validate answers, and send enquiries to your team or connected CRM. - [How Vatoo Works | Build & Launch an AI Chatbot](https://vatoo.ai/how-it-works): Connect your content, configure an AI agent, test real questions, and add it to your website. Follow Vatoo’s setup and ongoing review process. - [Vatoo Pricing | Plans, Features & Free Trial](https://vatoo.ai/pricing): Compare Essential and Premium features, message allowances, and monthly or annual billing. Test Premium with 1,000 messages to use within 3 months. No credit card. - [AI Chatbots by Industry: Examples and Workflows](https://vatoo.ai/industries): Explore practical AI chatbot uses for your industry, from property viewings and freight quotes to patient enquiries and online shopping. - [AI Chatbot Use Cases](https://vatoo.ai/use-cases): Explore practical AI chatbot workflows for sales, support, booking, intake, operations, and internal teams. - [AI Chatbot Integrations for CRM, Messaging & APIs](https://vatoo.ai/integrations): Connect Vatoo to your website, WhatsApp, HubSpot, Slack, and more. Explore setup guides for customer channels, CRM, support tools, APIs, and webhooks. - [AI Chatbot Platform Comparisons & Alternatives](https://vatoo.ai/alternatives): Compare Vatoo with Chatbase, Tidio, Intercom, Botpress, and more. Evaluate costs, knowledge, connected actions, and human handoff with practical trial checklists. - [Agentic AI & Multi-Agent Chatbots Explained](https://vatoo.ai/answers): What is an agentic chatbot? Learn how AI agents use knowledge, specialist roles, workflows, and human handoff, with practical advice for evaluating Vatoo. - [AI Chatbot Guides: Pricing, Comparisons & Setup](https://vatoo.ai/blogs): Research AI chatbot costs, compare platforms, and plan your first workflow. Practical guides for business teams and agencies evaluating Vatoo. - [AI Chatbot FAQ: Setup, Pricing & Accuracy](https://vatoo.ai/faq): Get answers about Vatoo’s free trial, plan allowances, content setup, AI accuracy, integrations, branding, and human handoff before you choose. - [Contact Vatoo | Book an AI Chatbot Demo](https://vatoo.ai/contact): Book a 30-minute Vatoo demo around your customer workflow. Discuss AI chatbot setup, pricing, integrations, and the questions your team needs answered. - [AI Chatbot Partners for Agencies & Consultants](https://vatoo.ai/partners): Explore Vatoo referrals and branded chatbot delivery for agencies and consultants. Discuss client fit, recurring commission, and partner terms. - [About Vatoo | AI for Better Customer Conversations](https://vatoo.ai/about): Vatoo helps businesses turn customer conversations into answers, bookings, and leads. Meet the team and the purpose behind Vatoo, formerly NIVA. - [Our Story | NIVA Is Now Vatoo](https://vatoo.ai/our-story): Why we renamed NIVA to Vatoo, and what we want every customer conversation to do. - [Meet the Vatoo Team](https://vatoo.ai/team): Meet the product, engineering, AI, and quality team building Vatoo. - [Security](https://vatoo.ai/security): Learn about Vatoo encryption, access control, monitoring, secure development, and data handling. - [Trust Center](https://vatoo.ai/trust): Review Vatoo platform health, data commitments, privacy practices, and security information. - [Privacy Policy](https://vatoo.ai/privacy): How Vatoo collects, uses, protects, and gives customers control over personal data. - [Terms of Service](https://vatoo.ai/terms): The terms governing access to and use of the Vatoo platform and related services. ### Plans Prices below are the published plan facts. Taxes may apply. Confirm how a message is counted, what happens at the allowance limit, and any third-party fees before purchase. | | Free trial | Essential | Premium | Enterprise | | --- | --- | --- | --- | --- | | Price | $0 | $49 monthly, or $468 yearly ($39 per month equivalent) | $149 monthly, or $1,428 yearly ($119 per month equivalent) | Quoted separately | | Messages | 1,000 to use within 3 months, then they expire | 3,000 / month | 15,000 / month | Custom | | Team access | Builder | 2 seats | 5 seats | Unlimited | | Branded chatbot, private knowledge, lead capture and analytics | Included | Included | Included | Included | | Smart forms | Included during trial | 2 | Unlimited | Unlimited | | Visual flow builder, cross-session memory, tools and API calls, multiple channels | Included during trial | Not included | Included | Included | | Custom SLA and residency | Not included | Not included | Not included | Included | Essential is for a branded website assistant, knowledge answers, lead capture, and two smart forms. Premium is for flows, tools and API calls, memory, or multiple channels. Trial access is broader than Essential: the trial includes Premium features. Enterprise covers custom volume, ERP and on-premise options, and a dedicated manager. Annual billing is the price shown as “billed yearly”, not an extra discount on top of the monthly-equivalent figure. ## Questions buyers ask **What is an AI chatbot for a website?** An AI chatbot is a chat window that lets visitors ask questions in their own words. Vatoo uses your website, documents, and instructions to answer questions and collect useful details for your team. **Do I need to know how to code?** You can build and configure your chatbot in Vatoo without coding. Someone with access to your website needs to add the embed code. Connecting custom systems or setting up complex actions may need a developer. **What can I use to teach my chatbot?** Add website pages, PDFs, Word documents, or video transcripts. Start with useful information such as your services, prices, opening hours, and frequently asked questions. Keep it up to date and test the answers before going live. **Can Vatoo collect leads and booking requests?** Yes. Use forms inside the chat to ask for names, contact details, and what visitors need. You can collect a booking request for your team to follow up. Checking live availability or confirming a booking requires a configured connection to your booking system. **What if the chatbot does not know the answer?** Set instructions for questions it cannot answer, such as asking for contact details so your team can follow up. AI can make mistakes. Review conversations, improve your content, and test important questions regularly. **Can I use Vatoo for client websites?** Agencies can discuss setting up chatbots for client websites with the Vatoo team. You can customize the chatbot’s name, colors, and avatar. Confirm client access, branding rights, pricing, and support responsibilities before offering it as a service. **Is Vatoo free to try?** The free trial includes 1,000 messages to use within 3 months, plus access to Premium features, with no credit card required. Unused messages expire after those 3 months and are not renewed. Use them to test your content, forms, and customer journey before choosing a paid plan. **How much does it cost after the trial?** Essential is $49 monthly or $468 billed yearly ($39 per month equivalent), with 3,000 messages per month. Premium is $149 monthly or $1,428 billed yearly ($119 per month equivalent), with 15,000 messages per month. Enterprise is quoted separately. Taxes may apply. **How do I launch a Vatoo chatbot on my website?** Choose a role, add your website or documents, and set your assistant’s voice and boundaries. Test customer questions and handoffs before adding the embed to your site. Timing depends on your content, website access, and integrations. **Do I need a developer?** You can configure a standard website assistant in the dashboard without coding. Someone with access to your website must add the embed. Custom APIs, authentication, and complex workflows may need technical help. **How do I keep AI answers accurate?** Connect current, approved content and define what the assistant should do when an answer is missing. AI can still make mistakes. Test important questions, review conversations, and route sensitive or unsupported requests to your team. **Can Vatoo capture leads and help with bookings?** Yes. Use Smart Forms to collect relevant details and flows to guide the next step. Confirmed bookings and live lookups depend on a configured connection to your system; otherwise, collect a request for your team to follow up. **Can I connect my CRM, helpdesk, or business tools?** Vatoo offers integration guides for customer channels, CRM, ERP, and support tools, plus custom APIs and webhooks. Check the specific connector, plan, permissions, and third-party requirements before starting. **Can agencies offer Vatoo under their own brand?** You can customise the assistant’s name, colours, and avatar. For delivery across clients, discuss workspace separation, branding rights, support ownership, and commercial terms with our team. **What is included in the free trial?** The free trial includes 1,000 messages to use within 3 months, plus access to Premium features, with no credit card required. Unused messages expire after those 3 months and are not renewed. Use them to test your content, forms, and customer journey before choosing a paid plan. **How much does Vatoo cost?** Essential is $49 monthly or $468 billed yearly ($39 per month equivalent), with 3,000 messages per month. Premium is $149 monthly or $1,428 billed yearly ($119 per month equivalent), with 15,000 messages per month. Enterprise is quoted separately. Taxes may apply. **Which plan should I choose after the trial?** Choose Essential for a branded website assistant, knowledge answers, lead capture, and two smart forms. Choose Premium when you need flows, tools and API calls, memory, or multiple channels. Compare ongoing features as well as message volume: trial access is broader than Essential. **What should I check before buying?** Estimate normal and peak message volume, then confirm how messages are counted and what happens at the allowance limit. Include any third-party fees, integration work, seats, and support requirements in your budget. **What happens when a customer needs a person?** Configure when the assistant should hand over and which team receives the request. Test the conversation history, collected details, and offline message so customers know what to expect when staff are unavailable. **What happens in the 30-minute demo?** Bring a website or sample document and one task, such as qualifying an enquiry or collecting a booking request. We’ll walk through how Vatoo could handle it, discuss integrations, and identify the setup and plan you need. ## Industries Vatoo publishes 59 industry pages. Each one describes the questions a chatbot can answer from that business’s own approved content, the details it can collect, an example conversation, the sources to start with, and the decisions that stay with the team. These pages are starting points. They do not already know a customer’s prices, policies, or availability. The same three limits apply on every industry page: - Answers come from content the business is allowed to use. AI can make mistakes, so important answers need review, and the team defines when a person takes over. - Live availability, record updates, and confirmed bookings need a supported integration with the right permissions. Without that connection, the chatbot collects a request for the team to follow up. - The free trial includes 1,000 messages to use within 3 months, with no credit card. Unused messages expire after those 3 months. Adding the website embed needs access to the site. Custom integrations may need technical help. ### Often requested - [Ecommerce AI Chatbot for Product Questions and Returns](https://vatoo.ai/industries/retail-ecommerce): Product questions, delivery information, and returns guidance. - [SaaS AI Chatbot for Support and Demo Requests](https://vatoo.ai/industries/saas-tech): Product questions, onboarding help, and demo enquiries. - [Marketing Agency Chatbot for Leads and Campaign Briefs](https://vatoo.ai/industries/marketing-agencies): Service questions, campaign briefs, and discovery-call requests. - [Real Estate AI Chatbot for Listings and Viewing Requests](https://vatoo.ai/industries/real-estate): Listing questions, buyer preferences, and viewing requests. - [Travel Agency Chatbot for Tour and Booking Enquiries](https://vatoo.ai/industries/travel-tourism): Tour questions, personalised trip enquiries, and booking guidance. - [Marina Chatbot for Berth Enquiries and Guest Questions](https://vatoo.ai/industries/marina-management): Berth enquiries, vessel details, and marina guest information. - [Hotel AI Chatbot for Room Enquiries and Guest Questions](https://vatoo.ai/industries/hospitality): Room questions, stay enquiries, and guest information. - [Home Services Chatbot for Job and Quote Requests](https://vatoo.ai/industries/home-services): Service-area checks, job enquiries, and visit requests. - [AI Chatbot for Consulting Firms: Project Enquiries](https://vatoo.ai/industries/consulting-firms): Service discovery, project scoping, and discovery-call requests. - [AI Chatbot for Insurance Teams](https://vatoo.ai/industries/insurance): Policy information, quote enquiries, and claims process guidance. - [AI Chatbot for Healthcare Providers](https://vatoo.ai/industries/healthcare): Clinic information, visit preparation, and routine appointment enquiries. ### Commerce #### Food & Beverage - [AI Chatbot for Food and Beverage Brands](https://vatoo.ai/industries/food-beverage): Product questions, trade enquiries, and order support. For food brands, beverage producers, wholesalers, and distributors. Answer questions about your food and drink range, order requirements, and delivery. Vatoo collects buyer details and quantities for your wholesale or customer service team. **Where enquiries get stuck.** A stockist needs pack sizes and ordering terms. A consumer might need ingredient information or a support contact. Help each visitor reach the appropriate answer. **Specific friction.** - **A stockist needs trade information.** A café buyer needs pack sizes and order minimums before deciding what to order. - **Delivery affects the order.** Volume and delivery area help the sales team check whether it can serve the buyer. - **Ingredients need an exact product match.** A question about allergens must use the current information for the specific product. **Questions visitors ask.** - Can our café request a wholesale price list? - What pack sizes and minimum orders do you offer? - Where can I find the ingredients for this product? **What the assistant can take on.** - **Explain product information.** Answer product, pack-size, and storage-information questions using current product sheets approved by your team. (Use: current product sheets and catalogue) - **Collect wholesale leads.** Ask about business type, products, quantities, and delivery area before your sales team discusses trade terms. (Ask for: business, products, volume, location) - **Guide order support.** Explain your delivery and returns process and collect an enquiry for damaged, missing, or incorrect items. (Share: support process and order contact) - **Find ingredient information.** Point consumers to current approved product sheets for the exact product they ask about. - **Take a stockist enquiry.** Collect the buyer’s business type, delivery area, and products of interest. - **Flag a product concern.** Direct quality and allergen questions that need investigation to the product team. **Example roles for a wholesale team.** - **Product catalogue guide.** Answers product and pack-size questions from current product sheets and directs uncertain ingredient questions to staff. - **Wholesale enquiries.** Collects the product range, purchase volume and delivery area for a trade sales conversation. **Content to start with.** - Product catalogues and approved ingredient information - Pack sizes, minimum orders, and delivery areas - Wholesale enquiry and product complaint procedures **What stays with the team.** Your team confirms trade pricing and supply. Allergen uncertainty, food safety concerns, and product complaints need direct review. **Limit.** Can it reassure a customer that a product is allergen-free? Use only the exact, current ingredient and allergen information your business approves. If information is missing or a customer's situation is unclear, direct them to your product team without guessing. **Example: Café wholesale enquiry.** Visitor: “Can our café request a wholesale price list?” Assistant: “I can collect a trade enquiry. Which products are you interested in, where is your café, and what order volume do you have in mind?” Details collected: Buyer: Independent café; Interest: Bottled drinks; Volume: Monthly wholesale order. Next: Sales team to discuss trade terms. #### Media & Entertainment - [AI Chatbot for Media and Entertainment](https://vatoo.ai/industries/media-entertainment): Audience support, subscription guidance, and licensing enquiries. For publishers, studios, streaming services, and entertainment businesses. Vatoo answers questions about your content, subscriptions, and events. Collect licensing and partnership enquiries with the details your commercial team needs. **Where enquiries get stuck.** One visitor may need account help, while another wants to use your content. Separating the enquiry early makes the next step clearer for everyone. **Specific friction.** - **A licence enquiry lacks the intended use.** The rights team needs the clip, territory, and usage period before it can review a request. - **Subscribers need another desk.** Billing and access questions should go to the subscription support route. - **Release information changes.** Audiences need the published schedule for the specific title or event. **Questions visitors ask.** - Who should I contact about licensing a clip for a campaign? - Where can I find help with my subscription? - How do I check the schedule for an upcoming release? **What the assistant can take on.** - **Find content information.** Use published catalogues, schedules, and programme pages to answer questions about your content and events. (Use: catalogues, release information, and schedules) - **Prepare licensing enquiries.** Ask which content, intended use, territory, and time period the requester wants your rights team to consider. (Ask for: content, use, territory, period) - **Explain subscription support.** Point audiences to approved billing, access, and cancellation instructions or the appropriate support contact. (Share: subscription help and account support routes) - **Find release information.** Help audiences locate a published release date, broadcast schedule, or event listing. - **Take a partnership enquiry.** Collect the proposed collaboration, audience, and timescale for the commercial team. - **Reach the rights team.** Direct questions about usage restrictions and contract terms to the licensing contact. **Example roles for a audience and rights teams.** - **Audience support guide.** Helps viewers find release schedules, catalogue details and the official subscription support route. - **Licensing enquiries.** Asks which content a partner wants to use, where it will appear and for how long. **Content to start with.** - Content catalogues and published schedules - Licensing enquiry requirements and commercial contacts - Subscription help articles and account procedures **What stays with the team.** Your rights team approves licences and usage terms. Account changes need your authenticated process; unpublished releases should not be inferred. **Limit.** Can a chatbot grant permission to use our content? No. It can explain your licensing process and collect the intended use. Your rights team must check ownership, permissions, territory, duration, and commercial terms before granting a licence. **Example: Clip licensing enquiry.** Visitor: “Who should I contact about licensing a clip for a campaign?” Assistant: “Which clip would you like to use, where will the campaign run, and for how long? I can collect those details for the rights team.” Details collected: Content: Short video clip; Use: Brand campaign; Period: Three months. Next: Rights team to review permission and terms. #### Retail & E-commerce - [Ecommerce AI Chatbot for Product Questions and Returns](https://vatoo.ai/industries/retail-ecommerce): Product questions, delivery information, and returns guidance. For online stores, retailers, direct-to-consumer brands, and sales teams. Vatoo answers product, delivery, and returns questions from your store content. Help shoppers compare published details and contact your team when they need more support. **Where enquiries get stuck.** Shoppers may be checking a size, material, delivery policy, or return rule. Make those details easier to find while they are looking at the product. **Specific friction.** - **A shopper is between sizes.** They need the guide for the exact item while the product is still on screen. - **Delivery can decide the purchase.** A shopper needs the shipping terms that apply to their destination. - **A return starts with a policy question.** Customers need the return window and the place to submit their request. **Questions visitors ask.** - How do I check whether this jacket is the right size? - What is your delivery policy for my area? - How do I start a return if the item does not fit? **What the assistant can take on.** - **Explain product details.** Help shoppers find materials, dimensions, sizing, and care information from your current product content. (Use: product pages and size guides) - **Clarify delivery and returns.** Explain your published delivery options, return window, and return process without promising an unconfirmed exception. (Use: shipping and returns policies) - **Prepare support enquiries.** Collect the item reference and issue so the support team can follow up through your order-help process. (Ask for: item reference and help needed) - **Find the returns procedure.** Guide customers to the published return window and the store’s official return route. - **Help shoppers outside store hours.** Answer questions about product sizing and care from the current product pages. - **Reach order support.** Collect the product reference and issue before the team looks up an order. **Example roles for a store support team.** - **Shopping assistant.** Helps shoppers compare product details and find the size guide for the item they are viewing. - **Order support guide.** Explains delivery and return policies and directs order-specific requests to the store’s support process. **Content to start with.** - Product pages, size guides, and care information - Current shipping and returns policies - Order support instructions and contact routes **What stays with the team.** Your store confirms refunds, order changes, and exceptions. Live stock, order status, or personalised order actions need a supported store connection. **Limit.** Can Vatoo track orders or check live stock? Live order and stock information requires a supported connection to your store and appropriate customer verification. Without it, Vatoo can explain policies and guide shoppers to your official order-help route. **Example: Product sizing question.** Visitor: “How do I check whether this jacket is the right size?” Assistant: “Which jacket and size are you looking at? I can help you find its size guide and explain the return process if it does not fit.” Details collected: Product: Everyday jacket; Question: Size guide; Also needed: Returns information. Next: Shopper guided to the relevant product details. ### Education, government, and nonprofits #### Childcare - [AI Chatbot for Childcare Providers](https://vatoo.ai/industries/childcare): Parent questions, nursery visits, and place enquiries. For nurseries, childcare centres, and early years providers. Answer parent questions about age groups, hours, fees, and visits. Vatoo collects childcare enquiries so your team can discuss places and arrange a tour. **Where enquiries get stuck.** Age ranges, daily routines, opening hours, and settling-in arrangements all matter. Clear information helps families decide whether to speak with your team. **Specific friction.** - **A place depends on more than age.** Session days and the preferred start month matter when staff check availability. - **Families need the everyday details.** Hours, routines, and settling-in arrangements help parents decide whether to visit. - **An enquiry is only the first step.** A visit lets the family and nursery discuss the child's needs before a place is offered. **Questions visitors ask.** - Can we arrange a visit for a two-year-old starting next term? - What are your opening hours and session options? - How does your settling-in process work? **What the assistant can take on.** - **Explain everyday nursery life.** Answer questions about age groups, sessions, routines, and meals using the information your nursery publishes. (Use: parent handbook and session information) - **Collect place enquiries.** Ask for age group, preferred start period, and sessions needed, then let your team check places. (Ask for: age group, start period, sessions) - **Arrange a tour request.** Collect a parent's contact details and preferred visit times. Explain what they can expect during the tour. (Collect: preferred visit and parent contact) - **Explain session options.** Help parents compare published full-day and part-day arrangements for the relevant age group. - **Take a waiting-list enquiry.** Collect the age group, sessions, and preferred start month for staff to check. - **Arrange a family conversation.** Offer the designated contact when a family wants to discuss a child’s individual needs. **Example roles for a nursery team.** - **Parent information guide.** Answers practical questions about daily routines, session times and settling in from the parent handbook. - **Nursery visit enquiries.** Collects the age group, days needed and intended start month so staff can discuss a visit or place. **Content to start with.** - Parent handbook and daily routines - Age groups, session options, and published fees - Tour, enrolment, and settling-in information **What stays with the team.** Your team confirms places and discusses individual care needs. Safeguarding concerns and sensitive information about children belong with designated staff. **Limit.** Can it confirm that a childcare place is available? It can collect the age group, sessions, and start period the family needs. Your nursery should confirm availability and suitability before offering a place. **Example: Nursery visit enquiry.** Visitor: “Can we arrange a visit for a two-year-old starting next term?” Assistant: “I can help you request a visit. Which days of childcare are you considering, and when would you like to come and look around?” Details collected: Age group: Two-year-olds; Sessions: Three days a week; Start: Next term. Next: Nursery team to discuss places and a visit. #### Education - [AI Chatbot for Schools and Training Providers](https://vatoo.ai/industries/education): Course questions, enrolment guidance, and parent enquiries. For schools, training centres, tutoring businesses, and course providers. Vatoo explains your courses, schedules, and enrolment steps. Help learners and parents find relevant information and request a conversation with your education team. **Where enquiries get stuck.** Learners want to know whether a course fits their level, schedule, and goals. Parents may need dates and practical information before arranging a conversation. **Specific friction.** - **The class must fit the learner.** Experience level and available evenings can narrow the choice more than a course name alone. - **Enrolment requirements are spread out.** A learner needs the correct prerequisites and application steps for the course they selected. - **Placement can need a conversation.** A learner with mixed experience may want an adviser to help choose a starting level. **Questions visitors ask.** - Do you have an evening course for beginners? - What do I need before I can enrol? - Can I speak to someone about the right class level? **What the assistant can take on.** - **Explain course options.** Answer questions about level, format, duration, and published fees using your course information. (Use: course pages and current schedules) - **Guide enrolment steps.** Show learners where to apply and what information your process asks them to prepare. (Share: application steps and entry requirements) - **Collect learner enquiries.** Ask about the subject, experience level, and preferred study times before a member of your team follows up. (Ask for: subject, level, preferred schedule) - **Find term dates.** Point learners and parents to current teaching dates and holiday information. - **Collect interest in a future class.** Ask for the subject and preferred schedule when someone cannot find a suitable session. - **Reach a course adviser.** Arrange a discussion when a learner needs help deciding which level to enter. **Example roles for a course team.** - **Course guide.** Helps learners compare class levels, schedules and entry requirements from the course catalogue. - **Enrolment enquiries.** Asks which class and study times suit the learner and collects questions for a course adviser. **Content to start with.** - Course descriptions, levels, and schedules - Published entry requirements and enrolment steps - Term dates, fees, and learner support contacts **What stays with the team.** Your staff make enrolment decisions and discuss individual learning or safeguarding needs. Student records require your approved access process. **Limit.** Can it decide which class a learner should join? It can explain the levels and prerequisites you publish and collect a learner's preferences. Your staff should confirm placement where an assessment or individual discussion is needed. **Example: Beginner course enquiry.** Visitor: “Do you have an evening course for beginners?” Assistant: “Which subject would you like to study, and which evenings are convenient? I can collect your preferences for the course team.” Details collected: Level: Beginner; Format: Evening classes; Preference: Twice a week. Next: Course team to advise on suitable options. #### Government - [AI Chatbot for Government Services](https://vatoo.ai/industries/government): Service navigation, application checklists, and department contacts. For local authorities, public agencies, and citizen service teams. Vatoo makes published public-service information easier to navigate. Explain application steps, show document checklists, and direct residents to the responsible department. **Where enquiries get stuck.** People arrive with a task: apply for a permit, report an issue, or find a service. Your website can help them start without knowing which office owns the process. **Specific friction.** - **People know the task, not the department.** A resident asking for a parking permit needs the right starting page. - **Forms can require preparation.** The correct checklist helps residents gather documents before starting an application. - **Some residents need help applying.** Assisted-service contacts make it possible to continue when an online form is difficult to use. **Questions visitors ask.** - Where do I start an application for a parking permit? - What documents do I need before applying? - Who can help if I cannot complete the online form? **What the assistant can take on.** - **Find the relevant service.** Use your published service directory to explain which department and application page match the visitor's enquiry. (Use: service directory and department information) - **Explain application steps.** Show the current checklist, published fees, and submission process without deciding whether someone qualifies. (Share: requirements and official application links) - **Offer a support route.** Direct complex enquiries to the relevant team and provide your alternative contact options for people who need help. (Share: department contacts and assisted-service options) - **Locate the correct form.** Show the official application link for the permit or service the resident selects. - **Explain service hours.** Share opening hours and alternatives for residents who cannot visit a counter. - **Find assisted support.** Help people reach the department that supports accessibility or individual application questions. **Example roles for a resident service desk.** - **Public service finder.** Helps residents locate the official service page, application form and document checklist for their task. - **Resident support guide.** Directs people who need help completing an application to the responsible department or assisted-service channel. **Content to start with.** - Published service pages and application checklists - Current fees, process steps, and department contacts - Accessibility and assisted-service information **What stays with the team.** Public officials make eligibility and application decisions. Appeals, sensitive cases, and identity documents belong in the authorised service process. **Limit.** Can Vatoo approve an application or determine eligibility? No. It can explain published requirements and help residents reach the correct service. Formal decisions, appeals, and identity verification remain with the responsible authority. **Example: Parking permit enquiry.** Visitor: “Where do I start an application for a parking permit?” Assistant: “I can help you find the application instructions. Are you asking about a resident, visitor, or business parking permit?” Details collected: Service: Parking permit; Type: Resident; Need: Application checklist. Next: Resident directed to the official application. #### Higher Education - [AI Chatbot for Universities and Colleges](https://vatoo.ai/industries/higher-education): Programme discovery, entry requirements, and admissions enquiries. For universities, colleges, and higher education admissions teams. Vatoo explains programme options, published entry requirements, and application steps. Help prospective students find answers and reach the right admissions team. **Where enquiries get stuck.** A prospective student may find a programme they like but still need its entry requirements, intake dates, or application route. Give those questions a clear home. **Specific friction.** - **Requirements vary by programme.** An applicant needs the entry criteria for a particular course and intake. - **Deadlines change the options.** The right intake depends on the programme and its published application dates. - **Qualifications need individual review.** International applicants may need an admissions specialist to assess their circumstances. **Questions visitors ask.** - Where can I find the entry requirements for your business degree? - Which intake can I apply for? - Who can advise me about an international qualification? **What the assistant can take on.** - **Explain programme options.** Answer questions about course structure, delivery format, and published requirements from your current programme pages. (Use: programme pages and entry requirements) - **Guide application preparation.** Point applicants to the relevant deadlines, document checklist, and application portal for their chosen programme. (Share: intake dates, checklist, application route) - **Prepare admissions enquiries.** Collect the programme of interest, intended intake, and question for your admissions team to review. (Ask for: programme, intake, enquiry) - **Compare intake dates.** Show the published entry dates and deadlines for the applicant’s chosen programme. - **Take an open-day enquiry.** Ask which campus and course interest the applicant so admissions can follow up. - **Reach international admissions.** Direct questions about overseas qualifications to the appropriate admissions specialist. **Example roles for a admissions office.** - **Programme guide.** Helps applicants locate the entry criteria, course structure and intake dates for a particular programme. - **Admissions enquiries.** Collects the programme, intended intake and applicant question for the admissions office to review. **Content to start with.** - Programme descriptions and entry requirements - Application deadlines and document checklists - Admissions, international office, and campus contacts **What stays with the team.** Admissions staff assess qualifications and make offers. Visa advice, exceptional circumstances, and individual student records need the appropriate specialist team. **Limit.** Can it tell an applicant whether they will be accepted? It can explain the entry criteria you publish, but meeting a listed requirement does not constitute an offer. Your admissions team must review the application and confirm any decision. **Example: Business degree enquiry.** Visitor: “Where can I find the entry requirements for your business degree?” Assistant: “Are you looking at undergraduate or postgraduate study, and which intake interests you? I can help you find the programme's published requirements.” Details collected: Programme: Undergraduate business; Intake: Autumn; Question: Entry requirements. Next: Applicant guided to programme information. #### Non-Profit - [AI Chatbot for Nonprofits and Charities](https://vatoo.ai/industries/non-profit): Programme information, volunteer interest, and donor questions. For charities, foundations, community organisations, and nonprofit teams. Vatoo explains your programmes and ways to get involved. Help visitors find donation information, volunteer opportunities, and the right contact for support enquiries. **Where enquiries get stuck.** A donor, a potential volunteer, and someone seeking support need different information. Help each visitor find an appropriate route without a long search. **Specific friction.** - **A volunteer wants a role that fits.** Location and availability help the coordinator find a practical way to get involved. - **Donors want to understand the work.** Published programme and spending information help donors decide where to give. - **Support enquiries can be personal.** Someone seeking help may need a private conversation with the programme team. **Questions visitors ask.** - How can I volunteer at a weekend community event? - Where can I find information about how donations are used? - How do I contact the team about your support programme? **What the assistant can take on.** - **Explain your programmes.** Use published programme descriptions and service locations to help visitors understand what your organisation offers. (Use: programme pages and public impact information) - **Collect volunteer interest.** Ask about interests, availability, and location, then let your volunteer coordinator discuss suitable opportunities. (Ask for: interests, availability, location) - **Guide donor questions.** Share your donation routes, published fundraising information, and the right contact for a donation enquiry. (Share: official donation pages and donor contacts) - **Find a local programme.** Guide visitors to programme descriptions, operating locations, and support contacts. - **Take event volunteer enquiries.** Let potential volunteers share the kind of work and dates they can offer. - **Reach donor support.** Direct receipt, payment, or gift-restriction enquiries to the fundraising team. **Example roles for a programme team.** - **Programme information guide.** Helps visitors find local programmes, public impact information and the right support contact. - **Volunteer enquiries.** Asks about interests, location and available time before the coordinator discusses a role. **Content to start with.** - Programme descriptions and service locations - Volunteer roles and enquiry requirements - Donation information and support contact routes **What stays with the team.** Your staff handle safeguarding, eligibility for support, volunteer checks, and sensitive personal situations. Donations go through your official payment pages. **Limit.** Can it decide whether someone qualifies for support? It can explain published programme information and help someone contact your team. Individual eligibility, safeguarding concerns, and sensitive case details should follow your organisation's established support process. **Example: Volunteer interest enquiry.** Visitor: “How can I volunteer at a weekend community event?” Assistant: “I can help you register your interest. What kind of event work appeals to you, and which weekends and locations would suit you?” Details collected: Interest: Community events; Availability: Weekend mornings; Next step: Volunteer coordinator contact. Next: Coordinator to discuss appropriate opportunities. ### Finance #### Finance & Banking - [AI Chatbot for Banks and Financial Services](https://vatoo.ai/industries/finance-banking): Product information, application guidance, and adviser appointments. For banks, credit providers, and financial service teams. Explain your published accounts, services, and application steps with Vatoo. Help visitors prepare questions and request an appointment with the appropriate banking team. **Where enquiries get stuck.** Fees, documents, and application steps can be spread across several pages. Help visitors find the published information they need without making a financial decision for them. **Specific friction.** - **Applicants need the right checklist.** A business account enquiry can require different documents depending on the type of business. - **The relevant fees are hard to find.** Customers need the current fee schedule for the account they are considering. - **Account questions need a secure channel.** Personal account details should go through the bank's authenticated process. **Questions visitors ask.** - What documents do I need to ask about a business account? - Where can I find the fees for this account? - Can I arrange a call with your business banking team? **What the assistant can take on.** - **Explain published products.** Make account features, fees, and eligibility information easier to find using your approved product summaries. (Use: current product information and fee schedules) - **Prepare application enquiries.** Share the document checklist and application route. Direct sensitive submissions to your approved account process. (Share: application steps and document checklists) - **Collect appointment requests.** Ask which service the visitor is interested in and how the relevant banking team can contact them. (Ask for: service interest and callback preference) - **Locate fee information.** Point visitors to the current fee schedule for the account they are exploring. - **Take a branch enquiry.** Gather the service and preferred branch for a callback from the banking team. - **Reach account support.** Direct personal account questions to the bank’s authenticated service channel. **Example roles for a banking service team.** - **Banking product guide.** Explains published account features, fees and application checklists for the product a visitor selects. - **Branch appointment enquiries.** Asks about the service, preferred branch and callback time so the right banking team can follow up. **Content to start with.** - Approved account and product summaries - Published fees and application checklists - Branch, appointment, and account support contacts **What stays with the team.** Authorised staff handle financial advice, eligibility decisions, identity checks, and account actions. Public chat should not request passwords or account credentials. **Limit.** Can it show balances or approve an application? This page describes product information and enquiry support. Account access needs authentication and an approved integration; application and credit decisions stay within your institution's authorised process. **Example: Business account enquiry.** Visitor: “What documents do I need to ask about a business account?” Assistant: “I can point you to the business account checklist. What type of business do you run, and would you like the team to contact you?” Details collected: Interest: Business account; Business type: Limited company; Next step: Banking team callback. Next: Enquiry for the business banking team. #### Insurance - [AI Chatbot for Insurance Teams](https://vatoo.ai/industries/insurance): Policy information, quote enquiries, and claims process guidance. For insurance brokers, insurers, and policyholder service teams. Vatoo explains your approved insurance information, collects quote enquiries, and guides people to the right claims process. Your team stays responsible for advice and decisions. **Where enquiries get stuck.** Visitors may be comparing cover or trying to understand how to report a claim. Clear wording and the correct contact route matter more than a confident guess. **Specific friction.** - **A claim starts with a process question.** Someone reporting a loss needs to know where to start and which documents to prepare. - **The wording matters.** An exclusion can only be explained in the context of the relevant policy document. - **A quote needs the right adviser.** Product interest and a contact preference give the authorised team a starting point. **Questions visitors ask.** - How do I start a home insurance claim? - Where can I find the exclusions for this policy? - Can someone contact me about a business insurance quote? **What the assistant can take on.** - **Find policy information.** Help visitors locate approved product summaries, definitions, and policy wording relevant to their question. (Use: approved wording and product documents) - **Collect quote enquiries.** Ask which insurance product and type of business or property the visitor wants to discuss with your team. (Ask for: product interest and callback details) - **Guide claims next steps.** Explain your reporting process and required documents, then direct policyholders to the official claims channel. (Share: reporting steps and claims contacts) - **Find policy wording.** Help a visitor locate the product document that contains definitions and exclusions. - **Take a renewal enquiry.** Collect the type of policy and preferred contact route for a renewal discussion. - **Reach a claims specialist.** Direct coverage and settlement questions to the authorised claims handler. **Example roles for a policyholder service team.** - **Policy information guide.** Helps visitors find the relevant policy wording, product summary and published renewal information. - **Claims process guide.** Explains where to report a claim and which documents to prepare before the insurer reviews it. **Content to start with.** - Approved product summaries and policy wording - Claims reporting steps and document checklists - Quote enquiry questions and support contacts **What stays with the team.** Your authorised team handles advice, underwriting, coverage interpretations, and claims decisions. The chatbot explains information and prepares enquiries. **Limit.** Can it tell a customer that a claim is covered? It should not promise coverage or a payout. It can help locate the relevant wording and explain the reporting process, while the authorised claims team reviews the policy and circumstances. **Example: Home claim process question.** Visitor: “How do I start a home insurance claim?” Assistant: “I can help you find the claim reporting steps. Which policy type is this about? Your claims team will review the circumstances and coverage.” Details collected: Policy type: Home insurance; Need: Start a claim; Next step: Official claims channel. Next: Claim decision stays with the insurer. #### Private Banking - [AI Chatbot for Private Banking](https://vatoo.ai/industries/private-banking): Service discovery, relationship-manager enquiries, and onboarding guidance. For private banks, relationship teams, and specialist client service teams. Vatoo explains your published private banking services and introductory process. Collect service interests and contact preferences for a personal follow-up from your team. **Where enquiries get stuck.** A prospective client may want to understand your services and initial process before discussing personal circumstances. Start with the information they need to arrange that conversation. **Specific friction.** - **Prospects want a discreet first contact.** A service interest and preferred contact time are enough to arrange an introduction. - **Services need a straightforward explanation.** Visitors may want to understand the bank's offering before discussing their personal situation. - **Onboarding uses trusted channels.** Identity documents and financial details need the bank's approved process. **Questions visitors ask.** - How do I arrange an introduction to a relationship manager? - Which private banking services do you offer? - What happens after an initial enquiry? **What the assistant can take on.** - **Explain the service offering.** Share approved descriptions of your banking and relationship services, with any published introductory requirements. (Use: approved service descriptions and FAQs) - **Collect introduction requests.** Ask for service interest, preferred location or time zone, and a convenient contact method for your relationship team. (Ask for: interest, location, contact preference) - **Explain onboarding steps.** Describe the published onboarding process and where clients can submit information through authorised channels. (Share: onboarding overview and official contact route) - **Prepare an introductory meeting.** Share the bank’s published first-meeting process and contact arrangements. - **Take an introduction enquiry.** Let a prospective client leave a convenient time zone and communication preference. - **Reach existing-client support.** Direct confidential account requests to the approved relationship channel. **Example roles for a relationship team.** - **Private banking guide.** Explains the bank’s service offering and the process for an initial introduction. - **Relationship team enquiries.** Records service interest and a convenient time and channel for a personal follow-up. **Content to start with.** - Approved private banking service descriptions - Published introduction and onboarding process - Relationship-team and client support contacts **What stays with the team.** Relationship managers handle suitability, financial advice, identity checks, and confidential account discussions through your approved processes. **Limit.** Should prospects share wealth or account information in chat? Use the initial chat to arrange an appropriate conversation. Detailed financial circumstances, identity documents, and account information should be collected only through your institution's approved channels. **Example: Relationship-team introduction.** Visitor: “How do I arrange an introduction to a relationship manager?” Assistant: “I can help you request an introduction. Which service interests you, and what is the best way and time for the relationship team to contact you?” Details collected: Interest: Private banking services; Request: Introductory conversation; Preference: Scheduled callback. Next: Relationship team to make contact. #### Wealth Management - [AI Chatbot for Wealth Management Firms](https://vatoo.ai/industries/wealth-management): Service information, fee questions, and adviser meeting requests. For wealth managers, financial planning firms, and adviser practices. Vatoo explains your wealth management services, published fees, and introductory process. Collect service interests and meeting requests for your advisers to follow up personally. **Where enquiries get stuck.** A prospect may be looking for retirement planning, ongoing advice, or help organising finances. Explain your offering and first-meeting process in straightforward language. **Specific friction.** - **A prospect wants to understand the service.** A planning topic and meeting preference help the firm arrange the right introduction. - **Fees matter before the first meeting.** Visitors want to understand the published charging model before discussing finances. - **Advice requires personal context.** An adviser needs a proper assessment before making a recommendation. **Questions visitors ask.** - Can I arrange an introductory meeting about retirement planning? - How does your firm charge for its services? - What happens at the first adviser meeting? **What the assistant can take on.** - **Explain your service model.** Help visitors understand your planning services, engagement process, and published fees using approved firm information. (Use: service descriptions and approved fee information) - **Collect meeting enquiries.** Ask which service interests the prospect and when and how they would like an adviser to contact them. (Ask for: service interest and meeting preference) - **Share meeting preparation.** Explain what the first meeting covers and how to provide documents through your firm's approved process. (Share: first-meeting guide and secure submission route) - **Explain published fees.** Point prospects to the firm’s approved fee information and what an introductory meeting covers. - **Take an adviser meeting request.** Collect the planning topic, meeting preference, and a convenient time to contact the prospect. - **Reach the advice team.** Direct personal investment or retirement decisions to an adviser who can assess the situation. **Example roles for a advisory practice.** - **Advisory services guide.** Explains published services, fees and what a prospective client can expect at the first meeting. - **Adviser introduction enquiries.** Collects the planning topic and preferred meeting format so an adviser can follow up personally. **Content to start with.** - Approved planning services and fee information - First-meeting and engagement process guides - Adviser contacts and document submission instructions **What stays with the team.** Your advisers assess personal circumstances, suitability, investments, and recommendations. Sensitive financial details belong in your approved advice process. **Limit.** Will the chatbot suggest investments or a retirement strategy? No. It can explain your firm's services and introductory process. Personal recommendations require a qualified adviser's assessment of the client's circumstances, objectives, and suitability. **Example: Retirement planning introduction.** Visitor: “Can I arrange an introductory meeting about retirement planning?” Assistant: “I can help you request an introductory meeting. Would you prefer a video call or an in-person conversation, and when is convenient?” Details collected: Interest: Retirement planning; Meeting: Introductory video call; Preference: Weekday morning. Next: Adviser to arrange a personal conversation. ### Health #### Dental - [AI Chatbot for Dental Practices](https://vatoo.ai/industries/dental): New patient questions, visit preparation, and appointment requests. For dental practices, dental groups, and specialist clinics. Vatoo answers questions about your dental services, practice hours, and first visits. Collect appointment requests while reception supports patients at the desk. **Where enquiries get stuck.** They may want to know whether you accept new patients, what a first visit involves, or how to request an appointment. Make those answers easy to find. **Specific friction.** - **New patients need a clear starting point.** They want to know how to request a check-up and when reception will confirm a time. - **First visits raise practical questions.** Patients can prepare more easily when they know what to bring and where to go. - **Urgent enquiries need a different route.** The practice's urgent contact instructions matter more than a routine appointment request. **Questions visitors ask.** - Are you taking new patients for a routine check-up? - What happens at my first dental appointment? - Who should I call if I need urgent dental help? **What the assistant can take on.** - **Explain practice information.** Share opening hours, services, access information, and published new-patient arrangements from your practice pages. (Use: practice FAQs and service information) - **Collect appointment requests.** Ask whether the visitor is a new patient, which routine appointment they want, and how reception can contact them. (Ask for: visit type, preferred day, contact) - **Share visit preparation.** Explain your approved first-visit instructions and provide the practice's contact route for questions that need a clinician. (Share: first-visit guidance and practice contacts) - **Explain registration.** Share the practice’s new-patient process and where required forms should be completed. - **Take a callback request.** Let prospective patients leave a suitable time for reception to discuss routine visits. - **Find urgent dental contacts.** Show the urgent contact instructions approved by the practice. **Example roles for a dental reception team.** - **Practice information guide.** Answers questions about new-patient registration, routine visits and your published urgent-care contacts. - **Reception enquiries.** Records the routine appointment type and preferred contact time for reception to review. **Content to start with.** - Practice hours, services, and new-patient FAQs - Approved first-visit preparation instructions - Appointment policies and urgent contact information **What stays with the team.** Your dental team handles symptoms, urgent concerns, treatment recommendations, and appointment confirmation. The chatbot supports practice administration. **Limit.** Can it advise patients about tooth pain or treatment? Use Vatoo for practice information and appointment requests. Clinical questions need your dental team; urgent concerns should be directed to your published urgent-care contact instructions. **Example: New patient check-up request.** Visitor: “Are you taking new patients for a routine check-up?” Assistant: “I can help you send a check-up request. Which day suits you? Reception will check new-patient availability and contact you to confirm.” Details collected: Patient: New to the practice; Visit: Routine check-up; Preferred day: Thursday. Next: Reception to confirm availability. #### Eldercare - [AI Chatbot for Care Homes and Eldercare](https://vatoo.ai/industries/eldercare): Care service information, family enquiries, and visit requests. For care homes, home-care providers, and senior living services. Explain your care services, visiting arrangements, and enquiry process. Vatoo helps families ask initial questions and request a call or visit with your care team. **Where enquiries get stuck.** Families may be comparing types of care, locations, and visiting arrangements. Clear information can help them prepare for a conversation with someone who understands their situation. **Specific friction.** - **Families may be exploring several homes.** Location and the type of care they are considering help the team arrange a useful first visit. - **Everyday arrangements matter.** Visiting times, facilities, and daily routines can help a family prepare its questions. - **Care needs are personal.** A qualified team member needs time and the right setting to discuss an individual assessment. **Questions visitors ask.** - Can we arrange a visit to discuss residential care? - What types of care do you provide? - How does the initial care assessment work? **What the assistant can take on.** - **Explain care options.** Share your published service descriptions, facilities, and visiting information in accessible language. (Use: care services and family information) - **Collect callback requests.** Ask about the service being explored, preferred location, and a convenient time for a family conversation. (Ask for: service, location, callback preference) - **Prepare a visit.** Explain the visit and assessment process and collect a preferred date for your team to arrange. (Share: visit arrangements and assessment steps) - **Explain visiting arrangements.** Share visiting times, location information, and the home’s family visit process. - **Take a family callback request.** Let relatives leave the service they are considering and a convenient time to talk. - **Speak with the care team.** Direct individual care questions to the staff responsible for assessments. **Example roles for a care enquiries team.** - **Family information guide.** Explains care options, visiting arrangements and what families can expect on a first visit. - **Care visit enquiries.** Records the location, service of interest and preferred callback time so a family can speak with the care team. **Content to start with.** - Care service descriptions and facility information - Visiting arrangements and family FAQs - Assessment process and enquiry contacts **What stays with the team.** Your care team assesses needs and suitability, confirms places, and handles health information or urgent welfare concerns personally. **Limit.** Can Vatoo assess a person's care needs? No. It can explain your services and arrange an enquiry. Care assessments, suitability decisions, and sensitive family discussions should be handled by your qualified team. **Example: Family visit request.** Visitor: “Can we arrange a visit to discuss residential care?” Assistant: “I can help you request a visit. Which location are you considering, and when would it be convenient for our team to call you?” Details collected: Interest: Residential care; Request: Visit and introductory call; Preferred time: Weekday afternoon. Next: Care team to contact the family. #### Healthcare - [AI Chatbot for Healthcare Providers](https://vatoo.ai/industries/healthcare): Clinic information, visit preparation, and routine appointment enquiries. For clinics, outpatient services, and healthcare reception teams. Vatoo answers clinic questions, shares approved visit instructions, and collects routine appointment requests. Give patients a clear way to contact your reception team. **Where enquiries get stuck.** Patients often need directions, opening hours, or instructions for arranging a visit. Make those basics easier to find while clinical questions go to your healthcare team. **Specific friction.** - **Routine requests reach a busy desk.** Reception needs the clinic, visit type, and a convenient way to contact the patient. - **First visits bring practical questions.** Patients often need appointment instructions, opening hours, or directions before setting out. - **Clinical questions need clinical staff.** Questions about symptoms or urgent care belong with the clinic's designated care team. **Questions visitors ask.** - How can I request a routine appointment at your clinic? - What should I bring to my first visit? - Where can I find your clinic's opening hours and directions? **What the assistant can take on.** - **Answer clinic questions.** Explain your locations, hours, services, accessibility information, and contact options using current clinic pages. (Use: clinic information and service descriptions) - **Collect routine visit requests.** Ask for the appointment category, preferred time, and contact route so reception can follow up. (Ask for: visit category, preferred time, contact) - **Share approved instructions.** Help patients find the preparation information your clinic has approved and the right contact for further questions. (Share: clinic-approved visit preparation) - **Find a clinic location.** Share current directions, opening hours, and access information for the selected site. - **Take a reception callback request.** Collect a convenient time to discuss a routine administrative question. - **Reach clinical support.** Show the clinic’s approved contact instructions when the question needs a healthcare professional. **Example roles for a clinic reception team.** - **Clinic information guide.** Answers questions about the selected clinic’s services, access and approved preparation instructions. - **Routine appointment enquiries.** Collects the visit category and callback preference for reception, with a separate contact route for clinical concerns. **Content to start with.** - Clinic services, opening hours, and location pages - Approved first-visit and preparation instructions - Appointment policies and patient contact routes **What stays with the team.** Clinicians handle symptoms, diagnosis, treatment, and urgent concerns. Review data handling before collecting health information in any chatbot setup. **Limit.** Is this a medical advice or emergency triage chatbot? No. The setup described here supports clinic information and routine administration. Clinical or urgent questions should use your approved clinician and emergency contact routes. **Example: Routine appointment enquiry.** Visitor: “How can I request a routine appointment at your clinic?” Assistant: “I can help you send a routine appointment request. Which clinic would you like to visit, and when is a convenient time for reception to contact you?” Details collected: Request: Routine appointment; Location: Main clinic; Contact preference: Afternoon callback. Next: Reception to arrange the next step. #### Medical Claims - [AI Chatbot for Medical Claims Support](https://vatoo.ai/industries/medical-claims): Claim preparation, submission guidance, and enquiry routing. For claims administrators, health plan service teams, and provider support teams. Vatoo explains approved medical claim procedures and submission checklists. Guide members and providers to the correct claims channel without promising a coverage or payment decision. **Where enquiries get stuck.** Members and providers need to know which process to follow and where to submit documents. Make those instructions clear before a claim reaches the review team. **Specific friction.** - **The checklist depends on who is submitting.** A member reimbursement can follow a different process from a provider claim. - **Documents need the correct destination.** Sending records through the approved channel helps put the claim in front of the right team. - **Claim status needs an authorised source.** Members need their official portal or claims contact for a decision about their own case. **Questions visitors ask.** - What documents do I need to submit a reimbursement claim? - Where should a provider send a claim enquiry? - How can I check the status through your official portal? **What the assistant can take on.** - **Explain submission steps.** Help people find the procedure and document checklist for their claim type using your approved guidance. (Use: claim-type instructions and checklists) - **Direct members and providers.** Ask whether the visitor is a member or provider, then explain the appropriate submission and support route. (Ask for: requester type and process question) - **Guide status enquiries.** Show how to access the official claims portal or contact the team for a case-specific question. (Share: portal guidance and claims contacts) - **Find the correct submission route.** Show the authorised portal for the requester’s claim type and provider or member role. - **Explain missing-document steps.** Direct claimants to the published correction process and support contact. - **Reach a claims reviewer.** Show the official review or appeal route for case-specific decisions. **Example roles for a claims support desk.** - **Member claims guide.** Helps members find the reimbursement checklist and official submission portal for their claim type. - **Provider enquiries.** Directs providers to their submission instructions and the authorised team for case-specific questions. **Content to start with.** - Approved claim procedures and document checklists - Member and provider submission routes - Portal instructions and claims team contacts **What stays with the team.** Claims specialists decide coverage, reimbursement, and appeals. Medical records and personal claim details need your approved secure process. **Limit.** Can Vatoo tell someone their claim is approved? Only an authorised claims source can provide a case-specific decision. This setup explains the process; accessing claim status would require appropriate authentication, permissions, and a supported integration. **Example: Reimbursement checklist enquiry.** Visitor: “What documents do I need to submit a reimbursement claim?” Assistant: “I can help you find the submission checklist. Is this a member reimbursement or a provider claim? Please use the approved claims channel for medical records.” Details collected: Requester: Member; Claim type: Reimbursement; Need: Document checklist. Next: Member directed to approved submission steps. #### Veterinary - [AI Chatbot for Veterinary Practices](https://vatoo.ai/industries/veterinary): Practice information, routine visit requests, and preparation guidance. For veterinary clinics, animal hospitals, and veterinary reception teams. Vatoo answers practice questions and collects routine appointment enquiries. Share approved visit instructions while your veterinary team focuses on animal care. **Where enquiries get stuck.** Owners may need opening hours, registration information, or a routine visit. Make those steps simple and keep your urgent veterinary contact instructions easy to find. **Specific friction.** - **A routine appointment needs the basics.** Species, visit reason, and registration status help reception prepare the request. - **New owners need registration steps.** The practice's approved process explains how to provide records before the visit. - **Urgent concerns need the veterinary team.** Owners need a clear urgent contact route when a routine appointment is unsuitable. **Questions visitors ask.** - Can I request a routine vaccination appointment for my dog? - How do I register a new pet with your practice? - Which number should I call for urgent veterinary help? **What the assistant can take on.** - **Answer practice questions.** Explain opening hours, services, registration steps, and location information from your approved practice content. (Use: practice services and new-client information) - **Collect routine appointment enquiries.** Ask for species, appointment type, and preferred day so reception can arrange the next step. (Ask for: species, visit type, preferred day) - **Share approved preparation.** Help owners find your visit preparation instructions and the correct practice contact for questions that need a vet. (Share: approved visit guidance and care contacts) - **Explain pet registration.** Share the practice’s new-client steps and approved process for transferring records. - **Take a routine visit enquiry.** Let owners share the species and visit category for reception to review. - **Find urgent veterinary contacts.** Show the practice’s urgent care instructions when an owner needs a veterinary professional. **Example roles for a veterinary reception team.** - **Practice information guide.** Explains registration, visit preparation and how to reach the practice for urgent veterinary help. - **Routine visit enquiries.** Asks for species, visit category and preferred day before reception arranges the next step. **Content to start with.** - Practice services, hours, and registration instructions - Approved routine visit preparation information - Appointment policies and urgent veterinary contacts **What stays with the team.** Veterinary professionals handle symptoms, diagnosis, treatment, and urgent concerns. The chatbot supports administration and directs owners to your practice. **Limit.** Can the chatbot tell an owner whether their pet needs urgent care? Do not use this administrative setup to assess urgency or diagnose a pet. Show your practice's approved urgent-contact instructions and direct health questions to a veterinary professional. **Example: Routine vaccination enquiry.** Visitor: “Can I request a routine vaccination appointment for my dog?” Assistant: “I can collect a routine appointment request. Is your dog already registered with the practice, and which day would suit you? Reception will confirm the next step.” Details collected: Pet: Dog; Visit: Routine vaccination enquiry; Preferred day: Monday. Next: Reception to review and arrange the visit. ### Hospitality and events #### Event Management - [AI Chatbot for Event Management](https://vatoo.ai/industries/event-management): Event briefs, venue questions, and planning enquiries. For event planners, production agencies, and venue teams. Vatoo answers package and planning questions, then collects dates, guest numbers, and venue needs. Give your event team the context to prepare a relevant proposal. **Where enquiries get stuck.** A date and a budget are only the start. Guest count, event format, location, and production needs all affect the proposal your team prepares. **Specific friction.** - **A headcount does not make an event brief.** Date, location, layout, and production requirements shape what a planner can offer. - **Package inclusions affect the budget.** The organiser needs to know whether the proposal should include catering, staging, and AV. - **Dates depend on more than one supplier.** A planner has to check availability before committing a venue or confirming a proposal. **Questions visitors ask.** - Can you help plan a company event for 120 guests? - Do your packages include catering and AV? - What do you need before preparing an event proposal? **What the assistant can take on.** - **Explain packages and services.** Use your published packages to answer questions about planning, production, catering coordination, and what is included. (Use: package details and service scope) - **Collect the event brief.** Ask about event type, date, location, guest count, and budget range before your team reviews the enquiry. (Ask for: date, location, guests, requirements) - **Answer attendee questions.** For a published event, explain the schedule, venue access, and registration process from current event information. (Share: agenda, venue details, registration steps) - **Prepare a venue enquiry.** Gather layout, guest count, and accessibility requirements for a planner to review. - **Take a production request.** Collect the event date and AV or staging needs for the production team. - **Discuss date changes.** Direct date changes and supplier commitments to the planner responsible for the event. **Example roles for a event planning team.** - **Event services guide.** Explains package inclusions, venue facilities and attendee information from your event materials. - **Planning enquiries.** Collects the date, guest count, format and production requirements for the planner preparing the proposal. **Content to start with.** - Event packages and included services - Venue capacities and briefing questions - Published agendas, access details, and booking terms **What stays with the team.** Your planners confirm venue availability, supplier commitments, budgets, and contracts. A chat enquiry does not reserve an event date. **Limit.** Can it produce and confirm a final event quote? It can explain published packages and collect the brief. Final pricing and availability depend on the venue, suppliers, production requirements, and your planning team's review. **Example: Company event enquiry.** Visitor: “Can you help plan a company event for 120 guests?” Assistant: “I can put together an event brief. What date and location are you considering, and do you need a venue, catering, or production support?” Details collected: Event: Company gathering; Guests: 120; Needs: Venue and AV. Next: Planning team to review the requirements. #### Hospitality - [Hotel AI Chatbot for Room Enquiries and Guest Questions](https://vatoo.ai/industries/hospitality): Room questions, stay enquiries, and guest information. For hotels, resorts, guesthouses, and accommodation providers. Vatoo helps guests understand your rooms, amenities, and stay policies. Collect room and group-stay enquiries while your reservations team looks after current guests. **Where enquiries get stuck.** Room types, parking, breakfast, accessibility, and check-in arrangements can shape a booking decision. Give guests a clear answer and a way to ask about their dates. **Specific friction.** - **The room must suit the people staying.** A family needs to check occupancy and room arrangements before settling on dates. - **Small amenities shape the decision.** Parking and breakfast can matter as much as the room rate when guests compare properties. - **Arrival requests need confirmation.** A late arrival or special room request needs someone at the property to confirm the arrangement. **Questions visitors ask.** - Do you have rooms suitable for a family of four? - Is parking available and is breakfast included? - Can we request a late arrival? **What the assistant can take on.** - **Explain rooms and amenities.** Answer questions about room types, facilities, and included services using your current property information. (Use: room descriptions and amenity details) - **Collect stay enquiries.** Ask for dates, guest numbers, and room preferences so reservations can check suitable options. (Ask for: dates, guests, room preferences) - **Share guest information.** Explain check-in instructions, published policies, and how guests can request help from your team. (Share: arrival guidance and guest contacts) - **Prepare for arrival.** Share the property’s check-in instructions, reception hours, and arrival contact. - **Take a group-stay enquiry.** Collect estimated room count, dates, and group needs for the reservations team. - **Request a change to a stay.** Explain how guests can ask reservations to review a change or special arrangement. **Example roles for a reservations desk.** - **Guest information guide.** Answers questions about room types, facilities, breakfast and arrival arrangements from the property’s guest guide. - **Reservations enquiries.** Collects travel dates, guest numbers and room preferences so reservations can check rooms and rates. **Content to start with.** - Room types, amenities, and property information - Arrival instructions and guest service details - Booking, cancellation, and group enquiry policies **What stays with the team.** Reservations staff or your connected booking system confirms rooms, rates, and changes. Special requests remain subject to your property's approval. **Limit.** Will it show live room availability and book a stay? Live availability and confirmed reservations need a supported connection to your booking system. Without that, Vatoo can explain room options and collect an enquiry for reservations to review. **Example: Family stay enquiry.** Visitor: “Do you have rooms suitable for a family of four?” Assistant: “I can collect a family-room enquiry. What are your arrival and departure dates, and how many adults and children will be staying?” Details collected: Guests: Two adults, two children; Stay: Three nights; Preference: Family room. Next: Reservations to confirm rooms and rates. #### Marina Management - [Marina Chatbot for Berth Enquiries and Guest Questions](https://vatoo.ai/industries/marina-management): Berth enquiries, vessel details, and marina guest information. For marinas, yacht harbours, boat clubs, and dock offices. Vatoo explains marina facilities and collects arrival dates, boat length, beam, and draft. Give your dock office the details it needs to review a berth request. **Where enquiries get stuck.** Dates alone are not enough. Your dock office needs vessel dimensions and service requirements before it can offer an appropriate berth or mooring. **Specific friction.** - **A berth request arrives without dimensions.** Dates and boat length help, but the dock office may still need beam and draft to check fit. - **Boaters ask about shoreside facilities.** Shore power and arrival arrangements can affect whether a visiting boat can stay. - **A space needs confirming.** The dock office checks the vessel and available berth before the boater can rely on a reservation. **Questions visitors ask.** - Can I request a berth for a 12-metre sailing boat next weekend? - What shore power and facilities do you offer? - Where can I find your arrival and check-in instructions? **What the assistant can take on.** - **Explain marina facilities.** Share published information about shore power, water, showers, fuel services, and shoreside amenities. (Use: facility information and marina policies) - **Collect berth enquiries.** Ask for arrival and departure dates, length, beam, draft, and service needs before your team checks a berth. (Ask for: dates, length, beam, draft) - **Share guest information.** Help guests find check-in instructions and marina office contacts from your approved visitor guide. (Share: visitor guide and dock office contacts) - **Explain marina rates.** Show published rate categories and the vessel dimensions the office uses to check a price. - **Take a late-arrival enquiry.** Collect the intended arrival time and show the marina’s approved arrival contact. - **Request help from the dock office.** Pass questions about berth suitability and unusual vessel requirements to marina staff. **Example roles for a dock office.** - **Marina guest guide.** Answers questions about shore power, facilities and check-in using the marina’s visitor guide. - **Berth enquiries.** Asks for dates, length, beam and draft so the dock office can check whether a berth will fit. **Content to start with.** - Marina facilities, berth categories, and published rates - Vessel requirements and booking policies - Visitor guide and arrival contact instructions **What stays with the team.** Your dock office confirms berth allocation and availability. Navigational directions, weather decisions, and vessel safety stay with the appropriate personnel. **Limit.** Can it confirm a berth reservation? It can collect a complete berth request. Confirmation requires your marina team or a supported connection to the booking system, including a check of availability and vessel suitability. **Example: Weekend berth request.** Visitor: “Can I request a berth for a 12-metre sailing boat next weekend?” Assistant: “What are your arrival and departure dates, beam, and draft? The dock office will use those details to check a suitable berth.” Details collected: Vessel: 12 m sailing boat; Beam / draft: 3.8 m / 1.9 m; Stay: Friday–Sunday. Next: Dock office to confirm a suitable berth. #### Restaurants - [AI Chatbot for Restaurants](https://vatoo.ai/industries/restaurants): Menu questions, table enquiries, and private-dining requests. For restaurants, cafés, dining groups, and private-dining teams. Vatoo explains your menu, opening hours, and reservation policies. Collect table and private-dining enquiries so guests can take the next step without waiting for a phone call. **Where enquiries get stuck.** Party size, opening times, a menu question, or an event requirement can shape the decision. Help guests find the practical details while service is busy. **Specific friction.** - **A table request arrives during service.** The host needs party size and time before checking the table plan. - **Guests check the menu before calling.** Current dishes and opening hours help someone decide whether to visit. - **Private dining requires a conversation.** Date, group size, and the occasion give the events team a useful starting point. **Questions visitors ask.** - Can I enquire about a table for eight on Saturday? - Where can I see your current menu? - Do you have a space for a private dinner? **What the assistant can take on.** - **Answer dining questions.** Share your current menu, opening hours, location, and published dining policies from information your team provides. (Use: menu, hours, and guest information) - **Collect table requests.** Ask for date, preferred time, party size, and contact details before your team or booking system confirms a table. (Ask for: date, time, party size, contact) - **Prepare private-dining enquiries.** Collect the occasion, date, guest count, and requirements so your events team can discuss a suitable arrangement. (Collect: occasion, guests, date, requirements) - **Explain private dining options.** Share room capacities, event formats, and published minimum-spend terms. - **Take a booking enquiry after service.** Collect the preferred date, time, and party size for the host to check. - **Reach the restaurant team.** Direct allergy questions and special arrangements to staff who can verify them. **Example roles for a front-of-house team.** - **Dining information guide.** Answers questions about the current menu, opening hours and published dining policies. - **Table and event enquiries.** Asks for the date, time and party size so the host can check a table or a private room. **Content to start with.** - Current menu, opening hours, and location details - Reservation and cancellation policies - Private-dining options and event enquiry requirements **What stays with the team.** Staff confirm tables, special arrangements, and dietary requests. Allergen questions need current approved information and direct staff review where uncertain. **Limit.** Can it guarantee a table or confirm an allergy request? A table requires confirmation by staff or a supported booking connection. Dietary requests should be checked with the restaurant; the chatbot must not infer that a meal is safe from an incomplete menu description. **Example: Group table enquiry.** Visitor: “Can I enquire about a table for eight on Saturday?” Assistant: “What time would you prefer on Saturday? I can collect the request for eight guests so the restaurant can check and confirm availability.” Details collected: Party size: Eight guests; Date: Saturday; Preferred time: 7 pm. Next: Restaurant to confirm the reservation. #### Travel & Tourism - [Travel Agency Chatbot for Tour and Booking Enquiries](https://vatoo.ai/industries/travel-tourism): Tour questions, personalised trip enquiries, and booking guidance. For travel agencies, tour operators, destination specialists, and tourism businesses. Vatoo explains your tours and booking policies, then collects dates, group size, and travel preferences. Help your agents prepare relevant options for the next enquiry. **Where enquiries get stuck.** Travel style, dates, party size, and budget shape the options an agent can suggest. Collect those preferences while the traveller is exploring your website. **Specific friction.** - **A destination is only part of a trip.** Dates, party size, and interests help an adviser choose options that suit the traveller. - **Package inclusions affect the choice.** Transfers, meals, and activities can differ between two similar itineraries. - **Changes need checking with reservations.** The team must check terms and availability before promising an amendment. **Questions visitors ask.** - Can you help plan ten days in Japan for a family of four? - What is included in this tour package? - How do I request a change to an existing booking? **What the assistant can take on.** - **Explain your tours.** Answer questions about itinerary, inclusions, pace, and published booking terms from your current tour information. (Use: tour pages, brochures, and booking policies) - **Build a travel enquiry.** Ask for destination, dates, group size, interests, and budget range before an agent prepares options. (Ask for: dates, travellers, interests, budget) - **Guide existing-booking requests.** Explain your published change process and collect an enquiry for the reservations team to review. (Share: change-request steps and support contacts) - **Explain tour inclusions.** Help travellers check meals, activities, transfers, and other items in a published package. - **Take a group trip enquiry.** Collect dates, party size, travel style, and preferred destination for a travel adviser. - **Reach reservations.** Direct existing-booking changes to the team that can verify availability and terms. **Example roles for a travel advisers.** - **Tour information guide.** Helps travellers compare itinerary details and see what each published package includes. - **Trip planning enquiries.** Collects dates, group size, interests and budget range to give a travel adviser a starting brief. **Content to start with.** - Current tour itineraries and package inclusions - Trip briefing questions and booking terms - Change procedures and traveller support contacts **What stays with the team.** Agents confirm prices, availability, and booking changes. Entry rules, travel suitability, and time-sensitive requirements need current specialist or official sources. **Limit.** Will Vatoo build and book a complete trip automatically? It can explain your published tours and gather a useful trip brief. Final itineraries, availability, prices, and bookings need your travel team or supported booking connections configured for those actions. **Example: Family trip enquiry.** Visitor: “Can you help plan ten days in Japan for a family of four?” Assistant: “What month would you like to travel, and what do you most want to experience? I can gather your preferences for a travel adviser.” Details collected: Destination: Japan; Travellers: Family of four; Duration: Ten days. Next: Travel adviser to prepare suitable options. ### Industrial and resources #### Agriculture - [AI Chatbot for Agriculture Businesses](https://vatoo.ai/industries/agriculture): Product enquiries, equipment questions, and grower requests. For agricultural suppliers, equipment dealers, and grower services. Answer questions about your agricultural products, delivery areas, and services. Vatoo collects crop, location, and quantity details for your sales team to follow up. **Where enquiries get stuck.** A product name alone rarely tells your team enough. Crop type, order size, location, and seasonal timing help them work out what to offer. **Specific friction.** - **A catalogue item is only a starting point.** Crop, growing area, and delivery location help a supplier understand what the farm needs. - **Delivery depends on the farm.** A grower may need to check coverage before working out an order quantity. - **Seasonal timing matters.** A planting window gives the sales team a specific date against which to check supply. **Questions visitors ask.** - Do you supply irrigation equipment for vegetable farms? - Can you deliver to farms in my area? - What details do you need for a bulk order quote? **What the assistant can take on.** - **Explain the product range.** Help growers explore equipment and supplies using your catalogue, published specifications, and service information. (Use: catalogues and product specifications) - **Prepare bulk enquiries.** Collect product, quantity, location, and required delivery period before your team checks stock and prepares a quote. (Ask for: quantity, location, delivery period) - **Direct service requests.** Ask for the equipment model and type of help needed. Show the right service contact or collect a callback request. (Collect: model and service request) - **Find delivery information.** Help growers check the published delivery area and how bulk orders are handled. - **Take a seasonal order enquiry.** Capture the product and target planting period while a grower is planning the season. - **Reach a product specialist.** Pass model compatibility and field-specific questions to the supplier’s technical team. **Example roles for a grower services team.** - **Equipment guide.** Helps growers find catalogue details, delivery areas and the service contact for a particular model. - **Grower enquiries.** Records the crop, quantity, farm location and planting window for the supplier to review. **Content to start with.** - Product catalogues and equipment guides - Delivery areas and order requirements - Service contacts and approved product FAQs **What stays with the team.** Your specialists confirm product suitability, stock, and pricing. Agronomic decisions and chemical application advice need qualified review. **Limit.** Will it recommend fertiliser or pesticide treatments? Keep recommendations that depend on crop conditions, soil testing, or local rules with your agronomist. Vatoo can explain approved product information and collect a request for specialist help. **Example: Irrigation equipment enquiry.** Visitor: “Do you supply irrigation equipment for vegetable farms?” Assistant: “I can help you send an enquiry. What crop do you grow, how large is the area, and where is the farm?” Details collected: Crop: Vegetables; Area: 12 hectares; Need: Irrigation equipment. Next: Requirements prepared for the sales team. #### Manufacturing - [AI Chatbot for Manufacturing Companies](https://vatoo.ai/industries/manufacturing): Capability questions, production quote requests, and product support. For manufacturers, contract producers, and industrial suppliers. Vatoo explains manufacturing capabilities and collects part, material, quantity, and delivery requirements. Prepare better enquiries for your engineering and sales teams. **Where enquiries get stuck.** A buyer may know what they want made but leave out material, quantity, or delivery timing. Help them understand what your team needs before pricing the work. **Specific friction.** - **A part description leaves gaps.** Material, quantity, finish, and delivery date affect the production quote. - **Buyers need to check capability.** A current list of processes and materials helps a buyer shortlist a supplier. - **Specifications need engineering review.** Drawings and tolerances need someone to check the part can be made as specified. **Questions visitors ask.** - Can I request a quote for 500 aluminium components? - Which materials and manufacturing processes do you support? - What drawings or specifications should I prepare? **What the assistant can take on.** - **Explain your capabilities.** Answer questions about published processes, materials, product ranges, and production capabilities from your technical information. (Use: capability pages and product specifications) - **Collect production requirements.** Ask for part description, material, quantity, and target delivery before engineering reviews the specification. (Ask for: part, material, quantity, delivery) - **Direct technical support.** Help customers find approved documentation or request product support with the model and issue described. (Collect: product reference and support question) - **Prepare drawings for review.** Explain the approved route for submitting part drawings and specifications. - **Take a distributor enquiry.** Ask about product range, territory, and business contact before sales follows up. - **Request an engineering review.** Collect tolerance or material questions for an engineer to assess against the specification. **Example roles for a estimating and engineering team.** - **Manufacturing capability guide.** Helps buyers check supported processes, materials and drawing requirements against your capability sheets. - **Production quote assistant.** Collects the part description, quantity, material and delivery target for commercial and engineering review. **Content to start with.** - Manufacturing capabilities and material specifications - Quote requirements and drawing submission instructions - Product documentation and technical support contacts **What stays with the team.** Engineers confirm tolerances, manufacturability, and technical suitability. Sales confirms production capacity, delivery dates, and final quotations. **Limit.** Can the chatbot approve a technical specification? It can explain your published capabilities and gather a quote brief. Technical acceptance, tolerance review, certification, and production commitments require your engineering and commercial teams. **Example: Component quote request.** Visitor: “Can I request a quote for 500 aluminium components?” Assistant: “I can prepare a quote enquiry. What manufacturing process do you need, when are the components required, and do you have drawings ready?” Details collected: Material: Aluminium; Quantity: 500 components; Documents: Drawings available. Next: Engineering and sales to review the requirements. #### Mining - [AI Chatbot for Mining Companies](https://vatoo.ai/industries/mining): Supplier enquiries, procurement guidance, and service requests. For mining operators, equipment suppliers, and mining service businesses. Vatoo explains your published procurement and service enquiry processes. Collect supplier capabilities and project interests before the right commercial team reviews them. **Where enquiries get stuck.** A general inbox can receive equipment proposals, contractor questions, and community enquiries together. A clear first step helps each requester find the right route. **Specific friction.** - **A supplier introduction needs context.** The service category and operating region help procurement assess where an enquiry belongs. - **Registration requires preparation.** Suppliers need the operator's current checklist before gathering evidence. - **Site and commercial requests can get mixed.** Equipment proposals and access requests must reach different authorised teams. **Questions visitors ask.** - How can our maintenance company register interest as a supplier? - Which documents are needed for your supplier review? - Where should I send an equipment service enquiry? **What the assistant can take on.** - **Explain supplier requirements.** Share the published registration process and qualification checklist without implying approval or preferred-supplier status. (Use: public supplier and procurement guidance) - **Collect capability enquiries.** Ask for service category, operating region, and company contact so procurement can assess the enquiry. (Ask for: category, region, company contact) - **Direct service questions.** Help requesters find the published equipment, maintenance, or site enquiry contact relevant to their request. (Share: approved service and site contact routes) - **Find tender instructions.** Help suppliers identify the published procurement channel for their category. - **Take an equipment proposal.** Collect the equipment type, supported region, and company contact for commercial review. - **Direct site access questions.** Show the published access contact for questions that require site authorisation. **Example roles for a procurement office.** - **Supplier registration guide.** Explains the published procurement route and the documents a prospective supplier should prepare. - **Commercial enquiries.** Records the equipment or service category, operating region and company contact for procurement review. **Content to start with.** - Public procurement and supplier requirements - Approved service categories and company information - Site enquiry and community contact procedures **What stays with the team.** Procurement staff approve suppliers and contracts. Site access, operational instructions, and safety matters remain with authorised personnel. **Limit.** Can it approve a contractor for mine-site access? No. It can explain the published access request process and point to the responsible team. Site clearance, induction completion, and operating permissions need your authorised controls. **Example: Maintenance supplier enquiry.** Visitor: “How can our maintenance company register interest as a supplier?” Assistant: “I can help you find the supplier process. What maintenance services do you offer, and which regions can your company support?” Details collected: Service: Equipment maintenance; Coverage: Regional operations; Request: Supplier registration guidance. Next: Procurement team to assess the enquiry. #### Oil & Gas - [AI Chatbot for Oil and Gas Services](https://vatoo.ai/industries/oil-gas): Service scope, supplier enquiries, and procurement information. For energy service providers, equipment suppliers, and procurement teams. Vatoo explains your oil and gas services and procurement process. Collect service category, project location, and timing for your commercial team to review. **Where enquiries get stuck.** Equipment, field services, and supplier proposals involve different requirements. Capturing the category and project context early makes it easier to reach the right team. **Specific friction.** - **A maintenance enquiry needs a scope.** The facility, work required, and planned shutdown window shape the discussion. - **Suppliers need the approved route.** A prospective vendor needs the correct registration process for its service category. - **Technical commitments need review.** Engineering and site teams confirm whether a proposed service is suitable. **Questions visitors ask.** - Can we discuss maintenance services for an energy facility? - What is your process for new supplier enquiries? - Which equipment and service capabilities do you publish? **What the assistant can take on.** - **Explain service capabilities.** Answer questions from your published equipment and service catalogue, with clear limits on what is included. (Use: approved capabilities and service descriptions) - **Collect project requirements.** Ask for service type, project location, stage, and target timing before your commercial team follows up. (Ask for: service, location, stage, timing) - **Guide supplier submissions.** Point potential suppliers to the current registration requirements and procurement contact for their category. (Share: supplier process and required information) - **Find procurement requirements.** Share the relevant supplier checklist and submission route for the service category. - **Take an equipment enquiry.** Collect the equipment type, project location, and required delivery period. - **Request technical scope review.** Route field-specific requirements and operational questions to the responsible technical team. **Example roles for a commercial services team.** - **Supplier process guide.** Helps vendors locate the registration requirements and procurement contact for their service category. - **Project service enquiries.** Collects the facility type, maintenance scope and required timing for a commercial review. **Content to start with.** - Published service capabilities and equipment information - Supplier registration and procurement requirements - Commercial enquiry fields and approved contacts **What stays with the team.** Qualified teams handle process safety, operating procedures, site permissions, and technical acceptance. Procurement approves suppliers and contractual commitments. **Limit.** Can the chatbot guide plant operations or maintenance procedures? Keep operational and safety-critical instructions within your authorised systems and teams. This setup supports public service information, supplier process questions, and commercial enquiries. **Example: Facility maintenance enquiry.** Visitor: “Can we discuss maintenance services for an energy facility?” Assistant: “I can prepare a service enquiry. Which type of facility and maintenance scope are involved, and when would you like to discuss the requirement?” Details collected: Service: Planned maintenance; Project: Energy facility; Timing: Upcoming shutdown period. Next: Commercial team to review the scope. #### Supply Chain - [AI Chatbot for Supply Chain Teams](https://vatoo.ai/industries/supply-chain): Supplier guidance, order enquiries, and procurement request routing. For supply chain service providers, procurement teams, and supplier support desks. Vatoo explains your supplier processes and collects procurement or order enquiries. Help partners find the right instructions and give your team the reference details to follow up. **Where enquiries get stuck.** Supplier registration, purchase-order questions, and delivery exceptions need different owners. Ask for the enquiry type and reference before passing the conversation along. **Specific friction.** - **An order question needs a reference.** The purchase-order number and issue type help the team find the right record. - **Supplier registration has its own route.** A new supplier needs the current checklist and procurement contact. - **Delivery changes need review.** A proposed date change only takes effect after the responsible buyer accepts it. **Questions visitors ask.** - Who can help with a question about our purchase order? - How do we apply to become a supplier? - Where should we report a change to a planned delivery? **What the assistant can take on.** - **Explain supplier processes.** Share approved onboarding steps, submission requirements, and the relevant procurement contact. (Use: supplier instructions and onboarding checklists) - **Collect order questions.** Ask for the order reference and issue type so your team can locate the appropriate record and respond. (Ask for: reference, enquiry type, company contact) - **Prepare exception enquiries.** Collect a brief description of a delivery or supply issue and direct it through your approved escalation process. (Collect: affected reference and change requested) - **Find invoice instructions.** Show the current invoicing process and the reference details suppliers should include. - **Record delivery changes.** Collect the order reference and proposed change for the supply team to review. - **Reach the procurement owner.** Direct approval and contractual questions to the person responsible for the order. **Example roles for a supplier support desk.** - **Supplier onboarding guide.** Helps partners find registration requirements, invoice instructions and procurement contacts. - **Order enquiries.** Collects the purchase-order reference and requested change so the responsible buyer can review it. **Content to start with.** - Supplier onboarding and procurement process guides - Order enquiry and delivery exception procedures - Invoice submission instructions and team contacts **What stays with the team.** Your teams approve suppliers, order changes, and commitments. Live inventory, purchase-order status, and commercial records need authorised system access. **Limit.** Can Vatoo access our ERP and update purchase orders? An ERP connection is a separate implementation with specific permissions and validation. Start with published process information and enquiry collection; discuss required read or write actions before promising them to users. **Example: Purchase-order enquiry.** Visitor: “Who can help with a question about our purchase order?” Assistant: “What is the purchase-order reference, and is your question about the specification, delivery date, or invoice process?” Details collected: Reference: Example PO-2048; Question: Delivery date change; Requester: Supplier contact. Next: Responsible team to review the order question. #### Warehouse & Logistics - [AI Chatbot for Warehousing and Fulfilment](https://vatoo.ai/industries/warehouse-logistics): Storage enquiries, fulfilment briefs, and handling requirements. For warehouse operators, fulfilment providers, and third-party logistics teams. Vatoo explains your warehousing and fulfilment services and collects stock, volume, and handling requirements. Help your team assess fit before preparing a proposal. **Where enquiries get stuck.** Pallet storage, ecommerce picking, returns, and special handling all change the scope. A useful enquiry explains the goods and activity your facility would need to support. **Specific friction.** - **Pallet count leaves out the activity.** Order frequency and the goods being stored affect the service a warehouse can offer. - **Fulfilment requirements vary.** Picking, packing, and returns can require different facilities and processes. - **Capacity needs a facility check.** Storage type and handling requirements must be reviewed before space is confirmed. **Questions visitors ask.** - Can you quote for storing 40 pallets and dispatching weekly orders? - Do you offer pick-and-pack for online stores? - What product information do you need to assess our requirements? **What the assistant can take on.** - **Explain warehouse services.** Help visitors understand your published storage, picking, packing, and returns services and the goods you handle. (Use: facility capabilities and service descriptions) - **Collect volume requirements.** Ask for product types, pallet or stock volume, order frequency, and handling needs before your team checks fit. (Ask for: goods, storage volume, order activity) - **Guide onboarding enquiries.** Explain your setup process and the data or documents your team requests before taking on a new customer. (Share: onboarding checklist and account contacts) - **Explain accepted goods.** Show the warehouse’s published handling capabilities and restrictions before collecting an enquiry. - **Take a fulfilment enquiry.** Collect stock types and weekly order volume for the commercial team. - **Request a capacity check.** Pass storage and special handling requirements to the facility team for confirmation. **Example roles for a warehouse sales team.** - **Warehouse services guide.** Helps potential clients check accepted goods, handling capabilities and onboarding requirements. - **Storage and fulfilment enquiries.** Collects pallet volume, order frequency and handling needs so the warehouse team can assess capacity. **Content to start with.** - Warehouse capabilities and accepted goods information - Storage and fulfilment quote requirements - Customer onboarding and service procedures **What stays with the team.** Your team confirms capacity, goods acceptance, handling requirements, and pricing. Live inventory or order status needs a warehouse-system connection. **Limit.** Can it tell customers their current stock levels? Live stock requires a supported warehouse management system connection and appropriate customer access controls. Without that setup, use the chatbot for service information and account enquiries. **Example: Storage and dispatch enquiry.** Visitor: “Can you quote for storing 40 pallets and dispatching weekly orders?” Assistant: “What goods are on the pallets, roughly how many orders go out each week, and are there any special storage or handling requirements?” Details collected: Storage: 40 pallets; Activity: Weekly order dispatch; Goods: Packaged household items. Next: Warehouse team to review capacity and scope. ### Infrastructure and utilities #### Energy & Utilities - [AI Chatbot for Energy and Utility Providers](https://vatoo.ai/industries/energy-utilities): Billing guidance, moving-home questions, and service reporting routes. For energy suppliers, water providers, and utility service teams. Vatoo explains published utility services, billing processes, and moving-home steps. Guide customers to account support and official reporting channels when they need more help. **Where enquiries get stuck.** A customer moving home needs a checklist. Someone reporting a hazard needs your official urgent contact route. Make both easy to find without implying the chat controls the network. **Specific friction.** - **Moving creates several tasks at once.** Someone leaving a property needs the right account steps and contact route. - **Bills prompt repeated questions.** Customers often need help finding the part of a bill or tariff guide that applies to them. - **A supply problem can be urgent.** Customers need to find the utility's official reporting route quickly. **Questions visitors ask.** - What do I need to do when I move out? - Where can I find help understanding my bill? - How do I report a supply problem? **What the assistant can take on.** - **Explain bills and services.** Answer general questions from your published tariff information and billing guides without exposing account-specific records. (Use: approved tariff and billing information) - **Guide moving-home steps.** Explain the process and information customers need before directing them to your account portal or support team. (Share: moving instructions and portal links) - **Show the reporting channel.** Make official outage and hazard reporting contacts easy to find using the current instructions your team approves. (Share: official reporting and urgent support routes) - **Locate account forms.** Direct customers to the official account process for a move or service change. - **Take a billing enquiry.** Help customers identify the official billing channel outside office hours. - **Find urgent network contacts.** Show the provider’s own hazard and outage reporting routes for the customer’s area. **Example roles for a utility service team.** - **Customer service guide.** Helps customers find published billing explanations, moving-home steps and account forms. - **Supply issue guide.** Directs reports to the utility’s official outage or urgent contact channel for the relevant area. **Content to start with.** - Billing guides and published service information - Moving-home and account support instructions - Official outage reporting and emergency contacts **What stays with the team.** Your teams handle account changes, billing disputes, network operations, and hazards. Live outage information needs an authoritative connected source. **Limit.** Can the chatbot give live outage updates? Only with a supported connection to an authoritative outage source. Without one, it should direct customers to your official status page and reporting contacts rather than estimate restoration times. **Example: Moving-home enquiry.** Visitor: “What do I need to do when I move out?” Assistant: “I can explain the moving process. Are you leaving a property or moving into one? Your account portal or support team can complete the account change.” Details collected: Request: Moving out; Timing: End of the month; Help needed: Account closure steps. Next: Customer directed to the account process. #### Renewable Energy - [AI Chatbot for Renewable Energy Companies](https://vatoo.ai/industries/renewable-energy): System questions, site-assessment enquiries, and project requirements. For solar installers, renewable energy providers, and energy project teams. Vatoo explains renewable energy systems and collects property, location, and project details. Help your team prepare a useful first conversation before assessing a site. **Where enquiries get stuck.** Visitors want to understand suitability, cost, and the installation process. Your team needs the building type, location, and project goals before giving a meaningful proposal. **Specific friction.** - **System interest starts before a survey.** Location and property type help the installer understand the proposed project. - **Owners want to know what happens on site.** The assessment process explains what the engineer needs to see and measure. - **Output and cost need a design.** A site review comes before a system recommendation or savings estimate. **Questions visitors ask.** - Can I request a solar assessment for our warehouse roof? - What happens during a site assessment? - Do you offer battery storage alongside solar? **What the assistant can take on.** - **Explain systems and services.** Answer questions about your published solar, storage, and renewable energy services using approved product information. (Use: system descriptions and product guides) - **Collect project details.** Ask for property type, location, project goal, and approximate energy-use context for your assessment team. (Ask for: site type, location, goal, usage context) - **Guide the assessment process.** Explain the steps from initial enquiry to site review and proposal, including what information your team requests. (Share: assessment steps and preparation checklist) - **Explain the installation process.** Show the published steps from site assessment to a final system proposal. - **Take a battery storage enquiry.** Collect the existing system type and storage goal for an installer to review. - **Request an engineering assessment.** Direct roof suitability and system sizing questions to the technical team. **Example roles for a site assessment team.** - **System information guide.** Explains the solar and storage services you offer and what happens during an assessment. - **Site assessment enquiries.** Collects the property type, location and energy goal before an engineer reviews the site. **Content to start with.** - System descriptions and approved product information - Site-assessment requirements and enquiry fields - Installation process and service policies **What stays with the team.** Engineers assess site suitability and design. Your team confirms quotations, savings estimates, incentives, and project commitments after review. **Limit.** Can it calculate guaranteed savings or payback? It can explain your published process and collect information for an assessment. Savings and payback depend on the site, usage, system design, tariffs, and costs, so your specialists should prepare and qualify any estimate. **Example: Commercial solar enquiry.** Visitor: “Can I request a solar assessment for our warehouse roof?” Assistant: “I can prepare a site-assessment request. Where is the warehouse, what is the approximate roof area, and what would you like the system to achieve?” Details collected: Property: Commercial warehouse; Interest: Rooftop solar; Next step: Site assessment. Next: Assessment team to review the site enquiry. #### Telecoms - [AI Chatbot for Telecom Providers](https://vatoo.ai/industries/telecoms): Plan questions, installation guidance, and connectivity enquiries. For broadband providers, mobile operators, and business connectivity teams. Vatoo explains your telecom plans and installation process using approved information. Collect coverage and support enquiries so your team can check the details that depend on the customer. **Where enquiries get stuck.** Customers also need to know what is available at their address, how installation works, and where to get support. Make the process clear before they commit. **Specific friction.** - **Service depends on the address.** Area-wide coverage does not guarantee a connection at a specific building. - **Plan details are easy to confuse.** Customers need the published features and terms of the plan they are considering. - **Installation needs preparation.** Site access and equipment requirements matter before a visit is confirmed. **Questions visitors ask.** - How do I check whether your broadband is available at my address? - What is included in the business internet plan? - What happens during installation? **What the assistant can take on.** - **Explain published plans.** Help customers compare included features, stated terms, and installation options using your current plan information. (Use: current plan details and service terms) - **Collect coverage enquiries.** Ask for the location and connection type required, then direct the customer to your availability checker or team. (Ask for: location and service interest) - **Share setup and support steps.** Provide approved router setup guidance and the correct contact route for faults or account questions. (Share: installation guides and support channels) - **Explain installation preparation.** Share the provider’s instructions for site access, equipment, and installation appointments. - **Take a business connectivity enquiry.** Collect location, service interest, and desired start period for a sales callback. - **Reach fault support.** Direct connection faults to the official diagnostics or support route. **Example roles for a connectivity team.** - **Plan and setup guide.** Explains published features, installation steps and where customers can check coverage at an address. - **Connectivity enquiries.** Records the service type, location and desired start date for the team checking availability. **Content to start with.** - Current plans, included features, and service terms - Installation and approved setup guides - Coverage-checking and fault-reporting instructions **What stays with the team.** Your provider systems confirm address availability, achievable service, and installation dates. Account changes and network issues require authorised support. **Limit.** Can it guarantee broadband speed at an address? It should explain only your approved service information. Address-level availability and expected speeds need a current check through your network or provisioning system, with any applicable qualifications. **Example: Broadband coverage enquiry.** Visitor: “How do I check whether your broadband is available at my address?” Assistant: “You can check your address through our availability process. Is this for a home or business connection, and which area are you in?” Details collected: Service: Business broadband; Need: Address availability check; Next step: Official coverage checker. Next: Availability to be verified for the address. ### Local services #### Automotive - [AI Chatbot for Car Dealers and Garages](https://vatoo.ai/industries/automotive): Vehicle questions, test-drive requests, and service enquiries. For car dealerships, independent garages, and vehicle service centres. Help buyers explore your vehicles and drivers request servicing. Vatoo collects the model, preferred date, and contact details for your dealership or garage. **Where enquiries get stuck.** Someone comparing cars needs different answers from someone arranging a service. A clear first question helps get each enquiry to the right department. **Specific friction.** - **A buyer needs to see the actual car.** Knowing the model and preferred day helps a sales adviser check a test drive. - **Workshop and sales enquiries mix.** A driver asking about hybrid servicing needs a technician rather than a showroom appointment. - **Trade-in values need a review.** Vehicle details give the appraiser somewhere to start before the inspection. **Questions visitors ask.** - Can I arrange a test drive of the compact SUV? - Do you service hybrid vehicles? - What information do you need for a trade-in enquiry? **What the assistant can take on.** - **Explain vehicle features.** Answer model and specification questions from your listings. Ask which vehicle interests the buyer before collecting a sales enquiry. (Use: current vehicle listings and specifications) - **Collect test-drive requests.** Ask for the vehicle, preferred day, and contact details. Your team confirms that the car and appointment are available. (Ask for: vehicle, day, contact details) - **Prepare service enquiries.** Collect make, model, service type, and preferred timing so the workshop can arrange the next step. (Collect: model, service needed, preferred date) - **Prepare a trade-in enquiry.** Explain which vehicle details the dealership asks for before discussing a valuation. - **Take a parts enquiry.** Collect the vehicle model and part description for the parts desk to check. - **Request a workshop callback.** Help a driver reach the service adviser when the right repair needs a technician’s assessment. **Example roles for a showroom and service desk.** - **Vehicle guide.** Answers model and equipment questions from the listings your dealership maintains. - **Showroom appointments.** Takes a test-drive request with the vehicle and preferred day so a salesperson can check availability. **Content to start with.** - Vehicle listings and specifications - Workshop services and opening hours - Test-drive and trade-in enquiry requirements **What stays with the team.** Your team confirms stock, appointments, trade-in values, finance terms, and repairs. Live inventory requires a connection to your vehicle system. **Limit.** Can it show which vehicles are in stock right now? Your uploaded listings can explain vehicles, but live stock needs a supported connection to the inventory source. Without that connection, collect an enquiry for the sales team to verify. **Example: Test-drive request.** Visitor: “Can I arrange a test drive of the compact SUV?” Assistant: “Which SUV are you interested in, and what day suits you? The sales team will check the vehicle and confirm a time with you.” Details collected: Vehicle: Compact SUV; Preferred day: Saturday; Request: Test drive. Next: Sales team to confirm vehicle and time. #### Beauty & Aesthetics - [AI Chatbot for Salons and Beauty Clinics](https://vatoo.ai/industries/beauty-aesthetics): Service menus, appointment requests, and preparation questions. For salons, beauty studios, spas, and aesthetic clinics. Vatoo explains your beauty services, prices, and booking policies. Collect appointment requests while your salon or clinic team focuses on the client in front of them. **Where enquiries get stuck.** Clients may need to understand a treatment, its duration, or whether a consultation comes first. A clear answer can help them decide to get in touch. **Specific friction.** - **Clients are unsure which service to choose.** A consultation, colour appointment, and treatment can require different preparation. - **Duration affects the booking.** Someone planning a visit after work needs the service length as well as the price. - **Suitability needs a practitioner.** Individual skin or treatment concerns belong in a conversation with the person providing care. **Questions visitors ask.** - Do I need a consultation before booking a skin treatment? - How long does a cut and colour appointment take? - What is your cancellation policy? **What the assistant can take on.** - **Explain the service menu.** Answer questions about published services, durations, and prices using the menu your team provides. (Use: current menu, prices, and service descriptions) - **Collect appointment requests.** Ask which service the client wants, their preferred day, and how your team should contact them. (Ask for: service, preferred time, contact) - **Share booking preparation.** Explain your published consultation, deposit, patch-test, and cancellation requirements before the appointment. (Share: approved preparation and booking policies) - **Explain deposit terms.** Show the salon’s published deposit and cancellation rules before the client requests a slot. - **Take an after-hours salon enquiry.** Let clients leave their preferred service and day while the salon is closed. - **Reach a practitioner.** Collect a consultation request when suitability or personalised aftercare needs a practitioner. **Example roles for a salon or clinic.** - **Service menu guide.** Explains published service prices, durations and consultation requirements before a client chooses a treatment. - **Appointment enquiries.** Collects the service and preferred day, and gives clients a way to speak with a practitioner about suitability. **Content to start with.** - Service menu, durations, and published prices - Consultation and preparation instructions - Deposit, cancellation, and rescheduling policies **What stays with the team.** Practitioners assess suitability and give treatment advice. Your booking system or team confirms appointment times and any required checks. **Limit.** Can it recommend an aesthetic treatment? It can explain your published treatments and request a consultation. Suitability, contraindications, and personalised aftercare should be assessed by your practitioner, rather than decided in the chat. **Example: Consultation request.** Visitor: “Do I need a consultation before booking a skin treatment?” Assistant: “I can explain the clinic's consultation process and help you request a time. Which treatment are you interested in?” Details collected: Interest: Skin consultation; Preferred day: Friday; Next step: Clinic callback. Next: Team to confirm the consultation. #### Fitness & Wellness - [AI Chatbot for Gyms and Fitness Studios](https://vatoo.ai/industries/fitness-wellness): Class discovery, membership questions, and trial-session requests. For gyms, fitness studios, yoga centres, and wellness businesses. Vatoo explains class levels, membership options, and trial visits. Collect enquiries while your instructors focus on the session, with your timetable and policies behind every answer. **Where enquiries get stuck.** A prospective member may be unsure which class is suitable for beginners, what a membership includes, or what to bring. Help them prepare before they arrive. **Specific friction.** - **First-time members need to find their level.** A beginner looking for an evening class needs a timetable and a clear class description. - **Memberships include different things.** Visitors may need to check class access and cancellation terms before joining. - **A trial needs a real space.** The studio has to confirm the session and any individual requirements before the first visit. **Questions visitors ask.** - Do you have a beginner-friendly evening class? - What does the monthly membership include? - Can I request a trial session before joining? **What the assistant can take on.** - **Explain classes and levels.** Use your class descriptions and published timetable to help visitors explore activities, formats, and experience levels. (Use: class descriptions and current timetable) - **Answer membership questions.** Explain published fees, what is included, and your cancellation or freeze policy without inventing exceptions. (Use: membership options and terms) - **Collect trial requests.** Ask about the class, location, and preferred session so your team can confirm the first visit. (Ask for: class, location, preferred session) - **Prepare for a first session.** Explain what the studio asks new members to bring and when to arrive. - **Take interest in a trial class.** Let prospective members leave preferred classes and days after reception closes. - **Reach an instructor.** Arrange a conversation when a visitor has an individual suitability question. **Example roles for a studio team.** - **Class and membership guide.** Helps prospective members find class levels, timetable information and membership terms. - **Trial session enquiries.** Collects a class, studio location and preferred session for staff to check before the first visit. **Content to start with.** - Class descriptions, levels, and timetables - Membership prices and booking terms - First-visit instructions and instructor contacts **What stays with the team.** Instructors advise on individual suitability and health concerns. Your booking system or staff confirms spaces and membership changes. **Limit.** Can the chatbot recommend exercises for an injury? Keep individual exercise and health advice with a qualified professional. Vatoo can explain class descriptions and help a visitor request a conversation with an instructor. **Example: First class enquiry.** Visitor: “Do you have a beginner-friendly evening class?” Assistant: “Which activity would you like to try, and which evenings work for you? I can collect a trial request for the studio team.” Details collected: Interest: Beginner yoga; Preference: Weekday evening; Request: Trial session. Next: Studio team to confirm a suitable session. #### Home Services - [Home Services Chatbot for Job and Quote Requests](https://vatoo.ai/industries/home-services): Service-area checks, job enquiries, and visit requests. For plumbers, electricians, cleaners, landscapers, and home service teams. Vatoo answers service-area questions and gathers job details for quotes and visits. Help homeowners contact your business even when your team is on another job. **Where enquiries get stuck.** Homeowners want to know if you cover their area and handle their type of job. Your team needs the location, work required, and timing to follow up. **Specific friction.** - **The crew is already on a job.** Homeowners still need a way to describe the work while the team is out. - **Coverage comes before a quote.** The location helps the office check whether it serves the property. - **A useful estimate needs the scope.** Property type, size, and frequency affect whether a phone quote or site visit makes sense. **Questions visitors ask.** - Can I request a quote for cleaning a three-bedroom home? - Do you cover my postcode? - What information do you need before arranging a visit? **What the assistant can take on.** - **Explain services and coverage.** Use your service list and coverage areas to answer the questions homeowners ask before requesting help. (Use: service descriptions and coverage areas) - **Collect quote details.** Ask about property type, work required, location, and preferred timing so your team can assess the job. (Ask for: job type, location, scope, timing) - **Prepare a visit request.** Collect contact details and preferred dates. Your team confirms whether an assessment or service visit is needed. (Collect: preferred dates and callback details) - **Check the service area.** Use published coverage details to help homeowners check whether their area is served. - **Collect requests while crews are out.** Let a homeowner describe the work and preferred day while the office is busy. - **Arrange an assessment callback.** Give the team the job context before discussing an on-site visit or final price. **Example roles for a service and dispatch team.** - **Service area guide.** Checks the company’s published service areas and explains which jobs the team takes on. - **Job quote enquiries.** Collects the property type, work required and preferred timing before the team decides whether to visit. **Content to start with.** - Service descriptions and coverage areas - Quote questions and visit requirements - Booking policies and urgent contact instructions **What stays with the team.** Your team confirms prices, visit times, and work needed after assessment. Emergencies need your published urgent contact route. **Limit.** Can the chatbot give a final price for a job? It can share prices you publish and collect the information needed for a quote. Work that depends on property condition or an on-site assessment should be priced by your team. **Example: Home cleaning enquiry.** Visitor: “Can I request a quote for cleaning a three-bedroom home?” Assistant: “I can collect the details for a quote. What area is the property in, and are you looking for a one-off clean or a regular service?” Details collected: Property: Three-bedroom home; Service: Regular cleaning; Frequency: Every two weeks. Next: Team to review the job and provide a quote. #### Pet Care - [AI Chatbot for Pet Care Businesses](https://vatoo.ai/industries/pet-care): Service questions, pet intake, and booking requests. For groomers, boarding businesses, pet daycares, and pet service teams. Vatoo explains grooming, boarding, and daycare services. Collect pet details, preferred dates, and owner enquiries so your team can check the right next step. **Where enquiries get stuck.** Owners need to understand your services, preparation rules, and booking process. Your team needs the pet's type, size, and required service before confirming a visit. **Specific friction.** - **The pet and the service both matter.** Size and coat type help staff understand a grooming enquiry before quoting or booking. - **Boarding has preparation requirements.** Owners need the current checklist for records, belongings, and arrival arrangements. - **A first visit needs staff attention.** The team needs a conversation before confirming that a daycare arrangement will suit the pet. **Questions visitors ask.** - Can I request grooming for a medium-sized dog? - What do I need to prepare before boarding? - How do you arrange a first daycare visit? **What the assistant can take on.** - **Explain services and policies.** Answer questions about grooming menus, boarding arrangements, and daycare routines from your approved information. (Use: service menu and booking policies) - **Collect pet and visit details.** Ask about species, size, service needed, and preferred dates so staff can assess the request. (Ask for: pet type, size, service, dates) - **Share visit preparation.** Explain the records, belongings, or preparation your business requests before a visit, using your current policy. (Share: preparation checklist and first-visit steps) - **Explain boarding preparation.** Share your approved checklist for belongings, records, and arrival arrangements. - **Take a daycare enquiry.** Collect the pet’s size, requested sessions, and owner contact for staff review. - **Arrange a first-visit discussion.** Give staff the context to discuss behaviour, suitability, and individual arrangements. **Example roles for a pet care team.** - **Pet visit guide.** Explains grooming services, boarding preparation and the records owners should bring. - **Booking enquiries.** Collects the pet’s size, the service needed and preferred dates for staff to review. **Content to start with.** - Grooming, boarding, and daycare service information - Visit preparation and record requirements - Booking terms and first-visit procedures **What stays with the team.** Your team confirms acceptance, appointments, and care arrangements. Health concerns and urgent animal care questions should go to a veterinarian. **Limit.** Can it confirm that a pet is suitable for boarding or daycare? It can explain your policies and collect an initial enquiry. Staff must review health record requirements, behaviour considerations, and the suitability of the care arrangement before accepting a booking. **Example: Dog grooming request.** Visitor: “Can I request grooming for a medium-sized dog?” Assistant: “Which grooming service would you like, and what breed or coat type does your dog have? I can collect your preferred day for the grooming team.” Details collected: Pet: Medium-sized dog; Service: Bath and trim; Preferred day: Wednesday. Next: Grooming team to review and confirm. ### Professional services #### Accounting & Tax - [AI Chatbot for Accounting Firms](https://vatoo.ai/industries/accounting-tax): Service questions, document checklists, and new client enquiries. For accounting firms, tax advisers, and bookkeeping practices. Vatoo answers questions about your accounting services, explains what clients need to prepare, and collects new enquiries while your team focuses on the work. **Where enquiries get stuck.** A new client might need bookkeeping, payroll, or a tax return. Finding out which service, business type, and deadline they have can take several emails. **Specific friction.** - **The type of work is unclear.** A note asking for accounting help could mean monthly bookkeeping, payroll, or a one-off return. - **Clients arrive without their records.** A first meeting is more useful when clients know which records to prepare and where to send them. - **Tax questions need an accountant.** A client's circumstances matter before anyone can answer a question about their return. **Questions visitors ask.** - Can you help with bookkeeping for my small business? - What should I prepare before our first meeting? - Do you offer payroll alongside year-end accounts? **What the assistant can take on.** - **Explain your services.** Answer questions about bookkeeping, accounts, and payroll using your service pages. Help visitors identify the right team to contact. (Use: service descriptions and package details) - **Collect a useful enquiry.** Ask about business type, help needed, and timing so your team can prepare for the first conversation. (Ask for: service, business type, preferred contact) - **Share preparation checklists.** Point clients to the documents your practice requests and your approved upload portal, without asking for financial records in open chat. (Share: your checklist and submission instructions) - **Prepare for year-end.** Share the practice’s list of records to gather before the year-end review. - **Take a payroll enquiry.** Let employers leave their pay frequency and the help they need even when the payroll desk is closed. - **Request an adviser callback.** Flag filing questions that depend on the client’s circumstances for an accountant. **Example roles for a accounting practice.** - **Practice guide.** Explains which services cover bookkeeping, payroll or year-end accounts using the practice’s service list. - **New client assistant.** Collects the business type, service needed and deadline so an accountant can prepare for the first call. **Content to start with.** - Service packages and client FAQs - New client document checklists - Appointment and secure-upload instructions **What stays with the team.** Your accountants handle tax advice, filing decisions, and access to client records. The chatbot helps with service information and initial enquiries. **Limit.** Can it answer individual tax questions? Use it to explain your published services and preparation steps. Questions about a person's liability, deductions, or filing obligations should go to a qualified adviser with the full context. **Example: New bookkeeping enquiry.** Visitor: “Can you help with bookkeeping for my small business?” Assistant: “I can collect a few details for the bookkeeping team. What type of business do you run, and how soon do you need help?” Details collected: Business: Small retailer; Service: Monthly bookkeeping; Timing: Next month. Next: Enquiry ready for the practice to review. #### Consulting Firms - [AI Chatbot for Consulting Firms: Project Enquiries](https://vatoo.ai/industries/consulting-firms): Service discovery, project scoping, and discovery-call requests. For management consultancies, specialist advisers, and independent consultants. Vatoo explains your consulting services and asks prospects about their goals, challenges, and timing. Give your consultants a useful brief before the first call. **Where enquiries get stuck.** Prospects may know what is not working without knowing which service they need. A few focused questions help your team understand their situation. **Specific friction.** - **The request starts with a symptom.** A prospect may describe lost customers before they know what their onboarding process needs. - **Prospects want to know whether you fit.** Examples of comparable engagements help them decide whether to speak to a consultant. - **Discovery calls start from scratch.** A short account of the challenge lets the consultant spend the call exploring options. **Questions visitors ask.** - Can you help us improve our customer onboarding process? - Do you work with businesses of our size? - What happens in the first discovery call? **What the assistant can take on.** - **Explain your engagements.** Help visitors compare service areas and engagement formats using your own descriptions and case studies. (Use: services, engagement formats, case studies) - **Capture the business challenge.** Ask about the goal, current challenge, team involved, and timing so a consultant can assess fit. (Ask for: goal, challenge, team, timing) - **Prepare a discovery call.** Collect contact details and preferred times, and share what to prepare for an initial conversation. (Collect: call request and project context) - **Find a relevant case study.** Help a prospect find a published engagement in their sector or problem area. - **Take an enquiry between meetings.** Capture the goal and ideal engagement start date while consultants are with other clients. - **Prepare a specialist introduction.** Direct a clearly scoped enquiry to the practice area that handles the work. **Example roles for a consulting practice.** - **Practice guide.** Helps prospects compare your consulting services and find relevant published engagements. - **Discovery call assistant.** Asks what the client wants to change, who is involved and when they need help. **Content to start with.** - Consulting services and engagement criteria - Published case studies and discovery questions - Consultation process and team information **What stays with the team.** Consultants define the scope, commercial proposal, and recommendations. Confidential client advice belongs in your agreed engagement process. **Limit.** Can it qualify a consulting lead for us? It can ask the qualification questions you choose, such as project type, company size, and timing. Your consultants decide whether the engagement is suitable and what to propose. **Example: Discovery-call brief.** Visitor: “Can you help us improve our customer onboarding process?” Assistant: “I can prepare a brief for a consultant. Where are customers getting stuck today, and what would you like the onboarding process to achieve?” Details collected: Focus: Customer onboarding; Goal: A clearer first-week experience; Timing: This quarter. Next: Consultant to assess fit and arrange a call. #### Law Firms - [AI Chatbot for Law Firms](https://vatoo.ai/industries/law-firms): Practice-area discovery, consultation requests, and initial intake. For law firms, legal practices, and client intake teams. Vatoo explains your practice areas and consultation process, then collects a brief initial enquiry. Help prospective clients understand how to contact your firm without giving legal advice in chat. **Where enquiries get stuck.** Prospective clients may not know the name of the service they need. Explain your practice areas and the first consultation before asking for detailed case information. **Specific friction.** - **Clients may not know the practice area.** A broad matter description and location help intake direct a consultation request. - **Prospects need to understand the first meeting.** Published preparation and fee information help a client decide whether to get in touch. - **Sensitive details need a private route.** Conflicts checks and a lawyer's review come before detailed advice. **Questions visitors ask.** - Can I arrange a consultation about a commercial lease? - Does your firm handle employment matters? - What should I prepare for the initial consultation? **What the assistant can take on.** - **Explain practice areas.** Use your service pages to help visitors understand which team handles their type of enquiry. (Use: practice descriptions and office information) - **Collect consultation requests.** Ask for a broad matter category, jurisdiction, and contact details using intake questions approved by your firm. (Ask for: matter category, location, contact) - **Share preparation steps.** Explain your consultation process, published fees, and how to provide documents through the appropriate channel. (Share: consultation and document instructions) - **Find the relevant office.** Explain office locations and contact options for the practice area a visitor selects. - **Take an initial contact request.** Let a prospective client leave a broad matter category and preferred contact time. - **Reach the intake team.** Direct deadline and confidentiality questions to firm staff before detailed facts are shared. **Example roles for a client intake team.** - **Practice area guide.** Helps prospective clients find the relevant practice and understand how the first consultation works. - **Consultation enquiries.** Collects a broad matter category, location and callback preference for the firm’s intake staff. **Content to start with.** - Practice-area pages and consultation information - Firm-approved intake questions - Office contacts and secure document instructions **What stays with the team.** Lawyers handle legal advice, deadlines, conflicts checks, and engagement decisions. Detailed confidential information belongs in your approved intake process. **Limit.** Does using the chatbot establish a lawyer-client relationship? The chatbot should explain your firm's engagement process and approved notices. A chat enquiry alone should not be presented as acceptance of a matter, legal advice, or completed conflicts clearance. **Example: Commercial lease enquiry.** Visitor: “Can I arrange a consultation about a commercial lease?” Assistant: “I can help you request an initial consultation. Which location does the lease relate to, and how would you like the intake team to contact you?” Details collected: Matter: Commercial lease; Enquiry: Initial consultation; Next step: Intake team callback. Next: Firm to review intake and conflicts. #### Legal & Compliance - [AI Chatbot for Legal and Compliance Teams](https://vatoo.ai/industries/legal-compliance): Policy navigation, process questions, and review requests. For compliance consultancies, legal operations teams, and policy support teams. Vatoo makes approved policies and compliance procedures easier to navigate. Explain process steps and collect questions for the team responsible for interpretation and approval. **Where enquiries get stuck.** People need the right document, checklist, and owner before they can move forward. Questions about exceptions or legal interpretation still need an authorised reviewer. **Specific friction.** - **A requester needs the correct review path.** A new supplier review and an exception request have different owners. - **Incomplete submissions delay review.** The right document checklist can save a requester another round of questions. - **Exceptions need a named owner.** People need to know who can interpret the policy and consider formal approval. **Questions visitors ask.** - Where do I start a supplier due-diligence review? - Which documents does your review process require? - Who can consider an exception to this policy? **What the assistant can take on.** - **Locate policy guidance.** Help visitors find approved policy summaries and the process that applies to their enquiry. (Use: current policies and process guidance) - **Explain review requirements.** Share the published checklist and submission route so requesters can prepare the information your team needs. (Share: document checklist and submission steps) - **Collect review enquiries.** Ask for the review type, responsible business area, and requested timing before a specialist responds. (Ask for: review type, business area, timing) - **Find a policy owner.** Show the responsible contact listed in the current policy or procedure. - **Take a review request.** Collect the review category and target date before the compliance team picks it up. - **Request an exception review.** Explain the formal route for exceptions and who has authority to consider them. **Example roles for a compliance team.** - **Policy finder.** Helps requesters locate the current policy, review checklist and responsible owner. - **Review enquiries.** Records the type of review, business area and timing for an authorised specialist to consider. **Content to start with.** - Approved policies and process guidance - Review checklists and submission instructions - Policy owners and escalation contacts **What stays with the team.** Your authorised specialists interpret obligations, approve exceptions, and make compliance decisions. Restricted internal policies need an appropriate access-controlled setup. **Limit.** Can it certify that a business or supplier is compliant? No. It can explain your review process and collect an enquiry. Formal assessments, approvals, legal interpretations, and certifications require the responsible specialists and supporting evidence. **Example: Supplier review enquiry.** Visitor: “Where do I start a supplier due-diligence review?” Assistant: “I can show you the supplier review process. What type of supplier is involved, and are you starting a new review or following up on one?” Details collected: Review: Supplier due diligence; Supplier type: Software provider; Stage: New review. Next: Requester directed to the approved process. #### Marketing Agencies - [Marketing Agency Chatbot for Leads and Campaign Briefs](https://vatoo.ai/industries/marketing-agencies): Service questions, campaign briefs, and discovery-call requests. For digital agencies, creative studios, and performance marketing teams. Vatoo explains your agency services and asks prospects about their goals, channels, and budget range. Help your team start discovery with a clearer brief. **Where enquiries get stuck.** Prospects may ask for ads, a new website, or more enquiries without explaining the audience or current problem. Focused questions help your team prepare. **Specific friction.** - **A broad goal leaves the brief open.** An agency needs to know the offer, audience, and launch date before proposing channels. - **Prospects need to understand the scope.** A paid campaign may also need a landing page, creative work, or tracking setup. - **Discovery time is limited.** Knowing the prospect's goal and current channels leaves more time to discuss the work. **Questions visitors ask.** - Can you help us generate enquiries for our new service? - Do you handle both landing pages and paid campaigns? - What do you need before a discovery call? **What the assistant can take on.** - **Explain agency services.** Help visitors understand your service scope and explore relevant examples from your published portfolio. (Use: service pages and approved case studies) - **Build a campaign brief.** Ask about the offer, target audience, existing channels, budget range, and launch timing. (Ask for: goal, audience, budget, timing) - **Collect discovery requests.** Gather the brief and contact details, then explain what the first conversation with your agency covers. (Collect: project context and preferred contact) - **Find relevant agency work.** Guide prospects to published campaign examples for their sector or service interest. - **Take a launch enquiry.** Collect a proposed launch date, channel, and objective while the team is on client work. - **Arrange a strategy call.** Give the strategist the prospect’s brief before discussing scope and budget. **Example roles for a new business team.** - **Agency services guide.** Helps prospects find relevant portfolio work and understand whether your team covers their channels. - **Campaign brief assistant.** Collects the offer, audience, goals and launch timing before the first discovery call. **Content to start with.** - Agency services and portfolio examples - Discovery questions and engagement criteria - Published package details and onboarding steps **What stays with the team.** Your agency sets strategy, budgets, scope, and performance commitments. Client websites can use separate content and settings after the setup is agreed. **Limit.** Can we use Vatoo on websites we manage for clients? You can explore client-specific chatbot setups using each business's content and branding. Discuss account ownership, access, plan requirements, and ongoing management with Vatoo before rolling out across clients. **Example: New campaign enquiry.** Visitor: “Can you help us generate enquiries for our new service?” Assistant: “I can help prepare a brief. Who is the new service for, which channels are you using today, and when would you like the campaign to launch?” Details collected: Goal: More service enquiries; Work: Landing page and paid ads; Launch: Next quarter. Next: Agency team to scope the opportunity. #### Recruitment & HR - [AI Chatbot for Recruitment and HR](https://vatoo.ai/industries/recruitment-hr): Role questions, application guidance, and employer hiring enquiries. For recruitment agencies, staffing firms, and talent teams. Vatoo explains published roles, application steps, and recruitment services. Help candidates find the right information and employers prepare a hiring enquiry. **Where enquiries get stuck.** Location, work pattern, and application steps can determine whether someone applies. Employer enquiries need the role and hiring timeline before your team can discuss support. **Specific friction.** - **Applicants need the correct vacancy.** A role name can appear across several locations, so the job reference matters. - **Work patterns affect the decision.** A candidate may need to check the advertised location or schedule before applying. - **Employer enquiries need a hiring brief.** Headcount, role type, and start date give a recruiter something specific to act on. **Questions visitors ask.** - Where do I apply for the customer support role? - Is this role remote or office-based? - Can your team help us hire several warehouse staff? **What the assistant can take on.** - **Explain advertised roles.** Answer questions about published requirements, work location, and application steps using the current job description. (Use: job descriptions and application links) - **Guide candidate enquiries.** Show candidates how to apply and where to ask for an update or help with the application process. (Share: application instructions and recruiter contacts) - **Collect employer requirements.** Ask for role type, location, headcount, and target start period before your team follows up. (Ask for: role, location, headcount, timing) - **Find application requirements.** Show the documents and submission steps specified in the job listing. - **Take a staffing enquiry.** Collect role type, headcount, and target start period for an employer callback. - **Reach the recruiting team.** Direct application status or accommodation requests to the relevant recruiter. **Example roles for a recruiting team.** - **Candidate guide.** Helps applicants find the correct vacancy, work location and application steps. - **Employer hiring enquiries.** Collects the role, headcount, location and target start date before a recruiter discusses the brief. **Content to start with.** - Current job descriptions and application instructions - Recruitment service pages and employer brief questions - Candidate support and recruiter contact details **What stays with the team.** Recruiters make screening and hiring decisions. Personal records, employee issues, and applicant status require your approved processes and access controls. **Limit.** Will the chatbot decide which candidates move forward? This setup provides role information and enquiry support. Hiring decisions and candidate assessments stay with your recruitment team; Vatoo should not be presented as automatically accepting or rejecting applicants. **Example: Candidate application question.** Visitor: “Where do I apply for the customer support role?” Assistant: “I can help you find the application route. Which location is the customer support role based in, or do you have the job reference?” Details collected: Role: Customer support; Enquiry: How to apply; Reference: Example role CS-12. Next: Candidate directed to the application page. ### Property #### Architecture & Engineering - [AI Chatbot for Architects and Engineers](https://vatoo.ai/industries/architecture-engineering): Project briefs, service questions, and consultation requests. For architecture studios, engineering consultancies, and design practices. Vatoo explains your design and engineering services, answers early project questions, and collects the scope, location, and timing for a useful first meeting. **Where enquiries get stuck.** Prospects need to know whether you handle their building type and project stage. Your team needs a brief before it can discuss scope or fees. **Specific friction.** - **The project stage is missing.** A concept sketch and a set of tender drawings call for different conversations. - **Clients need to see the fit.** Building type and location help prospective clients find relevant work in your portfolio. - **A fee needs a brief.** Your team needs the scope before discussing the design work and its cost. **Questions visitors ask.** - Can you help with the design of a small office renovation? - Do you work on projects in our city? - What should we prepare for a design consultation? **What the assistant can take on.** - **Explain your expertise.** Use your portfolio and service pages to explain project types, disciplines, and the stages your practice supports. (Use: services, sectors, and selected projects) - **Build an initial brief.** Ask for project type, site location, approximate scope, and target dates before a discovery meeting. (Ask for: location, scope, project stage) - **Prepare the first meeting.** Share your consultation process and drawing requirements. Collect preferred times for your team to arrange a call. (Share: meeting preparation and next steps) - **Find a comparable project.** Point a prospective client to portfolio examples for their building type. - **Capture a site enquiry.** Let a property owner describe the site and current design stage outside studio hours. - **Request a feasibility review.** Collect the questions a project architect should address at the first meeting. **Example roles for a design studio.** - **Studio guide.** Helps a prospect find projects of a similar size, building type and design stage in your portfolio. - **Project enquiries.** Asks where the site is, what needs to change and which plans are ready for a consultation. **Content to start with.** - Service pages and project portfolio - Project briefing questions - Consultation process and document requirements **What stays with the team.** Your architects and engineers assess feasibility, technical design, building requirements, and fees. The chatbot does not approve a design. **Limit.** Can it give a design fee or confirm planning approval? It can explain your published fee approach and process. A project fee, engineering judgment, or planning outcome needs review by your team and the relevant authority. **Example: Office renovation brief.** Visitor: “Can you help with the design of a small office renovation?” Assistant: “I can gather the basics for the design team. Where is the office, roughly how large is it, and what stage is the project at?” Details collected: Project: Office renovation; Size: 250 m²; Stage: Early planning. Next: Brief ready for a discovery conversation. #### Construction - [AI Chatbot for Construction Companies](https://vatoo.ai/industries/construction): Project enquiries, quote preparation, and supplier questions. For building contractors, construction firms, and specialist trades. Vatoo explains your construction services and collects project location, scope, and timing. Give your estimating team a clearer starting point for every enquiry. **Where enquiries get stuck.** Your estimator needs to know where the job is, what needs building, and when the client hopes to start. Missing details slow down the first conversation. **Specific friction.** - **A price request comes without a scope.** An estimator needs to know what is being built, where it is, and how far the design has progressed. - **Service areas affect the answer.** A client needs to know whether the contractor can take on a project in that location. - **The site visit needs preparation.** Drawings and project details help the estimator make good use of the visit. **Questions visitors ask.** - Can you quote for an extension to a commercial building? - Do you cover projects in our area? - What plans do you need before a site visit? **What the assistant can take on.** - **Explain the work you take on.** Help visitors understand your project types, service area, and scope using your company information. (Use: services, locations, and project examples) - **Collect a project brief.** Ask about site location, size, project stage, and target start date before your estimator follows up. (Ask for: location, scope, stage, timing) - **Guide supplier enquiries.** Explain how subcontractors and suppliers can approach your procurement team and which documents your process requires. (Share: supplier requirements and contacts) - **Prepare for a site visit.** Explain the plans and project documents your estimator wants to see before visiting. - **Take a tender enquiry.** Collect the work package and submission date so the estimating team can assess the opportunity. - **Find the right project contact.** Direct contract changes and site-specific matters to the responsible project team. **Example roles for a estimating team.** - **Contractor services guide.** Helps owners check coverage, past project types and which plans your estimators ask to see. - **Estimating enquiries.** Collects the site, scope and proposed start date before an estimator reviews the job. **Content to start with.** - Construction services and coverage areas - Project briefing and site-visit requirements - Supplier enquiry and procurement instructions **What stays with the team.** Your team provides binding quotes, contracts, site assessments, and safety instructions. Chat enquiries do not approve work or commit resources. **Limit.** Can it give an accurate construction estimate? It can explain a published pricing approach and collect a project brief. A firm estimate needs your team's review of scope, drawings, site conditions, and current costs. **Example: Commercial extension enquiry.** Visitor: “Can you quote for an extension to a commercial building?” Assistant: “I can gather a brief for the estimating team. Where is the site, what size extension are you considering, and do you have plans yet?” Details collected: Project: Commercial extension; Stage: Plans prepared; Target start: Next spring. Next: Estimator to review scope and next steps. #### Facilities Management - [AI Chatbot for Facilities Management](https://vatoo.ai/industries/facilities-management): Maintenance requests, site information, and service enquiries. For facilities providers, building operators, and maintenance helpdesks. Vatoo helps building users explain a maintenance issue, find service instructions, and request support. Collect location and equipment details before your facilities team follows up. **Where enquiries get stuck.** Messages such as 'the light is broken' leave your helpdesk chasing the building, floor, and exact area. A few simple questions can make the report more actionable. **Specific friction.** - **The team cannot locate the fault.** A building name, floor, and room can turn a vague lighting report into work the team can assess. - **Service requests go to different desks.** Occupants need the contact for the right building and equipment. - **Access needs authorisation.** A contractor can follow the published process, but site staff must confirm permission. **Questions visitors ask.** - How do I report a broken light in our office? - Which team handles air-conditioning requests? - Where can contractors find your site access process? **What the assistant can take on.** - **Guide routine reports.** Ask for the building, area, asset, and a brief description so your helpdesk can review the request. (Ask for: building, location, asset, issue) - **Explain service procedures.** Answer questions about routine maintenance reporting and published service hours from your approved building information. (Use: service guides and site instructions) - **Direct contractor enquiries.** Explain onboarding and access request steps without granting access or sharing restricted building details. (Share: contractor process and responsible contacts) - **Find the service desk.** Show building users the correct contact for their location and type of request. - **Collect routine issues after hours.** Let occupants record the affected area and equipment for the next helpdesk shift. - **Find the emergency repair route.** Show the site’s approved urgent contact when the situation needs immediate attention. **Example roles for a facilities helpdesk.** - **Building service guide.** Helps occupants and contractors find the correct desk, service hours and site access instructions. - **Maintenance intake.** Collects the building, floor, asset and fault description so the helpdesk can review a routine repair. **Content to start with.** - Maintenance reporting and service guides - Public site information and service hours - Contractor onboarding and emergency contacts **What stays with the team.** Your facilities team prioritises work, authorises access, and handles emergency repairs. Show the designated urgent route for safety issues. **Limit.** Does a chat report automatically create a work order? Collecting a report and creating a work order are separate actions. A supported connection to your maintenance system is needed to create or update records there; otherwise your team reviews the enquiry. **Example: Lighting maintenance request.** Visitor: “How do I report a broken light in our office?” Assistant: “Which building and floor is the light on? Please include the room or area so the facilities team can locate it.” Details collected: Building: Office block A; Location: Second-floor meeting room; Issue: Ceiling light not working. Next: Helpdesk to review and assign the work. #### Property Management - [AI Chatbot for Property Management](https://vatoo.ai/industries/property-management): Maintenance reports, tenant information, and landlord enquiries. For property managers, letting agencies, and residential building teams. Vatoo explains your tenant procedures and collects maintenance details. Help residents find the right support while giving property managers the location and context behind each request. **Where enquiries get stuck.** Incomplete messages leave managers chasing details before they can arrange a repair. Tenants also need a clear distinction between routine reporting and emergency contacts. **Specific friction.** - **A repair report needs an exact location.** The property reference and affected room help a manager find the fault. - **New tenants have practical questions.** A move-in checklist puts keys, access, and contact arrangements in one place. - **Urgent issues need a direct contact.** A routine repair form can delay a resident who needs the building's emergency route. **Questions visitors ask.** - How do I report a leaking kitchen tap? - Where can I find the move-in checklist? - Who should I contact about an urgent building issue? **What the assistant can take on.** - **Collect routine repair reports.** Ask for the property reference, location of the issue, and a brief description so the manager can review it. (Ask for: property reference, area, issue) - **Explain tenant procedures.** Share your approved move-in, inspection, and routine reporting information without interpreting individual tenancy disputes. (Use: tenant handbook and service procedures) - **Prepare landlord enquiries.** Ask about the property type, location, and management service needed before your lettings team follows up. (Collect: property type, location, service interest) - **Find move-in instructions.** Show residents the checklist and contacts for their move-in arrangements. - **Record routine maintenance needs.** Collect the unit reference and repair description for the manager to review. - **Reach urgent building support.** Show emergency repair and building contacts from the property’s tenant guide. **Example roles for a property management team.** - **Tenant information guide.** Helps residents find move-in instructions, routine reporting procedures and emergency building contacts. - **Maintenance enquiries.** Collects the property reference, affected room and issue so the manager can assess the request. **Content to start with.** - Tenant handbook and routine reporting procedures - Move-in information and management services - Emergency contacts and repair enquiry requirements **What stays with the team.** Managers handle emergencies, access permissions, repair priorities, and tenancy disputes. Work orders or live updates need your connected property system. **Limit.** Will submitting a repair request schedule a contractor? A report starts the review process. Your manager must assess the issue and arrange access; automatic scheduling requires a supported integration and the appropriate permissions. **Example: Routine repair enquiry.** Visitor: “How do I report a leaking kitchen tap?” Assistant: “What is the property reference, and where is the tap located? If this is causing flooding or another urgent issue, please use the emergency contact in your tenant guide.” Details collected: Property: Example property A12; Location: Kitchen sink; Issue: Dripping tap. Next: Property manager to review the repair request. #### Real Estate - [Real Estate AI Chatbot for Listings and Viewing Requests](https://vatoo.ai/industries/real-estate): Listing questions, buyer preferences, and viewing requests. For estate agents, property brokers, developers, and letting teams. Vatoo answers listing questions and asks buyers or renters about their preferences. Collect property interests and viewing requests while your agents are out showing homes. **Where enquiries get stuck.** Visitors may want to check parking, move-in timing, or a detail missing from the listing. A useful answer and a simple viewing request keep the conversation moving. **Specific friction.** - **A viewing request is missing the listing.** The agent needs the property reference, contact details, and a time the visitor can attend. - **One feature can decide interest.** Parking or a move-in date can determine whether a buyer wants to see the property. - **Preferences need context.** Area, budget, and timing help an agent choose which listings to discuss. **Questions visitors ask.** - Can I request a viewing of the two-bedroom apartment? - Does the property include parking? - Can someone help me find homes in my preferred area? **What the assistant can take on.** - **Answer listing questions.** Explain property features and published details using your current listings, with a clear route for anything that needs checking. (Use: listings, floor-plan descriptions, property details) - **Collect buyer preferences.** Ask for area, property type, budget range, and moving timeline to prepare an enquiry for your agent. (Ask for: area, type, budget, timeline) - **Prepare viewing requests.** Collect the property reference, preferred time, and contact details. Your agent checks availability and arranges the visit. (Collect: property reference and preferred viewing time) - **Prepare a seller enquiry.** Ask for property type and location before an agent discusses a valuation visit. - **Take viewing interest after hours.** Let a visitor name the listing and a preferred day while the agency is closed. - **Request a listing detail check.** Collect questions an agent needs to verify with the owner or listing record. **Example roles for a estate agency.** - **Property listing guide.** Answers questions about a specific listing using the features and details your agency has published. - **Viewing enquiries.** Collects the listing reference and preferred visit time for an agent to check and confirm. **Content to start with.** - Current property listings and feature information - Viewing process and buyer enquiry questions - Agency services and office contacts **What stays with the team.** Agents confirm listing availability, viewings, offers, and negotiations. Legal or mortgage advice belongs with the appropriate professional. **Limit.** Will it only show properties that are still available? That depends on how listings are maintained. Live availability requires a supported property-system connection; static content should be kept current and availability confirmed by your agent. **Example: Apartment viewing enquiry.** Visitor: “Can I request a viewing of the two-bedroom apartment?” Assistant: “Which listing are you interested in, and when would you like to visit? The agent will check availability and confirm a viewing time with you.” Details collected: Property: Two-bedroom apartment; Preferred time: Saturday morning; Request: Viewing. Next: Agent to confirm property and viewing time. ### Science and life sciences #### Biotechnology - [AI Chatbot for Biotechnology Companies](https://vatoo.ai/industries/biotechnology): Service discovery, project enquiries, and sample submission guidance. For biotechnology companies, research service providers, and laboratories. Help researchers explore your biotechnology services and submission requirements. Vatoo collects project details so your scientific team can review the right information. **Where enquiries get stuck.** Researchers may be checking a service, planning a study, or preparing samples. Knowing the project stage and service needed helps your team respond usefully. **Specific friction.** - **A project starts with an open question.** The method, material, and project stage help scientists decide what to review. - **Sample requirements are easy to miss.** The correct submission instructions depend on the sample and the service requested. - **A study needs scientific review.** The team has to assess feasibility before confirming a method or timeline. **Questions visitors ask.** - Can I request a quote for an assay development project? - What information do you need before reviewing our study? - Where can I find your sample submission instructions? **What the assistant can take on.** - **Explain service capabilities.** Guide visitors through your published assay, testing, or research services without implying suitability for an unreviewed study. (Use: service catalogues and capability summaries) - **Collect project enquiries.** Ask for the service, project stage, sample type, and target timing before scientific review. (Ask for: service, sample type, project timing) - **Find submission guidance.** Point researchers to your approved sample requirements, submission forms, and project contact. (Share: current submission instructions) - **Prepare a sample submission.** Help researchers locate the lab’s approved submission form and instructions for their sample type. - **Take an assay enquiry.** Collect the study stage and target start period for a scientist to review. - **Request a technical discussion.** Direct questions about method selection and feasibility to the scientific team. **Example roles for a scientific services team.** - **Laboratory services guide.** Helps a researcher locate a testing capability, submission form or sample requirement in your lab documentation. - **Research project enquiries.** Records the proposed service, sample type and project stage for a scientist to assess. **Content to start with.** - Service catalogues and technical capability summaries - Sample submission and project enquiry instructions - Approved FAQs and scientific team contacts **What stays with the team.** Your scientific team confirms methods, sample suitability, timelines, and study scope. Confidential research and regulated decisions need your approved process. **Limit.** Can the chatbot design an experiment or interpret results? Keep study design, method selection, and result interpretation with your scientists. Vatoo helps visitors understand published services and prepare an enquiry for that review. **Example: Assay development enquiry.** Visitor: “Can I request a quote for an assay development project?” Assistant: “I can prepare a project enquiry. What type of assay do you need, what stage is the study at, and when would you like to begin?” Details collected: Service: Assay development; Stage: Feasibility planning; Target start: Next quarter. Next: Scientific team to review the brief. #### Pharmaceuticals - [AI Chatbot for Pharmaceutical Companies](https://vatoo.ai/industries/pharmaceuticals): Approved product information, distribution enquiries, and specialist contacts. For pharmaceutical companies, distributors, and product information teams. Vatoo helps visitors find approved product information and contact the appropriate team. Organise medical information, distribution, and product quality enquiries around your published processes. **Where enquiries get stuck.** A distributor asking about supply, a clinician requesting information, and someone reporting a concern should not follow the same enquiry path. Make the relevant contact clear. **Specific friction.** - **A distributor needs a commercial contact.** Territory, company type, and product range help the commercial team review an approach. - **Product material depends on the audience.** A visitor needs the approved information for their product and enquiry. - **Quality concerns have a defined route.** Safety and quality teams need reports through the designated reporting procedure. **Questions visitors ask.** - How can our company enquire about distributing your products? - Where can I request approved product information? - How do I report a product quality concern? **What the assistant can take on.** - **Find product information.** Direct visitors to approved, audience-appropriate product materials and the medical information contact for further questions. (Use: approved product materials and contact routes) - **Collect distribution enquiries.** Ask for company type, territory, and product interest so your commercial team can assess the request. (Ask for: company, territory, product interest) - **Show reporting contacts.** Make your approved safety and product quality reporting routes easy to find without treating a chat as a completed report. (Share: safety and quality reporting instructions) - **Locate approved materials.** Guide visitors to published materials appropriate to their audience and product enquiry. - **Take a commercial callback request.** Let a distributor leave a territory, product range, and preferred contact time. - **Reach the safety team.** Show the designated safety-reporting route for an adverse event or product complaint. **Example roles for a product enquiries team.** - **Product information guide.** Directs visitors to approved materials and the appropriate medical information or safety reporting contact. - **Distribution enquiries.** Collects company type, territory and product interest for the commercial team. **Content to start with.** - Approved product information and audience restrictions - Distribution enquiry requirements - Medical information, safety, and quality reporting contacts **What stays with the team.** Medical information, adverse-event handling, quality investigations, and regulatory decisions stay with your designated teams and reporting procedures. **Limit.** Can the chatbot answer questions about dosage or side effects? It should direct individual medical questions to the appropriate professional or medical information team. Use only approved materials and explicit reporting routes; do not present general chat as a substitute for your safety reporting process. **Example: Distribution enquiry.** Visitor: “How can our company enquire about distributing your products?” Assistant: “I can help prepare an enquiry for the commercial team. Which territory does your company serve, and which product range are you interested in?” Details collected: Enquiry: Distribution partnership; Company type: Licensed distributor; Interest: Product range information. Next: Commercial team to review the enquiry. ### Technology #### Cybersecurity - [AI Chatbot for Cybersecurity Companies](https://vatoo.ai/industries/cybersecurity): Assessment enquiries, service questions, and incident contact guidance. For security consultancies, managed security providers, and assessment teams. Explain your cybersecurity services, collect assessment enquiries, and direct urgent concerns to the right contact. Vatoo helps visitors find the next step without sharing sensitive evidence in chat. **Where enquiries get stuck.** A buyer comparing security services needs information. A customer reporting an incident needs your response channel. Your website should make that distinction clear. **Specific friction.** - **The assessment scope is missing.** The systems, environment, and deadline determine who needs to join the scoping call. - **Service boundaries need explaining.** Prospects need to understand which systems your assessment covers before requesting a proposal. - **An active incident needs a direct route.** An urgent report should reach the designated response channel without waiting for a sales callback. **Questions visitors ask.** - Can I request a security assessment for our company? - Which systems does your assessment service cover? - How do existing customers report an urgent incident? **What the assistant can take on.** - **Explain your service scope.** Answer questions about assessments, monitoring, and advisory services from your published scope and service descriptions. (Use: service scope and assessment FAQs) - **Collect assessment enquiries.** Ask about organisation size, systems in scope, and target timing so your specialists can arrange a scoping call. (Ask for: scope, organisation size, timing) - **Show the incident route.** Present your approved emergency reporting instructions and support contacts when a visitor needs incident assistance. (Share: your designated incident reporting channel) - **Prepare for a scoping call.** Explain what a prospect should have ready for a discussion about assessment scope. - **Take a monitoring enquiry.** Collect the service of interest and organisation size for the security sales team. - **Reach the incident team.** Show the designated incident channel when a customer reports an active threat. **Example roles for a security team.** - **Security services guide.** Explains the published scope of your assessments and points existing customers to the official incident channel. - **Assessment enquiries.** Collects the systems in scope and target review date so a specialist can arrange a scoping call. **Content to start with.** - Security service descriptions and scope - Assessment briefing questions - Approved incident reporting contacts and instructions **What stays with the team.** Active incidents, credentials, sensitive evidence, and remediation decisions go through your security team's approved channels. **Limit.** Can customers upload incident logs or credentials? Do not use a public enquiry chat to request credentials or sensitive incident evidence. Direct customers to your approved reporting process and have your security team review any planned data collection. **Example: Security assessment enquiry.** Visitor: “Can I request a security assessment for our company?” Assistant: “I can collect an assessment enquiry. Which systems should it cover, and when would you like your security team to discuss the scope?” Details collected: Scope: Business web application; Service: Security assessment; Timing: Before next release. Next: Specialist to scope the assessment. #### IT Services - [AI Chatbot for IT Service Providers](https://vatoo.ai/industries/it-services): Service enquiries, approved help guides, and support intake. For managed IT providers, IT consultancies, and service desks. Vatoo answers service questions, shares approved help guides, and collects useful support details. Help your IT team understand the issue before the first reply. **Where enquiries get stuck.** The affected application, number of users, and problem description help your service desk decide where to start. Collect that context without requesting passwords. **Specific friction.** - **The first report lacks context.** The affected system, error, and number of users help a technician judge the impact. - **Service scope is a recurring question.** A small business wants to understand support hours and what its package includes. - **Access changes need verification.** A published reset guide can be shared, while the account change follows the approved process. **Questions visitors ask.** - How do I report that our team cannot access the shared drive? - Do you offer IT support for small offices? - Where can I find your approved password-reset instructions? **What the assistant can take on.** - **Explain support services.** Answer questions about your service packages, support hours, and onboarding process using your published information. (Use: service catalogue and support terms) - **Collect issue details.** Ask which system is affected, what the user sees, and how many people are impacted before a technician reviews it. (Ask for: system, symptoms, affected users) - **Share approved help guides.** Point users to current self-service instructions and the escalation route when the guide does not resolve the problem. (Share: approved help articles and support contacts) - **Explain support tiers.** Show the published service scope and contact routes for different support packages. - **Collect issues after office hours.** Gather the affected service and number of users so the desk has context at follow-up. - **Reach the incident channel.** Show the escalation process for a major outage or security-sensitive problem. **Example roles for a service desk.** - **IT service guide.** Explains support packages and helps users locate approved setup or troubleshooting instructions. - **Support intake.** Asks which system is affected, what the user sees and how many people are impacted before a technician follows up. **Content to start with.** - IT service catalogue and support hours - Approved troubleshooting and self-service guides - Support intake fields and escalation contacts **What stays with the team.** Technicians handle permissions, privileged access, incidents, and system changes. Creating tickets in your helpdesk requires a supported connection. **Limit.** Can it reset passwords or grant system access? Sharing an approved reset guide is different from changing an account. Account actions require authentication, permissions, and an approved integration; Vatoo should not collect a user's password. **Example: Shared-drive support enquiry.** Visitor: “How do I report that our team cannot access the shared drive?” Assistant: “Which shared drive is affected, what message do you see, and is this happening to one person or the whole team? Please do not share passwords.” Details collected: System: Shared drive; Impact: Five users; Issue: Access denied. Next: Service desk to investigate. #### SaaS & Tech - [SaaS AI Chatbot for Support and Demo Requests](https://vatoo.ai/industries/saas-tech): Product questions, onboarding help, and demo enquiries. For SaaS businesses, software platforms, and product support teams. Vatoo answers product questions from your help content and collects demo or support enquiries. Give SaaS users guidance while your team handles the questions that need deeper attention. **Where enquiries get stuck.** A buyer comparing plans needs different help from a user setting up an account. Give both a useful answer without making them search the entire help centre. **Specific friction.** - **Users get stuck mid-task.** An invitation question needs the setup instructions for the user's workspace. - **Plan differences slow a decision.** A buyer may only need to know which plan includes a particular feature. - **A demo needs a purpose.** Knowing the team size and what the buyer wants to test makes the call more useful. **Questions visitors ask.** - How do I invite teammates to our workspace? - Which plan includes the feature our team needs? - Can I request a demo for our business? **What the assistant can take on.** - **Answer product questions.** Explain features and plan differences from your current documentation and pricing information. (Use: product docs and approved plan information) - **Guide common setup tasks.** Help users find the relevant onboarding instructions and ask which step they need help with. (Share: setup guides and help articles) - **Prepare demo or support requests.** Collect team size and goals for demos, or the affected feature and issue for support follow-up. (Ask for: goal or issue and preferred contact) - **Explain a plan difference.** Help buyers locate current feature availability and plan limits in your pricing information. - **Capture demo interest.** Collect the team’s size, goal, and preferred time for a product conversation. - **Reach technical support.** Capture the affected feature and observed issue before a support specialist investigates. **Example roles for a product support team.** - **Product support guide.** Helps users find the setup instructions for the feature they are trying to use. - **Demo enquiries.** Asks what a buyer wants to test and how large their team is before sales arranges a demo. **Content to start with.** - Help centre articles and onboarding guides - Feature documentation and published plan details - Demo questions and support escalation instructions **What stays with the team.** Your team handles bugs, account permissions, billing exceptions, and product commitments. Account-specific actions require authentication and a supported connection. **Limit.** Will it perform actions inside our software? Explaining a documented task does not automatically give the chatbot access to your app. Account changes or other product actions need an approved integration, permissions, and testing for your specific setup. **Example: Workspace setup question.** Visitor: “How do I invite teammates to our workspace?” Assistant: “I can help you find the teammate invitation guide. Are you setting up a new workspace or adding people to an existing one?” Details collected: Task: Invite teammates; Workspace: Existing workspace; Need: Setup instructions. Next: User guided to the relevant help article. ### Transport and logistics #### Aviation - [Aviation Chatbot for Ground Handling and FBO Enquiries](https://vatoo.ai/industries/aviation): Handling requests, aircraft service enquiries, and facility information. For FBOs, aircraft maintenance providers, and ground handling teams. Vatoo helps FBOs and aviation service teams explain facilities, collect handling requests, and prepare maintenance enquiries with the aircraft and timing details they need. **Where enquiries get stuck.** Your team needs more than an arrival date. Aircraft type, location, and requested services help them review an enquiry without starting the conversation again. **Specific friction.** - **An arrival enquiry lacks flight details.** Aircraft type, airport, and arrival time help operations identify which handling services to check. - **Each facility offers different services.** A crew planning a stop needs the published facilities for that particular airport. - **A request still needs clearance.** Parking, fuel, and handling arrangements need confirmation from operations before the crew relies on them. **Questions visitors ask.** - Can I request ground handling for a business jet arrival? - What services are available at your facility? - Who should I contact about aircraft maintenance? **What the assistant can take on.** - **Explain facility services.** Share published operating hours, passenger facilities, and available services from your location information. (Use: facility pages and service descriptions) - **Collect handling details.** Ask for aircraft type, airport, planned arrival, and requested services for an operations review. (Ask for: aircraft, airport, date, service) - **Prepare maintenance enquiries.** Collect the aircraft model and type of maintenance enquiry, then explain how to reach your technical team. (Collect: aircraft model and service required) - **Prepare a parking request.** Ask about aircraft type and intended stay before the ground team checks space. - **Take a fuel service enquiry.** Let operators specify the airport, date, and service needed for operations to review. - **Find the duty contact.** Show the operator’s published contact route for time-sensitive changes to arrival plans. **Example roles for a ground handling desk.** - **Airport services guide.** Uses the selected airport’s facility information to answer questions about parking, facilities and published services. - **Ground handling enquiries.** Collects the airport, aircraft type, arrival date and requested services for operations to confirm. **Content to start with.** - Facility services and published operating hours - Handling enquiry requirements - Maintenance capabilities and team contacts **What stays with the team.** Operations staff confirm handling, slots, fuel, and parking. Flight planning, airworthiness, and safety decisions stay with qualified personnel. **Limit.** Does a chat request confirm handling or a slot? No. Treat it as a request until your operations team or a connected system confirms it. The chatbot should not issue flight clearances or safety-critical operating instructions. **Example: Ground handling enquiry.** Visitor: “Can I request ground handling for a business jet arrival?” Assistant: “I can collect a handling request for operations. Which airport, aircraft type, and planned arrival date should they review?” Details collected: Aircraft: Light business jet; Arrival: Next Tuesday; Services: Handling and parking. Next: Operations review required. #### Last-Mile Delivery - [AI Chatbot for Last-Mile Delivery](https://vatoo.ai/industries/last-mile-delivery): Parcel questions, delivery issue reports, and change requests. For courier companies, local delivery operators, and fulfilment teams. Vatoo explains delivery policies, collects parcel enquiries, and points recipients to tracking and support. Give your delivery team the context to investigate missed or disputed deliveries. **Where enquiries get stuck.** A recipient checking a tracking update needs a different response from someone reporting a missing parcel. Collect enough context to reach the right support process. **Specific friction.** - **A missed parcel leaves the recipient unsure.** A reference and delivery notice help support identify the next step. - **Tracking and policy answer different questions.** A recipient checking today's parcel needs the carrier's live status source. - **An address change needs verification.** A change request has to reach the carrier before anyone can promise a new destination. **Questions visitors ask.** - What should I do if I missed my parcel delivery? - Where can I check the latest tracking information? - How do I request a delivery address change? **What the assistant can take on.** - **Explain delivery options.** Share your published missed-delivery, collection, and redelivery process without promising a slot that has not been confirmed. (Use: delivery policies and recipient FAQs) - **Prepare issue reports.** Collect a tracking reference and issue type so your support team can locate and investigate the shipment. (Ask for: tracking reference and issue type) - **Route change requests.** Explain how recipients request address or delivery changes through your approved process. (Share: change-request instructions and limits) - **Explain collection options.** Show published collection or redelivery instructions when a parcel could not be delivered. - **Take a missing parcel enquiry.** Collect the reference and reported issue for recipient support to investigate. - **Reach the delivery team.** Direct address disputes or delivery exceptions to the carrier’s authorised process. **Example roles for a delivery support desk.** - **Delivery options guide.** Helps a recipient find tracking, collection and redelivery instructions from the carrier. - **Parcel issue intake.** Collects the tracking reference and reported issue so support can investigate a missing or disputed delivery. **Content to start with.** - Delivery policies and missed-delivery instructions - Tracking links and change-request procedures - Lost or disputed delivery support process **What stays with the team.** Your operations team verifies parcel status, approves changes, and investigates disputes. Live tracking requires a connected tracking source. **Limit.** Can it change a delivery address immediately? It can collect or explain a change request. Applying a change requires the appropriate carrier connection, identity checks, and approval within your delivery process. **Example: Missed delivery enquiry.** Visitor: “What should I do if I missed my parcel delivery?” Assistant: “I can help you find the next step. Do you have a tracking reference, and did the driver leave a delivery notice?” Details collected: Parcel reference: Example parcel 1042; Issue: Missed delivery; Request: Redelivery information. Next: Recipient directed to the redelivery process. #### Logistics - [Logistics AI Chatbot for Freight Quote Requests](https://vatoo.ai/industries/logistics): Freight enquiries, shipment briefs, and shipping process questions. For freight forwarders, logistics providers, and transport sales teams. Vatoo answers freight service questions and collects origin, destination, cargo, and timing. Give your logistics sales team a shipment brief they can use to prepare a quote. **Where enquiries get stuck.** Cargo dimensions, weight, route, and ready date affect the options your team can offer. Asking for those basics early avoids another round of emails. **Specific friction.** - **A route alone cannot be priced.** The quote desk needs cargo, dimensions, weight, and the ready date alongside the origin and destination. - **Shippers need to know what to measure.** Clear packing and measurement requirements help them submit useful figures. - **Capacity and rates need checking.** A freight specialist must confirm the available options before committing to a price. **Questions visitors ask.** - Can you quote for three pallets from Mumbai to Dubai? - What shipment details do you need for a freight quote? - Which transport services do you offer on this route? **What the assistant can take on.** - **Explain freight services.** Help visitors understand your air, sea, and road services, supported routes, and published shipment requirements. (Use: service lanes and shipment guidelines) - **Collect quote requirements.** Ask for origin, destination, cargo type, dimensions, weight, and ready date so your team can review suitable options. (Ask for: route, cargo, dimensions, weight, date) - **Guide document preparation.** Point shippers to your approved document checklist and the contact for shipment-specific questions. (Share: shipping checklist and operations contacts) - **Prepare cargo dimensions.** Explain which measurements and weights the freight team needs before quoting. - **Take a shipment enquiry after hours.** Collect the route and cargo-ready date while the freight desk is closed. - **Flag a special shipment.** Direct customs, unusual cargo, and service exceptions to the appropriate specialist. **Example roles for a freight desk.** - **Freight quote assistant.** Asks for the route, pallet dimensions, weight and ready date so the freight desk can prepare a quote. - **Shipping support guide.** Helps shippers find the document checklist for a service and the operations contact for special cargo. **Content to start with.** - Freight services and supported routes - Cargo requirements and quote fields - Approved shipping checklists and support contacts **What stays with the team.** Your freight team confirms rates, capacity, transit commitments, and shipment exceptions. Customs decisions need the appropriate specialist. **Limit.** Can Vatoo give a live freight rate? A live rate needs a supported connection to your rating system and complete shipment details. Without that, Vatoo collects the enquiry for your team to price and confirm. **Example: Pallet freight enquiry.** Visitor: “Can you quote for three pallets from Mumbai to Dubai?” Assistant: “I can collect a quote request. What are the dimensions and total weight of the three pallets, and when will they be ready?” Details collected: Route: Mumbai → Dubai; Cargo: Three pallets; Ready date: Next week. Next: Freight team to check options and rates. #### Port & Terminal - [AI Chatbot for Ports and Terminals](https://vatoo.ai/industries/port-terminal): Terminal service enquiries, documentation guidance, and access processes. For port authorities, terminal operators, and cargo service teams. Vatoo explains published terminal services, access procedures, and documentation requirements. Collect cargo and service enquiries for your commercial or operations team to review. **Where enquiries get stuck.** A haulier asking about access needs a different answer from a shipper requesting handling services. Clear process information helps each enquiry reach the right desk. **Specific friction.** - **Cargo details change the handling request.** Type, dimensions, timing, and required service help operations understand what is coming. - **Drivers need the right access process.** The current gate and pass instructions matter before a driver travels to the terminal. - **Approvals stay with operations.** Cargo acceptance, gate status, and release each require an authorised decision or system. **Questions visitors ask.** - Who can help with a breakbulk cargo handling enquiry? - Where can drivers find the terminal access process? - What information is needed for a terminal service request? **What the assistant can take on.** - **Explain terminal services.** Help visitors understand your published cargo handling services, facilities, and commercial contact routes. (Use: terminal capabilities and service information) - **Collect cargo enquiries.** Ask for cargo type, dimensions or volume, intended date, and requested service before operations reviews the details. (Ask for: cargo, volume, date, service) - **Guide access and paperwork.** Point users to approved pass applications, documentation checklists, and official operational portals. (Share: access process and document requirements) - **Find gate access instructions.** Show hauliers the terminal’s current pass and entry application process. - **Take a terminal service enquiry.** Collect cargo category, target date, and required handling service for review. - **Reach port operations.** Direct live gate, vessel, or hazardous cargo questions to official operational contacts. **Example roles for a terminal service desk.** - **Port user guide.** Helps drivers and shippers find published gate, pass and documentation procedures. - **Cargo handling enquiries.** Collects cargo type, volume, intended date and handling needs for terminal operations. **Content to start with.** - Published terminal services and cargo capabilities - Access procedures and document requirements - Official port user portals and enquiry contacts **What stays with the team.** Operations teams approve cargo acceptance, access, and handling arrangements. Live vessel, gate, or terminal status needs an authoritative connected system. **Limit.** Can it issue a port pass or authorise cargo release? No. It can explain the application or release process and direct the user to the official system. Access permissions and cargo release require the terminal's authorised checks and approvals. **Example: Breakbulk handling enquiry.** Visitor: “Who can help with a breakbulk cargo handling enquiry?” Assistant: “What type of cargo is involved, what are its approximate dimensions, and when is handling required? I can gather this for the terminal team.” Details collected: Cargo: Industrial machinery; Service: Breakbulk handling; Timing: Planned vessel arrival. Next: Terminal team to review the requirement. #### Rail Transport - [AI Chatbot for Rail Transport](https://vatoo.ai/industries/rail-transport): Travel information, freight enquiries, and rail support contacts. For passenger rail operators, rail freight providers, and customer service teams. Vatoo explains published rail services, travel policies, and freight enquiry requirements. Direct passengers and business customers to the appropriate booking or support channel. **Where enquiries get stuck.** A passenger may need accessibility information; a shipper needs route and cargo requirements. Help each find the correct service without confusing published information with live operations. **Specific friction.** - **Freight enquiries need route and volume.** A shipper's goods, frequency, and destinations help the freight team assess the request. - **Passengers need journey-specific help.** Accessibility information and the assistance route can vary between stations. - **Live running information changes.** A passenger checking a delay needs the official live service rather than a static timetable. **Questions visitors ask.** - How can I ask about moving goods by rail? - Where can I find assistance information for my journey? - Which channel has the latest train running information? **What the assistant can take on.** - **Explain passenger information.** Help people find published ticket policies, station facilities, and assistance request procedures. (Use: travel policies and station information) - **Collect rail freight enquiries.** Ask for origin, destination, cargo type, volume, and timing before the freight team reviews the requirement. (Ask for: route, cargo, volume, timing) - **Direct live service questions.** Point passengers to your official running-information and disruption channels for current updates. (Share: official live information and support routes) - **Find station information.** Help passengers locate published station facilities and assistance arrangements. - **Take a group travel enquiry.** Collect the route, travel dates, and group size before bookings staff respond. - **Find disruption updates.** Point passengers to the operator’s official live running information. **Example roles for a rail service team.** - **Passenger information guide.** Helps passengers find station facilities, assistance procedures and the official live running service. - **Rail freight enquiries.** Asks what goods will move, between which locations and how frequently before the freight team responds. **Content to start with.** - Published rail services and station information - Freight enquiry requirements and travel policies - Official live-service channels and assistance contacts **What stays with the team.** Your teams confirm capacity, bookings, assistance arrangements, and operational changes. Safety questions and disruptions use official operating channels. **Limit.** Does Vatoo know if a train is delayed right now? Live running information needs a supported connection to your authoritative service feed. Otherwise, direct users to the official live-status channel rather than answering from a static timetable. **Example: Rail freight enquiry.** Visitor: “How can I ask about moving goods by rail?” Assistant: “I can prepare an enquiry for the freight team. What goods are you moving, between which locations, and at what frequency?” Details collected: Cargo: Palletised goods; Frequency: Weekly; Request: Rail freight options. Next: Freight team to review route and capacity. #### Shipping & Maritime - [AI Chatbot for Shipping and Maritime](https://vatoo.ai/industries/shipping-maritime): Ocean freight enquiries, cargo details, and shipping documentation. For shipping agencies, ocean freight providers, and maritime service businesses. Vatoo explains your maritime services and collects ports, cargo, container needs, and ready dates. Help your shipping team review enquiries with fewer missing details. **Where enquiries get stuck.** Ports, commodity, container type, and timing all matter when reviewing a shipping enquiry. A useful conversation gathers those basics before a commercial quote. **Specific friction.** - **An equipment request is only the start.** Container size, cargo, ports, and readiness date together form a usable shipment brief. - **Cargo details affect acceptance.** Commodity and weight help the team identify the relevant requirements. - **Documents follow a specific process.** Shippers need the correct submission checklist and operations contact. **Questions visitors ask.** - Can I request an ocean freight quote for a 40-foot container? - Which cargo details do you need before quoting? - Where can I find your shipping document checklist? **What the assistant can take on.** - **Explain shipping services.** Answer questions about your published ocean freight, agency, and maritime service offerings. (Use: service descriptions and route information) - **Collect shipment requirements.** Ask for loading and destination ports, commodity, container size, weight, and cargo-ready date. (Ask for: ports, cargo, container, weight, date) - **Guide document questions.** Direct shippers to the approved documentation process and the operations contact for specific requirements. (Share: document checklist and operations contacts) - **Prepare container requirements.** Explain the cargo, weight, and equipment details your shipping team asks for. - **Take an ocean freight enquiry.** Let shippers share ports and a cargo-ready date across time zones. - **Request a booking amendment.** Direct schedule changes or cargo amendments to the authorised booking team. **Example roles for a ocean freight team.** - **Ocean freight guide.** Explains published service lanes, container types and the shipping documents a customer should prepare. - **Container quote enquiries.** Collects ports, commodity, container size and cargo-ready date for the shipping team to review. **Content to start with.** - Maritime services and published trade lanes - Container and cargo enquiry requirements - Approved shipping document and support procedures **What stays with the team.** Your team confirms cargo acceptance, rates, bookings, and amendments. Live schedules and tracking require authoritative system connections. **Limit.** Can the chatbot guarantee a sailing or cargo acceptance? No. It can collect requirements and explain published services. Your carrier or operations team must confirm space, schedules, cargo acceptance, and any special handling requirements. **Example: Container shipment enquiry.** Visitor: “Can I request an ocean freight quote for a 40-foot container?” Assistant: “What are the loading and destination ports, what cargo is inside, and when will it be ready? The shipping team can then review the options.” Details collected: Container: 40-foot dry container; Cargo: Furniture; Ready date: Next month. Next: Shipping team to review rates and capacity. #### Transportation - [AI Chatbot for Transport Operators](https://vatoo.ai/industries/transportation): Transfer enquiries, group-trip briefs, and passenger service questions. For coach operators, shuttle services, private transfer firms, and fleet teams. Vatoo explains your passenger transport services and gathers routes, dates, and group requirements. Help your team review transfer and group-travel enquiries with the details included. **Where enquiries get stuck.** Passenger count, luggage, route, and timing affect the vehicle and service required. Gathering those details early helps your team prepare a useful reply. **Specific friction.** - **A group transfer needs the full route.** Pickup, destination, timing, and passenger count help determine the right vehicle. - **Service area comes first.** A passenger needs to know whether the operator serves both ends of the journey. - **Accessibility needs confirmation.** Staff need to check the vehicle and arrangements against the passenger's requirements. **Questions visitors ask.** - Can I request an airport transfer for a group of twelve? - Which areas do your shuttle services cover? - How do I ask about accessible transport options? **What the assistant can take on.** - **Explain transport options.** Use your service information to explain routes, vehicle categories, luggage policies, and published passenger facilities. (Use: service areas, vehicles, and passenger policies) - **Collect group-trip requirements.** Ask for pickup, destination, date, passenger count, and luggage or accessibility requirements for staff review. (Ask for: route, date, passengers, requirements) - **Guide booking questions.** Explain your booking, change, and cancellation process and collect an enquiry for your operations team. (Share: booking terms and support contacts) - **Explain luggage arrangements.** Share published luggage allowances and ask about special items for the operator to review. - **Take an early transfer enquiry.** Collect the journey date and pickup preference even when the booking office is closed. - **Confirm accessibility needs.** Pass stated passenger requirements to the operator for vehicle and service confirmation. **Example roles for a transport booking office.** - **Passenger service guide.** Explains published coverage, vehicle options and luggage policies for a planned journey. - **Group trip enquiries.** Collects pickup, destination, passenger count and timing so operations can check a suitable vehicle. **Content to start with.** - Transport services, coverage, and vehicle information - Group enquiry and accessibility request requirements - Booking, change, and cancellation procedures **What stays with the team.** Operations confirms vehicles, accessibility arrangements, fares, and schedules. Live arrival updates require an authoritative connected source. **Limit.** Does a chat request reserve a vehicle? It collects a request unless you have implemented a supported booking connection. Your operations team must confirm vehicle availability, passenger requirements, price, and journey details. **Example: Group airport transfer enquiry.** Visitor: “Can I request an airport transfer for a group of twelve?” Assistant: “Which airport and destination, what date and time, and how much luggage will the twelve passengers have? I can prepare a quote request.” Details collected: Passengers: Twelve; Trip: Airport to hotel; Luggage: One suitcase each. Next: Transport team to confirm vehicle and price. ## Use cases 102 workflow pages. Each one is a no-code conversational agent built from Vatoo’s AI Agents, Flow Engine, and Smart Forms. Use AI Agents for answers from approved sources, Smart Forms for required details, and the Flow Engine for branches and handoffs. Connected actions depend on the APIs, permissions, and plan you configure. Test incomplete requests and failed actions before launch. The visual flow builder, tools and API calls, cross-session memory, and multiple channels are Premium capabilities; the free trial includes those Premium features, and Essential does not. ### Accounting & Tax Client Intake Chatbot - [Accounting & Tax Client Intake Chatbot](https://vatoo.ai/use-cases/accounting-client-intake-chatbot): Onboard new clients and answer routine tax questions. Vatoo collects intake details, routes by service, and frees up your advisors. Category: Accounting & Tax. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Accounting firms lose billable time to repetitive client questions and manual intake. New-client onboarding is slow and inconsistent. **Approach.** An accounting persona answers routine questions from a knowledge base, the Flow Engine runs client intake through Smart Forms, branches by service type (personal, business, tax), and fires a webhook to the practice-management system. **Flow.** 1. Trigger: "new client" or service question 2. Knowledge base: answer routine questions 3. Form: client and service details 4. Condition: branch by service type 5. Webhook: send to practice-management system **Compared with the manual process.** - **Billable time.** Lost to FAQs → Protected - **Intake.** Manual → Structured - **Onboarding speed.** Slow → Faster - **Routing.** Manual → By service type ### Agentic-Commerce Discovery & Reorder Chatbot - [Agentic-Commerce Discovery & Reorder Chatbot](https://vatoo.ai/use-cases/agentic-commerce-product-discovery-chatbot): Meet the shift to conversational product discovery. Vatoo answers natural-language product queries from your catalogue, guides selection, and enables one-message reorders. Category: Retail & E-commerce. Public-facing deployment for prospects and customers on a website or app. **Problem.** Shoppers increasingly research and select products through conversation rather than keyword search and category browsing, and brands that only expose a traditional storefront lose discovery to AI-driven channels. **Approach.** A retail persona indexes a clean product catalogue into a knowledge base and answers natural-language discovery queries (needs, constraints, comparisons), guides selection, and enables fast reorders by recalling past purchases via memory. A per-persona tool can check live price or stock, and a webhook pushes the cart or order. Note: this is a brand-owned conversational discovery layer, not an external agent-checkout protocol integration. **Flow.** 1. Trigger: a needs-based or comparison product query 2. Knowledge base: match products from the catalogue by criteria 3. API call: check live price and stock 4. Memory: surface past purchases for one-message reorder 5. Webhook: push the cart or order **Compared with the manual process.** - **Discovery.** Keyword search and browsing → Conversational matching - **Reorders.** Manual re-navigation → One-message via memory - **Comparisons.** Manual across pages → Guided in chat - **Catalogue value.** Static pages → Queryable knowledge layer ### Agriculture Advisory Chatbot - [Agriculture Advisory Chatbot](https://vatoo.ai/use-cases/agriculture-advisory-chatbot): Answer crop, input and product questions for farmers. Vatoo serves grounded guidance from your catalogue and captures dealer and order enquiries. Category: Agriculture. Public-facing deployment for prospects and customers on a website or app. **Problem.** Agri-input suppliers field repetitive questions on products, dosage and dealers across regions and languages, with slow follow-up on buying interest. **Approach.** An agriculture persona answers product, usage and dealer questions from a knowledge base, captures dealer and order enquiries via Smart Forms, and routes by region via webhook. Multilingual configuration supports local languages. **Flow.** 1. Trigger: product, usage or dealer question 2. Knowledge base: answer from product catalogue and guides 3. Form: farmer details, product interest, location 4. Condition: route by region or dealer 5. Webhook: send the enquiry to the regional sales team **Compared with the manual process.** - **Product questions.** Field-rep time → Self-served - **Dealer routing.** Manual → By region - **Language coverage.** Limited → Multilingual - **Buying interest.** Slow follow-up → Captured instantly ### Airline Loyalty & Miles Chatbot - [Airline Loyalty & Miles Chatbot](https://vatoo.ai/use-cases/airline-loyalty-account-chatbot): Answer loyalty and miles questions instantly. Vatoo checks balances and tier status via API and explains redemption options, cutting call-centre load. Category: Aviation / Loyalty. Public-facing deployment for prospects and customers on a website or app. **Problem.** Loyalty members generate high call volume for balance, tier and redemption questions that don't need a human. **Approach.** A loyalty persona uses a per-persona tool to check balance and tier status via API and explains redemption and earning rules from a knowledge base, with memory recognising members across sessions. **Flow.** 1. Trigger: "my miles" or a loyalty question 2. API call: check balance and tier status 3. Knowledge base: explain earning and redemption rules 4. Message: deliver the balance and relevant options 5. Memory: recognise the member next time **Compared with the manual process.** - **Balance enquiries.** Agent-handled → API self-service - **Redemption questions.** Call-centre time → Self-served - **Member recognition.** Anonymous → Remembered - **Call volume.** High → Deflected ### Auto Parts Fitment Chatbot - [Auto Parts Fitment Chatbot](https://vatoo.ai/use-cases/auto-parts-fitment-chatbot): Help buyers find parts that fit. Vatoo collects vehicle details, checks the catalogue, confirms fitment, and captures the order enquiry. Category: Automotive / Parts. Public-facing deployment for prospects and customers on a website or app. **Problem.** Parts buyers struggle to confirm fitment, leading to wrong orders, returns and abandoned carts. **Approach.** A parts persona collects vehicle make, model and year, queries a catalogue knowledge base or API to confirm fitment, and captures the order enquiry via a Smart Form routed by webhook. **Flow.** 1. Trigger: "will this fit my car" or part search 2. Form: make, model, year, variant 3. API or knowledge base: confirm fitment and options 4. Message: present compatible parts 5. Webhook: capture the order enquiry **Compared with the manual process.** - **Wrong orders.** Common → Reduced with fitment checks - **Returns.** High → Lower - **Cart abandonment.** Fitment doubt → Reduced - **Buyer confidence.** Low → Confirmed fitment ### Automotive Test Drive & Service Chatbot - [Automotive Test Drive & Service Chatbot](https://vatoo.ai/use-cases/automotive-test-drive-booking-chatbot): Book test drives and service appointments from the chat. Vatoo qualifies the buyer, routes to the dealership, and captures the lead in your CRM. Category: Automotive. Public-facing deployment for prospects and customers on a website or app. **Problem.** Dealership websites generate interest but lose it to slow follow-up. Service bookings clog the phone lines and the showroom team is stretched. **Approach.** An automotive persona handles model questions from a knowledge base, the Flow Engine books test drives or service slots through Smart Forms, and a webhook pushes the lead to the dealership CRM with routing by location or model. **Flow.** 1. Trigger: "test drive" or "book service" 2. Form: model or service type, preferred date 3. Condition: branch by dealership location 4. Webhook: send to dealership CRM and calendar 5. Confirm: reply with a booking reference **Compared with the manual process.** - **Lead follow-up.** Slow, manual → Instant capture - **Service phone lines.** Congested → Self-service booking - **Showroom time.** Stretched → Qualified leads only - **After-hours interest.** Lost → Captured ### Aviation Passenger Services Chatbot - [Aviation Passenger Services Chatbot](https://vatoo.ai/use-cases/aviation-passenger-services-chatbot): Answer flight, baggage and booking questions, and check status via API. Vatoo gives passengers instant self-service and reduces call-centre load. Category: Aviation. Public-facing deployment for prospects and customers on a website or app. **Problem.** Airline and airport call centres are overwhelmed during disruptions, and passengers can't get fast answers on status, baggage or policy. **Approach.** An aviation persona answers policy and baggage questions from a knowledge base, a per-persona tool checks live flight status via API, and Smart Forms capture booking or assistance requests routed by webhook. **Flow.** 1. Trigger: flight, baggage or booking question 2. Knowledge base: answer policy and baggage questions 3. API call: check live flight status 4. Form: capture booking or assistance request 5. Webhook: route to the relevant team **Compared with the manual process.** - **Call-centre load.** Spikes during disruption → Deflected - **Status questions.** Hold times → Instant via API - **Self-service.** Limited → 24/7 - **Booking capture.** Manual → Inline ### Beauty Salon Appointment Chatbot - [Beauty Salon Appointment Chatbot](https://vatoo.ai/use-cases/beauty-salon-appointment-chatbot): Book treatments automatically. Vatoo surfaces a booking form at the right moment, answers service questions, and remembers client preferences. Category: Beauty & Aesthetics. Public-facing deployment for prospects and customers on a website or app. **Problem.** Salons lose bookings when the phone goes unanswered during treatments, and clients want quick answers on services and pricing. **Approach.** A beauty persona answers service and pricing questions from a knowledge base, the Smart Form Engine surfaces a booking form on intent, and memory recalls client preferences and history. **Flow.** 1. Trigger: "book" a treatment or service question 2. Knowledge base: answer service and pricing questions 3. Form: treatment, stylist preference, date and time 4. Webhook: push to salon scheduling system 5. Memory: store client preferences **Compared with the manual process.** - **Missed bookings.** Phone unanswered → Captured inline - **Service questions.** Staff-answered → Self-served - **Client preferences.** Forgotten → Remembered - **Off-hours bookings.** Lost → Captured ### Beneficiary Eligibility Screening Chatbot - [Beneficiary Eligibility Screening Chatbot](https://vatoo.ai/use-cases/beneficiary-eligibility-screening-chatbot): Help people check if they qualify for support. Vatoo asks eligibility questions, explains the right program, and captures applications for review. Category: Non-Profit / Public Sector. Public-facing deployment for prospects and customers on a website or app. **Problem.** People struggle to navigate which support programs they qualify for, and intake teams spend time screening ineligible applicants. **Approach.** A services persona explains programs from a knowledge base, the Flow Engine screens eligibility via structured questions, branches to the right program, and captures applications via Smart Forms routed by webhook. On-prem deployment supports sensitive data. **Flow.** 1. Trigger: "do I qualify" or support question 2. Form: situation and eligibility criteria 3. Condition: branch to the matching program 4. Form: capture application details 5. Webhook: route the application for review **Compared with the manual process.** - **Program navigation.** Confusing → Guided - **Ineligible intake.** High → Screened out - **Application capture.** Manual → Structured - **Data sensitivity.** Shared infra → On-prem option ### Boat Service & Haul-Out Chatbot - [Boat Service & Haul-Out Chatbot](https://vatoo.ai/use-cases/boat-service-haulout-booking-chatbot): Book yard services and haul-outs without phone tag. Vatoo captures vessel and service details, checks slot availability, and books the job. Category: Marina & Boating. Public-facing deployment for prospects and customers on a website or app. **Problem.** Boatyards juggle seasonal service demand by phone, losing bookings and capturing inconsistent vessel and job details. **Approach.** A boatyard persona answers service and pricing questions from a knowledge base, the Flow Engine captures vessel and service details via Smart Forms, checks slot availability via API, and books the job via webhook. Memory recalls each vessel. **Flow.** 1. Trigger: "book a service" or "haul-out" 2. Knowledge base: answer service and pricing questions 3. Form: vessel details, service type, preferred dates 4. API call: check yard slot availability 5. Webhook: book the job and store the vessel record **Compared with the manual process.** - **Service bookings.** Phone-bound → Self-served - **Job detail.** Inconsistent → Structured - **Seasonal demand.** Overwhelm → Absorbed - **Vessel records.** Re-asked → Remembered ### Catering Order Enquiry Chatbot - [Catering Order Enquiry Chatbot](https://vatoo.ai/use-cases/catering-order-enquiry-chatbot): Capture catering enquiries with full detail. Vatoo collects headcount, date, menu and dietary needs, then routes the quote request to your catering team. Category: Restaurants / Catering. Public-facing deployment for prospects and customers on a website or app. **Problem.** Catering enquiries arrive with missing details (headcount, dietary needs, delivery time), causing slow, incomplete quoting. **Approach.** A catering persona answers menu and capacity questions from a knowledge base, the Flow Engine captures full catering details via Smart Forms, branches by event size, and routes a complete quote request to the catering team via webhook. **Flow.** 1. Trigger: catering enquiry 2. Knowledge base: answer menu and capacity questions 3. Form: headcount, date, time, menu, dietary needs 4. Condition: branch by event size 5. Webhook: route a complete quote request **Compared with the manual process.** - **Enquiry detail.** Incomplete → Fully captured - **Quote speed.** Back-and-forth → Faster - **Dietary capture.** Missed → Structured - **Lead loss.** High → Reduced ### Clinic Insurance Verification Chatbot - [Clinic Insurance Verification Chatbot](https://vatoo.ai/use-cases/clinic-intake-insurance-verification-chatbot): Verify coverage and complete intake before the visit. Vatoo collects insurance details, checks eligibility via API, and pushes verified intake to your EHR. Category: Healthcare. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Front-office staff spend hours on insurance verification and pre-visit intake, and unverified coverage causes billing problems later. **Approach.** A clinic persona collects insurance and intake details via Smart Forms, a per-persona tool checks eligibility via a verification API, and a webhook pushes verified intake to the EHR or practice system. Deploy on compliant infrastructure for patient data. **Flow.** 1. Trigger: pre-visit intake or "check my coverage" 2. Form: insurance carrier, member ID, plan details 3. API call: eligibility verification 4. Form: complete remaining intake fields 5. Webhook: push verified intake to the EHR **Compared with the manual process.** - **Verification time.** Manual calls → API-driven - **Billing surprises.** Common → Reduced with upfront checks - **Intake completeness.** Variable → Structured - **Front-office load.** High → Reduced ### Construction RFI & Quote Chatbot - [Construction RFI & Quote Chatbot](https://vatoo.ai/use-cases/construction-rfi-quote-chatbot): Capture project enquiries and RFIs inline. Vatoo collects scope details, routes by trade or region, and pushes structured requests to your team. Category: Construction. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Contractors lose project enquiries to slow follow-up, and RFIs arrive as unstructured emails that are hard to triage and route. **Approach.** A construction persona answers service and capability questions from a knowledge base, the Flow Engine captures project scope and RFIs via Smart Forms, branches by trade or region, and fires a webhook to the estimating team. **Flow.** 1. Trigger: "quote", "RFI" or project question 2. Form: project scope, location, timeline 3. Condition: branch by trade or region 4. Webhook: send structured request to estimating 5. Confirm: reply with a reference **Compared with the manual process.** - **Enquiry follow-up.** Slow → Instant capture - **RFI structure.** Unstructured email → Standardised form - **Routing.** Manual → By trade or region - **Lead loss.** High → Reduced ### Conversational Feedback & NPS Chatbot - [Conversational Feedback & NPS Chatbot](https://vatoo.ai/use-cases/conversational-feedback-nps-chatbot): Collect richer feedback than a static survey. Vatoo runs conversational NPS and follow-ups, captures the why, and routes detractors for fast recovery. Category: Cross-industry. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Static surveys get low response and shallow answers, so teams miss the reasons behind scores and act too late on unhappy customers. **Approach.** A feedback persona runs a conversational NPS via the Flow Engine, asks adaptive follow-ups to capture the why, and branches to route detractors for fast recovery and promoters for referral prompts, all logged via webhook. **Flow.** 1. Trigger: post-interaction or scheduled prompt 2. Form: NPS score 3. Condition: branch by score band 4. Form: adaptive follow-up on the reason 5. Webhook: route detractors to recovery, promoters to referral **Compared with the manual process.** - **Response depth.** Shallow → Conversational why - **Detractor recovery.** Too late → Routed fast - **Promoter leverage.** Missed → Referral prompt - **Response rate.** Low → Higher in-context ### Conversational KYC Onboarding Chatbot - [Conversational KYC Onboarding Chatbot](https://vatoo.ai/use-cases/conversational-kyc-onboarding-chatbot): Compress onboarding from 20+ minutes to minutes. Vatoo guides applicants through KYC document collection conversationally, reduces drop-off, and logs an audit trail. Category: Finance & Banking. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Manual onboarding takes 20 minutes or more and loses applicants at every document step, while compliance teams need a clean, timestamped record of what was collected and when. **Approach.** An onboarding persona guides applicants through KYC steps via the Flow Engine, collects details and document references through Smart Forms, branches on missing items to reduce drop-off, and fires a webhook to the verification or core system. Every interaction is logged and timestamped, supporting an audit trail; per-bot isolation and BYOK support data sovereignty. Identity-document verification itself runs in the connected verification system. **Flow.** 1. Trigger: "open an account" 2. Knowledge base: explain requirements and eligibility 3. Form: identity details and required document references 4. Condition: missing item? branch to collect it 5. Webhook: submit to the verification or core system with a logged record **Compared with the manual process.** - **Onboarding time.** 20+ minutes manual → Minutes, guided - **Drop-off.** High at document steps → Reduced with branching - **Audit trail.** Assembled under pressure → Logged and timestamped - **Eligibility questions.** Staff-answered → Self-served ### Coworking Space Tour Chatbot - [Coworking Space Tour Chatbot](https://vatoo.ai/use-cases/coworking-space-tour-booking-chatbot): Convert space interest into booked tours. Vatoo answers plan questions, checks availability, and books tours or captures membership enquiries. Category: Real Estate / Coworking. Public-facing deployment for prospects and customers on a website or app. **Problem.** Coworking operators lose enquiries to slow responses and spend time answering plan, pricing and availability questions. **Approach.** A workspace persona answers plan and amenity questions from a knowledge base, an API tool checks desk or room availability, and the Smart Form Engine books tours or captures membership enquiries routed via webhook. **Flow.** 1. Trigger: plan question or "book a tour" 2. Knowledge base: answer plan and amenity questions 3. API call: check desk or room availability 4. Form: tour or membership details 5. Webhook: book the tour or route the enquiry **Compared with the manual process.** - **Enquiry response.** Slow → Instant - **Tour bookings.** Phone and email → Inline - **Plan questions.** Staff time → Self-served - **Availability.** Manual → API-checked ### Dental Recall & Reactivation Chatbot - [Dental Recall & Reactivation Chatbot](https://vatoo.ai/use-cases/dental-recall-reminder-chatbot): Bring lapsed patients back automatically. Vatoo recognises returning patients, surfaces a recall booking form, and pushes appointments to your practice software. Category: Healthcare / Dental. Public-facing deployment for prospects and customers on a website or app. **Problem.** Dental practices lose recurring revenue when patients miss six-month recalls, and manual recall calls are time-consuming and inconsistent. **Approach.** A dental persona recognises returning patients via cross-session memory, answers treatment and pricing questions from a knowledge base, surfaces a recall booking Smart Form on intent, and pushes confirmed slots to the practice-management system via webhook. **Flow.** 1. Trigger: patient returns or asks about a checkup 2. Memory: recognise the patient and last visit context 3. Knowledge base: answer treatment and pricing questions 4. Form: preferred date, hygienist or dentist, reason 5. Webhook: push the booking to practice-management software **Compared with the manual process.** - **Recall bookings.** Manual calls → Self-served, 24/7 - **Lapsed patients.** Forgotten → Recognised and reactivated - **Front-desk time.** Spent on recall calls → Freed - **Treatment questions.** Staff-answered → Deflected ### Developer API Docs Chatbot - [Developer API Docs Chatbot](https://vatoo.ai/use-cases/developer-api-docs-chatbot): Let developers ask your API docs directly. Vatoo indexes your reference and guides, returns grounded answers with context, and captures unanswered gaps. Category: SaaS & Tech / Developer Tools. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Developers abandon integrations when they can't quickly find the right endpoint, parameter or example in sprawling documentation. **Approach.** A developer persona indexes API reference, guides and changelogs into a private knowledge base and answers grounded technical questions. A feedback Smart Form captures questions the docs didn't answer, surfacing documentation gaps to the team via webhook. **Flow.** 1. Trigger: API or integration question 2. Knowledge base: answer from reference, guides and changelog 3. Message: deliver the answer with source context 4. Form: capture unresolved questions as doc-gap feedback 5. Webhook: send gaps to the docs team backlog **Compared with the manual process.** - **Endpoint findability.** Manual search → Instant grounded answers - **Integration drop-off.** High on friction → Reduced - **Doc gaps.** Invisible → Captured and routed - **Support tickets.** Many basic ones → Deflected ### E-commerce Product & Order Chatbot - [E-commerce Product & Order Chatbot](https://vatoo.ai/use-cases/ecommerce-product-support-chatbot): Answer product questions, check order status, and recover carts. Vatoo indexes your catalogue and calls your order API live inside the chat. Category: Retail & E-commerce. Public-facing deployment for prospects and customers on a website or app. **Problem.** Shoppers abandon carts when product questions go unanswered, and support is flooded with "where is my order" tickets that don't need a human. **Approach.** A retail persona answers product and policy questions from a catalogue knowledge base. A per-persona tool calls the order-status API live, and proactive agents engage idle or returning shoppers to recover carts. **Flow.** 1. Trigger: product question or "where is my order" 2. Knowledge base: answer from indexed catalogue and policies 3. API call: fetch live order status by order number 4. Proactive: re-engage idle shopper with an offer or help 5. Lead capture: collect email for follow-up **Compared with the manual process.** - **Cart abandonment.** Unanswered questions → Inline answers reduce drop-off - **Order-status tickets.** Human-handled → Self-served via API - **Support volume.** High tier-1 load → Deflected to bot - **Conversion.** Passive site → Proactive re-engagement ### Education Admissions Chatbot - [Education Admissions Chatbot](https://vatoo.ai/use-cases/education-admissions-chatbot): Answer admissions questions and capture applicant enquiries 24/7. Vatoo deflects FAQs and routes prospective students to the right department. Category: Education. Public-facing deployment for prospects and customers on a website or app. **Problem.** Admissions teams are buried in repetitive questions about courses, fees, deadlines and requirements, while prospective students expect instant answers. **Approach.** An admissions persona answers course, fee and deadline questions from a knowledge base, captures applicant enquiries via Smart Forms, and routes to the relevant department by webhook. **Flow.** 1. Trigger: course, fee or deadline question 2. Knowledge base: answer from prospectus and policy content 3. Form: applicant details and area of interest 4. Condition: route by department or programme 5. Webhook: send enquiry to admissions CRM **Compared with the manual process.** - **FAQ volume.** Staff-answered → Deflected - **Response time.** Days → Instant - **Enquiry capture.** Email forms → Conversational - **Routing.** Manual → Automated by programme ### Event Registration Chatbot - [Event Registration Chatbot](https://vatoo.ai/use-cases/event-registration-chatbot): Drive registrations and answer attendee questions. Vatoo captures sign-ups inline and pushes them to your event platform automatically. Category: Event Management. Public-facing deployment for prospects and customers on a website or app. **Problem.** Event sites get spikes of attendee questions about agenda, pricing and logistics, and registration drop-off is high when answers aren't instant. **Approach.** An event persona answers agenda, pricing and logistics questions from a knowledge base, the Smart Form Engine surfaces registration inline, and webhooks push sign-ups to the event platform. **Flow.** 1. Trigger: "register" or agenda question 2. Knowledge base: answer agenda, pricing and logistics 3. Form: attendee details and ticket type 4. Webhook: push registration to the event platform 5. Confirm: reply with a registration reference **Compared with the manual process.** - **Registration drop-off.** High → Reduced with inline form - **Attendee questions.** Staff time → Deflected - **Sign-up capture.** Separate page → Inline in chat - **Spike handling.** Overwhelmed → Bot absorbs load ### Exhibitor & Sponsor Enquiry Chatbot - [Exhibitor & Sponsor Enquiry Chatbot](https://vatoo.ai/use-cases/exhibitor-sponsor-enquiry-chatbot): Capture sponsorship and exhibitor interest with full detail. Vatoo explains packages, qualifies budget and goals, and routes leads to the events sales team. Category: Event Management. Public-facing deployment for prospects and customers on a website or app. **Problem.** Event organisers field sponsor and exhibitor enquiries without structured qualification, slowing the higher-value sales motion. **Approach.** An events-sales persona explains packages from a knowledge base, the Flow Engine captures company, budget and goals via Smart Forms, branches by package interest, and routes qualified leads to the events sales team via webhook. **Flow.** 1. Trigger: "sponsor" or "exhibit" enquiry 2. Knowledge base: explain packages and benefits 3. Form: company, budget, goals, package interest 4. Condition: branch by package tier 5. Webhook: route the qualified lead to events sales **Compared with the manual process.** - **Enquiry qualification.** Thin → Structured - **Package questions.** Sales time → Self-served - **Lead value.** Mixed → Qualified by budget - **Response speed.** Slow → Instant ### Finance & Banking Product Chatbot - [Finance & Banking Product Chatbot](https://vatoo.ai/use-cases/finance-product-enquiry-chatbot): Answer product questions and capture qualified leads with a compliance-tuned persona. Vatoo routes enquiries and keeps data isolated per bot. Category: Finance & Banking. Public-facing deployment for prospects and customers on a website or app. **Problem.** Financial product pages convert poorly because prospects have detailed, compliance-sensitive questions that need accurate answers fast. **Approach.** A compliance-tuned finance persona answers product questions strictly from an approved knowledge base, captures qualified leads through Smart Forms, and routes to the right team. Per-bot data isolation and BYOK support data-sovereignty needs. **Flow.** 1. Trigger: product question or "apply" 2. Knowledge base: answer from approved content only 3. Form: capture qualified contact details 4. Condition: route by product type 5. Webhook: send lead to CRM **Compared with the manual process.** - **Answer accuracy.** Generic → Grounded in approved content - **Lead quality.** Unqualified → Pre-qualified - **Data sovereignty.** Shared infra → BYOK and isolation - **Routing.** Manual → Automated ### Fitness Membership & Class Chatbot - [Fitness Membership & Class Chatbot](https://vatoo.ai/use-cases/fitness-membership-signup-chatbot): Sign up members and book classes from the chat. Vatoo answers plan questions, captures sign-ups, and remembers members across visits. Category: Fitness & Wellness. Public-facing deployment for prospects and customers on a website or app. **Problem.** Prospective members ask about plans and classes at odd hours and don't convert without an instant answer. Front-desk staff juggle bookings and enquiries. **Approach.** A fitness persona answers plan and class questions from a knowledge base, Smart Forms capture sign-ups and class bookings, and memory recognises returning members and their preferences. **Flow.** 1. Trigger: "join" or "book a class" 2. Knowledge base: answer plan and class questions 3. Form: plan choice or class, contact details 4. Webhook: push to membership or scheduling system 5. Memory: remember the member for next time **Compared with the manual process.** - **Sign-up conversion.** Lost without instant answer → Captured 24/7 - **Class bookings.** Phone and desk → Self-served - **Member recognition.** Anonymous → Remembered - **Front-desk load.** High → Reduced ### Fraud Report & Dispute Intake Chatbot - [Fraud Report & Dispute Intake Chatbot](https://vatoo.ai/use-cases/fraud-report-dispute-intake-chatbot): Let customers report fraud and disputes instantly. Vatoo captures structured details, triggers the right workflow by type, and escalates urgent cases with full context. Category: Finance & Banking. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Customers reporting suspected fraud or disputing a transaction face phone queues at a stressful moment, and intake details arrive inconsistently, slowing investigation. **Approach.** A fraud-and-disputes persona captures structured report details (transaction, amount, date, reason) via Smart Forms, branches by case type, and fires a webhook to the fraud or disputes workflow, escalating urgent cases immediately with a full context summary. Interactions are logged for the audit trail. Decisioning stays in the connected system; the bot handles structured intake and routing. **Flow.** 1. Trigger: "report fraud" or "dispute a charge" 2. Knowledge base: reassure and explain next steps 3. Form: transaction, amount, date, reason 4. Condition: branch by case type and urgency 5. Webhook: route to the fraud or disputes workflow with a summary **Compared with the manual process.** - **Reporting speed.** Phone queues → Instant self-service - **Intake quality.** Inconsistent → Structured - **Urgent cases.** Wait in queue → Escalated with context - **Audit record.** Manual notes → Logged automatically ### Freight Claims Intake Chatbot - [Freight Claims Intake Chatbot](https://vatoo.ai/use-cases/freight-claims-intake-chatbot): Standardise damage and loss claims intake. Vatoo collects structured claim details and evidence references, then routes to the claims team automatically. Category: Logistics & Freight. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Freight claims arrive as messy emails with missing details, causing back-and-forth and slow resolution. **Approach.** A claims persona explains the process from a knowledge base, the Flow Engine collects structured claim details (shipment reference, damage type, value) via Smart Forms, branches by claim type, and fires a webhook to the claims system with a complete record. **Flow.** 1. Trigger: "file a claim" 2. Knowledge base: explain the claims process and requirements 3. Form: shipment reference, claim type, value, description 4. Condition: branch by claim type 5. Webhook: create a structured claim record **Compared with the manual process.** - **Claim completeness.** Missing details → Structured intake - **Resolution time.** Slow back-and-forth → Faster - **Process questions.** Staff-answered → Self-served - **Routing.** Manual → By claim type ### Gaming Player Support Chatbot - [Gaming Player Support Chatbot](https://vatoo.ai/use-cases/gaming-player-support-chatbot): Support players instantly. Vatoo answers from your game wiki and FAQs, checks account status via API, and escalates complex tickets with full context. Category: Gaming. Public-facing deployment for prospects and customers on a website or app. **Problem.** Game studios face high support volume for account, payment and gameplay questions, with players expecting instant help across time zones. **Approach.** A player-support persona answers from an indexed game wiki and FAQ knowledge base, a per-persona tool checks account or purchase status via API, and complex tickets escalate to a human with an AI summary attached. **Flow.** 1. Trigger: gameplay, account or payment question 2. Knowledge base: answer from wiki and FAQs 3. API call: check account or purchase status 4. Condition: unresolved? escalate with an AI summary 5. Form: capture a ticket where needed **Compared with the manual process.** - **Support volume.** High tier-1 → Deflected - **Time-zone coverage.** Limited → 24/7 - **Account checks.** Agent lookups → API self-service - **Escalations.** Cold → With context ### Government Citizen Services Chatbot - [Government Citizen Services Chatbot](https://vatoo.ai/use-cases/government-citizen-services-chatbot): Help citizens find services and submit requests 24/7. Vatoo answers from official content and routes service requests without call-centre load. Category: Government. Public-facing deployment for prospects and customers on a website or app. **Problem.** Government call centres and counters are overwhelmed with routine questions about services, forms and eligibility, creating long waits for citizens. **Approach.** A citizen-services persona answers from official knowledge content, Smart Forms capture service requests, and webhooks route them to the right department. On-prem deployment supports data-residency requirements. **Flow.** 1. Trigger: service question or request 2. Knowledge base: answer from official content 3. Form: capture request details and contact 4. Condition: route by service or department 5. Webhook: send to the case-management system **Compared with the manual process.** - **Call-centre load.** High → Deflected - **Citizen wait.** Long queues → Instant - **Service requests.** Manual intake → Structured - **Data residency.** Shared infra → On-prem option ### Healthcare Appointment Intake Chatbot - [Healthcare Appointment Intake Chatbot](https://vatoo.ai/use-cases/healthcare-appointment-intake-chatbot): Collect symptoms, urgency and insurance, then push to your booking system. Vatoo triages urgent cases and books routine appointments without front-desk load. Category: Healthcare. Public-facing deployment for prospects and customers on a website or app. **Problem.** Front desks are overwhelmed by appointment calls, and patients wait on hold. Urgent cases aren't always flagged early, and routine bookings consume staff time. **Approach.** A healthcare advisor persona runs intake through the Flow Engine: it collects symptoms and urgency, branches urgent cases to a call prompt, collects insurance and date preferences, and fires a webhook to the booking system. Knowledge base answers common clinic questions. (Deploy on compliant infrastructure for patient data.) **Flow.** 1. Trigger: "book an appointment" 2. Form: symptom description and urgency 3. Condition: urgent? prompt to call the clinic 4. Form: insurance details and preferred date 5. Webhook: send to the booking system API **Compared with the manual process.** - **Front-desk calls.** High volume on hold → Self-service intake - **Urgent triage.** Inconsistent → Branched and flagged - **Routine bookings.** Staff time → Automated - **After-hours intake.** Voicemail → Captured 24/7 ### Healthcare No-Show Reduction Chatbot - [Healthcare No-Show Reduction Chatbot](https://vatoo.ai/use-cases/healthcare-no-show-reduction-chatbot): Cut no-shows with a two-way confirm, remind, surface-barriers and reactivate sequence. Vatoo confirms intent, handles frictionless rescheduling, and syncs to your practice system. Category: Healthcare. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Outpatient no-show rates still run 15 to 30 percent, and a static one-way reminder does little to recover the appointment. The real drivers are forgotten visits, scheduling conflicts and unflagged logistics barriers that a single SMS never surfaces. **Approach.** A patient-engagement persona runs a two-way Flow: confirm intent, remind, surface barriers (transport, timing) via Smart Forms, and offer frictionless rescheduling when a patient signals they cannot attend. Memory holds each patient's appointment context, and a webhook syncs confirmations and reschedules to the practice-management system. Deploy on compliant infrastructure for patient data. **Flow.** 1. Trigger: upcoming appointment or reschedule intent 2. Form: confirm, cancel, or flag a barrier 3. Condition: barrier or conflict? branch to a reschedule path 4. API or form: offer alternative open slots 5. Webhook: sync the confirmation or reschedule to the PM system **Compared with the manual process.** - **No-show rate.** One-way reminders, 15 to 30 percent → Two-way confirm and rebook - **Rescheduling.** High friction, patients no-show → Frictionless in chat - **Barrier visibility.** Hidden until missed → Surfaced early - **Front-desk calls.** Manual reminder and rebook → Automated ### Home Services Booking Chatbot - [Home Services Booking Chatbot](https://vatoo.ai/use-cases/home-services-booking-dispatch-chatbot): Book trades and dispatch jobs fast. Vatoo captures the job, location and urgency, routes by trade and area, and books a visit into your system. Category: Home Services. Public-facing deployment for prospects and customers on a website or app. **Problem.** Home-services firms lose jobs when calls go unanswered and capture too little detail to dispatch the right technician efficiently. **Approach.** A home-services persona answers service and pricing questions from a knowledge base, the Flow Engine captures job type, location and urgency via Smart Forms, branches by trade and area, and books a visit via webhook. **Flow.** 1. Trigger: "book a" service or job question 2. Knowledge base: answer service and pricing questions 3. Form: job type, location, urgency, photos reference 4. Condition: branch by trade and area 5. Webhook: dispatch and book the visit **Compared with the manual process.** - **Missed jobs.** Calls unanswered → Captured 24/7 - **Dispatch detail.** Thin → Structured - **Routing.** Manual → By trade and area - **Pricing questions.** Staff time → Self-served ### Hotel Reservation & Concierge Chatbot - [Hotel Reservation & Concierge Chatbot](https://vatoo.ai/use-cases/hotel-reservation-concierge-chatbot): Capture room bookings and answer guest questions around the clock. Vatoo surfaces a booking form at the right moment and remembers repeat guests across stays. Category: Hospitality. Public-facing deployment for prospects and customers on a website or app. **Problem.** Direct bookings leak to OTAs because guests can't get instant answers on the hotel's own site. Front desk staff field repetitive questions on amenities, check-in times and rates instead of serving guests in person. **Approach.** A Concierge persona answers amenity, policy and rate questions from a private knowledge base. The Smart Form Engine surfaces a reservation form when booking intent is detected, and memory greets returning guests with their preferences already known. **Flow.** 1. Trigger: guest asks about availability or rates 2. Knowledge base: answer amenity, policy and rate questions 3. Form: dates, room type, guest count surfaced inline 4. Webhook: push reservation request to PMS or booking engine 5. Memory: store guest preferences for the next stay **Compared with the manual process.** - **Direct bookings.** Lost to OTAs → Captured on your own site - **After-hours service.** Voicemail → Instant answers - **Repeat guests.** Treated as new → Preferences remembered - **Front desk load.** Repetitive questions → Deflected to bot ### Immigration Eligibility Screening Chatbot - [Immigration Eligibility Screening Chatbot](https://vatoo.ai/use-cases/immigration-eligibility-screening-chatbot): Screen immigration enquiries by visa pathway. Vatoo asks structured questions, routes by likely route, and books consultations, within non-advice content. Category: Legal & Compliance / Immigration. Public-facing deployment for prospects and customers on a website or app. **Problem.** Immigration firms field complex enquiries spanning many visa routes, and manual screening before consultation is slow and inconsistent. **Approach.** An immigration persona answers general process questions from approved non-advice content, the Flow Engine screens by structured questions and branches to a likely route, and a webhook books a paid consultation for qualified enquiries. **Flow.** 1. Trigger: visa or immigration question 2. Knowledge base: general process info (non-advice) 3. Form: nationality, purpose, status, timeline 4. Condition: branch to a likely visa pathway 5. Webhook: book a consultation and create a CRM record **Compared with the manual process.** - **Screening.** Manual, slow → Structured first pass - **Route matching.** Ad hoc → Branched by pathway - **Consultation booking.** Phone → Inline - **Compliance.** Off-script risk → Approved content only ### Insurance FNOL Claims Chatbot - [Insurance FNOL Claims Chatbot](https://vatoo.ai/use-cases/insurance-claims-fnol-chatbot): Capture first notice of loss instantly. Vatoo guides claimants through structured claim details and routes a complete FNOL to your claims system. Category: Insurance. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Claimants report losses by phone with variable detail, slowing claims handling and frustrating customers at a stressful moment. **Approach.** An insurance claims persona guides claimants through the Flow Engine, capturing structured loss details, dates and evidence references via Smart Forms, branches by claim type, and fires a webhook to the claims system with a complete FNOL. **Flow.** 1. Trigger: "report a claim" 2. Knowledge base: reassure and explain the process 3. Form: policy number, loss type, date, description 4. Condition: branch by claim type 5. Webhook: create a complete FNOL in the claims system **Compared with the manual process.** - **FNOL completeness.** Variable → Structured - **Reporting speed.** Phone queues → 24/7 self-service - **Claimant experience.** Stressful → Guided - **Handling time.** Slow → Faster start ### Insurance Quote Intake Chatbot - [Insurance Quote Intake Chatbot](https://vatoo.ai/use-cases/insurance-quote-intake-chatbot): Collect quote details inline and deliver a live premium estimate. Vatoo gathers structured inputs, calls your rating API, and opens a CRM opportunity. Category: Insurance. Public-facing deployment for prospects and customers on a website or app. **Problem.** Quote forms are long and impersonal, so prospects abandon them. Agents then spend time on incomplete submissions and basic policy questions. **Approach.** An insurance persona answers policy questions from a knowledge base. The Flow Engine collects quote inputs through conversational Smart Forms, an API node calls the rating engine, the estimate is delivered inline, and a webhook opens a CRM opportunity. **Flow.** 1. Trigger: "get a quote" 2. Form: coverage type, key risk details 3. API call: rating engine returns a premium estimate 4. Message: deliver the estimate inline 5. Webhook: create a CRM opportunity for follow-up **Compared with the manual process.** - **Form abandonment.** Long static forms → Conversational, lower drop-off - **Quote speed.** Manual callback → Live estimate inline - **Agent time.** Incomplete submissions → Pre-qualified leads - **Policy questions.** Agent-answered → Self-served ### Interactive ROI Calculator Chatbot - [Interactive ROI Calculator Chatbot](https://vatoo.ai/use-cases/interactive-roi-calculator-chatbot): Turn pricing curiosity into qualified leads. Vatoo collects inputs, computes an ROI or price estimate via API, shows the result, and captures the lead. Category: Cross-industry / B2B. Public-facing deployment for prospects and customers on a website or app. **Problem.** Static ROI calculators and hidden pricing pages cause drop-off and capture no context about who is interested. **Approach.** A presales persona collects relevant inputs via Smart Forms, an API node computes an ROI or price estimate, the result is shown inline, and a webhook captures the lead with all inputs for sales context. **Flow.** 1. Trigger: "how much" or "what's my ROI" 2. Form: relevant inputs (volume, current cost, size) 3. API call: compute the ROI or price estimate 4. Message: present the result inline 5. Webhook: capture the lead with inputs for sales **Compared with the manual process.** - **Calculator drop-off.** High on static tools → Conversational - **Lead context.** None → Inputs captured - **Pricing friction.** Hidden, frustrating → Transparent estimate - **Sales handoff.** Cold → Context-rich ### Internal Agent-Assist Chatbot - [Internal Agent-Assist Chatbot](https://vatoo.ai/use-cases/internal-agent-assist-chatbot): Give live agents instant, grounded answers. Vatoo surfaces the right policy or procedure mid-call from your internal knowledge base, cutting handle time. Category: Cross-industry / Customer Service. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Contact-centre agents put customers on hold to hunt for answers across systems, inflating handle time and inconsistency. **Approach.** An internal agent-assist persona indexes policies, procedures and product info into a private knowledge base and returns grounded answers instantly. Per-persona tools can pull account context via API, and memory keeps the case thread. **Flow.** 1. Trigger: agent asks a question mid-interaction 2. Knowledge base: return the relevant policy or procedure 3. API call: optional account or order context 4. Message: deliver a concise, grounded answer 5. Memory: keep case context across the interaction **Compared with the manual process.** - **Handle time.** Inflated by hold → Reduced - **Answer consistency.** Variable by agent → Standardised - **Hold time.** Frequent → Reduced - **New-agent ramp.** Slow → Faster ### Internal Metrics Lookup Chatbot - [Internal Metrics Lookup Chatbot](https://vatoo.ai/use-cases/internal-bi-metrics-lookup-chatbot): Let staff ask for metrics and reports in plain language. Vatoo answers definitions from your data dictionary and fetches figures via API. Category: Cross-industry / Data. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Staff flood data teams with requests for routine metrics and definitions, and self-serve BI tools are too complex for casual users. **Approach.** An internal data persona answers metric definitions from a data-dictionary knowledge base and uses a per-persona tool to fetch current figures via an API or reporting endpoint, returning them inline. Access stays internal via multi-tenant isolation. **Flow.** 1. Trigger: "what is" a metric or "show me" a figure 2. Knowledge base: answer definitions from the data dictionary 3. API call: fetch the current figure from the reporting endpoint 4. Message: deliver the figure with its definition 5. Form: capture custom report requests for the data team **Compared with the manual process.** - **Routine data requests.** Data-team time → Self-served - **Metric definitions.** Inconsistent → Single source - **BI tool friction.** High for casual users → Plain-language access - **Custom requests.** Ad hoc → Structured intake ### Internal Compliance Policy Chatbot - [Internal Compliance Policy Chatbot](https://vatoo.ai/use-cases/internal-compliance-policy-chatbot): Give staff fast, grounded answers on compliance and policy. Vatoo answers strictly from approved internal content and routes edge cases to the compliance team. Category: Legal & Compliance / Cross-industry. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Employees can't easily find current compliance and policy guidance, leading to risky guesses or constant escalation to a stretched compliance team. **Approach.** A compliance persona answers strictly from an approved, indexed policy knowledge base, with per-bot isolation and (at Enterprise) on-prem deployment for sensitive content. Edge cases route to the compliance team via webhook with full context. **Flow.** 1. Trigger: compliance or policy question 2. Knowledge base: answer from approved content only 3. Condition: edge case or ambiguity? flag for review 4. Webhook: route to the compliance team with context 5. Memory: keep the staff member's context **Compared with the manual process.** - **Policy findability.** Hard to locate → Instant, grounded - **Risky guesses.** Common → Reduced - **Compliance escalations.** High → Only true edge cases - **Data sensitivity.** Shared infra → Isolation and on-prem option ### Internal Employee Onboarding Chatbot - [Internal Employee Onboarding Chatbot](https://vatoo.ai/use-cases/internal-employee-onboarding-chatbot): Guide new hires through day-one tasks automatically. Vatoo walks through steps, collects acknowledgements, hands off to IT, and logs completion to your HRIS. Category: Recruitment & HR / Cross-industry. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** New-hire onboarding is manual and inconsistent: paperwork chases, missed steps, and HR and IT both juggling the same checklist for every joiner. **Approach.** The Flow Engine guides new hires through welcome steps, Smart Forms collect policy acknowledgements, a persona handoff routes to IT for account setup, and a webhook logs completion to the HRIS. Memory tracks each hire's progress. **Flow.** 1. Trigger: new-hire session start 2. Flow: guide through welcome and day-one steps 3. Form: policy and document acknowledgements 4. Handoff: route to the IT persona for account setup 5. Webhook: log completion to the HRIS **Compared with the manual process.** - **Onboarding consistency.** Variable → Standardised flow - **Paperwork chasing.** Manual → Collected inline - **HR and IT load.** Duplicated effort → Automated handoff - **Completion tracking.** Manual → Logged to HRIS ### Internal Facilities Request Chatbot - [Internal Facilities Request Chatbot](https://vatoo.ai/use-cases/internal-facilities-request-chatbot): Handle workplace requests in one place. Vatoo logs maintenance, desk and access requests, routes by type, and pushes tickets to your facilities system. Category: Cross-industry / Facilities. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Workplace and facilities requests come via email, chat and walk-ups with no structure, so triage is slow and items get lost. **Approach.** A facilities persona answers workplace FAQs from a knowledge base, the Flow Engine captures requests (maintenance, desk booking, access) via Smart Forms, branches by type and urgency, and fires a webhook to the facilities or ticketing system. **Flow.** 1. Trigger: a facilities request or question 2. Knowledge base: answer workplace FAQs 3. Form: request type, location, urgency 4. Condition: branch by type and urgency 5. Webhook: create a ticket in the facilities system **Compared with the manual process.** - **Request channels.** Scattered → One structured intake - **Triage.** Manual → Branched - **Lost items.** Common → Tracked - **FAQ load.** Staff time → Deflected ### Internal Field Service Chatbot - [Internal Field Service Chatbot](https://vatoo.ai/use-cases/internal-field-service-chatbot): Support field technicians on site with instant manual lookups and guided fixes. Vatoo answers from equipment docs and logs issues back to your system. Category: Construction / Manufacturing. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Field technicians waste time calling the office or flipping through manuals on site, and issue reporting is inconsistent and delayed. **Approach.** A field-service persona indexes equipment manuals and troubleshooting guides into a knowledge base, the Flow Engine runs guided diagnostics with conditional branches, and Smart Forms log issues and parts requests back to the ops system via webhook. **Flow.** 1. Trigger: equipment or troubleshooting question 2. Knowledge base: answer from manuals and guides 3. Flow: guided diagnostic with branches 4. Form: log the issue or parts request 5. Webhook: send to the field-ops or ticketing system **Compared with the manual process.** - **Manual lookups.** Paper and calls → Instant in-chat - **Office calls.** Frequent → Reduced - **Issue logging.** Delayed, inconsistent → Structured inline - **First-time fix.** Lower → Improved with guidance ### Internal Finance & AP Chatbot - [Internal Finance & AP Chatbot](https://vatoo.ai/use-cases/internal-finance-ap-enquiry-chatbot): Answer staff questions on expenses, invoices and AP process. Vatoo indexes finance policy and can check status via API, reducing finance-team interruptions. Category: Accounting & Tax / Cross-industry. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Finance teams are interrupted constantly by expense-policy, invoice-status and reimbursement questions, slowing month-end and core work. **Approach.** An internal finance persona answers expense and AP policy questions from a knowledge base, a per-persona tool checks invoice or reimbursement status via API, and Smart Forms capture exception requests routed to finance by webhook. **Flow.** 1. Trigger: expense, invoice or AP question 2. Knowledge base: answer from finance policy 3. API call: check invoice or reimbursement status 4. Form: capture an exception or query 5. Webhook: route to the finance team **Compared with the manual process.** - **Finance interruptions.** Constant → Reduced - **Status checks.** Manual lookups → API self-service - **Policy questions.** Staff-answered → Deflected - **Month-end focus.** Disrupted → Protected ### Internal HR Policy Chatbot - [Internal HR Policy Chatbot](https://vatoo.ai/use-cases/internal-hr-policy-chatbot): Give employees instant answers on HR policy, leave and benefits. Vatoo answers from your handbook and routes complex cases to HR with context. Category: Recruitment & HR / Cross-industry. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** HR teams answer the same policy, leave and benefits questions repeatedly, pulling time away from strategic work, and employees struggle to find answers in long handbooks. **Approach.** An internal HR persona answers from an indexed handbook and benefits knowledge base, the Smart Form Engine captures leave or benefits requests, and complex cases route to HR via webhook with full context. Memory keeps employee context across questions. **Flow.** 1. Trigger: HR policy, leave or benefits question 2. Knowledge base: answer from handbook and policy content 3. Form: capture a leave or benefits request 4. Condition: complex case? route to HR 5. Webhook: notify HR with full context **Compared with the manual process.** - **Repetitive HR questions.** Staff time → Deflected - **Answer findability.** Buried in handbook → Instant - **Request intake.** Email → Structured - **HR focus.** Reactive → On strategic work ### Internal Incident Runbook Chatbot - [Internal Incident Runbook Chatbot](https://vatoo.ai/use-cases/internal-incident-runbook-chatbot): Get on-call engineers to the right runbook fast. Vatoo surfaces the matching procedure from your runbook library and captures incident details. Category: SaaS & Tech / Operations. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** During incidents, on-call engineers waste critical minutes finding the right runbook across wikis under pressure. **Approach.** An internal ops persona indexes runbooks and procedures into a knowledge base and surfaces the matching steps instantly, with a Smart Form to capture incident details routed to the incident channel via webhook. Memory keeps the incident thread. **Flow.** 1. Trigger: an incident or "how do I handle" question 2. Knowledge base: surface the matching runbook steps 3. Form: capture incident details and severity 4. Webhook: post to the incident channel or tracker 5. Memory: keep the incident context **Compared with the manual process.** - **Runbook lookup.** Slow under pressure → Instant - **Time to mitigate.** Lost to search → Reduced - **Incident capture.** Ad hoc → Structured - **On-call stress.** High → Lower ### Internal IT Helpdesk Chatbot - [Internal IT Helpdesk Chatbot](https://vatoo.ai/use-cases/internal-it-helpdesk-chatbot): Deflect repetitive IT tickets with an internal bot. Vatoo answers from your IT knowledge base, runs guided troubleshooting flows, and escalates with a summary. Category: SaaS & Tech / Cross-industry. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** IT teams are buried in repetitive tickets (password resets, VPN, access requests) that don't need a specialist, slowing response on genuinely complex issues. **Approach.** An internal IT-support persona answers from an IT knowledge base, the Flow Engine runs guided troubleshooting with conditional branches, Smart Forms capture access or hardware requests, and unresolved issues escalate to a human with an AI summary. Multi-tenant isolation keeps it internal-only. **Flow.** 1. Trigger: employee IT question 2. Knowledge base: answer from IT documentation 3. Flow: guided troubleshooting with branches 4. Form: capture access or hardware request 5. Webhook or escalation: create a ticket with an AI summary **Compared with the manual process.** - **Tier-1 tickets.** High volume → Deflected - **Resolution speed.** Queue wait → Instant self-service - **Specialist focus.** Diluted → On complex issues - **Request intake.** Email and forms → Structured ### Internal Legal Request Intake Chatbot - [Internal Legal Request Intake Chatbot](https://vatoo.ai/use-cases/internal-legal-request-intake-chatbot): Triage legal and contract requests from the business. Vatoo captures structured intake, routes by request type, and pushes to your legal queue with context. Category: Legal & Compliance / Cross-industry. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** In-house legal teams receive vague requests through many channels, causing back-and-forth and unclear prioritisation. **Approach.** An internal legal-intake persona explains the process from a knowledge base, the Flow Engine captures structured intake (request type, counterparty, value, deadline) via Smart Forms, branches by type, and fires a webhook to the legal queue with full context. **Flow.** 1. Trigger: "I need legal help" or contract request 2. Knowledge base: explain the intake process 3. Form: request type, counterparty, value, deadline 4. Condition: branch by request type 5. Webhook: create a legal request with full context **Compared with the manual process.** - **Request clarity.** Vague → Structured intake - **Channels.** Scattered → Single front door - **Prioritisation.** Unclear → Type and deadline captured - **Back-and-forth.** High → Reduced ### Internal Offboarding Chatbot - [Internal Offboarding Chatbot](https://vatoo.ai/use-cases/internal-offboarding-chatbot): Make leavers' last days smooth and compliant. Vatoo guides offboarding steps, collects exit data, triggers IT deprovisioning, and logs completion. Category: Recruitment & HR / Cross-industry. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Offboarding is error-prone: access isn't always revoked promptly, assets go uncollected, and exit feedback is inconsistently captured. **Approach.** An HR persona guides leavers through offboarding steps via the Flow Engine, captures exit-interview responses and asset returns via Smart Forms, triggers IT deprovisioning via a persona handoff or webhook, and logs completion to the HRIS. **Flow.** 1. Trigger: offboarding session start 2. Flow: guide through return and handover steps 3. Form: exit-interview responses and asset returns 4. Webhook: trigger IT deprovisioning 5. Webhook: log completion to the HRIS **Compared with the manual process.** - **Access revocation.** Delayed → Triggered on exit - **Asset collection.** Missed → Tracked - **Exit feedback.** Inconsistent → Captured - **Compliance.** Gaps → Standardised ### Internal Procurement Request Chatbot - [Internal Procurement Request Chatbot](https://vatoo.ai/use-cases/internal-procurement-request-chatbot): Streamline purchase requests. Vatoo explains policy, captures structured requisitions, routes by category and value, and pushes to your procurement system. Category: Cross-industry / Procurement. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Employees don't know procurement policy or which form to use, so purchase requests arrive incomplete and routing is manual. **Approach.** A procurement persona explains policy and thresholds from a knowledge base, the Flow Engine captures structured requisitions via Smart Forms, branches by category and value for the right approval path, and fires a webhook to the procurement system. **Flow.** 1. Trigger: "I need to buy" or a policy question 2. Knowledge base: explain policy and approval thresholds 3. Form: item, category, cost, justification 4. Condition: branch by category and value 5. Webhook: create a requisition in the procurement system **Compared with the manual process.** - **Request completeness.** Often incomplete → Structured - **Policy questions.** Procurement time → Self-served - **Approval routing.** Manual → By category and value - **Cycle time.** Slow → Faster ### Internal Sales Enablement Chatbot - [Internal Sales Enablement Chatbot](https://vatoo.ai/use-cases/internal-sales-enablement-chatbot): Give reps instant answers on pricing, battlecards and product details. Vatoo indexes your sales content so reps stop pinging Slack mid-deal. Category: SaaS & Tech / Cross-industry. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Sales reps lose deal momentum hunting for pricing, competitive battlecards and product answers across scattered docs and Slack channels. **Approach.** An internal sales-enablement persona answers from an indexed knowledge base of pricing, battlecards and product content. Per-persona tools can pull live data (e.g. inventory or CRM lookups), and memory keeps rep context across questions. **Flow.** 1. Trigger: rep asks a pricing or product question 2. Knowledge base: answer from enablement content 3. API call: optional live CRM or inventory lookup 4. Message: deliver the answer with source context 5. Memory: keep deal context across the session **Compared with the manual process.** - **Answer-finding.** Scattered docs and Slack → One bot - **Deal momentum.** Stalls mid-call → Instant answers - **Content freshness.** Stale copies → Single indexed source - **Ramp time.** Slow for new reps → Faster ### Internal SAP / ERP Assistant Chatbot - [Internal SAP / ERP Assistant Chatbot](https://vatoo.ai/use-cases/internal-sap-erp-assistant-chatbot): Help staff navigate SAP and ERP tasks. Vatoo answers from SOPs and can search SAP OSS notes and T-code docs via API mid-conversation. Category: Manufacturing / Cross-industry. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** ERP interfaces are complex and training is costly. Staff lose time hunting for the right T-code, process step or OSS note, and the help desk fields repetitive how-to questions. **Approach.** An SAP persona answers process questions from an internal SOP knowledge base and uses a per-persona tool to search the SAP Support Portal (OSS notes, T-code docs) via API mid-conversation. Requires an API-enabled S-User ID. Note: Vatoo documents read and search operations; write-back to ERP is not a documented capability. **Flow.** 1. Trigger: SAP or ERP how-to question 2. Knowledge base: answer from internal SOPs 3. API call: search SAP OSS notes or T-code documentation 4. Message: deliver guidance with references 5. Escalation: route complex cases to the ERP team **Compared with the manual process.** - **ERP how-to load.** Help-desk time → Self-served - **Note and T-code lookup.** Manual portal search → In-chat API search - **Training cost.** High → Reduced with on-demand help - **Staff productivity.** Lost to navigation → Restored ### Internal SOP Knowledge Chatbot - [Internal SOP Knowledge Chatbot](https://vatoo.ai/use-cases/internal-sop-knowledge-chatbot): Turn your SOPs and process docs into an instant-answer assistant. Vatoo indexes internal documentation so staff find the right procedure in seconds. Category: Manufacturing / Cross-industry. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Critical procedures live in scattered PDFs and wikis. Staff either guess or interrupt colleagues, and inconsistent process execution creates risk and rework. **Approach.** An internal operations persona indexes SOPs, process docs and policies into a private vector knowledge base, and answers staff questions with the most relevant procedure injected into every response. Updates to a single source propagate instantly. **Flow.** 1. Trigger: procedure or process question 2. Knowledge base: retrieve the relevant SOP chunk 3. Message: deliver the procedure with context 4. Form: optional feedback or exception logging 5. Memory: keep context across related questions **Compared with the manual process.** - **Procedure findability.** Scattered docs → Instant - **Process consistency.** Variable → Standardised answers - **Colleague interruptions.** Frequent → Reduced - **Doc updates.** Out of sync → Single source propagates ### Internal Warehouse Operations Chatbot - [Internal Warehouse Operations Chatbot](https://vatoo.ai/use-cases/internal-warehouse-ops-chatbot): Help warehouse staff find SOPs, bin locations and process steps fast. Vatoo answers from internal docs and can query stock status via API. Category: Logistics / WMS. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Warehouse staff lose time hunting for put-away rules, bin logic and exception handling, and supervisors get interrupted for routine answers. **Approach.** A warehouse operations persona indexes SOPs and process guides into a knowledge base, runs guided exception-handling flows, and uses an API tool to check stock or location status from the WMS where available. **Flow.** 1. Trigger: process or location question 2. Knowledge base: answer from warehouse SOPs 3. API call: check stock or bin status from the WMS 4. Flow: guided exception handling with branches 5. Form: log an exception or discrepancy **Compared with the manual process.** - **SOP lookup.** Paper and supervisors → Instant in-chat - **Supervisor interruptions.** Frequent → Reduced - **Stock checks.** Terminal hopping → In-chat via API - **Process consistency.** Variable → Standardised ### Interview Self-Scheduling Chatbot - [Interview Self-Scheduling Chatbot](https://vatoo.ai/use-cases/interview-self-scheduling-chatbot): End interview scheduling back-and-forth. Vatoo answers candidate questions, offers open interview slots, books them, and syncs to the hiring team's calendar. Category: Recruitment & HR. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Recruiters lose hours to interview scheduling back-and-forth, and strong candidates drop off during slow coordination, especially at high application volumes. **Approach.** A recruitment persona answers role and process questions from a knowledge base, the Flow Engine offers open interview slots via Smart Forms (optionally checking a calendar API), books the slot, and fires a webhook to the ATS and the hiring team's calendar. A clear disclosure notes where AI is used and where humans decide, supporting transparency expectations. **Flow.** 1. Trigger: "schedule my interview" or role question 2. Knowledge base: answer role and process questions 3. API or form: present available interview slots 4. Form: confirm the chosen slot and contact details 5. Webhook: book to the ATS and hiring-team calendar **Compared with the manual process.** - **Scheduling effort.** Manual back-and-forth → Self-served - **Candidate drop-off.** High on slow coordination → Reduced - **Recruiter hours.** Hours per week on logistics → Freed - **Transparency.** Unclear AI use → Disclosed in flow ### Document & Knowledge Base Q&A Chatbot - [Document & Knowledge Base Q&A Chatbot](https://vatoo.ai/use-cases/knowledge-base-document-qa-chatbot): Turn your PDFs, docs, URLs and YouTube content into an instant-answer bot. Vatoo indexes your content into a private vector DB and answers only from what you teach it. Category: Cross-industry. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Organisations hold answers in scattered PDFs, manuals, web pages and videos that nobody can search effectively, so the same questions get asked repeatedly. **Approach.** Vatoo indexes PDFs, DOCX, URLs, plain text and YouTube transcripts into a private, per-bot vector database. The most relevant chunks are retrieved and injected into every answer, with no cross-contamination between bots and per-source update control. **Flow.** 1. Upload PDFs, docs, URLs or YouTube transcripts 2. Vatoo chunks, embeds and indexes into a private collection 3. Visitor or staff asks a question 4. Relevant chunks retrieved and injected into the answer 5. Update a single source any time; index refreshes **Compared with the manual process.** - **Content searchability.** Scattered, unsearchable → Instant Q&A - **Answer grounding.** Generic AI → Only your content - **Source control.** Bulk re-upload → Per-source updates - **Data isolation.** Mixed → Private per bot ### Lead Capture & Analytics Chatbot - [Lead Capture & Analytics Chatbot](https://vatoo.ai/use-cases/lead-capture-analytics-chatbot): Capture every lead automatically and see exactly what visitors ask. Vatoo logs full sessions, captures name and email after two exchanges, and exports to any CRM. Category: Cross-industry. Public-facing deployment for prospects and customers on a website or app. **Problem.** Businesses run chatbots but lose the leads and insights: no structured capture, no visibility into what visitors actually ask, and no easy export to the CRM. **Approach.** Vatoo captures lead name and email naturally after two exchanges, logs full session history attributed to the correct bot, and exports to CSV for any CRM. Tenant users see only their own leads, and analytics reveal common questions and drop-off points. **Flow.** 1. Visitor starts a conversation 2. After two exchanges, capture name and email naturally 3. Full session history logged and attributed to the bot 4. Analytics: review common questions and patterns 5. Export leads to CSV for any CRM **Compared with the manual process.** - **Lead capture.** Missed or manual → Automatic after two exchanges - **Visitor insight.** None → Full session history - **CRM handoff.** Manual → CSV export - **Data access.** Mixed → Per-tenant isolation ### Legal Intake & Screening Chatbot - [Legal Intake & Screening Chatbot](https://vatoo.ai/use-cases/legal-intake-screening-chatbot): Screen and intake potential clients automatically. Vatoo collects case details, checks conflict criteria, and routes qualified matters to the right practice. Category: Legal & Compliance. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Law firms spend paralegal time screening enquiries that don't fit, while genuine matters wait. Intake is manual and inconsistent across practice areas. **Approach.** A legal-intake persona answers general questions from an approved knowledge base, the Flow Engine screens enquiries through Smart Forms, branches by matter type and basic conflict criteria, and routes qualified matters by webhook. (Answers stay strictly within approved, non-advice content.) **Flow.** 1. Trigger: "need a lawyer" or matter question 2. Form: matter type and basic details 3. Condition: branch by practice area and screening criteria 4. Form: contact details for qualified matters 5. Webhook: route to the relevant practice group **Compared with the manual process.** - **Screening time.** Paralegal hours → Automated first pass - **Intake consistency.** Variable → Standardised - **Routing.** Manual → By practice area - **Response speed.** Delayed → Instant ### Freight Quote Chatbot for Logistics - [Freight Quote Chatbot for Logistics](https://vatoo.ai/use-cases/logistics-freight-quote-chatbot): Generate live freight quotes inside the chat. Vatoo collects cargo details, calls your rate engine, and delivers a quote plus a CRM opportunity in seconds. Category: Logistics & Freight. Public-facing deployment for prospects and customers on a website or app. **Problem.** Freight quoting is slow and manual: customers email cargo details, ops staff look up rates, and quotes come back hours later, often after the customer has gone elsewhere. **Approach.** A logistics persona collects origin, destination and cargo details through a Smart Form, an API node calls the freight rate engine mid-conversation, the quote is delivered inline, and a webhook opens a CRM opportunity. This acts as a conversational front end to a TMS or rating layer. **Flow.** 1. Trigger: "freight quote" 2. Form: origin, destination, weight, dimensions, mode 3. API call: freight rate engine returns pricing 4. Message: deliver the quote inline 5. Webhook: create a CRM opportunity **Compared with the manual process.** - **Quote turnaround.** Hours → Seconds, inline - **Lost deals.** Customer goes elsewhere → Quote before they leave - **Ops workload.** Manual lookups → Automated rating call - **Lead capture.** Email only → Structured CRM record ### Manufacturing Enquiry Chatbot - [Manufacturing Enquiry Chatbot](https://vatoo.ai/use-cases/manufacturing-distributor-enquiry-chatbot): Answer product spec and distributor questions and capture B2B leads. Vatoo indexes your spec sheets and routes enquiries to the right team. Category: Manufacturing. Public-facing deployment for prospects and customers on a website or app. **Problem.** Manufacturers field technical spec, availability and distributor questions across long sales cycles, and enquiries are slow to route to the right rep or region. **Approach.** A manufacturing persona answers spec and availability questions from an indexed knowledge base of datasheets, captures B2B leads through Smart Forms, and routes by product line or region via webhook. **Flow.** 1. Trigger: spec, availability or distributor question 2. Knowledge base: answer from datasheets and catalogues 3. Form: company, product interest, volume 4. Condition: route by product line or region 5. Webhook: send to CRM and notify the rep **Compared with the manual process.** - **Spec questions.** Engineer time → Self-served - **Lead routing.** Slow, manual → Automated - **B2B capture.** Email → Structured - **Response speed.** Days → Instant ### Marina Berth Booking Chatbot - [Marina Berth Booking Chatbot](https://vatoo.ai/use-cases/marina-berth-booking-chatbot): Let visitors book berths inside the chat. Vatoo collects vessel details, checks availability, and pushes confirmed bookings to your marina CRM. No staff, no code. Category: Marina & Boating. Public-facing deployment for prospects and customers on a website or app. **Problem.** Marinas lose bookings to after-hours enquiries and phone tag. Staff spend hours answering the same berth-availability and pricing questions, and walk-in enquiries go cold before anyone replies. **Approach.** A Marina Manager persona handles enquiries 24/7. The Flow Engine triggers on "book a berth", surfaces a Smart Form for vessel details and dates inline, optionally calls a live availability API, and fires a webhook to the marina CRM on completion. Cross-session memory recognises returning sailors and their vessels. **Flow.** 1. Trigger: visitor says "book a berth" 2. Condition: returning visitor? Load memory and greet by name 3. Form: vessel length, type, arrival and departure dates 4. API call: check live berth availability 5. Webhook: push confirmed booking to marina CRM with a reference number **Compared with the manual process.** - **Enquiry response.** Hours to next business day → Instant, 24/7 - **Booking capture.** Lost after hours → Captured inline any time - **Staff workload.** Manual phone and email → Bot handles routine enquiries - **Returning sailors.** Re-explain every time → Recognised, context preserved ### Media Subscription Support Chatbot - [Media Subscription Support Chatbot](https://vatoo.ai/use-cases/media-subscription-support-chatbot): Convert and support subscribers. Vatoo answers plan and access questions, checks subscription status via API, and captures sign-ups at the paywall. Category: Media & Publishing. Public-facing deployment for prospects and customers on a website or app. **Problem.** Publishers lose conversions at the paywall and field repetitive access, billing and plan questions from subscribers. **Approach.** A media persona answers plan and access questions from a knowledge base, a per-persona tool checks subscription status via API, and the Smart Form Engine surfaces sign-up at the paywall moment, with proactive prompts on metered limits. **Flow.** 1. Trigger: paywall hit or access question 2. API call: check subscription or access status 3. Knowledge base: answer plan and billing questions 4. Form: surface a sign-up offer at the paywall 5. Webhook: push the new subscriber to billing **Compared with the manual process.** - **Paywall conversion.** Passive → Proactive offer - **Access questions.** Support time → Self-served - **Status checks.** Manual → API-driven - **Subscriber support.** Ticket-heavy → Deflected ### Mortgage Pre-Qualification Chatbot - [Mortgage Pre-Qualification Chatbot](https://vatoo.ai/use-cases/mortgage-prequalification-chatbot): Pre-qualify mortgage enquiries inline. Vatoo collects income and deposit details, runs an affordability estimate via API, and routes warm leads to a broker. Category: Finance & Banking / Mortgage. Public-facing deployment for prospects and customers on a website or app. **Problem.** Mortgage brokers spend time on enquiries that don't qualify, while serious buyers abandon long forms and slow callbacks. **Approach.** A mortgage persona answers product questions from a knowledge base, the Flow Engine collects income, deposit and property details conversationally, an API node returns an affordability estimate, and a webhook routes qualified leads to a broker. **Flow.** 1. Trigger: "mortgage" or "how much can I borrow" 2. Form: income, deposit, property price, term 3. API call: affordability and indicative rate estimate 4. Message: deliver the estimate inline 5. Webhook: route a qualified lead to the broker CRM **Compared with the manual process.** - **Lead quality.** Mixed → Pre-qualified - **Form abandonment.** Long static forms → Conversational - **Estimate speed.** Callback → Inline - **Broker time.** Wasted on poor fits → Focused ### Multi-Persona Support Routing Chatbot - [Multi-Persona Support Routing Chatbot](https://vatoo.ai/use-cases/multi-persona-support-routing-chatbot): One bot, a team of specialist agents inside. Vatoo routes each message to the right persona automatically, invisibly to the visitor, across sales, support and billing. Category: Cross-industry. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** A single generic bot gives shallow answers across many topics, while building separate bots per function fragments the experience and the data. **Approach.** Vatoo runs multiple specialist personas inside one bot. The AI routes each message to the right persona automatically (sales, support, billing, technical), invisibly to the visitor, with shared cross-session memory so context follows the customer across handoffs. **Flow.** 1. Visitor sends any message 2. AI evaluates intent and selects the right persona 3. Persona answers from its own knowledge and tools 4. Handoff: route to another persona if the topic shifts 5. Memory: shared context follows the visitor throughout **Compared with the manual process.** - **Answer depth.** Shallow generalist → Specialist per topic - **Experience.** Fragmented across bots → One seamless bot - **Routing.** Manual menus → AI-decided - **Context.** Lost on handoff → Shared memory ### Multilingual Global Support Chatbot - [Multilingual Global Support Chatbot](https://vatoo.ai/use-cases/multilingual-global-support-chatbot): Support customers in their own language at scale. Vatoo answers from one knowledge base across languages and routes escalations with translated context. Category: Cross-industry. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Global businesses can't staff every language around the clock, so non-English customers get slower, lower-quality support. **Approach.** A support persona answers from a single knowledge base across multiple languages, detecting and replying in the customer's language, capturing leads and tickets via Smart Forms, and escalating to humans with translated context via webhook. **Flow.** 1. Trigger: a question in any supported language 2. Detect language and respond in kind 3. Knowledge base: answer from the shared content 4. Form: capture a lead or ticket 5. Webhook: escalate with translated context if unresolved **Compared with the manual process.** - **Language coverage.** English-centric → Many languages - **After-hours non-English.** Unstaffed → 24/7 - **Content upkeep.** Per-language copies → Single source - **Escalations.** Lost in translation → Translated context ### Non-Profit Donor & Volunteer Chatbot - [Non-Profit Donor & Volunteer Chatbot](https://vatoo.ai/use-cases/non-profit-donor-volunteer-chatbot): Capture donations interest and volunteer sign-ups. Vatoo answers programme questions and routes supporters to the right next step. Category: Non-Profit. Public-facing deployment for prospects and customers on a website or app. **Problem.** Small non-profit teams can't respond fast enough to donor and volunteer interest, and momentum is lost between a visitor's intent and a human reply. **Approach.** A non-profit persona answers programme and impact questions from a knowledge base, Smart Forms capture donor interest and volunteer sign-ups, and webhooks route supporters to the CRM. **Flow.** 1. Trigger: "donate", "volunteer" or programme question 2. Knowledge base: answer from programme content 3. Form: supporter details and interest 4. Condition: donor or volunteer branch 5. Webhook: send to the CRM or fundraising platform **Compared with the manual process.** - **Supporter follow-up.** Delayed → Instant capture - **Volunteer sign-up.** Manual → Self-served - **Programme questions.** Staff time → Deflected - **Momentum.** Lost → Captured at intent ### Partner Program Enrollment Chatbot - [Partner Program Enrollment Chatbot](https://vatoo.ai/use-cases/partner-program-enrollment-chatbot): Recruit and onboard channel partners. Vatoo explains tiers, captures partner applications, screens fit, and routes to your channel team. Category: SaaS & Tech / Channel. Public-facing deployment for prospects and customers on a website or app. **Problem.** Channel teams field partner enquiries with inconsistent qualification, slowing recruitment and diluting partner quality. **Approach.** A partner persona explains program tiers and benefits from a knowledge base, the Flow Engine captures partner applications via Smart Forms, screens fit by region and model, and routes qualified applicants to the channel team via webhook. **Flow.** 1. Trigger: "become a partner" 2. Knowledge base: explain tiers and benefits 3. Form: company, region, model, customer base 4. Condition: fit-screening branch 5. Webhook: route qualified applicants to the channel team **Compared with the manual process.** - **Partner qualification.** Inconsistent → Screened - **Recruitment speed.** Slow → Faster - **Program questions.** Manager time → Self-served - **Partner quality.** Diluted → Improved fit ### Payment Plan Self-Service Chatbot - [Payment Plan Self-Service Chatbot](https://vatoo.ai/use-cases/payment-plan-self-service-chatbot): Let customers set up and check payment plans without calling. Vatoo explains options, captures arrangements, and pushes them to your billing system. Category: Finance / Collections. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Collections and billing teams handle high call volumes for routine payment-plan setup and balance questions, an awkward, costly process for both sides. **Approach.** A billing persona explains plan options from a knowledge base, the Flow Engine captures a proposed arrangement via Smart Forms, an API tool checks current balance, and a webhook submits the arrangement to the billing system for approval. A calm, neutral tone is configured at the persona level. **Flow.** 1. Trigger: "payment plan" or balance question 2. API call: retrieve current balance and status 3. Knowledge base: explain available plan options 4. Form: proposed amount and frequency 5. Webhook: submit the arrangement to billing for approval **Compared with the manual process.** - **Call volume.** High for routine plans → Self-served - **Customer experience.** Awkward calls → Private self-service - **Balance questions.** Agent-handled → API self-service - **Arrangement intake.** Manual → Structured ### Personal Trainer Lead Chatbot - [Personal Trainer Lead Chatbot](https://vatoo.ai/use-cases/personal-trainer-lead-chatbot): Turn fitness interest into booked consults. Vatoo captures goals and availability, matches a trainer, and books an intro session. Category: Fitness & Wellness. Public-facing deployment for prospects and customers on a website or app. **Problem.** Independent trainers and studios lose leads when prospects can't quickly express their goals and book an intro session. **Approach.** A fitness persona captures goals, experience and availability via Smart Forms, the Flow Engine matches a trainer by specialism, and a webhook books an intro consultation. Memory keeps returning prospect context. **Flow.** 1. Trigger: "work with a trainer" 2. Form: goals, experience, availability 3. Condition: match a trainer by specialism 4. Webhook: book an intro consultation 5. Memory: keep prospect context for follow-up **Compared with the manual process.** - **Lead capture.** Lost → Structured intake - **Trainer matching.** Manual → By specialism - **Intro bookings.** Phone → Inline - **Follow-up.** Cold → Context kept ### Pharmacy Refill & Medication Chatbot - [Pharmacy Refill & Medication Chatbot](https://vatoo.ai/use-cases/pharmacy-refill-enquiry-chatbot): Take refill requests and answer pharmacy questions 24/7. Vatoo collects prescription details, checks status via API, and routes requests to the pharmacy team. Category: Pharmacy / Healthcare. Public-facing deployment for prospects and customers on a website or app. **Problem.** Pharmacy phone lines are jammed with refill requests and stock and opening-hours questions, creating long waits and tying up pharmacists. **Approach.** A pharmacy persona answers stock, hours and general medication-handling questions from a knowledge base (non-clinical advice only), captures refill requests via Smart Forms, optionally checks status through an API tool, and routes to the pharmacy via webhook. Deploy on compliant infrastructure for patient data. **Flow.** 1. Trigger: "refill" or a pharmacy question 2. Knowledge base: answer stock, hours and handling questions 3. Form: prescription number and patient details 4. API call: check refill or stock status if available 5. Webhook: send the refill request to the pharmacy queue **Compared with the manual process.** - **Phone congestion.** Refill calls dominate → Self-service intake - **Wait times.** Long queues → Instant - **Pharmacist time.** Tied up on calls → Protected - **Status checks.** Manual lookups → API-driven ### Post-Discharge Follow-Up Chatbot - [Post-Discharge Follow-Up Chatbot](https://vatoo.ai/use-cases/post-discharge-followup-chatbot): Keep patients engaged between visits. Vatoo runs post-discharge check-ins and medication-adherence prompts, captures concerning responses, and flags the care team. Category: Healthcare. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Engagement between visits is where outcomes are won or lost, but manual follow-up calls do not scale, so post-discharge instructions and medication adherence slip, driving readmissions. **Approach.** A care-follow-up persona runs scheduled check-in Flows, captures symptom and adherence responses via Smart Forms, branches concerning answers to a care-team alert via webhook, and uses memory to track each patient's plan over time. Framed as non-clinical support that escalates to humans; deploy on compliant infrastructure. **Flow.** 1. Trigger: scheduled post-discharge or adherence check-in 2. Form: symptom check and medication-taken status 3. Condition: concerning trend? branch to escalation 4. Webhook: flag the care team with the captured context 5. Memory: track the care plan across check-ins **Compared with the manual process.** - **Between-visit contact.** Manual calls, limited → Automated check-ins - **Adherence.** Slips silently → Prompted and logged - **Concerning signs.** Caught late → Flagged early - **Care-team load.** Manual outreach → Exception-based ### Post-Interaction Summary Handoff Chatbot - [Post-Interaction Summary Handoff Chatbot](https://vatoo.ai/use-cases/post-interaction-summary-handoff-chatbot): End the repeat-yourself problem. Vatoo hands off to a human with a structured summary of the conversation, so customers never re-explain and agents start informed. Category: Cross-industry. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** When a bot escalates, customers are forced to repeat everything to the agent, which is the single most cited friction point and inflates handle time. **Approach.** On escalation, the persona generates a structured summary of the conversation and intent and passes it to the human via webhook, while memory preserves context if the customer returns later. This delivers the warm, context-rich handoff that distinguishes modern agentic support from scripted bots. **Flow.** 1. Trigger: escalation to a human 2. Generate: a structured summary of intent and history 3. Webhook: deliver the summary to the agent or ticketing system 4. Memory: preserve context for any return visit 5. Continue: agent starts informed, no repetition **Compared with the manual process.** - **Customer repetition.** Re-explain everything → Eliminated - **Handle time.** Inflated by re-context → Reduced - **Agent start.** Cold → Informed - **Returning customers.** Lost context → Remembered ### Proactive Conversion & Retention Agent - [Proactive Conversion & Retention Agent](https://vatoo.ai/use-cases/proactive-conversion-retention-agent): Don't wait for visitors to ask. Vatoo's goal-driven agents trigger on idle, return visits and page context to qualify, rescue carts, and drive renewals. Category: Cross-industry. Public-facing deployment for prospects and customers on a website or app. **Problem.** Most chatbots are passive: they wait for a question and miss the moment a visitor is about to leave or is ready to convert. **Approach.** Vatoo's proactive, goal-driven agents (Pro+ plans) pursue defined goals and fire on triggers like idle time, return visits and page context, executing multi-step plans to qualify leads, rescue carts or prompt renewals, with performance monitoring built in. **Flow.** 1. Define a goal: "qualify this lead" or "rescue this cart" 2. Set proactive triggers: idle, return visit, page context 3. Agent initiates the conversation when conditions match 4. Execute a multi-step plan toward the goal 5. Monitor performance and flag underperforming prompts **Compared with the manual process.** - **Engagement.** Passive, wait-for-ask → Proactive at the right moment - **Cart recovery.** Lost silently → Actively rescued - **Lead qualification.** Manual → Goal-driven and automatic - **Optimisation.** Guesswork → Performance monitored ### Proactive Renewal & Retention Chatbot - [Proactive Renewal & Retention Chatbot](https://vatoo.ai/use-cases/proactive-renewal-retention-chatbot): Stop silent lapses. Vatoo proactively engages customers ahead of renewal, answers questions, captures the renewal, and routes wavering customers for retention. Category: Insurance. Public-facing deployment for prospects and customers on a website or app. **Problem.** Policies and subscriptions lapse silently at renewal because the only outreach is an easily ignored notice, and there is no two-way moment to answer questions or save the customer. **Approach.** A retention persona uses proactive triggers to engage customers ahead of renewal, answers coverage and pricing questions from a knowledge base, captures the renewal via a Smart Form, and branches wavering customers to a retention path routed by webhook. Memory recalls the customer's prior policy context. **Flow.** 1. Trigger: approaching renewal date or renewal question 2. Knowledge base: answer coverage and pricing questions 3. Condition: renew now or wavering? branch accordingly 4. Form: capture the renewal or a retention request 5. Webhook: process the renewal or route to retention **Compared with the manual process.** - **Silent lapses.** Common → Engaged proactively - **Renewal questions.** Unanswered → Self-served - **Wavering customers.** Lost → Routed to retention - **Prior context.** Re-asked → Remembered ### Product Waitlist Qualification Chatbot - [Product Waitlist Qualification Chatbot](https://vatoo.ai/use-cases/product-waitlist-qualification-chatbot): Turn a waitlist into qualified pipeline. Vatoo captures use case and fit, segments sign-ups, and routes high-fit prospects to sales while others wait. Category: SaaS & Tech. Public-facing deployment for prospects and customers on a website or app. **Problem.** Waitlists collect emails with no context, so launch teams can't prioritise outreach or distinguish high-fit prospects from the curious. **Approach.** A product persona captures use case, company and intent via Smart Forms, the Flow Engine segments sign-ups by fit, routes high-fit prospects to sales via webhook, and uses memory to recognise returning sign-ups. **Flow.** 1. Trigger: "join the waitlist" 2. Form: use case, company, role, intent 3. Condition: segment by fit 4. Webhook: route high-fit prospects to sales 5. Memory: recognise returning sign-ups **Compared with the manual process.** - **Waitlist context.** Email only → Use case captured - **Prioritisation.** None → Segmented by fit - **Sales handoff.** Manual → Automated for high-fit - **Launch outreach.** Untargeted → Prioritised ### Property Management Tenant Chatbot - [Property Management Tenant Chatbot](https://vatoo.ai/use-cases/property-management-tenant-request-chatbot): Let tenants submit maintenance requests and get answers 24/7. Vatoo captures the request, categorises it, and pushes it to your PM system. Category: Property Management. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Property managers field maintenance requests and tenant questions by phone and email, with no structure and slow triage, leading to missed or duplicated tickets. **Approach.** A property-management persona answers lease and policy questions from a knowledge base, the Flow Engine captures maintenance requests via Smart Forms, branches by urgency or category, and fires a webhook to the PM or ticketing system. **Flow.** 1. Trigger: maintenance request or tenant question 2. Knowledge base: answer lease and policy questions 3. Form: issue description, location, urgency 4. Condition: branch by category or urgency 5. Webhook: create a ticket in the PM system **Compared with the manual process.** - **Request intake.** Phone and email → Structured inline - **Triage.** Manual, slow → Branched by urgency - **Tenant answers.** Office hours → 24/7 - **Duplicate tickets.** Common → Reduced ### Real Estate Viewing & Lead Chatbot - [Real Estate Viewing & Lead Chatbot](https://vatoo.ai/use-cases/real-estate-viewing-booking-chatbot): Turn property interest into booked viewings. Vatoo qualifies the buyer, routes by area to the right agent, and books the slot, all inside the chat. Category: Real Estate. Public-facing deployment for prospects and customers on a website or app. **Problem.** Property portals generate enquiries at all hours, but leads go cold while agents are showing other properties. Manual routing means the wrong agent often gets the lead. **Approach.** A property persona qualifies the enquiry, the Flow Engine branches by area or property type to route the lead, a Smart Form captures contact details and preferred times, and a webhook books the slot on the right agent's calendar. **Flow.** 1. Trigger: visitor says "viewing" or "book a visit" 2. Form: name, phone, preferred date and time 3. Condition: branch by area or property type 4. Webhook: send to the matched agent's calendar API 5. Confirm: reply with a booking reference **Compared with the manual process.** - **Lead response.** Delayed, often cold → Instant capture - **Routing accuracy.** Manual, error-prone → Auto-routed by area - **Viewings booked.** Phone tag → Booked inline - **Agent time.** Chasing enquiries → Focused on showings ### Recruitment Candidate Screening Chatbot - [Recruitment Candidate Screening Chatbot](https://vatoo.ai/use-cases/recruitment-candidate-screening-chatbot): Screen and capture candidates 24/7. Vatoo answers role questions, pre-qualifies applicants, and pushes them to your ATS automatically. Category: Recruitment & HR. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Recruiters spend hours on early-stage screening and answering the same role questions, while strong candidates drop off due to slow responses. **Approach.** A recruitment persona answers role and process questions from a knowledge base, the Flow Engine screens candidates through Smart Forms, branches on basic criteria, and fires a webhook to the ATS. **Flow.** 1. Trigger: "apply" or role question 2. Knowledge base: answer role and process questions 3. Form: experience, location, availability 4. Condition: branch on basic screening criteria 5. Webhook: push candidate to the ATS **Compared with the manual process.** - **Screening time.** Recruiter hours → Automated first pass - **Candidate drop-off.** High on slow replies → Reduced - **Role FAQs.** Recruiter-answered → Deflected - **ATS entry.** Manual → Automated ### Rental Application Pre-Screening Chatbot - [Rental Application Pre-Screening Chatbot](https://vatoo.ai/use-cases/rental-application-prescreening-chatbot): Pre-screen renters before viewings. Vatoo captures budget, move-in date and criteria, filters fit, and books viewings for qualified applicants. Category: Real Estate / Rentals. Public-facing deployment for prospects and customers on a website or app. **Problem.** Lettings agents waste time on viewings with applicants who don't meet criteria, while qualified renters wait. **Approach.** A lettings persona answers listing questions from a knowledge base, the Flow Engine pre-screens applicants on budget, move-in date and criteria, branches qualified ones, and books viewings via webhook. **Flow.** 1. Trigger: rental enquiry or "book a viewing" 2. Knowledge base: answer listing questions 3. Form: budget, move-in date, occupants, criteria 4. Condition: qualification branch 5. Webhook: book a viewing for qualified applicants **Compared with the manual process.** - **Unqualified viewings.** Common → Filtered out - **Agent time.** Wasted → Focused - **Qualified renters.** Delayed → Fast-tracked - **Listing questions.** Agent-answered → Self-served ### Restaurant Reservation Chatbot - [Restaurant Reservation Chatbot](https://vatoo.ai/use-cases/restaurant-reservation-chatbot): Take table bookings and answer menu and allergen questions any time. Vatoo surfaces a reservation form automatically and pushes bookings to your system. Category: Restaurants. Public-facing deployment for prospects and customers on a website or app. **Problem.** Phone reservations are missed during service, and staff repeatedly answer the same menu, allergen and opening-hours questions. **Approach.** A restaurant persona answers menu and allergen questions from a knowledge base. The Smart Form Engine surfaces a reservation form when booking intent appears, and a webhook sends the booking to your reservation system. **Flow.** 1. Trigger: "book a table" or menu question 2. Knowledge base: answer menu, allergen and hours questions 3. Form: party size, date, time, contact 4. Webhook: push to reservation platform 5. Confirm: reply with a booking reference **Compared with the manual process.** - **Missed calls.** Lost during service → Captured any time - **Menu questions.** Staff-answered → Self-served - **Booking effort.** Phone only → Inline form - **Off-hours bookings.** Lost → Captured 24/7 ### SaaS Churn Deflection Chatbot - [SaaS Churn Deflection Chatbot](https://vatoo.ai/use-cases/saas-churn-deflection-chatbot): Save subscriptions at the cancel moment. Vatoo understands the reason, offers a tailored retention path, and routes genuine cancels cleanly. Category: SaaS & Tech. Public-facing deployment for prospects and customers on a website or app. **Problem.** Customers cancel in a single click with no chance to address the real reason, so recoverable churn is lost. **Approach.** A retention persona engages at the cancellation step, the Flow Engine branches on the stated reason (price, missing feature, not using it) to offer a tailored path, and a webhook logs the outcome and routes confirmed cancels to billing. **Flow.** 1. Trigger: cancellation intent 2. Form: reason for cancelling 3. Condition: branch by reason to a tailored offer or guidance 4. Message: present a retention path or accept the cancel 5. Webhook: log the outcome and route to billing **Compared with the manual process.** - **Recoverable churn.** Lost at one click → Engaged and saved - **Cancel insight.** None → Reason captured - **Retention offers.** Generic → Reason-tailored - **Clean cancels.** Abrupt → Routed with context ### SaaS Lead Qualification Chatbot - [SaaS Lead Qualification Chatbot](https://vatoo.ai/use-cases/saas-lead-qualification-chatbot): Qualify inbound visitors against your ICP automatically. Vatoo scores fit, captures contact details, and alerts the right rep in Slack with a CRM record created. Category: SaaS & Tech. Public-facing deployment for prospects and customers on a website or app. **Problem.** Sales teams waste hours on unqualified demo requests while genuine ICP-fit prospects wait for a reply. Manual lead scoring is slow and inconsistent. **Approach.** A sales persona engages pricing and demo intent. The Flow Engine asks qualifying questions (company size, use case), branches hot or cold against ICP criteria, captures contact details via a Smart Form, and fires a webhook to the CRM plus a Slack alert for hot leads. **Flow.** 1. Trigger: "pricing" or "demo" intent detected 2. Questions: company size, use case, timeline 3. Condition: ICP match? branch hot or cold 4. Form: name, work email, phone 5. Webhook: create CRM record and post a Slack alert for hot leads **Compared with the manual process.** - **Lead scoring.** Manual, inconsistent → Automatic against ICP - **Rep time.** Spent on poor fits → Focused on hot leads - **Response speed.** Hours → Instant Slack alert - **CRM hygiene.** Manual entry → Auto-created records ### SaaS In-App Onboarding Chatbot - [SaaS In-App Onboarding Chatbot](https://vatoo.ai/use-cases/saas-product-onboarding-chatbot): Guide new users to first value. Vatoo answers setup questions from your docs, walks through activation steps, and flags stuck users to customer success. Category: SaaS & Tech. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** New SaaS users churn before reaching first value because setup is confusing and support docs are hard to search in the moment. **Approach.** An onboarding persona answers setup questions from an indexed docs knowledge base, the Flow Engine walks users through activation steps with branches, memory tracks progress across sessions, and a webhook alerts customer success when a user stalls. **Flow.** 1. Trigger: new user or setup question 2. Knowledge base: answer from product docs 3. Flow: guided activation steps with branches 4. Memory: track activation progress across sessions 5. Webhook: alert customer success on a stalled user **Compared with the manual process.** - **Time to first value.** Slow, self-directed → Guided - **Early churn.** High → Reduced - **Docs search.** Manual → In-context answers - **CS intervention.** Reactive → Proactive on stall ### Security Questionnaire Assist Chatbot - [Security Questionnaire Assist Chatbot](https://vatoo.ai/use-cases/security-questionnaire-assist-chatbot): Speed up vendor security reviews. Vatoo answers questionnaire items from your approved security knowledge base so sales and security respond faster. Category: SaaS & Tech / Security. Internal staff deployment. Its knowledge and conversation logs stay in that deployment and are kept separate from customer-facing bots through Vatoo’s multi-tenant isolation. **Problem.** Sales deals stall while teams manually answer repetitive security and compliance questionnaires from a scattered set of prior responses. **Approach.** An internal security persona indexes approved security, privacy and compliance answers into a knowledge base and returns grounded responses to questionnaire items, with a feedback form to flag answers needing review by security. Kept internal via isolation. **Flow.** 1. Trigger: paste or ask a questionnaire item 2. Knowledge base: return the approved grounded answer 3. Message: deliver the answer with source reference 4. Form: flag items needing security review 5. Webhook: route flagged items to the security team **Compared with the manual process.** - **Questionnaire turnaround.** Slow, manual → Faster - **Answer consistency.** Variable → Approved source - **Deal velocity.** Stalled → Improved - **Security workload.** Repetitive → Reduced ### Sentiment-Aware Support Routing Chatbot - [Sentiment-Aware Support Routing Chatbot](https://vatoo.ai/use-cases/sentiment-aware-support-routing-chatbot): Route by mood, not just topic. Vatoo detects frustration in the conversation and escalates at-risk interactions to a human early, with a summary attached. Category: Cross-industry. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Topic-only routing misses the customers who are about to churn because they are frustrated, so negative interactions escalate too late and damage loyalty. **Approach.** A support persona evaluates conversational sentiment alongside intent, and the Flow Engine branches frustrated or high-risk interactions to early human escalation with an AI summary via webhook, while routine, positive interactions stay fully automated. Captured sentiment signals feed analytics for Voice-of-Customer insight. **Flow.** 1. Trigger: any support interaction 2. Assess: intent plus conversational sentiment 3. Condition: frustration or risk detected? branch to escalation 4. Webhook: hand off to a human with an AI summary 5. Analytics: log sentiment signals for VoC review **Compared with the manual process.** - **Escalation timing.** Too late → Early on detected risk - **Churn risk.** Missed → Surfaced - **Routine handling.** Same path for all → Stays automated - **VoC insight.** None → Sentiment captured ### Shipment Tracking & Status Chatbot - [Shipment Tracking & Status Chatbot](https://vatoo.ai/use-cases/shipment-tracking-status-chatbot): Give customers instant shipment status. Vatoo looks up tracking via API, explains exceptions, and captures delivery change requests. Category: Logistics & Freight. Public-facing deployment for prospects and customers on a website or app. **Problem.** "Where is my shipment" enquiries flood logistics support, and customers grow anxious when status isn't instantly available. **Approach.** A logistics persona uses a per-persona tool to look up live tracking via API, explains exceptions from a knowledge base, and captures delivery-change or reschedule requests via Smart Forms routed by webhook. **Flow.** 1. Trigger: "track my shipment" 2. Form or input: tracking or reference number 3. API call: fetch live shipment status and ETA 4. Knowledge base: explain any exception or delay 5. Form + webhook: capture a delivery-change request **Compared with the manual process.** - **Status enquiries.** Human-handled → Self-served via API - **Customer anxiety.** High on no info → Instant status - **Support volume.** Tracking dominates → Deflected - **Delivery changes.** Phone-bound → Captured inline ### SME Business Loan Intake Chatbot - [SME Business Loan Intake Chatbot](https://vatoo.ai/use-cases/sme-business-loan-intake-chatbot): Qualify small-business borrowers inline. Vatoo collects revenue and need, runs an indicative eligibility check via API, and routes warm files to lending. Category: Finance & Banking / SME Lending. Public-facing deployment for prospects and customers on a website or app. **Problem.** SME lending teams sift through many enquiries that don't meet basic criteria, while qualified businesses face slow responses. **Approach.** An SME lending persona answers product questions from a knowledge base, the Flow Engine collects revenue, tenure and need, an API node returns indicative eligibility, and a webhook routes qualified files to lending. **Flow.** 1. Trigger: "business loan" or "working capital" 2. Form: revenue, time in business, amount, purpose 3. API call: indicative eligibility check 4. Message: deliver the indicative outcome 5. Webhook: route a qualified file to lending **Compared with the manual process.** - **Enquiry sifting.** Manual → Pre-qualified - **Eligibility speed.** Callback → Inline - **Product questions.** Officer time → Self-served - **Qualified files.** Slow → Fast-tracked ### Solar Installer Lead & Estimate Chatbot - [Solar Installer Lead & Estimate Chatbot](https://vatoo.ai/use-cases/solar-installer-lead-chatbot): Qualify solar leads and give a ballpark estimate. Vatoo collects roof and usage details, returns an indicative figure via API, and books a site survey. Category: Energy & Utilities / Solar. Public-facing deployment for prospects and customers on a website or app. **Problem.** Solar installers get many low-intent enquiries and spend time on site surveys for leads that never convert. **Approach.** A solar persona answers product and incentive questions from a knowledge base, the Flow Engine collects roof, usage and location details, an API node returns an indicative system size and saving estimate, and a webhook books a site survey for qualified leads. **Flow.** 1. Trigger: "solar quote" or product question 2. Form: address, roof type, monthly usage 3. API call: indicative system size and savings estimate 4. Message: deliver the estimate inline 5. Webhook: book a site survey for qualified leads **Compared with the manual process.** - **Lead quality.** Mixed → Pre-qualified - **Wasted surveys.** Common → Reduced - **Estimate speed.** Callback → Inline - **Incentive questions.** Rep time → Self-served ### Student Services Support Chatbot - [Student Services Support Chatbot](https://vatoo.ai/use-cases/student-services-support-chatbot): Support enrolled students 24/7. Vatoo answers from handbooks and policies, checks status via API, and routes complex cases to the right office. Category: Education. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Student services offices are overwhelmed by routine questions on timetables, fees, deadlines and procedures, especially at term boundaries. **Approach.** A student-services persona answers from indexed handbooks and policies, a per-persona tool checks enrolment or fee status via API where available, and complex cases route to the right office via webhook with context. **Flow.** 1. Trigger: a student question 2. Knowledge base: answer from handbooks and policies 3. API call: check enrolment or fee status if available 4. Condition: complex case? route to the right office 5. Webhook: notify the office with context **Compared with the manual process.** - **Routine questions.** Office time → Deflected - **Term-boundary spikes.** Overwhelm → Absorbed - **Status checks.** Manual → API-driven - **Routing.** Manual → Automated ### Subcontractor Pre-Qualification Chatbot - [Subcontractor Pre-Qualification Chatbot](https://vatoo.ai/use-cases/subcontractor-prequalification-chatbot): Standardise subcontractor vetting. Vatoo collects trade, capacity, insurance and compliance details, then routes pre-qualified subs to procurement. Category: Construction. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** General contractors collect subcontractor qualification data through inconsistent forms and emails, slowing procurement and creating compliance gaps. **Approach.** A procurement persona explains requirements from a knowledge base, the Flow Engine captures trade, capacity, insurance and compliance details via Smart Forms, branches on completeness, and routes pre-qualified subs to procurement via webhook. **Flow.** 1. Trigger: "register as a subcontractor" 2. Form: trade, capacity, certifications, insurance 3. Condition: completeness and compliance branch 4. Form: contact and document references 5. Webhook: send the pre-qualified sub to procurement **Compared with the manual process.** - **Vetting consistency.** Variable forms → Standardised - **Compliance gaps.** Common → Reduced - **Procurement speed.** Slow → Faster - **Data quality.** Messy → Structured ### Telecom Proactive Outage Care Chatbot - [Telecom Proactive Outage Care Chatbot](https://vatoo.ai/use-cases/telecom-proactive-outage-care-chatbot): Get ahead of outage call spikes. Vatoo proactively informs affected customers, checks status via API, captures fault reports, and deflects the inbound surge. Category: Telecoms. Public-facing deployment for prospects and customers on a website or app. **Problem.** Network incidents trigger call-centre spikes as customers all ask the same status questions at once, overwhelming agents exactly when pressure is highest. **Approach.** A telecom care persona checks outage and account status via an API tool, proactively communicates known issues, captures new fault reports via Smart Forms, and routes them by webhook, absorbing the inbound surge with self-service. Memory keeps each customer's service context. **Flow.** 1. Trigger: outage question or proactive notification 2. API call: check outage and account status 3. Message: communicate the known issue and ETA 4. Form: capture a new fault report if not already known 5. Webhook: route the fault report to operations **Compared with the manual process.** - **Call spikes.** Overwhelm during outages → Deflected - **Status questions.** Repeated to agents → Self-served via API - **Fault reports.** Phone-bound → Structured intake - **Customer anxiety.** High with no info → Proactively informed ### Telecom Support Deflection Chatbot - [Telecom Support Deflection Chatbot](https://vatoo.ai/use-cases/telecom-support-deflection-chatbot): Deflect tier-1 telecom tickets with routed personas. Vatoo answers plan and billing questions, checks account status via API, and escalates with a summary. Category: Telecoms. Public-facing deployment for prospects and customers on a website or app. **Problem.** Telecom support lines are flooded with repetitive plan, billing and coverage questions, driving up cost-per-contact and wait times. **Approach.** Multiple personas (billing, technical, plans) are routed automatically. The knowledge base answers common questions, per-persona tools check account or coverage status, and human escalation carries an AI summary when needed. **Flow.** 1. Trigger: any support question 2. Routing: send to billing, technical or plans persona 3. Knowledge base or API: answer or check account status 4. Condition: unresolved? escalate with an AI summary 5. Lead capture or ticket creation as needed **Compared with the manual process.** - **Tier-1 volume.** High human load → Deflected - **Wait times.** Long queues → Instant answers - **Routing.** IVR menus → AI auto-routing - **Escalations.** Cold handoff → With AI summary ### Telecom Plan Upgrade Chatbot - [Telecom Plan Upgrade Chatbot](https://vatoo.ai/use-cases/telecom-upgrade-recommendation-chatbot): Drive upgrades proactively. Vatoo reviews usage via API, recommends a better-fit plan, and captures the upgrade, increasing ARPU without agent time. Category: Telecoms. Public-facing deployment for prospects and customers on a website or app. **Problem.** Telecom upsell relies on outbound calls that customers dislike, leaving revenue on the table when usage outgrows the current plan. **Approach.** A telecom persona uses a per-persona tool to review usage via API, the Flow Engine recommends a better-fit plan from a knowledge base, and proactive triggers engage customers who exceed limits, capturing the upgrade via webhook. **Flow.** 1. Trigger: usage threshold or upgrade question 2. API call: review current usage and plan 3. Knowledge base: recommend a better-fit plan 4. Message: present the upgrade with the saving 5. Webhook: capture the upgrade and notify billing **Compared with the manual process.** - **Upsell channel.** Disliked calls → Self-service in chat - **ARPU.** Flat → Lifted on fit - **Usage insight.** Hidden from customer → Surfaced - **Agent time.** Outbound calls → Freed ### Travel & Tourism Booking Chatbot - [Travel & Tourism Booking Chatbot](https://vatoo.ai/use-cases/travel-itinerary-booking-chatbot): Turn travel interest into bookings. Vatoo answers destination questions, checks availability via API, and captures booking requests inline. Category: Travel & Tourism. Public-facing deployment for prospects and customers on a website or app. **Problem.** Travel buyers research at all hours across time zones and abandon when questions go unanswered. Manual enquiry handling is slow and seasonal spikes overwhelm staff. **Approach.** A travel persona answers destination and package questions from a knowledge base, an API tool checks live availability, and Smart Forms capture booking requests routed to the right team by webhook. **Flow.** 1. Trigger: destination or package question 2. Knowledge base: answer from package and destination content 3. API call: check live availability 4. Form: traveller details and dates 5. Webhook: send booking request to the operator **Compared with the manual process.** - **Time-zone coverage.** Office hours → 24/7 - **Enquiry handling.** Manual, slow → Instant - **Seasonal spikes.** Staff overwhelmed → Bot absorbs load - **Booking capture.** Lost → Inline ### Travel Visa & Document Checklist Chatbot - [Travel Visa & Document Checklist Chatbot](https://vatoo.ai/use-cases/travel-visa-document-checklist-chatbot): Give travellers a tailored document checklist. Vatoo asks destination and nationality, returns the right requirements, and captures booking interest. Category: Travel & Tourism. Public-facing deployment for prospects and customers on a website or app. **Problem.** Travel agencies repeatedly explain visa and document requirements that vary by destination and nationality, consuming agent time. **Approach.** A travel persona collects destination and nationality, the Flow Engine branches to the right document checklist from a knowledge base, and a Smart Form captures booking or service interest routed via webhook. (Requirements framed as general guidance to verify.) **Flow.** 1. Trigger: "what documents do I need" 2. Form: destination and nationality 3. Condition: branch to the matching checklist 4. Message: deliver the tailored checklist (verify with authorities) 5. Form + webhook: capture booking interest **Compared with the manual process.** - **Requirement questions.** Agent time → Self-served - **Checklist accuracy.** Inconsistent → Branched per case - **Agent load.** Repetitive → Reduced - **Booking interest.** Lost → Captured ### Utility Billing & Outage Chatbot - [Utility Billing & Outage Chatbot](https://vatoo.ai/use-cases/utility-billing-outage-chatbot): Deflect billing and outage calls. Vatoo answers tariff and bill questions, checks outage status via API, and captures service requests automatically. Category: Energy & Utilities. Public-facing deployment for prospects and customers on a website or app. **Problem.** Utility contact centres spike during outages and billing cycles, overwhelming agents with status and tariff questions. **Approach.** A utilities persona answers tariff and billing questions from a knowledge base, a per-persona tool checks outage or account status via API, and Smart Forms capture service requests (new connection, meter issue) routed by webhook. **Flow.** 1. Trigger: billing, tariff or outage question 2. Knowledge base: answer tariff and billing questions 3. API call: check outage or account status 4. Form: capture a service request 5. Webhook: route to the relevant team **Compared with the manual process.** - **Call spikes.** Overwhelm during outages → Deflected - **Tariff questions.** Agent time → Self-served - **Outage status.** Hold times → Instant via API - **Service requests.** Manual intake → Structured ### Venue & Banquet Enquiry Chatbot - [Venue & Banquet Enquiry Chatbot](https://vatoo.ai/use-cases/venue-event-enquiry-chatbot): Capture event enquiries with full detail. Vatoo collects date, headcount and event type, checks availability, and routes qualified leads to your events team. Category: Hospitality / Events. Public-facing deployment for prospects and customers on a website or app. **Problem.** Venues lose high-value event enquiries to slow responses and capture too little detail to qualify them efficiently. **Approach.** An events persona answers package and capacity questions from a knowledge base, the Flow Engine captures event type, date, headcount and budget via Smart Forms, optionally checks availability via API, and routes qualified leads via webhook. **Flow.** 1. Trigger: event or venue enquiry 2. Knowledge base: answer package and capacity questions 3. Form: event type, date, headcount, budget band 4. API call: check date availability if available 5. Webhook: route the qualified lead to the events team **Compared with the manual process.** - **Enquiry detail.** Thin → Fully qualified - **Response speed.** Slow → Instant - **High-value leads.** Lost → Captured - **Availability.** Manual → API-checked ### Veterinary Appointment & Triage Chatbot - [Veterinary Appointment & Triage Chatbot](https://vatoo.ai/use-cases/veterinary-appointment-triage-chatbot): Help pet owners book and triage urgency around the clock. Vatoo collects symptoms, flags emergencies, and books routine visits into your clinic system. Category: Veterinary. Public-facing deployment for prospects and customers on a website or app. **Problem.** Vet clinics field anxious after-hours calls and struggle to separate true emergencies from routine visits, while staff repeat the same prep and policy guidance. **Approach.** A veterinary persona answers care and policy questions from a knowledge base, the Flow Engine triages by symptom and urgency with conditional branches, prompts emergencies to call, and books routine visits via a webhook to the clinic system. Memory stores each pet's profile. **Flow.** 1. Trigger: "book" or a symptom question 2. Form: pet type, symptom, duration, severity 3. Condition: emergency? prompt to call the clinic now 4. Form: routine booking details and preferred time 5. Webhook: send to the clinic management system; store pet profile **Compared with the manual process.** - **Emergency triage.** Inconsistent → Branched and flagged - **After-hours calls.** High volume → Self-service intake - **Pet records.** Re-asked each time → Remembered - **Routine bookings.** Phone-bound → Automated ### Voice-of-Customer Insight Chatbot - [Voice-of-Customer Insight Chatbot](https://vatoo.ai/use-cases/voice-of-customer-insight-chatbot): Turn every conversation into insight. Vatoo logs full interactions and structured signals, surfacing the questions, gaps and sentiment that should feed business decisions. Category: Cross-industry. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Most customer conversations are never analysed, so businesses miss the recurring questions, content gaps and sentiment trends that should guide product, marketing and service decisions. **Approach.** A support or sales persona logs full session history attributed to the correct bot and captures structured signals (top questions, drop-off points, sentiment) through analytics, with a feedback Smart Form for unresolved questions routed via webhook to the relevant team, turning conversations into a usable insight layer. **Flow.** 1. Trigger: any customer conversation 2. Log: full session history attributed to the bot 3. Capture: top questions, drop-off points, sentiment 4. Form: flag unresolved questions or gaps 5. Webhook: route insights to product, marketing or service **Compared with the manual process.** - **Conversation analysis.** Rarely done → Captured at scale - **Content gaps.** Invisible → Surfaced - **Decision input.** Anecdotal → Signal-based - **Unresolved questions.** Lost → Routed to owners ### Warranty & RMA Intake Chatbot - [Warranty & RMA Intake Chatbot](https://vatoo.ai/use-cases/warranty-rma-intake-chatbot): Standardise returns and warranty claims. Vatoo verifies eligibility, captures structured RMA details, and routes approved returns to your system. Category: Manufacturing / Retail. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Warranty and returns requests arrive incomplete, eligibility is checked manually, and customers wait through slow back-and-forth. **Approach.** A warranty persona explains policy from a knowledge base, the Flow Engine captures product and purchase details via Smart Forms, an API tool checks warranty eligibility, branches on outcome, and routes approved RMAs via webhook. **Flow.** 1. Trigger: "return" or "warranty claim" 2. Form: product, serial, purchase date, issue 3. API call: check warranty eligibility 4. Condition: branch on eligibility outcome 5. Webhook: create an approved RMA and send instructions **Compared with the manual process.** - **RMA completeness.** Incomplete → Structured - **Eligibility checks.** Manual → API-driven - **Resolution time.** Slow → Faster - **Policy questions.** Agent-answered → Self-served ### Wealth Advisory Intake Chatbot - [Wealth Advisory Intake Chatbot](https://vatoo.ai/use-cases/wealth-advisory-intake-chatbot): Qualify and onboard advisory prospects. Vatoo captures goals and assets, screens suitability, and books a discovery call, all within compliance-approved content. Category: Finance & Banking / Wealth. Public-facing deployment for prospects and customers on a website or app. **Problem.** Advisory firms get many low-fit enquiries and need an efficient, compliant way to screen prospects before allocating advisor time. **Approach.** A wealth persona answers only from compliance-approved content, the Flow Engine captures goals, time horizon and asset bands, screens suitability with branches, and books a discovery call via webhook. Per-bot isolation and BYOK support data sovereignty. **Flow.** 1. Trigger: advisory enquiry 2. Knowledge base: answer from approved content only 3. Form: goals, horizon, asset band, risk comfort 4. Condition: suitability branch 5. Webhook: book a discovery call and create a CRM record **Compared with the manual process.** - **Prospect screening.** Manual → Automated suitability - **Advisor time.** Low-fit calls → Qualified only - **Compliance.** Risk of off-script answers → Approved content only - **Data sovereignty.** Shared infra → BYOK and isolation ### WhatsApp & Omnichannel Engagement Chatbot - [WhatsApp & Omnichannel Engagement Chatbot](https://vatoo.ai/use-cases/whatsapp-omnichannel-engagement-chatbot): Meet customers on the channels they use. Vatoo extends the same personas, knowledge and flows to messaging channels, keeping context consistent across touchpoints. Category: Cross-industry. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Customers expect to reach businesses on messaging channels, not just a website widget, but maintaining separate bots per channel fragments knowledge and context. **Approach.** One set of personas, knowledge base and flows serves multiple channels, so the same answers, lead capture and webhooks operate consistently wherever the customer is, with shared memory keeping context across touchpoints. Channel availability beyond the web widget is an Enterprise or roadmap capability; confirm current supported channels before positioning. **Flow.** 1. Trigger: a message on any connected channel 2. Knowledge base and persona: answer consistently 3. Form: capture leads or requests in-channel 4. Webhook: route to the same downstream systems 5. Memory: keep context across channels **Compared with the manual process.** - **Channel reach.** Web widget only → Messaging channels too - **Knowledge upkeep.** Per-channel bots → Single source - **Cross-channel context.** Fragmented → Shared memory - **Customer effort.** Channel-specific → Consistent everywhere ### White-Label Chatbot Platform for Agencies - [White-Label Chatbot Platform for Agencies](https://vatoo.ai/use-cases/white-label-agency-reseller-platform): Resell branded vertical chatbots to clients in hours. Vatoo's multi-tenant admin, full white-label and 250+ personas let agencies launch in any vertical fast. Category: SaaS & Tech / Agencies. Can be public-facing or internal. The same engines power both; the direction depends on which knowledge sources and systems you connect. **Problem.** Agencies want to offer AI chatbots but can't justify building per-client bots from scratch, and most platforms charge extra for white-label or lack client isolation. **Approach.** Vatoo provides full white-label (name, colours, avatar, configurable "Powered by"), multi-tenant client isolation, and a 250+ persona library so an agency can launch a branded vertical bot per client in hours. BYOK controls AI costs at scale. **Flow.** 1. Pick a client's vertical from pre-configured domains 2. Subscribe to relevant personas from the library 3. Upload the client's knowledge and configure branding 4. Build flows and forms; embed with one script tag 5. Manage all clients from a multi-tenant admin dashboard **Compared with the manual process.** - **Build cost per client.** Weeks of work → Hours - **White-label.** Often a paid add-on → Included on all plans - **Client isolation.** Often missing → Built-in multi-tenant - **Vertical coverage.** Limited → 250+ personas, 25 verticals ## Integrations 18 setup guides. A standard website assistant can be configured without coding; someone with website access adds the embed. Custom APIs, authentication, and complex workflows may need technical help. Check the connector, plan, permissions, and third-party requirements before starting. Availability of a named connector is described on its guide, not guaranteed for every account. ### Custom API Integration - [AI Chatbot API Integration & Webhooks](https://vatoo.ai/integrations/custom_api): Connect your AI chatbot to business software with REST APIs and webhooks. Follow Vatoo’s guide to permissions, configured actions, and testing. Connect a customer question to a useful action in your business software. Use a supported API to look up information or submit a request; authentication, field mapping, and testing depend on the system you connect. Setup guide level: Easy. Typical time: 10–15 minutes. The linked page has the click-by-click steps. **Before you start.** - A Vatoo account with at least one active chatbot - Business software that offers API or developer access, check your software's settings for a section labelled API, Developer, or Integrations - An API key, access token, or login credentials for that software, your software provider can give you this, usually from the same settings area **Setup outline.** 1. **Add Your API Connection.** Not sure which login method your system uses? Look for an "API", "Developer", or "Security" section in your software's settings, or ask your software provider's support team. They'll know exactly which option to use. 2. **Define What to Send and Receive.** Test it right here. Once you've saved an endpoint, switch to the _Test_ tab inside that same endpoint window. Fill in example values and click Run Test, you'll see the real response from your system instantly. Every test is logged so you can review what was sent and what came back. 3. **Choose How Your Chatbot Uses It.** How it feels to your visitor Hi! I can book you in. What's your name? Sarah Johnson Which date works for you? Next Thursday ✓ Done! Your appointment is booked for Thursday. You'll receive a confirmation shortly. How it feels to your visitor Do you have anything free next Saturday for two people? Let me check that for you… _(checking availability)_ Yes! We have 3 options open on Saturday. A morning slot at 10am, afternoon at 2pm, and evening at 6pm. Which works best for you? You can use both options at the same time. For example, a Flow handles new bookings step-by-step while the Smart AI handles free-text questions like "what's my booking status?" or "is the 5pm slot still available?" 4. **Test and Go Live.** When everything looks right in the preview, click Publish on your bot. From that point on, every submission, lookup, and action your chatbot handles goes directly into your system, automatically, 24 hours a day. **If it fails.** - **Test Connection fails with "Could not connect".** Double-check the base address, make sure it includes https:// at the start and has no trailing slash. Also confirm your API key or token was copied in full with no extra spaces. - **Endpoint test returns an error or unexpected result.** Open the View Logs panel on that endpoint to see the exact response body. The error message from your system will usually tell you exactly what's wrong, a missing required field, an incorrect value format, or an expired token. - **The AI method is not calling my system during chat.** Check that the tool is switched on in Settings → Tools. Also review the description you wrote, make sure it clearly says when to use it. Try rephrasing it: "Call this when the visitor asks about \[specific topic\]." - **The Flow submits but my system shows no data.** Go back to your API Call block in the Flow builder and check the field mappings, confirm each collected answer is mapped to the correct parameter name exactly as your system expects it. ### Discord Integration - [Discord AI Chatbot Integration](https://vatoo.ai/integrations/discord): Connect Vatoo to Discord so members can ask your AI assistant through slash commands. Review bot permissions, setup steps, and troubleshooting. Let your Discord community ask your assistant through slash commands. Connect approved knowledge so members can find answers without leaving the channel. Setup guide level: Medium. Typical time: 15–20 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot configured - Discord account with server management permission **Setup outline.** 1. **Create a Discord Application.** 2. **Add a Bot and Get Token.** Bot token is shown only once. Keep it secure. 3. **Get Your Discord Server (Server) ID.** The copied Server ID is your Guild ID used for slash command registration. 4. **Configure in Vatoo Botmaster.** 5. **Set Interactions Endpoint URL.** If verification fails, ensure your server is publicly reachable via HTTPS. 6. **Create the Slash Command.** 7. **Invite the Bot to Your Server.** 8. **Test the Integration.** **If it fails.** - **Interactions URL verification fails.** Server not reachable via HTTPS. Use ngrok for local dev. - **401 on PING.** Public Key copied wrong · re-check in General Information. - **Slash command not visible.** Wait up to 1 hour for global command propagation, or use guild-specific commands for instant testing. - **Bot does not reply.** Check Discord card shows Active in Vatoo Omnichannel. ### Email Integration - [Chatbot Email Notifications & Lead Alerts](https://vatoo.ai/integrations/email): Send Vatoo chatbot lead alerts, form submissions, and handoff notifications to your team by email. Follow the setup guide and test delivery. Keep your team informed when a lead arrives, a form is submitted, or a conversation needs attention. Configure email notifications around the events that matter to your workflow. Setup guide level: Easy. Typical time: 3–5 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot configured and active - An email address to receive notifications **Setup outline.** 1. **Open Email Configuration.** 2. **Set Notification Recipients.** Use a shared team inbox (e.g. team@yourcompany.com) so multiple people get notified without listing each individually. 3. **Choose Notification Triggers.** 4. **Add an Email Signature (Optional).** 5. **Save and Test.** If the test email lands in spam, ask your email admin to whitelist the Vatoo sending domain. **If it fails.** - **Test email not received.** Check spam folder. Verify the email address is correct. Check that Vatoo's sending domain is not blocked. - **No lead notifications despite leads in dashboard.** Ensure "Notify on New Lead" is toggled on and saved. - **Emails going to spam.** Ask your IT team to whitelist the Vatoo sending domain or add an SPF/DKIM entry. ### Freshdesk Integration - [Freshdesk Chatbot Integration for Support Tickets](https://vatoo.ai/integrations/erp_freshdesk): Connect Vatoo to Freshdesk and turn customer chats into support tickets with context. Review credentials, ticket setup, and troubleshooting. Turn a support conversation into a Freshdesk ticket with useful context. Configure which records the assistant can read or update and how unresolved requests reach your support team. Setup guide level: Easy. Typical time: 5–10 minutes. The linked page has the click-by-click steps. **Before you start.** - Freshdesk account (free tier available) - Vatoo botmaster account with active bot - Freshdesk API Key (Profile Settings → View API Key) **Setup outline.** 1. **Find Your Freshdesk API Key.** The API key is unique per agent. Use an admin account's key for full access. 2. **Find Your Freshdesk Subdomain.** 3. **Connect Freshdesk in Vatoo Botmaster.** The integration name is just a friendly label. You can name it anything. 4. **Test the Connection.** 5. **Enable Components and Configure Write Permissions.** Enable write access only for operations you want the bot to perform automatically. Start with read-only. 6. **Test with Your Bot.** **If it fails.** - **401 Unauthorized · test connection fails.** API key is wrong or was not copied fully. Re-copy from Freshdesk Profile Settings → Your API Key. Also confirm the subdomain is correct (no https://, no trailing slash). - **Subdomain not found / DNS error.** Make sure you entered just the subdomain part (e.g. "acme" not "acme.freshdesk.com"). If you're on an EU data centre your subdomain may differ · check your login URL carefully. - **Ticket search returns no results.** Freshdesk search requires at least one filter. Try adding a status or date range. Full-text search indexes ticket subjects and descriptions · ensure the query word appears in ticket content. - **Create ticket fails with 422.** Subject and requester email are required to create a ticket. Ensure the bot passes both params. The email must be a valid address. - **Reply fails with 403.** The API key owner may not have permission to reply on tickets. Use an admin account's API key, or check agent permissions in Freshdesk Admin → Roles. ### HubSpot Integration - [HubSpot Chatbot Integration for Lead Capture](https://vatoo.ai/integrations/erp_hubspot): Connect Vatoo to HubSpot to capture enquiries and update customer records from chat. Review account permissions, field mapping, and setup steps. Capture enquiries and connect customer conversations to HubSpot records. Choose which contacts, companies, deals, or tickets your assistant can access, then test the permitted operations. Setup guide level: Easy. Typical time: 5–10 minutes. The linked page has the click-by-click steps. **Before you start.** - HubSpot account (any tier · CRM is free) - HubSpot admin access or ability to create Private Apps - Vatoo botmaster account with active bot **Setup outline.** 1. **Open Private Apps in HubSpot.** Private Apps are the recommended authentication method for server-to-server integrations in HubSpot · no OAuth redirect required. 2. **Create a New Private App.** 3. **Add the Required Scopes.** You can edit scopes later by returning to the Private App and clicking "Edit scopes", but you must re-copy the token after saving. 4. **Create the App and Copy the Access Token.** If you lose the token you can regenerate it from the Private App detail page · but all existing copies will be invalidated. 5. **Connect HubSpot in Vatoo Botmaster.** The integration name is just a friendly label shown in the dashboard. You can name it anything. 6. **Test the Connection.** 7. **Enable Components and Configure Write Permissions.** Start with read-only operations first. Enable write access only for operations you are confident the bot should perform automatically. **If it fails.** - **"401 Unauthorized" error.** The access token is invalid or has expired. Go to HubSpot → Settings → Private Apps, open your app, and regenerate the token. Paste the new token into Vatoo. - **"403 Forbidden" error.** The Private App is missing a required scope. Return to HubSpot → Settings → Private Apps → your app → Scopes, add the missing scope, save, and re-copy the token into Vatoo. - **Contact search returns empty results.** HubSpot full-text search requires exact word tokens. Try a broader or more specific query. Searching by email address is the most reliable way to find a specific contact. - **Marketing endpoint returns an error.** Marketing Email access requires Marketing Hub (Starter or higher). This endpoint is not available on the free CRM plan. - **Deal stage not found.** Stage IDs must match HubSpot's internal identifiers. Ask the bot to "get pipeline stages" first to see the valid stage IDs for your pipelines. - **Write operations fail.** Ensure the relevant write scopes were added to your Private App and that the "Allow Write" toggle is enabled for the specific operation in Vatoo's Components page. ### Odoo ERP Integration - [Odoo AI Chatbot Integration](https://vatoo.ai/integrations/erp_odoo): Connect Vatoo to Odoo to look up business records and run configured tasks from chat. Review API access, permissions, and the setup checklist. Help your team look up business information and complete configured tasks in Odoo. Start with one module and a limited set of operations, then test the workflow before expanding access. Setup guide level: Easy. Typical time: 10–15 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot configured and active - Odoo instance (cloud or self-hosted) · version 14 or higher - Odoo user account with access to the modules you want to connect - API Key generation rights (Settings → Technical · requires developer mode) **Setup outline.** 1. **Enable Developer Mode in Odoo.** Developer mode is required to access the API Keys menu. You can disable it again after generating the key. 2. **Generate an API Key.** If you cannot find API Keys in the menu, ensure developer mode is active. In Odoo 16+ go to Settings → Users & Companies → API Keys. 3. **Find Your Database Name.** 4. **Connect Odoo in Vatoo Botmaster.** • Odoo URL · full URL including https:// (e.g. https://mycompany.odoo.com) • Database Name · as found in step 3 • Username / Email · your Odoo login email • API Key · the key generated in step 2 The integration name is just a friendly label shown in the dashboard. You can name it anything. 5. **Test the Connection.** 6. **Enable Components.** Start with read-only operations first. Enable write access only for operations you are confident the bot should perform automatically. 7. **Test with Your Bot.** Each Odoo call is logged under ERP Integrations → operation logs so you can audit every query. **If it fails.** - **Test connection fails: "Authentication failed".** Check that the API key is correct and was not accidentally truncated. Re-generate a new key if unsure. Confirm the username/email matches the Odoo account. - **Test connection fails: "Connection refused" or timeout.** Your Odoo URL is unreachable. Check the URL includes https://, no trailing slash issues, and that the server is accessible from the internet (for cloud) or your network (for self-hosted). - **Database not found error.** The database name is case-sensitive and must match exactly. For Odoo.com, the database name is usually the subdomain portion only (not the full domain). - **Bot says "ERP component is not enabled".** Go to ERP Integrations → Components and toggle on the component the user is asking about. - **Bot won't create leads / write operations not working.** Write operations require the "Write Allowed" toggle to be enabled per operation in the Components page. Check the toggle for the specific operation (e.g. create\_lead). - **Access error on specific Odoo models.** The Odoo user account linked to the API key may lack access to certain modules. In Odoo go to Settings → Users and check the user's access rights for the relevant module. ### SAP Business One Integration - [SAP Business One AI Chatbot Integration](https://vatoo.ai/integrations/erp_sap): Connect Vatoo to SAP Business One through the Service Layer. Review access requirements, configured actions, and troubleshooting before launch. Connect your assistant to SAP Business One through the Service Layer. Define the data and operations needed for a specific workflow, such as looking up a record or collecting a request. Setup guide level: Intermediate. Typical time: 10–15 minutes. The linked page has the click-by-click steps. **Before you start.** - SAP Business One 9.0 or later (Service Layer must be installed and running) - Service Layer port accessible from Vatoo server (default 50000/50001) - A SAP B1 user account with API access (not Windows/domain login) - Company database name (shown in SAP → Administration → Choose Company) - Vatoo Botmaster account with active bot **Setup outline.** 1. **Verify Service Layer Is Running.** Service Layer is installed with SAP Business One Server Tools. If missing, re-run the SAP B1 installer and check the Service Layer component. 2. **Gather Your Connection Details.** 3. **Connect in Vatoo Botmaster.** If the test fails with a connection error, check that the port is open and the hostname resolves from Vatoo's server, not just locally. 4. **Enable Components.** Start with read-only access. Enable write operations (create order, create invoice) only after testing read operations work correctly. 5. **Test With Your Bot.** **If it fails.** - **Connection test fails with "Authentication failed"..** Double-check Company Database name · it is case-sensitive and must match exactly. Verify the SAP username and password are for a SAP B1 user (not a Windows/AD login). Confirm the user is not locked out in SAP → Administration → Setup → General → Users. - **Cannot connect to host · connection refused or timeout..** Confirm Service Layer is running on the SAP server (check Windows Services). Verify the port number · HTTP default is 50000, HTTPS is 50001. Check firewall rules on the SAP server allow the port inbound from your Vatoo server. Test connectivity: curl http://:50000/b1s/v1/$metadata - **SSL certificate error..** Most on-premise SAP servers use self-signed certificates. Set Verify SSL to false in the connection config. Alternatively, install a proper SSL certificate on the SAP server and set it to true. - **Bot returns "No items found" or empty results..** Check the component is enabled in Manage Components. Verify the SAP user has read access to that data in SAP → Administration → Setup → General → Users → Authorizations. Check Operation Logs to see the exact OData query sent and any SAP error returned. - **Write operation fails with SAP error..** SAP Business One enforces mandatory fields · for example, Sales Orders require a valid CardCode and at least one DocumentLine. Check the Operation Log for the specific SAP error message. Ensure the SAP user has the appropriate write permissions in SAP User Authorizations. - **Service Layer returns 400 on OData filter queries..** SAP Service Layer uses strict OData syntax. String values in filters must be single-quoted. Date fields use format YYYY-MM-DD. Check Operation Logs to see the exact filter sent · report the error to Vatoo support if the query looks malformed. ### Zendesk Integration - [Zendesk Chatbot Integration for Ticket Handoff](https://vatoo.ai/integrations/erp_zendesk): Connect Vatoo to Zendesk to create support tickets from customer conversations. Follow the guide to API access, ticket routing, and troubleshooting. Connect customer questions to Zendesk ticket workflows. Configure the records your assistant can access and test ticket creation, updates, and escalation with your support team. Setup guide level: Easy. Typical time: 5–10 minutes. The linked page has the click-by-click steps. **Before you start.** - Zendesk account (Support plan required for API access) - Vatoo botmaster account with active bot - Zendesk admin access to generate an API token **Setup outline.** 1. **Enable API Access and Generate a Token.** API token access is per-agent. The token is associated with the email you use in the next step. 2. **Find Your Zendesk Subdomain.** 3. **Connect Zendesk in Vatoo Botmaster.** The integration name is just a friendly label. You can name it anything. 4. **Test the Connection.** 5. **Enable Components and Configure Write Permissions.** Start with read-only. Enable write access only for operations you are confident should be automated. 6. **Test with Your Bot.** **If it fails.** - **401 Unauthorized · test connection fails.** The agent email and API token combination is wrong. Re-generate the token in Admin Center → Apps and integrations → APIs → Zendesk API. Ensure the email matches the account that owns the token. - **Subdomain not found.** Enter just the subdomain (e.g. "acme" not "acme.zendesk.com"). EU-hosted accounts may use a different TLD · check your actual login URL. - **Search returns empty results.** Zendesk search uses a query language. At minimum provide "type:ticket" which Vatoo adds automatically. Add a status or keyword to narrow results. - **Create ticket fails · 422 Unprocessable Entity.** Subject is required. If providing a requester, the email must be valid. For internal-only tickets you can omit the requester but a comment body is still recommended. - **Reply operation fails with 403.** The agent associated with the API token may lack permission to update certain tickets. Check the agent's role in Admin Center → People → Team members. - **Cannot find Zendesk API option in Admin Center.** API token access requires a Zendesk Support plan. The feature is not available on the free trial. Upgrade to at least a Team plan to unlock API tokens. ### Instagram DM Integration - [Instagram DM AI Chatbot Integration](https://vatoo.ai/integrations/instagram): Connect Vatoo to Instagram Direct Messages to help customers in chat. Review Meta account requirements, webhook setup, and approval dependencies. Help customers who contact your business through Instagram Direct Messages. Connect your account, configure the approved answers, and test the handoff before enabling automated replies. Setup guide level: Medium. Typical time: 20–30 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot configured - Instagram Business or Creator account - Facebook Page linked to your Instagram account - Meta Developer account (free) **Setup outline.** 1. **Create a Meta Developer App.** 2. **Add Instagram Product.** 3. **Generate a Page Access Token.** For production use a System User token · it does not expire. 4. **Get App Secret.** 5. **Configure in Vatoo Botmaster.** Remember your Verify Token · you need it in the next step. 6. **Subscribe to Webhooks.** 7. **Test the Integration.** **If it fails.** - **Webhook verification fails.** Verify Token mismatch · make sure you pasted the same token in both Vatoo and Meta. - **No reply to DMs.** Check messages subscription is checked in the webhook settings. - **Token expired.** Short-lived tokens expire in 1 hour. Use a long-lived or System User token. - **403 on webhook POST.** App Secret wrong · re-copy from Settings → Basic. ### LINE Integration - [LINE AI Chatbot Integration](https://vatoo.ai/integrations/line): Connect Vatoo to LINE and make your AI assistant available in customer conversations. Follow the guide to channel access, webhooks, and testing. Bring your assistant to customer conversations on LINE. Connect the messaging channel and test answers, follow-up messages, and provider requirements for your account. Setup guide level: Easy. Typical time: 10–15 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot configured - LINE account - LINE Developers account (free at developers.line.biz) **Setup outline.** 1. **Create a LINE Developers Account and Provider.** 2. **Create a Messaging API Channel.** 3. **Get Channel Credentials.** 4. **Configure in Vatoo Botmaster.** 5. **Set Webhook URL in LINE.** 6. **Disable Auto-Reply (Optional but Recommended).** Disabling auto-reply ensures only Vatoo responds to messages. 7. **Test the Integration.** **If it fails.** - **Webhook verify fails.** Server not reachable via HTTPS. Use ngrok for local dev. - **403 on webhook POST.** Channel Secret wrong · re-copy from Basic settings. - **Bot and LINE both reply.** Disable Auto-reply messages in LINE Official Account features. - **Reply after 30s uses push · fails on free plan.** Upgrade to a paid LINE plan for push messages, or optimize AI response time. ### Live Support Integration - [AI Chatbot Human Handoff & Live Support](https://vatoo.ai/integrations/live_support): Give customers a route from Vatoo AI chat to your support team. Configure human handoff and test how conversation context reaches an available agent. Give customers a clear route to a person when automation is not enough. Set escalation triggers, assign your support team, and preserve the conversation history so customers do not have to start again. Setup guide level: Easy. Typical time: 5 minutes. The linked page has the click-by-click steps. **Before you start.** - Active Vatoo bot with at least one conversation - At least one staff member to handle escalations (or you as owner) - Live Support enabled in configuration (disabled by default) **Setup outline.** 1. **Enable Live Support.** Live Support is off by default · no escalations fire until you explicitly enable it. 2. **Set Escalation Triggers.** Start with 3–5 clear phrases. Too many keywords can cause false triggers. 3. **Customise User-Facing Messages.** 4. **Invite Support Staff.** Staff accounts have restricted access · they only see the Live Support queue and their own handled chats. 5. **Handling an Escalation (Staff Flow).** 6. **(Optional) Configure Working Hours.** If working hours are not configured, escalations always trigger regardless of time. **If it fails.** - **Escalation does not fire when user types the keyword..** Check that Live Support is enabled in Configuration. Also verify the keyword list is saved · go back to Configuration and confirm the keywords appear. Keyword matching is case-insensitive and checks if the phrase appears anywhere in the message. - **User messages during escalation are not visible in the agent chat..** The agent detail page polls for new messages every 2 seconds automatically. If messages are missing, try refreshing the page. Ensure the escalation is in Pending or Claimed status · resolved or dismissed escalations stop buffering new messages. - **Agent replies are not appearing in the user's chat widget..** The widget polls /api/escalation-poll// every 2 seconds when escalated. Check browser console for network errors. Ensure the widget is the Vatoo embed and has not been cached · clear widget JS cache or hard refresh the page. - **Staff invite email was not received..** Check spam/junk folder. Verify DEFAULT_FROM_EMAIL and email backend are configured in Django settings. You can also copy the invite token link from the Pending Invites table and share it manually. - **After resolving, the bot does not resume responding..** Resolving or handing back to the bot clears the is_escalated flag on the session. If the bot still does not respond, confirm the session's active_escalation was cleared · check in Django admin under ChatbotSession for the session ID. A page refresh on the user's widget will also re-sync state. - **Staff member cannot log in after accepting invite..** Ensure the invite was not already used (is_accepted = True) or expired. The login page is at /botmaster/login/. Staff use their email address as username. If login still fails, an owner can reset their password via Django admin. ### Mattermost Integration - [Mattermost AI Chatbot Integration](https://vatoo.ai/integrations/mattermost): Connect Vatoo to Mattermost so teams can ask questions about approved business content. Review bot credentials, permissions, and connection steps. Make business knowledge available inside your Mattermost workspace. Connect your server and configure where the assistant can receive questions and post replies. Setup guide level: Medium. Typical time: 10–20 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot configured - Mattermost server with System Admin access - Mattermost version 5.0 or higher **Setup outline.** 1. **Enable Bot Accounts.** 2. **Create a Bot Account.** Note down the bot username · you need it to prevent reply loops. 3. **Configure in Vatoo Botmaster.** 4. **Create an Outgoing Webhook.** Content Type must be form-encoded, not JSON. 5. **Add Webhook Token to Vatoo.** 6. **Add Bot to Channel and Test.** **If it fails.** - **No reply at all.** Check outgoing webhook URL is correct and server is reachable. - **Token mismatch in logs.** Webhook token doesn't match · re-copy from outgoing webhook settings. - **Bot replies to itself.** Bot Username field not set in Vatoo config. - **channel\_id missing.** Content Type must be application/x-www-form-urlencoded, not JSON. ### Microsoft Teams Integration - [Microsoft Teams AI Chatbot Integration](https://vatoo.ai/integrations/msteams): Connect Vatoo to Microsoft Teams to help employees find approved answers. Review app setup, permissions, and deployment requirements in the guide. Help employees find approved answers in Microsoft Teams. Set up your bot registration and permissions, then test direct messages and channel mentions with your team. Setup guide level: Medium. Typical time: 25–35 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot already created and configured - Microsoft Azure account, free tier is sufficient for bot registration (no paid plan required) - Microsoft Teams access, Microsoft 365 subscription OR Teams Free. For org-wide deployment (bot searchable by all employees) a Microsoft 365 Business/Enterprise plan with Teams Admin Center access is required - Public HTTPS webhook URL, Azure cannot reach localhost. Use your production domain or a tunnel like ngrok (ngrok http 8000) for development - Stable internet connection during setup, Azure validates the messaging endpoint in real time **Setup outline.** 1. **Create an Azure Bot Registration.** The bot handle is just an Azure resource name, the display name shown to Teams users is set later in the Teams app manifest. 2. **Get your App ID and create a Client Secret.** Critical: copy the secret Value (looks like _xK9Q~abc...), not the Secret ID (which is a GUID). Pasting the Secret ID causes a 400 error when fetching tokens. 3. **Configure in Vatoo Botmaster.** The App ID you paste here must exactly match what Azure uses in its JWT tokens. If you get 401 errors, verify the App ID by checking Azure → App Registrations → your app → Overview → Application (client) ID. 4. **Set the Messaging Endpoint in Azure.** For local development: run ngrok http 8000, use the https://xxxx.ngrok-free.app URL as the endpoint. Restart ngrok = new URL = update Azure endpoint again. 5. **Enable the Microsoft Teams Channel.** 6. **Test in Azure Web Chat first.** Always verify in Azure Web Chat before testing in the Teams app. It isolates auth problems from Teams deployment problems. 7. **Add the Bot to Microsoft Teams.** Teams Free users can sideload apps. Microsoft 365 is required to publish to the org catalog so all employees can discover the bot via search. **If it fails.** - **401 Unauthorized in webhook logs.** Almost always an App ID mismatch. The App ID in Vatoo must match exactly what Azure sends in the JWT aud claim. Verify: Azure Portal → App Registrations → your app → Overview → Application (client) ID. Update Vatoo config if different. - **400 Bad Request when fetching access token.** Client Secret is wrong. You likely saved the Secret ID (a GUID) instead of the secret Value. Go to App Registrations → Certificates & secrets → create a new secret → copy the Value column. - **Webhook returns 200 but no reply appears in Teams / Web Chat.** Check server logs for [MSTeams] send_message HTTP 4xx. Common cause: Activity.From field missing or service\_url not captured correctly. Ensure Vatoo is up to date. - **Bot not appearing in Teams search.** Bots must be published to the org app catalog or sideloaded before they appear in search. Simply registering in Azure is not enough. Use Teams Admin Center to publish, or sideload a manifest .zip for testing. - **Azure Web Chat works but Teams gives no response.** Confirm Microsoft Teams channel is enabled in Azure → Channels → Teams → status Running. Also confirm the Messaging Endpoint URL in Azure Configuration is the current public URL (ngrok URLs change each restart). - **ngrok URL not accepted by Azure (CSRF / SSL error).** Ensure your Django settings include CSRF_TRUSTED_ORIGINS = ['https://*.ngrok-free.app']. Azure must reach your server via HTTPS, HTTP-only URLs are rejected. ### Slack Integration - [Slack AI Chatbot Integration](https://vatoo.ai/integrations/slack): Connect Vatoo to Slack to answer team questions from approved content. Review bot permissions, event subscriptions, and workspace setup steps. Answer team questions where work is already happening. Connect Vatoo to Slack and test which conversations, content, and workflows your assistant should handle. Setup guide level: Easy. Typical time: 10–15 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot configured and active - Slack workspace where you have Admin or Owner access **Setup outline.** 1. **Create a Slack App.** 2. **Add Bot Permissions.** 3. **Install the App to Your Workspace.** 4. **Get Your Signing Secret.** 5. **Configure in Vatoo Botmaster.** Keep the Webhook URL. You will paste it in the next step. 6. **Enable Event Subscriptions.** 7. **Invite the Bot to a Channel.** For DMs just open a direct message with the bot. No invite needed. **If it fails.** - **URL not verified (red ✗).** Your server is not publicly reachable. Use ngrok for local dev. - **Bot does not reply.** Check the Slack card shows Active in Vatoo Omnichannel. - **not\_in\_channel error.** Invite the bot to the channel first with /invite. - **invalid\_auth error.** Token copied incorrectly. Regenerate from OAuth & Permissions. ### Telegram Integration - [Telegram AI Chatbot Integration](https://vatoo.ai/integrations/telegram): Connect your Vatoo AI assistant to Telegram. Follow the guide to bot credentials, webhook configuration, and testing customer conversations. Make your assistant available through Telegram. Connect your bot, test how messages are received, and decide which customer questions it should answer or pass to your team. Setup guide level: Easy. Typical time: 5–10 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot configured - A Telegram account **Setup outline.** 1. **Create a Bot via BotFather.** 2. **Configure in Vatoo Botmaster.** Setting a secret token protects your webhook from fake requests. Use a strong random string. 3. **Verify Webhook Registration.** 4. **Test the Integration.** 5. **Optional: Configure Bot via BotFather.** **If it fails.** - **Webhook not registered.** Server must be publicly reachable via HTTPS. Use ngrok for local dev. - **403 in logs.** Secret token mismatch · re-save config to re-register webhook. - **Bot does not reply in groups.** Go to BotFather → /mybots → Bot Settings → Group Privacy → Turn off. - **last\_error\_message in getWebhookInfo.** Usually SSL certificate issue · must use a valid HTTPS cert. ### Web Widget Integration - [Add an AI Chatbot to Your Website](https://vatoo.ai/integrations/web_widget): Add a branded Vatoo AI chatbot to your website with an embed snippet. Configure its appearance and test the widget on desktop and mobile. Add a branded AI assistant to your website with the Vatoo embed. Configure its content and appearance, test answers and handoffs, then publish it through your website platform. Setup guide level: Easy. Typical time: 2–5 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot configured and active - Access to your website's HTML (or theme settings for CMS platforms) **Setup outline.** 1. **Get Your Widget Embed Code.** Each bot has its own unique snippet. Make sure you copy from the correct bot if you have multiple. 2. **Paste the Snippet into Your Website.** Place the snippet near the end of the page, then test that it loads correctly with your site’s consent and script settings. 3. **WordPress or Shopify (CMS).** 4. **Verify the Widget Loads.** 5. **Customize Appearance (Optional).** You can also restrict which domains the widget loads on from Security → Allowed Origins. **If it fails.** - **Widget does not appear.** Check the snippet is pasted before . Open browser DevTools → Console for JS errors. - **Bot replies with an error.** Ensure the bot is active and at least one knowledge source is connected. - **Widget blocked by CSP.** Add your Vatoo domain to your Content-Security-Policy header: script-src and connect-src. - **Widget shows on staging, not production.** Check Allowed Origins in Security settings · add your production domain. ### WhatsApp (Meta Cloud API) Integration - [WhatsApp Cloud API Chatbot Integration](https://vatoo.ai/integrations/whatsapp_cloud): Connect Vatoo to WhatsApp through Meta’s Business Cloud API. Review account requirements, webhook setup, verification, and testing steps. Answer customer questions through the WhatsApp Business Cloud API. Connect your approved business account and test messaging permissions, templates, and the customer handoff before launch. Setup guide level: Medium. Typical time: 20–30 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot configured - Meta Business Account (verified) - Meta Developer account - A phone number to register for WhatsApp Business **Setup outline.** 1. **Create a Meta Developer App.** 2. **Set Up WhatsApp Business Account.** 3. **Generate a Permanent Access Token.** System User tokens do not expire unlike regular user tokens. 4. **Get App Secret.** 5. **Configure in Vatoo Botmaster.** 6. **Configure Webhook in Meta.** 7. **Test the Integration.** During development, only numbers added as testers in Meta can message your bot. **If it fails.** - **Webhook verification fails.** Verify Token mismatch · paste the exact same token in both places. - **No reply.** Check messages is subscribed in webhook fields. Check phone number is verified. - **Token expired error.** Use a System User token · regular user tokens expire. - **Message not delivered.** Outside of 24h window · you need a pre-approved message template. ### WhatsApp (Twilio) Integration - [Twilio WhatsApp AI Chatbot Integration](https://vatoo.ai/integrations/whatsapp): Connect Vatoo to WhatsApp through Twilio. Review sender requirements, webhook setup, and sandbox testing before enabling customer conversations. Connect Vatoo to WhatsApp through Twilio. Use a test environment to review the conversation, then confirm your production sender, provider charges, and messaging requirements. Setup guide level: Medium. Typical time: 15–20 minutes. The linked page has the click-by-click steps. **Before you start.** - Vatoo botmaster account with a bot configured - Twilio account (free tier works for sandbox testing) **Setup outline.** 1. **Create a Twilio Account.** 2. **Activate the WhatsApp Sandbox.** Each tester must join the sandbox individually using the join code. 3. **Configure in Vatoo Botmaster.** 4. **Set Webhook in Twilio.** 5. **Test the Integration.** 6. **Go Production (Optional).** Meta approval can take 1–7 business days. **If it fails.** - **No reply at all.** Check webhook URL is saved in Twilio sandbox settings. - **403 in logs.** Auth Token wrong · re-copy from Twilio dashboard. - **Signature fails on ngrok.** ngrok URL changes each restart · update Twilio webhook URL. - **"This number is not in sandbox".** Phone did not join · send the join code again. ## Comparisons These are buyer checklists published by Vatoo, not independent benchmarks. Pricing and product scope change; confirm the current offer on the vendor page linked from each guide. Do not treat a competitor as a simple FAQ bot. Compare the workflow, usage allowances, human handoff, and maintenance for the plan you would actually buy. ### Vatoo vs Botpress - [Vatoo vs Botpress](https://vatoo.ai/alternatives/botpress): Compare Vatoo and Botpress for AI chatbot workflows, connected actions, usage costs, and maintenance. Use a practical checklist to test both platforms. **Focus.** Agent building and deployment. Botpress positions itself around AI customer support and connected actions. Its pricing includes conversation allowances and AI usage provisions. Compare the selected plan, additional usage, human support workflow, and maintenance requirements. Vendor page reviewed for this guide: https://botpress.com/pricing **Question to settle.** How do conversation packs, AI credits, and workspace permissions affect your expected monthly cost? **Trial task.** Build one branched workflow, trigger a connected action, and test what happens when the action fails. ### Vatoo vs Botsonic - [Vatoo vs Botsonic](https://vatoo.ai/alternatives/botsonic): Compare Vatoo and Botsonic for knowledge-based AI chatbots. Check content limits, agent actions, branding, and setup against your customer workflow. **Focus.** Knowledge-based AI agents. Botsonic offers tiered AI chatbot and agent plans. Evaluate source limits, agent capabilities, branding, and the support available for your deployment. Vendor page reviewed for this guide: https://botsonic.com/pricing **Question to settle.** Which knowledge, integration, and branding capabilities are included in the tier you would actually buy? **Trial task.** Import a representative document set and test accurate answers, missing information, and updates to a source. ### Vatoo vs Chatbase - [Vatoo vs Chatbase](https://vatoo.ai/alternatives/chatbase): Compare Vatoo and Chatbase for AI support and lead capture. Evaluate knowledge, actions, message allowances, and integrations with the same trial tasks. **Focus.** AI agents trained on business content. Chatbase offers customer-facing agents for support, sales, and product guidance. Compare message credits, actions, channels, and helpdesk capabilities in the plan you would buy. Vendor page reviewed for this guide: https://www.chatbase.co/pricing **Question to settle.** How do message credits, agent limits, actions, and optional add-ons fit your forecast? **Trial task.** Ask a source-based question, qualify a lead, and check whether the complete context reaches your chosen system. ### Vatoo vs ChatBot.com - [Vatoo vs ChatBot.com](https://vatoo.ai/alternatives/chatbot-com): Compare Vatoo and ChatBot.com for customer-service automation. Review workflow design, usage allowances, connected tools, and the handoff to your team. **Focus.** Customer-service chatbot workflows. ChatBot.com offers chatbot plans with defined feature and usage allowances. Evaluate the complete support journey, including the tools your human team already uses. Vendor page reviewed for this guide: https://www.chatbot.com/pricing/ **Question to settle.** What is included for your traffic level, and how does the bot hand a conversation to a person? **Trial task.** Run the same support request through a normal answer, a follow-up question, and a human handoff. ### Vatoo vs Crisp - [Vatoo vs Crisp](https://vatoo.ai/alternatives/crisp): Compare Vatoo and Crisp for customer messaging and AI support. Test lead capture, inbox handoff, team access, and the total cost of your chosen setup. **Focus.** Customer messaging and team inbox. Crisp publishes workspace plans covering customer messaging and support capabilities. Consider the needs of the people answering messages alongside the automation itself. Vendor page reviewed for this guide: https://crisp.chat/en/pricing/ **Question to settle.** Which inbox, automation, AI, and team capabilities are available in your chosen workspace plan? **Trial task.** Have a bot collect context and then ask a teammate to continue the conversation without repeating questions. ### Vatoo vs Drift - [Vatoo vs Drift](https://vatoo.ai/alternatives/drift): Compare Vatoo with Drift’s current Salesloft Chat Agents offering. Evaluate lead qualification, meeting booking, CRM handoff, and implementation needs. **Focus.** B2B sales conversations. Salesloft now presents its chat offering as Chat Agents. Use the current product page to evaluate fit for your sales process rather than relying on an older Drift feature list. Vendor page reviewed for this guide: https://www.salesloft.com/platform/chat-agents **Question to settle.** How does the current chat offering fit your qualification, meeting-booking, and sales ownership process? **Trial task.** Qualify an inbound enquiry, assign the right owner, and confirm the booking and CRM record. ### Vatoo vs Intercom - [Vatoo vs Intercom](https://vatoo.ai/alternatives/intercom): Compare Vatoo and Intercom for AI customer support. Evaluate Fin, helpdesk seats, usage costs, connected actions, and human handoff in your workflow. **Focus.** Customer service and AI support. Intercom combines a human support workspace with Fin AI. Evaluate helpdesk seats, AI outcomes, channels, and connected workflows together, especially if your team already works in its inbox. Vendor page reviewed for this guide: https://www.intercom.com/pricing **Question to settle.** What is the combined cost of the seats, AI usage, and channels your support operation needs? **Trial task.** Test a question that is answered, one that needs an action, and one that must reach a human agent. ### Vatoo vs Tidio - [Vatoo vs Tidio](https://vatoo.ai/alternatives/tidio): Compare Vatoo and Tidio for live chat, AI support, and lead capture. Check conversation allowances, workflows, handoff, and your projected monthly cost. **Focus.** Live chat and AI customer service. Tidio publishes plans for its customer-service offering. Match the live-chat and AI capabilities to your customer volume and the work you expect to automate. Vendor page reviewed for this guide: https://www.tidio.com/pricing/ **Question to settle.** Which allowances apply to human conversations, AI conversations, and automation in your selected plan? **Trial task.** Ask a product question, collect an enquiry, and hand over an unresolved conversation with its history. ### Vatoo vs Yellow.ai - [Vatoo vs Yellow.ai](https://vatoo.ai/alternatives/yellow-ai): Compare Vatoo and Yellow.ai for conversational automation. Review channels, implementation scope, integrations, and ongoing support before choosing. **Focus.** Enterprise conversational automation. Yellow.ai provides pricing information and a sales-led evaluation route. For an enterprise shortlist, compare implementation scope, channels, and operating requirements explicitly. Vendor page reviewed for this guide: https://yellow.ai/pricing/ **Question to settle.** What does the proposal include for implementation, channels, integrations, support, and ongoing usage? **Trial task.** Review one end-to-end workflow with the people responsible for security, integration, and day-to-day operations. ### Vatoo vs Zendesk - [Vatoo vs Zendesk](https://vatoo.ai/alternatives/zendesk): Compare Vatoo and Zendesk for AI support and ticket workflows. Evaluate agent seats, automation costs, escalation context, and day-to-day ownership. **Focus.** Helpdesk operations and AI service. Zendesk publishes support and service plans. If your team relies on ticket operations, assess how AI automation fits that workspace and its reporting requirements. Vendor page reviewed for this guide: https://www.zendesk.com/pricing/ **Question to settle.** Which agent seats, AI features, usage allowances, and add-ons are needed for your existing support process? **Trial task.** Resolve a routine request, escalate an exception, and inspect the resulting ticket, ownership, and reporting. ## Guides Practical buying and setup guides. They explain how to evaluate a workflow. They do not claim measured conversion gains or certification. ### Insurance chatbots: a practical guide to enquiries and intake - [Insurance Chatbots: Enquiries & Claims Intake](https://vatoo.ai/blogs/best-ai-chatbot-for-insurance): Evaluate insurance chatbots for approved policy answers, quote requests, claims intake, and escalation to your team. Industries · Vatoo Editorial · Published February 11, 2026 · Updated November 6, 2026. A useful insurance chatbot helps someone understand the next step and provide the information your team needs. Start with a bounded task such as collecting a quote request or directing a policy question. Keep coverage decisions and claims decisions with the authorised process. **Choose one task before choosing a platform** Separate general product questions, quote intake, and claims intake. Each needs different content, fields, and handoff rules. Define whether the assistant is collecting a request or completing an action through an authorised system. Make that distinction clear in the customer’s confirmation. **Ground answers in the right document** Provide current, approved product information and identify the applicable version. Test similar product names, missing details, and questions that depend on a customer’s own policy. A general knowledge answer should not be presented as a decision about an individual customer’s cover. **Design quote intake around the follow-up** - Ask only for information needed at this stage. - Explain what happens after the request is submitted. - Check required fields and contact details. - Route the request to a defined owner with conversation context. - Test missing information and a failed delivery to the receiving system. **Make claims intake clear** A customer reporting a problem should know whether the assistant has recorded a request or created a claim in the connected system. Use confirmation identifiers only when returned by that system. Provide a route to staff for complex or unsupported situations and make the next step explicit. **Evaluate the workflow, not a promised conversion rate** | Area | Evidence to collect | | --- | --- | | Answer quality | Responses match approved source material. | | Data quality | Required fields reach the receiving team correctly. | | Customer clarity | Confirmation explains the request status and next step. | | Escalation | Staff receive the transcript and relevant details. | | Operations | An owner can update content and review failures. | **Testing Vatoo** Use an AI Agent for approved knowledge answers, Smart Forms for structured intake, and flows for configured routing. Begin with sample data and check the integration and plan requirements. Review data handling with your organisation before putting sensitive customer information into the workflow. **Continue your evaluation** - [Explore Smart Forms](https://vatoo.ai/smart-form-engine) - [Review security information](https://vatoo.ai/security) - [Insurance workflow overview](https://vatoo.ai/industries/insurance) This is a workflow evaluation guide. It does not claim measured conversion gains, regulatory certification, or automated insurance decisions. **Questions this guide answers.** - **Can a chatbot confirm cover from general product information?** A general product answer is not a decision about an individual policy. Route policy-specific questions through the authorised process. - **What should a first pilot measure?** Supported answers, complete intake, successful delivery, and clear escalation to the responsible team. **Related guides.** - [Real estate chatbots: qualify enquiries and guide viewing requests](https://vatoo.ai/blogs/best-ai-chatbot-for-real-estate) - [Hindi and Hinglish chatbots: design for real customer questions](https://vatoo.ai/blogs/hindi-first-ai-chatbots) - [AI chatbot pricing in 2026: how to compare total cost](https://vatoo.ai/blogs/what-ai-chatbots-really-cost-2026) ### Real estate chatbots: qualify enquiries and guide viewing requests - [Real Estate Chatbots: Leads & Viewing Requests](https://vatoo.ai/blogs/best-ai-chatbot-for-real-estate): Plan a property chatbot that answers listing questions, collects buyer requirements, and passes useful viewing requests to agents. Industries · Vatoo Editorial · Published February 4, 2026 · Updated November 6, 2026. Property visitors often need a specific answer before they will enquire: availability, price, location, or viewing options. A chatbot can make that next step easier when its information is current and the request reaches the right agent. **Keep property information current** Decide where listing facts come from and who maintains them. If the assistant reads a document, establish how it is updated. If it checks a live property system, test missing records and unavailable connections. Do not let an old listing become a promise of availability. **Qualify for a useful follow-up** Choose the few details an agent needs to respond: the property or area, the type of enquiry, preferred timing, and a contact method. Explain why those details help. Avoid collecting extra personal information just because a form can hold it. **Separate a viewing request from a confirmed appointment** If there is no live calendar connection, collect preferred times and say that an agent will confirm. With a connected calendar, check that the slot was actually reserved before showing a booking confirmation. Test conflicts, cancellations, and requests outside working hours. **A representative pilot** - Ask about a current listing and compare the answer with the source. - Ask about a listing that has been withdrawn. - Submit a viewing request with incomplete contact details. - Simulate an unavailable calendar or CRM. - Ask to speak with an agent and inspect the handoff. **Compare results your team can use** | Measure | What to look for | | --- | --- | | Answer quality | Current facts without invented availability. | | Enquiry quality | Enough information for a relevant follow-up. | | Booking accuracy | Requested and confirmed times clearly distinguished. | | Routing | Correct agent receives the details. | | Maintenance | A clear owner can update sources and fix gaps. | **How Vatoo can support the workflow** Use approved listing content for answers and Smart Forms for structured enquiries. Add a flow when the journey needs multiple steps or connected actions. Confirm the required integration, access permissions, and plan before promising live availability or calendar booking. **Continue your evaluation** - [Explore Flow Engine](https://vatoo.ai/flow-engine) - [Explore integration guides](https://vatoo.ai/integrations) - [Real estate overview](https://vatoo.ai/industries/real-estate) The examples describe a workflow to test. They are not customer benchmarks or promises of response-time or conversion improvements. **Questions this guide answers.** - **Do I need a calendar integration to collect viewing requests?** No. You can collect preferred times for an agent to confirm. A confirmed live booking needs the appropriate connected calendar workflow. - **What should agents receive?** The property or area, customer requirements, preferred timing, contact details, and relevant conversation context. **Related guides.** - [Insurance chatbots: a practical guide to enquiries and intake](https://vatoo.ai/blogs/best-ai-chatbot-for-insurance) - [Hindi and Hinglish chatbots: design for real customer questions](https://vatoo.ai/blogs/hindi-first-ai-chatbots) - [AI chatbot pricing in 2026: how to compare total cost](https://vatoo.ai/blogs/what-ai-chatbots-really-cost-2026) ### Hindi and Hinglish chatbots: design for real customer questions - [Hindi & Hinglish Chatbots: A Practical Guide](https://vatoo.ai/blogs/hindi-first-ai-chatbots): Plan a Hindi and Hinglish chatbot around language switching, clear forms, approved answers, and human handoff. India Growth · Vatoo Editorial · Published August 27, 2026 · Updated November 6, 2026. Language support is useful only when customers can complete the task. A Hindi-speaking visitor may type in Devanagari, Romanised Hindi, English, or a mixture of all three. Design and test the whole conversation, including forms and handoffs, around the messages your customers actually send. **Start with your own conversations** Review anonymised questions from your service or sales team. Note the words customers use for products, prices, appointment times, and common problems. Avoid assuming that all Indian customers prefer Hindi; choose priority languages from your audience and service coverage. **Test meaning across scripts** An example request such as “kal appointment mil sakta hai?” includes both a task and a relative date. The assistant should clarify the date and availability before confirming anything. Test spelling variations and language switching, and ask a fluent reviewer to assess clarity rather than judging only grammatical correctness. **Keep the workflow in the customer’s language** - Explain why you need a phone number or other personal detail. - Keep field labels, validation messages, and confirmations understandable. - Show dates, currencies, and time zones clearly. - Preserve exact product names and policy terms where translation could change their meaning. - Offer a clear handoff when the assistant cannot resolve the request. **Build a small evaluation set** | Test | What a useful response does | | --- | --- | | Hindi question, English source | Answers the same facts without inventing detail. | | Mixed-language request | Understands the intent and asks a relevant follow-up. | | Ambiguous date | Confirms the intended date before taking action. | | Missing answer | Explains the limit and offers the next step. | | Human handoff | Passes the conversation and language context to staff. | **Evaluate Vatoo with your content** Connect a small set of current, approved documents. Configure the assistant’s role and tone, then test a practical enquiry or booking-request form. Review the languages your team will support and the messaging channel you intend to use. Translation quality, integrations, and staff coverage should all be tested before a wider rollout. **Measure the complete task** Track whether the customer received a supported answer, submitted a usable request, or reached the right person. Compare outcomes by language and request type. Use failures to improve content and instructions; a multilingual feature label alone does not establish a better customer experience. **Continue your evaluation** - [Explore Vatoo features](https://vatoo.ai/features) - [WhatsApp setup guide](https://vatoo.ai/integrations/whatsapp) - [Forms inside chat](https://vatoo.ai/smart-form-engine) **Questions this guide answers.** - **Should every Indian business start with Hindi?** No. Prioritise languages using your customers’ needs and your ability to maintain content and human support. - **Is translating the greeting enough?** No. Test answers, forms, error messages, confirmations, and handoffs throughout the customer journey. **Related guides.** - [Real estate chatbots: qualify enquiries and guide viewing requests](https://vatoo.ai/blogs/best-ai-chatbot-for-real-estate) - [Insurance chatbots: a practical guide to enquiries and intake](https://vatoo.ai/blogs/best-ai-chatbot-for-insurance) - [AI chatbot pricing in 2026: how to compare total cost](https://vatoo.ai/blogs/what-ai-chatbots-really-cost-2026) ### Vatoo vs Tidio: compare workflows, support, and cost - [Vatoo vs Tidio: Workflows & Pricing Guide](https://vatoo.ai/blogs/niva-vs-tidio-pricing-comparison): Evaluate Vatoo and Tidio using the same customer questions, lead-capture workflow, human handoff, and monthly usage forecast. Comparisons · Vatoo Editorial · Published February 18, 2026 · Updated November 6, 2026. Tidio combines live chat, helpdesk capabilities, Lyro AI, and automation flows. Vatoo brings business knowledge, specialist roles, Smart Forms, and connected workflows into a branded assistant. Both deserve to be evaluated on the work you need done, rather than an outdated list of missing features. **Start with the team’s daily work** If staff spend much of their day managing customer messages, examine Tidio’s human support workspace alongside Lyro. If your first task is a branded website assistant that answers questions and collects structured enquiries, test Vatoo’s knowledge, form, and flow setup. Neither category description replaces a trial of your requirements. **Compare the paid configuration you would actually use** | Requirement | What to check in both products | | --- | --- | | AI usage | The unit counted, monthly allowance, and behaviour at the limit. | | Human support | Staff access, conversation history, and offline handoff. | | Lead capture | Required fields, validation, consent copy, and delivery destination. | | Workflow actions | The supported connector, permissions, success confirmation, and failure path. | | Branding | Widget identity and the rights needed for client delivery. | Use Tidio’s current pricing page to identify the allowances for live support, Lyro, and Flows in your selected configuration. For Vatoo, compare Essential with Premium: the trial offers Premium access, while ongoing Essential access excludes the visual flow builder, tools and API calls, memory, and multiple channels. There is no single fair cost comparison without your volume and feature requirements. **Run the same five tests** - Ask a question answered by a document you supplied. - Ask a question for which the document has no answer. - Submit a qualified enquiry with the fields sales actually needs. - Make a connected action fail and inspect the customer message. - Ask for a human and check what the staff member receives. **Choose based on evidence from your trial** Record setup time, answer quality, successful actions, and staff follow-up. Include third-party fees and annual commitments in the cost estimate. If the better product requires a different way of working, include training and maintenance in the decision. **Continue your evaluation** - [Compare Vatoo plans](https://vatoo.ai/pricing) - [Vatoo and Tidio evaluation checklist](https://vatoo.ai/alternatives/tidio) - [Explore Smart Forms](https://vatoo.ai/smart-form-engine) **Sources** Reviewed 4 November 2026: [Tidio product](https://www.tidio.com/ai-agent/) and [Tidio pricing](https://www.tidio.com/pricing/). Published by Vatoo; this is a buyer guide, not an independent benchmark or measured cost-saving claim. **Questions this guide answers.** - **Does Vatoo Essential include the Flow Engine?** No. The published plan comparison lists the visual flow builder in Premium and the Premium-feature trial, not ongoing Essential access. - **Which platform costs less?** Compare the exact configuration, usage, billing term, and third-party costs needed for your workflow. **Related guides.** - [AI chatbot pricing in 2026: how to compare total cost](https://vatoo.ai/blogs/what-ai-chatbots-really-cost-2026) - [Per-resolution AI pricing: when it works and what to check](https://vatoo.ai/blogs/per-resolution-pricing-trap) - [Vatoo vs Voiceflow: choose for your team and workflow](https://vatoo.ai/blogs/niva-vs-voiceflow) ### Vatoo vs Voiceflow: choose for your team and workflow - [Vatoo vs Voiceflow: Team & Workflow Guide](https://vatoo.ai/blogs/niva-vs-voiceflow): Compare Vatoo and Voiceflow on agent design, knowledge, integrations, testing, and the effort needed after launch. Comparisons · Vatoo Editorial · Published August 27, 2026 · Updated November 6, 2026. Voiceflow is a conversational AI platform with tools for agent building, knowledge, workflows, testing, and analytics. Describing it as only a prototyping tool would miss the current product. A useful comparison asks who will build and maintain the assistant, and what the customer needs to complete. **Identify who owns the assistant** List the people responsible for content, conversation design, integrations, and performance review. Give them a representative change to make during the trial. A platform that fits the launch team may still be difficult for the team that owns it afterwards. **What to evaluate in Voiceflow** Explore its workflow and agent-design tools, testing approach, knowledge setup, and connected actions. Use your own conversation rather than a vendor’s prepared scenario. Ask which collaboration, deployment, and usage provisions apply to the proposed plan. **What to evaluate in Vatoo** Start with a specialist role, add approved content, and build one form or flow. Check how your team edits answers, reviews conversations, and routes exceptions. Vatoo may fit teams looking for a business-focused starting point and branded delivery; custom integration requirements still need technical evaluation. **Use a shared scorecard** | Area | Trial task | | --- | --- | | Knowledge | Update a policy and check the new answer. | | Workflow | Collect requirements and send them to a test destination. | | Failure handling | Simulate missing data or an unavailable endpoint. | | Team ownership | Ask the future operator to change a form or instruction. | | Cost | Forecast normal and peak usage with all required access. | **A template is a starting point** Ready-made roles can help organise the initial configuration. They do not know your prices, policies, or system permissions until you provide them. Equally, a flexible builder does not imply an impractical rollout. Judge the finished workflow and the work needed to maintain it. **Make the buying decision** Choose the platform that meets the customer task, supports your team’s skills, and makes ongoing cost understandable. If the result is close, test a second workflow or a difficult handoff. Do not decide on a polished demo alone. New to the terminology? Our [guide to agentic and multi-agent chatbots](https://vatoo.ai/answers) explains how business knowledge, specialist roles, and connected actions work together. **Continue your evaluation** - [How Vatoo works](https://vatoo.ai/how-it-works) - [Compare Vatoo plans](https://vatoo.ai/pricing) - [Explore AI Agents](https://vatoo.ai/ai-agents) **Sources** Reviewed 4 November 2026: [Voiceflow platform](https://www.voiceflow.com/). Confirm current plans and requirements directly with Voiceflow. Published by Vatoo; no independent performance benchmark is claimed. **Questions this guide answers.** - **Is Voiceflow only for prototypes?** No. Its current platform includes capabilities for building, testing, and operating agents. Evaluate those against your production requirements. - **Can Vatoo replace every custom agent build?** Do not assume so. Validate required actions, permissions, channels, and failure handling during an evaluation. **Related guides.** - [Vatoo vs Tidio: compare workflows, support, and cost](https://vatoo.ai/blogs/niva-vs-tidio-pricing-comparison) - [AI chatbot pricing in 2026: how to compare total cost](https://vatoo.ai/blogs/what-ai-chatbots-really-cost-2026) - [Per-resolution AI pricing: when it works and what to check](https://vatoo.ai/blogs/per-resolution-pricing-trap) ### Per-resolution AI pricing: when it works and what to check - [Per-Resolution AI Pricing: Costs & Tradeoffs](https://vatoo.ai/blogs/per-resolution-pricing-trap): Understand AI resolution fees, forecast cost at different volumes, and compare usage pricing with monthly message allowances. Pricing · Vatoo Editorial · Published January 21, 2026 · Updated November 6, 2026. Per-resolution pricing connects part of the bill to work the vendor considers completed. It can make sense when outcomes are valuable and clearly defined. It needs closer review when your team cannot explain what is counted or predict how often customers will return. **Define a resolution before comparing prices** Ask for the vendor’s definition, including assumed resolutions, reopened conversations, repeated contacts, and transfers to staff. Confirm whether an AI response that produces no customer reply counts. The commercial definition and your customer’s idea of a solved problem may differ. **Calculate the variable part of the bill** Multiply billable resolutions by the contracted rate, then add platform fees, required seats, channels, and other charges. The following rates are hypothetical examples, not current vendor quotes. | Monthly billable resolutions | At $0.50 each | At $1.00 each | At $2.00 each | | --- | --- | --- | --- | | 500 | $250 | $500 | $1,000 | | 2,000 | $1,000 | $2,000 | $4,000 | | 5,000 | $2,500 | $5,000 | $10,000 | **A higher invoice can still represent better value** If automation resolves more useful work, usage charges may rise while manual work falls. Evaluate both changes. Count human follow-up, quality reviews, and reopened requests rather than assuming every automated answer removes a whole support interaction. **Questions for a trial or vendor call** - Can we inspect the records behind billable outcomes? - How are disputed or reopened resolutions handled? - Can we set alerts or spending controls? - What happens during a traffic spike or at a usage limit? - Which fees continue when an issue reaches a human? **Compare with an allowance-based plan fairly** A monthly plan with included messages makes the base subscription visible, but it still has limits. Estimate messages per conversation and the tier needed for your workflow. Do not compare 3,000 resolutions with 3,000 messages as though they represent the same workload. **How to evaluate Vatoo** Vatoo publishes monthly message allowances and feature differences. Test the free trial against real questions, form submissions, and handoffs. Confirm the behaviour at the allowance limit, then compare total cost at normal and peak volume with any outcome-priced alternative. **Continue your evaluation** - [Vatoo plan allowances](https://vatoo.ai/pricing) - [Build a total-cost budget](https://vatoo.ai/blogs/what-ai-chatbots-really-cost-2026) **Sources** Reviewed 4 November 2026: [Intercom pricing](https://www.intercom.com/pricing) and [Zendesk pricing](https://www.zendesk.com/pricing/). Always confirm the outcome definition and contractual charges directly. The calculation table is illustrative. **Questions this guide answers.** - **Is per-resolution pricing always expensive?** No. It depends on the fee, the quality and value of the resolved work, and all other operating costs. - **Does a message allowance remove usage risk?** No. Forecast demand and confirm how usage is counted and handled at the limit. **Related guides.** - [AI chatbot pricing in 2026: how to compare total cost](https://vatoo.ai/blogs/what-ai-chatbots-really-cost-2026) - [Vatoo vs Tidio: compare workflows, support, and cost](https://vatoo.ai/blogs/niva-vs-tidio-pricing-comparison) - [Vatoo vs Voiceflow: choose for your team and workflow](https://vatoo.ai/blogs/niva-vs-voiceflow) ### AI chatbot pricing in 2026: how to compare total cost - [AI Chatbot Pricing in 2026: Total Cost Guide](https://vatoo.ai/blogs/what-ai-chatbots-really-cost-2026): Compare platform fees, messages, resolutions, seats, and setup costs. Build a useful budget for your normal month and your busiest month. Pricing · Vatoo Editorial · Published January 14, 2026 · Updated November 6, 2026. An AI chatbot’s entry price is only useful when you know what it includes. A message allowance, a conversation allowance, and a resolved support request are different units. Before comparing vendors, write down the work you want to automate and the people who will run it. **Start with the workload, not the cheapest plan** For a website assistant, estimate customer conversations and the number of messages needed to reach an answer or next step. For support, include requests that need a person after the AI responds. For lead capture, measure whether the enquiry contains enough information for a useful follow-up. A low cost per chat is not a saving if the team has to redo the work. **Understand what each billing model counts** | Billing unit | What to establish | Why it matters | | --- | --- | --- | | Seat | Which builders and support staff need paid access? | The number of visitors says little about team cost. | | Message or credit | Which messages consume credits, and at what rate? | Long conversations can consume more than a single question. | | Conversation | When does a conversation start and end? | A returning visitor may create another billable session. | | Resolution or outcome | What qualifies, and how are reopened cases treated? | A billed outcome must be compared with customer success. | | Platform allowance | What happens when included usage runs out? | A monthly subscription does not imply unlimited use. | **Build a normal-month and peak-month budget** Use the same assumptions for every quote. Include required seats, channels, connectors, support, and implementation. Ask whether external model or messaging-provider fees are included. Annual discounts should be compared using the full annual commitment, not only the monthly equivalent. - List your must-have workflow and integrations before selecting a tier. - Estimate normal and peak traffic from your own analytics. - Ask each vendor to explain usage counting and allowance-limit behaviour in writing. - Include the time needed to prepare content, test changes, and review escalations. - Separate one-time setup costs from recurring charges. **A worked example, not a vendor quote** Suppose a plan costs $100 per month, with $40 in required extras and $300 in one-time setup. Its first-year cost is ($100 + $40) × 12 + $300 = $1,980, before taxes, usage charges, or your team’s time. This illustration is a calculation method, not a market average or a promised saving. **Where Vatoo fits** Vatoo’s free trial includes 1,000 messages to use within 3 months, plus Premium feature access. Unused trial messages expire after those 3 months. Essential includes 3,000 messages per month; Premium includes 15,000. Essential is $49 monthly or $468 billed yearly. Premium is $149 monthly or $1,428 billed yearly. Compare the ongoing feature set as well as the allowance: flows, tools, memory, and multiple channels are Premium capabilities. Confirm usage counting, limit handling, and third-party fees before purchase. **Compare cost per useful outcome** Run one representative workflow with each shortlisted product. Record whether the answer was supported, the action completed, and the handoff reached the right person. Combine those results with total operating cost. The best choice is the one your team can maintain and your customers can use successfully. **Continue your evaluation** - [Compare Vatoo plans](https://vatoo.ai/pricing) - [Understand per-resolution pricing](https://vatoo.ai/blogs/per-resolution-pricing-trap) - [Compare chatbot platforms](https://vatoo.ai/alternatives) **Sources** Vendor packaging reviewed 4 November 2026: [Intercom pricing](https://www.intercom.com/pricing), [Chatbase pricing](https://www.chatbase.co/pricing), [Tidio pricing](https://www.tidio.com/pricing/), and [Botpress pricing](https://botpress.com/pricing). These illustrate different charging models; consult each vendor for current terms. Vatoo figures come from our published pricing page. No customer survey or market-average savings are claimed. **Questions this guide answers.** - **Is a flat monthly plan unlimited?** No. Check its usage allowance, included features, and what happens at the limit. - **Should I choose annual billing first?** Test the workflow and confirm the required tier before comparing the annual commitment with monthly billing. **Related guides.** - [Per-resolution AI pricing: when it works and what to check](https://vatoo.ai/blogs/per-resolution-pricing-trap) - [Vatoo vs Tidio: compare workflows, support, and cost](https://vatoo.ai/blogs/niva-vs-tidio-pricing-comparison) - [Vatoo vs Voiceflow: choose for your team and workflow](https://vatoo.ai/blogs/niva-vs-voiceflow)