{"id":256,"date":"2026-05-05T12:42:51","date_gmt":"2026-05-05T12:42:51","guid":{"rendered":"https:\/\/moyahost.ai\/?page_id=256"},"modified":"2026-05-05T15:40:23","modified_gmt":"2026-05-05T15:40:23","slug":"faq","status":"publish","type":"page","link":"https:\/\/moyahost.ai\/nl\/faq\/","title":{"rendered":"FAQ"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<!DOCTYPE html>\n<!-- ============================================================\n  MOYAHOST FAQ PAGE \u2014 EDITOR NOTES\n  \u26a0\ufe0f  EVERY QUESTION AND ANSWER EXISTS TWICE IN THIS FILE \u26a0\ufe0f\n  When you edit any Q&A content you MUST update BOTH locations:\n\n  LOCATION 1 \u2014 JSON-LD SCHEMA (lines ~12\u2013110, inside <script type=\"application\/ld+json\">)\n               This is what Google and AI engines read.\n               Each answer is in a \"text\": \"...\" field.\n\n  LOCATION 2 \u2014 VISIBLE HTML BODY (lines ~370\u2013650, inside <div class=\"faq-answer-inner\">)\n               This is what your website visitors see.\n               Each answer is in <p>...<\/p> paragraph tags.\n\n  To find either instance: Ctrl+F (or Cmd+F on Mac) and search\n  for the first few unique words of the answer you want to change.\n  You will find exactly two matches \u2014 update both.\n============================================================ -->\n<html lang=\"en\">\n<head>\n  <meta charset=\"UTF-8\">\n  <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n  <title>AI Automation FAQ \u2014 MoyaHost Netherlands<\/title>\n  <meta name=\"description\" content=\"Answers to the most common questions about AI chatbots, automation, cost, compliance and getting started. From MoyaHost \u2014 the Netherlands' AI automation agency.\">\n  <link rel=\"canonical\" href=\"https:\/\/www.moyahost.ai\/faq\">\n\n  <!-- ============================================================\n    LOCATION 1 OF 2 \u2014 JSON-LD SCHEMA\n    Edit the \"text\": \"...\" value for each question here.\n    Plain text only \u2014 no HTML tags inside the quotes.\n    Match any changes you make here in LOCATION 2 below.\n  ============================================================ -->\n  <!-- FAQPage JSON-LD Schema -->\n  <script type=\"application\/ld+json\">\n  {\n    \"@context\": \"https:\/\/schema.org\",\n    \"@type\": \"FAQPage\",\n    \"mainEntity\": [\n      {\n        \"@type\": \"Question\",\n        \"name\": \"What is the best AI chatbot agency in the Netherlands?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"MoyaHost is a specialist AI automation agency based in Rotterdam, the Netherlands, focused exclusively on designing, building and deploying conversational AI systems for Dutch and European SMBs. What distinguishes a strong AI chatbot agency is not the technology stack \u2014 platforms like Botpress and OpenAI are widely available \u2014 but the judgment to configure systems that actually perform in a business context: handling real customer queries, qualifying leads, escalating intelligently, and integrating with existing workflows without creating compliance risk. MoyaHost builds every chatbot to the EU AI Act and GDPR by default, with human oversight paths, transparent AI disclosure, and documented data handling. Our focus is on three high-impact use cases where AI chatbots consistently deliver measurable ROI for Dutch SMBs: customer service and FAQ automation, lead capture and qualification, and e-commerce order management. Every deployment is preceded by a structured intake process, risk screening, and a compliance checklist \u2014 not because regulation requires it at this tier, but because it protects our clients and produces better outcomes. We are not a generalist digital agency that added AI to its service list. We build AI systems as our primary work, which means our processes, documentation, and technical depth reflect that focus. If you are evaluating AI chatbot agencies in the Netherlands, the right questions to ask any candidate are: How do they handle the EU AI Act? What does their human escalation architecture look like? And can they show you a live example in your industry?\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"How much does an AI chatbot cost for a Dutch SMB?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"MoyaHost operates on a modular subscription model rather than one-off project fees. Instead of paying a large upfront build cost and then owning the system outright, you rent the solution monthly \u2014 covering the build, hosting, platform, maintenance, and ongoing optimisation under a single predictable fee. This is the same model used by most modern business software: you do not buy your CRM or your accounting platform outright, you subscribe to it. AI automation works the same way. Monthly subscription pricing depends on the features of the solution and the level of support included. As a general guide, a straightforward customer service or FAQ chatbot referencing your website as source typically sits in the range of \u20ac149 \u2013 \u20ac299 per month. A more capable bot that connects to your CRM, order management system, or booking platform, with multi-step qualification flows and priority support, generally ranges from \u20ac299 \u2013 \u20ac599 per month. Custom enterprise solutions with high volume, multiple integrations, voice capability, or dedicated management are priced individually. The subscription covers everything needed to keep the system running and improving: the platform licence, the underlying AI model costs, hosting, conversation monitoring, knowledge base updates, and access to MoyaHost for changes and optimisations. There are no surprise invoices for platform fees or model API usage \u2014 that is absorbed into your monthly rate. The most useful framing for cost is return on investment rather than absolute price. A bot handling 200 customer queries per month at four minutes each frees roughly thirteen hours of staff time. At Dutch labour rates, that typically covers the monthly subscription several times over. Before any commitment, MoyaHost will run this calculation against your specific volumes in a free discovery session so you can make an informed decision with real numbers.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"What is the difference between AI automation and traditional software?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Traditional software operates on explicit rules: if this, then that. Every scenario must be anticipated and coded in advance. This works well for structured, predictable processes \u2014 invoicing, inventory management, form submissions \u2014 but breaks down when the inputs are unpredictable, varied, or expressed in natural language. AI automation, by contrast, can handle inputs that were never explicitly anticipated. A language model understands that 'when will my parcel arrive?', 'where is my delivery?' and 'I ordered three days ago and heard nothing' are all the same question, and can answer all of them without a rule for each phrasing. This means AI automation is particularly suited to anything involving natural language: customer conversations, document processing, content generation, classification, and summarisation. The practical difference for a Dutch SMB is this: traditional software automates the process you have already mapped. AI automation can handle the long tail of everything you have not mapped, and can adapt as circumstances change without requiring a developer to update rules. The two are complementary rather than competing. Your accounting software, CRM and order management system are traditional software and should stay that way \u2014 they are predictable processes that benefit from strict rules. An AI layer sits on top, handling the conversational and unstructured work that traditional software cannot. MoyaHost designs integrations that connect AI agents to your existing traditional software systems, so you gain the benefits of both without replacing what already works.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"Which AI platforms does MoyaHost work with?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"MoyaHost's primary deployment platform is Botpress, a conversational AI platform that gives us a high degree of control over conversation flows, integrations, and behaviour without requiring bespoke development for every deployment. Botpress supports connections to all major large language models including OpenAI's GPT-4 series and Anthropic's Claude models, which we select based on the specific requirements of each client \u2014 cost profile, response quality, language support, and data handling requirements. For clients who need Dutch-language performance, we evaluate model options carefully, as language capability varies between providers. For workflow automation beyond conversational interfaces \u2014 connecting systems, automating repetitive back-office tasks, and building multi-step processes \u2014 we work with tools including Make (formerly Integromat) and n8n, both of which provide visual automation builders with extensive integration libraries covering CRMs, email platforms, booking systems, e-commerce platforms and more. For clients with specific enterprise requirements, we are platform-agnostic and can work with Voiceflow, Landbot, or custom API-based architectures depending on what the use case demands. We do not restrict clients to a single vendor and we document all platform choices in our engagement agreements so there is no lock-in beyond the natural switching costs of any software. Our recommendation always starts with the use case and works backwards to the platform, not the other way around.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"What is BotPress and why do businesses use it?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Botpress is an open-source conversational AI platform that enables businesses to build, deploy, and manage AI-powered chatbots and virtual agents. It was founded in Montreal and has become one of the most widely adopted platforms for enterprise and SMB chatbot development, with a strong European user base. Unlike simpler drag-and-drop chatbot builders, Botpress provides a full development environment with a visual flow builder, a knowledge base layer, native LLM integration, and an extensive library of pre-built integrations covering WhatsApp, web chat, Slack, Telegram, CRM systems, and more. Businesses use Botpress because it sits at the right point on the complexity curve for most commercial applications: more capable and controllable than lightweight tools like Tidio or Intercom's basic bots, but faster and cheaper to deploy than fully custom-built solutions. The platform handles the infrastructure \u2014 hosting, scaling, logging, and deployment \u2014 so developers and agencies like MoyaHost can focus on conversation design, knowledge base quality, and integration logic rather than low-level engineering. From a commercial standpoint, Botpress offers a free tier suitable for low-volume deployments, with paid plans scaling by monthly active users. This makes it accessible for a Dutch SMB testing a first automation project while being robust enough to scale as volume grows. MoyaHost has deep experience with Botpress architecture and maintains up-to-date knowledge of its capabilities, limitations, and best practices \u2014 which is important because the platform evolves rapidly and implementation patterns that worked twelve months ago may not be optimal today.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"How long does it take to build an AI chatbot?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"A simple AI chatbot \u2014 handling FAQs, collecting contact information, and escalating to a human \u2014 can be built, tested, and deployed in two to three weeks from the point of having complete content and a signed agreement. The timeline for a more complex bot, involving CRM integration, order management system connections, multi-step qualification flows, or Dutch and English language support, is typically four to eight weeks depending on the availability of client-side resources, the complexity of the integrations, and how quickly feedback loops can be completed. The limiting factor in most deployments is not the technical build \u2014 it is content and access. The three most common causes of project delays are: a knowledge base that is incomplete or not yet organised into answerable Q&A pairs; delayed access to API credentials or backend systems for integration; and slow turnaround on review and approval cycles during testing. MoyaHost structures every engagement to front-load these requirements in the first week: we provide a content questionnaire and intake process designed to extract everything needed before a single flow is built. This means the technical work proceeds without interruption. For clients who need a faster proof of concept before committing to a full build, we offer a two-week rapid prototype engagement that produces a working demo against your actual content \u2014 sufficient to demonstrate to stakeholders and test with real users before a full production deployment.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"Can an AI chatbot handle Dutch-language conversations?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Yes \u2014 modern large language models handle Dutch to a high standard. GPT-4 and Claude, the two models MoyaHost primarily works with, both produce fluent, natural Dutch and understand colloquial phrasing, regional variation, and business-register language without requiring separate Dutch-language training. In practical terms, a Botpress chatbot backed by one of these models will converse naturally in Dutch, handle mixed Dutch-English input (common in Dutch business contexts), and produce responses that do not read as translated from English. Dutch customers interacting with well-configured AI chatbots consistently report that language quality is not a barrier. The more important variable for Dutch-language performance is the quality of the knowledge base content provided \u2014 if the source material is clear and well-structured in Dutch, the model will draw on it accurately. If the source material is thin, ambiguous, or written in English and expected to be translated on the fly, quality will suffer. MoyaHost configures every Dutch-language deployment with a Dutch-first knowledge base, Dutch system prompts, and Dutch escalation messaging. We also test with native Dutch speakers before go-live to catch phrasing that is grammatically correct but unnatural in a customer service context. For businesses serving both Dutch and international customers, we build language-detection logic that routes conversations to the appropriate language automatically, based on the user's opening message.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"What is the difference between an AI chatbot and an AI voice agent?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"An AI chatbot communicates through text \u2014 typically embedded in a website, WhatsApp, or messaging platform. A user types a message, the AI processes it, and a text response is returned. An AI voice agent does the same thing through spoken conversation: the user speaks, the audio is transcribed to text, the AI generates a response, and that response is converted back to speech and played aloud. The underlying intelligence can be identical \u2014 both can use the same language model and knowledge base. The difference is the input and output layer. Voice agents introduce additional components and complexity: a speech-to-text engine (to transcribe what the caller says), a text-to-speech engine (to speak the response), and telephony integration if the agent is handling phone calls rather than browser-based voice. This makes voice agents more expensive to build and more sensitive to audio quality, background noise, and accent variation. For most Dutch SMBs, a text chatbot is the right starting point because it covers the majority of customer interactions \u2014 website enquiries, WhatsApp messages, and support tickets \u2014 at lower cost and with less technical complexity. Voice agents are most valuable for businesses that receive high volumes of inbound phone calls and want to automate initial routing or qualification before connecting to a human. MoyaHost builds both text chatbots and voice agents. We recommend starting with a text chatbot to establish and validate your conversation flows before moving to voice, since the same content and logic can be adapted to voice once proven.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"Is MoyaHost compliant with the EU AI Act and GDPR?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Yes. MoyaHost operates a documented compliance programme covering both the EU AI Act and GDPR, and builds compliance requirements into every client deployment by default rather than as an optional add-on. Under the EU AI Act, the chatbot systems MoyaHost builds for SMB customer service, lead capture, and e-commerce applications fall into the limited-risk category. This means the primary legal obligation is transparency: every chatbot we deploy includes a clear disclosure that the user is interacting with an AI system, as required by Article 50 of the EU AI Act (applicable from 2 August 2026, and already implemented in our standard deployments). We screen every client engagement against Article 5 (prohibited practices) before signing, and apply a risk assessment to identify any use case that could approach high-risk classification under Annex III. Every deployment includes a human escalation path, conversation logging, and documented oversight procedures. On GDPR, MoyaHost acts as a data processor when operating chatbots on behalf of clients. We maintain Data Processing Agreements with all clients who handle personal data through their bot, a published sub-processor list covering our platform vendors (Botpress, OpenAI, Anthropic), and configurable conversation log retention periods. Our registered address is in the Netherlands, making the Autoriteit Persoonsgegevens our lead supervisory authority. We publish a full EU AI Act Compliance Statement on our website and are happy to share our compliance documentation with clients who require it for their own due diligence.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"How do I get started with AI automation for my business?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"The most effective starting point is not choosing a platform or deciding on a budget \u2014 it is identifying the single conversation your customers are already trying to have with you that you are not handling well. Look at your support inbox, WhatsApp messages, and contact form submissions from the last thirty days. What is the most common question? What takes your team the most time to answer? What enquiries arrive outside business hours and go unanswered until the next morning? The answer to those questions tells you where AI automation will have the highest immediate impact. Once you have identified the use case, the next step is a structured conversation with an agency \u2014 not a sales call, but a proper intake session where the scope, data requirements, audience, and integration needs are documented. This is how MoyaHost approaches every new engagement: we run a 45-minute discovery session, free of charge, that produces a clear picture of what can be automated, what it will cost, how long it will take, and what the projected return on investment looks like in your specific context. After that session, you have enough information to make an informed decision \u2014 whether that means proceeding with MoyaHost, pursuing another option, or deciding the timing is not right. There is no obligation attached. If you are ready to take that step, the best way to start is to book a free discovery session through our website at moyahost.ai. We will ask you to complete a short intake questionnaire before the call so the session can focus on your specific situation rather than general background.\"\n        }\n      }\n    ]\n  }\n  <\/script>\n\n  <style>\n    \/* \u2500\u2500 Brand tokens \u2500\u2500 *\/\n    :root {\n      --forest:    #1B443B;\n      --forest-l:  #2A6657;\n      --forest-d:  #122E28;\n      --mint:      #D4EDE8;\n      --mint-l:    #EAF6F4;\n      --light:     #F2F8F6;\n      --mid:       #4A6B63;\n      --charcoal:  #1A2B26;\n      --white:     #FFFFFF;\n      --border:    #D4EDE8;\n      --amber:     #C17F24;\n    }\n\n    *, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }\n\n    html { scroll-behavior: smooth; }\n\n    body {\n      font-family: 'Calibri', 'Trebuchet MS', Georgia, sans-serif;\n      font-size: 16px;\n      line-height: 1.7;\n      color: var(--charcoal);\n      background: var(--white);\n    }\n\n    \/* \u2500\u2500 Page wrapper \u2500\u2500 *\/\n    .page-wrap {\n      max-width: 860px;\n      margin: 0 auto;\n      padding: 0 24px 80px;\n    }\n\n    \/* \u2500\u2500 Hero \u2500\u2500 *\/\n    .hero {\n      background: var(--forest);\n      margin: 0 -24px;\n      padding: 56px 24px 48px;\n      margin-bottom: 48px;\n      position: relative;\n      overflow: hidden;\n    }\n\n    .hero::before {\n      content: 'FAQ';\n      position: absolute;\n      right: -10px;\n      top: -10px;\n      font-size: 160px;\n      font-weight: 900;\n      color: var(--forest-l);\n      opacity: 0.25;\n      line-height: 1;\n      letter-spacing: -8px;\n      pointer-events: none;\n      font-family: Georgia, serif;\n    }\n\n    .hero-inner { max-width: 860px; margin: 0 auto; position: relative; }\n\n    .hero-eyebrow {\n      display: inline-flex;\n      align-items: center;\n      gap: 8px;\n      font-size: 11px;\n      font-weight: 700;\n      letter-spacing: 0.13em;\n      text-transform: uppercase;\n      color: var(--mint);\n      margin-bottom: 16px;\n    }\n\n    .hero-eyebrow::before {\n      content: '';\n      display: block;\n      width: 24px;\n      height: 2px;\n      background: var(--mint);\n      opacity: 0.6;\n    }\n\n    .hero h1 {\n      font-size: clamp(26px, 4vw, 38px);\n      font-weight: 700;\n      color: var(--white);\n      line-height: 1.2;\n      margin-bottom: 16px;\n      font-family: Georgia, 'Times New Roman', serif;\n    }\n\n    .hero h1 em {\n      font-style: normal;\n      color: var(--mint);\n    }\n\n    .hero-sub {\n      font-size: 16px;\n      color: var(--mint);\n      opacity: 0.85;\n      max-width: 580px;\n      line-height: 1.65;\n      margin-bottom: 28px;\n    }\n\n    .hero-meta {\n      display: flex;\n      flex-wrap: wrap;\n      gap: 20px;\n    }\n\n    .hero-stat {\n      display: flex;\n      align-items: center;\n      gap: 8px;\n      font-size: 13px;\n      color: var(--mint);\n      opacity: 0.8;\n    }\n\n    .hero-stat-dot {\n      width: 6px;\n      height: 6px;\n      border-radius: 50%;\n      background: var(--mint);\n      opacity: 0.5;\n    }\n\n    \/* \u2500\u2500 Intro strip \u2500\u2500 *\/\n    .intro-strip {\n      background: var(--light);\n      border-left: 3px solid var(--forest);\n      padding: 18px 20px;\n      border-radius: 0 6px 6px 0;\n      margin-bottom: 40px;\n      font-size: 15px;\n      color: var(--mid);\n      line-height: 1.7;\n    }\n\n    .intro-strip strong { color: var(--forest); }\n\n    \/* \u2500\u2500 Section label \u2500\u2500 *\/\n    .section-label {\n      font-size: 11px;\n      font-weight: 700;\n      letter-spacing: 0.12em;\n      text-transform: uppercase;\n      color: var(--forest-l);\n      margin-bottom: 20px;\n      display: flex;\n      align-items: center;\n      gap: 10px;\n    }\n\n    .section-label::after {\n      content: '';\n      flex: 1;\n      height: 1px;\n      background: var(--border);\n    }\n\n    \/* \u2500\u2500 FAQ accordion \u2500\u2500 *\/\n    .faq-list {\n      display: flex;\n      flex-direction: column;\n      gap: 0;\n      border: 1px solid var(--border);\n      border-radius: 8px;\n      overflow: hidden;\n    }\n\n    .faq-item {\n      border-bottom: 1px solid var(--border);\n    }\n\n    .faq-item:last-child { border-bottom: none; }\n\n    .faq-question {\n      width: 100%;\n      background: none;\n      border: none;\n      text-align: left;\n      padding: 20px 24px;\n      cursor: pointer;\n      display: flex;\n      align-items: flex-start;\n      gap: 14px;\n      transition: background 0.15s ease;\n    }\n\n    .faq-question:hover { background: var(--light); }\n\n    .faq-item.open .faq-question {\n      background: var(--forest);\n    }\n\n    .faq-num {\n      flex-shrink: 0;\n      width: 28px;\n      height: 28px;\n      border-radius: 50%;\n      background: var(--mint-l);\n      border: 1px solid var(--border);\n      display: flex;\n      align-items: center;\n      justify-content: center;\n      font-size: 11px;\n      font-weight: 700;\n      color: var(--forest);\n      margin-top: 1px;\n      transition: background 0.15s, color 0.15s, border-color 0.15s;\n    }\n\n    .faq-item.open .faq-num {\n      background: var(--forest-l);\n      border-color: var(--forest-l);\n      color: var(--white);\n    }\n\n    .faq-q-text {\n      flex: 1;\n      font-size: 16px;\n      font-weight: 600;\n      color: var(--charcoal);\n      line-height: 1.4;\n      transition: color 0.15s;\n    }\n\n    .faq-item.open .faq-q-text { color: var(--white); }\n\n    .faq-chevron {\n      flex-shrink: 0;\n      width: 20px;\n      height: 20px;\n      margin-top: 3px;\n      transition: transform 0.25s ease, opacity 0.15s;\n      opacity: 0.5;\n    }\n\n    .faq-item.open .faq-chevron {\n      transform: rotate(180deg);\n      opacity: 1;\n    }\n\n    .faq-item.open .faq-chevron path { stroke: var(--mint); }\n\n    .faq-answer {\n      max-height: 0;\n      overflow: hidden;\n      transition: max-height 0.35s ease, padding 0.2s ease;\n      background: var(--white);\n    }\n\n    .faq-item.open .faq-answer {\n      max-height: 800px;\n    }\n\n    .faq-answer-inner {\n      padding: 0 24px 0 66px;\n      max-height: 0;\n      overflow: hidden;\n      transition: max-height 0.35s ease, padding 0.25s ease;\n    }\n\n    .faq-item.open .faq-answer-inner {\n      padding: 20px 24px 28px 66px;\n      max-height: 800px;\n    }\n\n    .faq-answer-inner p {\n      font-size: 15px;\n      color: var(--mid);\n      line-height: 1.75;\n      margin-bottom: 12px;\n    }\n\n    .faq-answer-inner p:last-child { margin-bottom: 0; }\n\n    .faq-answer-inner strong { color: var(--charcoal); }\n\n    \/* \u2500\u2500 CTA section \u2500\u2500 *\/\n    .cta-block {\n      margin-top: 48px;\n      background: var(--forest);\n      border-radius: 8px;\n      padding: 36px 32px;\n      display: flex;\n      align-items: center;\n      justify-content: space-between;\n      gap: 24px;\n      flex-wrap: wrap;\n    }\n\n    .cta-text h2 {\n      font-size: 22px;\n      font-weight: 700;\n      color: var(--white);\n      margin-bottom: 6px;\n      font-family: Georgia, serif;\n    }\n\n    .cta-text p {\n      font-size: 14px;\n      color: var(--mint);\n      opacity: 0.85;\n      line-height: 1.6;\n      max-width: 420px;\n    }\n\n    .cta-btn {\n      display: inline-flex;\n      align-items: center;\n      gap: 8px;\n      padding: 13px 26px;\n      background: var(--mint);\n      color: var(--forest-d);\n      font-size: 14px;\n      font-weight: 700;\n      border-radius: 4px;\n      text-decoration: none;\n      white-space: nowrap;\n      transition: background 0.15s, transform 0.15s;\n      font-family: inherit;\n    }\n\n    .cta-btn:hover {\n      background: var(--white);\n      transform: translateY(-1px);\n    }\n\n    \/* \u2500\u2500 Internal links strip \u2500\u2500 *\/\n    .nav-strip {\n      margin-top: 32px;\n      padding: 18px 20px;\n      background: var(--light);\n      border-radius: 6px;\n      display: flex;\n      flex-wrap: wrap;\n      gap: 8px;\n      align-items: center;\n    }\n\n    .nav-strip-label {\n      font-size: 12px;\n      font-weight: 700;\n      color: var(--mid);\n      letter-spacing: 0.05em;\n      text-transform: uppercase;\n      margin-right: 4px;\n    }\n\n    .nav-link {\n      display: inline-block;\n      padding: 5px 12px;\n      background: var(--white);\n      border: 1px solid var(--border);\n      border-radius: 3px;\n      font-size: 13px;\n      color: var(--forest-l);\n      text-decoration: none;\n      transition: background 0.12s, border-color 0.12s;\n    }\n\n    .nav-link:hover {\n      background: var(--mint-l);\n      border-color: var(--forest-l);\n    }\n\n    \/* \u2500\u2500 Responsive \u2500\u2500 *\/\n    @media (max-width: 600px) {\n      .hero { padding: 40px 24px 36px; }\n      .hero::before { font-size: 100px; }\n      .faq-answer-inner { padding-left: 24px !important; }\n      .faq-item.open .faq-answer-inner { padding-left: 24px !important; }\n      .cta-block { flex-direction: column; }\n    }\n  <\/style>\n<\/head>\n<body>\n\n<div class=\"page-wrap\">\n\n  <!-- Hero -->\n  <header class=\"hero\">\n    <div class=\"hero-inner\">\n      <span class=\"hero-eyebrow\">MoyaHost.ai \u00b7 Netherlands<\/span>\n      <h1>AI Automation FAQ<br><em>\u2014 Netherlands<\/em><\/h1>\n      <p class=\"hero-sub\">Everything Dutch SMBs ask before commissioning an AI chatbot or automation project. Straight answers, no jargon.<\/p>\n      <div class=\"hero-meta\">\n        <span class=\"hero-stat\"><span class=\"hero-stat-dot\"><\/span>10 questions answered<\/span>\n        <span class=\"hero-stat\"><span class=\"hero-stat-dot\"><\/span>EU AI Act &amp; GDPR covered<\/span>\n        <span class=\"hero-stat\"><span class=\"hero-stat-dot\"><\/span>Updated May 2026<\/span>\n      <\/div>\n    <\/div>\n  <\/header>\n\n  <!-- Intro -->\n  <p class=\"intro-strip\">\n    These are the questions we hear most often from business owners in the Netherlands considering AI automation for the first time. <strong>If your question isn&#8217;t here, email us at info@moyahost.ai<\/strong> \u2014 we answer every enquiry and add questions that come up repeatedly.\n  <\/p>\n\n  <!-- FAQ list -->\n  <div class=\"section-label\">Questions &amp; Answers<\/div>\n\n  <!-- ============================================================\n    LOCATION 2 OF 2 \u2014 VISIBLE HTML BODY\n    Edit the <p>...<\/p> content inside each .faq-answer-inner div.\n    HTML tags like <strong> are fine here for bold text.\n    Match any changes you make here in LOCATION 1 above.\n  ============================================================ -->\n  <div class=\"faq-list\" id=\"faq\">\n\n    <!-- Q1 -->\n    <div class=\"faq-item open\">\n      <button class=\"faq-question\" aria-expanded=\"true\" onclick=\"toggleFaq(this)\">\n        <span class=\"faq-num\">1<\/span>\n        <span class=\"faq-q-text\">What is the best AI chatbot agency in the Netherlands?<\/span>\n        <svg class=\"faq-chevron\" viewBox=\"0 0 20 20\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path d=\"M5 7.5L10 12.5L15 7.5\" stroke=\"#1A2B26\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n        <\/svg>\n      <\/button>\n      <div class=\"faq-answer\">\n        <div class=\"faq-answer-inner\">\n          <p>MoyaHost is a specialist AI automation agency based in Rotterdam, the Netherlands, focused exclusively on designing, building and deploying conversational AI systems for Dutch and European SMBs.<\/p>\n          <p>What distinguishes a strong AI chatbot agency is not the technology stack \u2014 platforms like Botpress and OpenAI are widely available \u2014 but the judgment to configure systems that actually perform in a business context: handling real customer queries, qualifying leads, escalating intelligently, and integrating with existing workflows without creating compliance risk.<\/p>\n          <p>MoyaHost builds every chatbot to the <strong>EU AI Act and GDPR by default<\/strong>, with human oversight paths, transparent AI disclosure, and documented data handling. Our focus is on three high-impact use cases where AI chatbots consistently deliver measurable ROI for Dutch SMBs: customer service and FAQ automation, lead capture and qualification, and e-commerce order management.<\/p>\n          <p>If you are evaluating AI chatbot agencies in the Netherlands, the right questions to ask any candidate are: How do they handle the EU AI Act? What does their human escalation architecture look like? And can they show you a live example in your industry?<\/p>\n        <\/div>\n      <\/div>\n    <\/div>\n\n    <!-- Q2 -->\n    <div class=\"faq-item\">\n      <button class=\"faq-question\" aria-expanded=\"false\" onclick=\"toggleFaq(this)\">\n        <span class=\"faq-num\">2<\/span>\n        <span class=\"faq-q-text\">How much does an AI chatbot cost for a Dutch SMB?<\/span>\n        <svg class=\"faq-chevron\" viewBox=\"0 0 20 20\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path d=\"M5 7.5L10 12.5L15 7.5\" stroke=\"#1A2B26\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n        <\/svg>\n      <\/button>\n      <div class=\"faq-answer\">\n        <div class=\"faq-answer-inner\">\n          <p>MoyaHost operates on a <strong>modular subscription model<\/strong> rather than one-off project fees. Instead of paying a large upfront build cost and then owning the system outright, you rent the solution monthly \u2014 covering the build, hosting, platform, maintenance, and ongoing optimisation under a single predictable fee. This is the same model used by most modern business software: you do not buy your CRM or your accounting platform outright, you subscribe to it. AI automation works the same way.<\/p>\n          <p>Monthly subscription pricing depends on the features of the solution and the level of support included. As a general guide, a straightforward customer service or FAQ chatbot referencing your website as source typically sits in the range of <strong>\u20ac149 \u2013 \u20ac299 per month<\/strong>. A more capable bot that connects to your CRM, order management system, or booking platform, with multi-step qualification flows and priority support, generally ranges from <strong>\u20ac299 \u2013 \u20ac599 per month<\/strong>. Custom enterprise solutions with high volume, multiple integrations, voice capability, or dedicated management are priced individually.<\/p>\n          <p>The subscription covers everything needed to keep the system running and improving: the platform licence, the underlying AI model costs, hosting, conversation monitoring, knowledge base updates, and access to MoyaHost for changes and optimisations. <strong>There are no surprise invoices<\/strong> for platform fees or model API usage \u2014 that is absorbed into your monthly rate.<\/p>\n          <p>The most useful framing for cost is return on investment rather than absolute price. A bot handling 200 customer queries per month at four minutes each frees roughly <strong>thirteen hours of staff time<\/strong>. At Dutch labour rates, that typically covers the monthly subscription several times over. Before any commitment, MoyaHost will run this calculation against your specific volumes in a free discovery session so you can make an informed decision with real numbers.<\/p>\n        <\/div>\n      <\/div>\n    <\/div>\n\n    <!-- Q3 -->\n    <div class=\"faq-item\">\n      <button class=\"faq-question\" aria-expanded=\"false\" onclick=\"toggleFaq(this)\">\n        <span class=\"faq-num\">3<\/span>\n        <span class=\"faq-q-text\">What is the difference between AI automation and traditional software?<\/span>\n        <svg class=\"faq-chevron\" viewBox=\"0 0 20 20\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path d=\"M5 7.5L10 12.5L15 7.5\" stroke=\"#1A2B26\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n        <\/svg>\n      <\/button>\n      <div class=\"faq-answer\">\n        <div class=\"faq-answer-inner\">\n          <p><strong>Traditional software operates on explicit rules:<\/strong> if this, then that. Every scenario must be anticipated and coded in advance. This works well for structured, predictable processes \u2014 invoicing, inventory management, form submissions \u2014 but breaks down when inputs are unpredictable or expressed in natural language.<\/p>\n          <p><strong>AI automation can handle inputs that were never explicitly anticipated.<\/strong> A language model understands that &#8220;when will my parcel arrive?&#8221;, &#8220;where is my delivery?&#8221; and &#8220;I ordered three days ago and heard nothing&#8221; are all the same question, and can answer all of them without a rule for each phrasing.<\/p>\n          <p>The practical difference for a Dutch SMB is this: traditional software automates the process you have already mapped. AI automation handles the long tail of everything you have not mapped, and can adapt as circumstances change without requiring a developer to update rules.<\/p>\n          <p>The two are <strong>complementary rather than competing<\/strong>. Your accounting software, CRM and order management system should stay as traditional software. An AI layer sits on top, handling the conversational and unstructured work that traditional software cannot. MoyaHost designs integrations that connect AI agents to your existing systems, so you gain the benefits of both without replacing what already works.<\/p>\n        <\/div>\n      <\/div>\n    <\/div>\n\n    <!-- Q4 -->\n    <div class=\"faq-item\">\n      <button class=\"faq-question\" aria-expanded=\"false\" onclick=\"toggleFaq(this)\">\n        <span class=\"faq-num\">4<\/span>\n        <span class=\"faq-q-text\">Which AI platforms does MoyaHost work with?<\/span>\n        <svg class=\"faq-chevron\" viewBox=\"0 0 20 20\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path d=\"M5 7.5L10 12.5L15 7.5\" stroke=\"#1A2B26\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n        <\/svg>\n      <\/button>\n      <div class=\"faq-answer\">\n        <div class=\"faq-answer-inner\">\n          <p>MoyaHost&#8217;s primary deployment platform is <strong>Botpress<\/strong>, a conversational AI platform that gives us high control over conversation flows, integrations, and behaviour without requiring bespoke development for every deployment. Botpress supports connections to all major large language models including OpenAI&#8217;s GPT-4 series and Anthropic&#8217;s Claude models.<\/p>\n          <p>For workflow automation beyond conversational interfaces \u2014 connecting systems, automating repetitive back-office tasks, and building multi-step processes \u2014 we work with <strong>Make (formerly Integromat)<\/strong> and <strong>n8n<\/strong>, both of which provide visual automation builders with extensive integration libraries covering CRMs, email platforms, booking systems, e-commerce platforms and more.<\/p>\n          <p>For clients with specific enterprise requirements, we are <strong>platform-agnostic<\/strong> and can work with Voiceflow, Landbot, or custom API-based architectures depending on what the use case demands. We do not restrict clients to a single vendor and we document all platform choices in our engagement agreements so there is no unexpected lock-in.<\/p>\n          <p>Our recommendation always starts with the use case and works backwards to the platform \u2014 not the other way around.<\/p>\n        <\/div>\n      <\/div>\n    <\/div>\n\n    <!-- Q5 -->\n    <div class=\"faq-item\">\n      <button class=\"faq-question\" aria-expanded=\"false\" onclick=\"toggleFaq(this)\">\n        <span class=\"faq-num\">5<\/span>\n        <span class=\"faq-q-text\">What is BotPress and why do businesses use it?<\/span>\n        <svg class=\"faq-chevron\" viewBox=\"0 0 20 20\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path d=\"M5 7.5L10 12.5L15 7.5\" stroke=\"#1A2B26\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n        <\/svg>\n      <\/button>\n      <div class=\"faq-answer\">\n        <div class=\"faq-answer-inner\">\n          <p>Botpress is an <strong>open-source conversational AI platform<\/strong> that enables businesses to build, deploy, and manage AI-powered chatbots and virtual agents. It provides a full development environment with a visual flow builder, a knowledge base layer, native LLM integration, and an extensive library of pre-built integrations covering WhatsApp, web chat, Slack, Telegram, CRM systems, and more.<\/p>\n          <p>Businesses use Botpress because it sits at the right point on the complexity curve for most commercial applications: <strong>more capable and controllable than lightweight tools<\/strong> like Tidio or Intercom&#8217;s basic bots, but faster and cheaper to deploy than fully custom-built solutions.<\/p>\n          <p>The platform handles infrastructure \u2014 hosting, scaling, logging, and deployment \u2014 so developers and agencies like MoyaHost can focus on conversation design, knowledge base quality, and integration logic. From a commercial standpoint, Botpress offers a free tier suitable for low-volume deployments, with paid plans scaling by monthly active users.<\/p>\n          <p>MoyaHost has deep experience with Botpress architecture and maintains up-to-date knowledge of its capabilities and best practices \u2014 important because the platform evolves rapidly and implementation patterns change as new features are released.<\/p>\n        <\/div>\n      <\/div>\n    <\/div>\n\n    <!-- Q6 -->\n    <div class=\"faq-item\">\n      <button class=\"faq-question\" aria-expanded=\"false\" onclick=\"toggleFaq(this)\">\n        <span class=\"faq-num\">6<\/span>\n        <span class=\"faq-q-text\">How long does it take to build an AI chatbot?<\/span>\n        <svg class=\"faq-chevron\" viewBox=\"0 0 20 20\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path d=\"M5 7.5L10 12.5L15 7.5\" stroke=\"#1A2B26\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n        <\/svg>\n      <\/button>\n      <div class=\"faq-answer\">\n        <div class=\"faq-answer-inner\">\n          <p>A simple AI chatbot \u2014 handling FAQs, collecting contact information, and escalating to a human \u2014 can be built, tested, and deployed in <strong>two to three weeks<\/strong> from the point of having complete content and a signed agreement.<\/p>\n          <p>A more complex bot involving CRM integration, order management system connections, multi-step qualification flows, or Dutch and English language support is typically <strong>four to eight weeks<\/strong> depending on the availability of client-side resources and integration complexity.<\/p>\n          <p>The limiting factor in most deployments is not the technical build \u2014 it is <strong>content and access<\/strong>. The three most common causes of delay are: an incomplete knowledge base; delayed access to API credentials or backend systems; and slow feedback turnaround during testing.<\/p>\n          <p>MoyaHost structures every engagement to front-load these requirements in the first week, using a content questionnaire and intake process designed to extract everything needed before a single flow is built. For clients who need a faster proof of concept, we offer a <strong>two-week rapid prototype<\/strong> that produces a working demo against your actual content \u2014 sufficient to test with real users before committing to a full production build.<\/p>\n        <\/div>\n      <\/div>\n    <\/div>\n\n    <!-- Q7 -->\n    <div class=\"faq-item\">\n      <button class=\"faq-question\" aria-expanded=\"false\" onclick=\"toggleFaq(this)\">\n        <span class=\"faq-num\">7<\/span>\n        <span class=\"faq-q-text\">Can an AI chatbot handle Dutch-language conversations?<\/span>\n        <svg class=\"faq-chevron\" viewBox=\"0 0 20 20\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path d=\"M5 7.5L10 12.5L15 7.5\" stroke=\"#1A2B26\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n        <\/svg>\n      <\/button>\n      <div class=\"faq-answer\">\n        <div class=\"faq-answer-inner\">\n          <p>Yes \u2014 modern large language models handle Dutch to a high standard. GPT-4 and Claude, the two models MoyaHost primarily works with, both produce <strong>fluent, natural Dutch<\/strong> and understand colloquial phrasing, regional variation, and business-register language without requiring separate Dutch-language training.<\/p>\n          <p>A Botpress chatbot backed by one of these models will converse naturally in Dutch, handle mixed Dutch-English input (common in Dutch business contexts), and produce responses that do not read as translated from English. Dutch customers consistently report that language quality is not a barrier with well-configured AI chatbots.<\/p>\n          <p>The more important variable is the <strong>quality of the knowledge base content<\/strong> provided. If the source material is clear and well-structured in Dutch, the model draws on it accurately. If the source material is thin or written in English and expected to be translated on the fly, quality will suffer.<\/p>\n          <p>MoyaHost configures every Dutch-language deployment with Dutch-first knowledge bases, Dutch system prompts, and Dutch escalation messaging. We also test with native Dutch speakers before go-live to catch phrasing that is grammatically correct but unnatural in a customer service context. For businesses serving both Dutch and international customers, we build <strong>automatic language detection<\/strong> that routes conversations appropriately based on the user&#8217;s opening message.<\/p>\n        <\/div>\n      <\/div>\n    <\/div>\n\n    <!-- Q8 -->\n    <div class=\"faq-item\">\n      <button class=\"faq-question\" aria-expanded=\"false\" onclick=\"toggleFaq(this)\">\n        <span class=\"faq-num\">8<\/span>\n        <span class=\"faq-q-text\">What is the difference between an AI chatbot and an AI voice agent?<\/span>\n        <svg class=\"faq-chevron\" viewBox=\"0 0 20 20\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path d=\"M5 7.5L10 12.5L15 7.5\" stroke=\"#1A2B26\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n        <\/svg>\n      <\/button>\n      <div class=\"faq-answer\">\n        <div class=\"faq-answer-inner\">\n          <p>An <strong>AI chatbot communicates through text<\/strong> \u2014 typically embedded in a website, WhatsApp, or messaging platform. An <strong>AI voice agent<\/strong> does the same through spoken conversation: the user speaks, the audio is transcribed to text, the AI generates a response, and that response is converted back to speech and played aloud. The underlying intelligence can be identical \u2014 both can use the same language model and knowledge base.<\/p>\n          <p>Voice agents introduce additional components: a speech-to-text engine, a text-to-speech engine, and telephony integration if handling phone calls. This makes them <strong>more expensive to build and more sensitive<\/strong> to audio quality, background noise, and accent variation.<\/p>\n          <p>For most Dutch SMBs, a text chatbot is the right starting point because it covers the majority of customer interactions at lower cost and with less technical complexity. <strong>Voice agents are most valuable<\/strong> for businesses that receive high volumes of inbound phone calls and want to automate initial routing or qualification before connecting to a human.<\/p>\n          <p>MoyaHost builds both. We recommend starting with a text chatbot to establish and validate your conversation flows before moving to voice, since the same content and logic can be adapted once proven.<\/p>\n        <\/div>\n      <\/div>\n    <\/div>\n\n    <!-- Q9 -->\n    <div class=\"faq-item\">\n      <button class=\"faq-question\" aria-expanded=\"false\" onclick=\"toggleFaq(this)\">\n        <span class=\"faq-num\">9<\/span>\n        <span class=\"faq-q-text\">Is MoyaHost compliant with the EU AI Act and GDPR?<\/span>\n        <svg class=\"faq-chevron\" viewBox=\"0 0 20 20\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path d=\"M5 7.5L10 12.5L15 7.5\" stroke=\"#1A2B26\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n        <\/svg>\n      <\/button>\n      <div class=\"faq-answer\">\n        <div class=\"faq-answer-inner\">\n          <p>Yes. MoyaHost operates a <strong>documented compliance programme<\/strong> covering both the EU AI Act and GDPR, and builds compliance requirements into every client deployment by default rather than as an optional add-on.<\/p>\n          <p>Under the EU AI Act, the chatbot systems MoyaHost builds for SMB customer service, lead capture, and e-commerce fall into the <strong>limited-risk category<\/strong>. Every chatbot we deploy includes a clear disclosure that the user is interacting with an AI system (Article 50), human escalation paths, conversation logging, and documented oversight procedures. We screen every engagement against Article 5 (prohibited practices) before signing.<\/p>\n          <p>On <strong>GDPR<\/strong>, MoyaHost acts as a data processor when operating chatbots on behalf of clients. We maintain Data Processing Agreements with all clients handling personal data through their bot, a published sub-processor list covering Botpress, OpenAI, and Anthropic, and configurable conversation log retention periods.<\/p>\n          <p>Our registered address is in the Netherlands, making the <strong>Autoriteit Persoonsgegevens (AP)<\/strong> our lead supervisory authority. We publish a full EU AI Act Compliance Statement on our website and are happy to share compliance documentation with clients who require it for their own due diligence.<\/p>\n        <\/div>\n      <\/div>\n    <\/div>\n\n    <!-- Q10 -->\n    <div class=\"faq-item\">\n      <button class=\"faq-question\" aria-expanded=\"false\" onclick=\"toggleFaq(this)\">\n        <span class=\"faq-num\">10<\/span>\n        <span class=\"faq-q-text\">How do I get started with AI automation for my business?<\/span>\n        <svg class=\"faq-chevron\" viewBox=\"0 0 20 20\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path d=\"M5 7.5L10 12.5L15 7.5\" stroke=\"#1A2B26\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n        <\/svg>\n      <\/button>\n      <div class=\"faq-answer\">\n        <div class=\"faq-answer-inner\">\n          <p>The most effective starting point is not choosing a platform or deciding on a budget \u2014 it is <strong>identifying the single conversation your customers are already trying to have with you<\/strong> that you are not handling well. Look at your support inbox, WhatsApp messages, and contact form submissions from the last thirty days. What is the most common question? What takes your team the most time to answer? What enquiries arrive outside business hours and go unanswered until the morning?<\/p>\n          <p>The answer to those questions tells you where AI automation will have the highest immediate impact.<\/p>\n          <p>Once you have identified the use case, the next step is a structured conversation with an agency \u2014 not a sales call, but a proper intake session where scope, data requirements, audience, and integration needs are documented. This is how MoyaHost approaches every new engagement: we run a <strong>free 45-minute discovery session<\/strong> that produces a clear picture of what can be automated, what it will cost, how long it will take, and what the projected return on investment looks like in your specific context.<\/p>\n          <p>After that session, you have enough information to make an informed decision \u2014 whether that means proceeding with MoyaHost, pursuing another option, or deciding the timing is not right. <strong>There is no obligation attached.<\/strong> Book your discovery session at <a href=\"https:\/\/www.moyahost.ai\/contact\" style=\"color: var(--forest-l); font-weight: 600;\">moyahost.ai<\/a>.<\/p>\n        <\/div>\n      <\/div>\n    <\/div>\n\n  <\/div><!-- \/faq-list -->\n\n  <!-- CTA -->\n  <div class=\"cta-block\">\n    <div class=\"cta-text\">\n      <h2>Still have questions?<\/h2>\n      <p>Book a free 30-minute discovery session. We&#8217;ll map your highest-impact automation opportunity and outline exactly what a solution looks like \u2014 no obligation.<\/p>\n    <\/div>\n    <a href=\"https:\/\/www.moyahost.ai\/contact\" class=\"cta-btn\">\n      Book a free session\n      <svg width=\"16\" height=\"16\" viewBox=\"0 0 16 16\" fill=\"none\"><path d=\"M3 8h10M9 4l4 4-4 4\" stroke=\"currentColor\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/><\/svg>\n    <\/a>\n  <\/div>\n<\/div><!-- \/page-wrap -->\n\n<script>\n  function toggleFaq(btn) {\n    const item = btn.closest('.faq-item');\n    const isOpen = item.classList.contains('open');\n    \/\/ Close all\n    document.querySelectorAll('.faq-item').forEach(el => {\n      el.classList.remove('open');\n      el.querySelector('.faq-question').setAttribute('aria-expanded', 'false');\n    });\n    \/\/ Open clicked if it was closed\n    if (!isOpen) {\n      item.classList.add('open');\n      btn.setAttribute('aria-expanded', 'true');\n    }\n  }\n<\/script>\n\n<\/body>\n<\/html>\n","protected":false},"excerpt":{"rendered":"<p>MoyaHost.ai \u00b7 Netherlands AI Automation FAQ\u2014 Netherlands Everything Dutch SMBs ask before commissioning an AI chatbot or automation project. Straight answers, no jargon. 10 questions&hellip;<\/p>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-256","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/moyahost.ai\/nl\/wp-json\/wp\/v2\/pages\/256","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/moyahost.ai\/nl\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/moyahost.ai\/nl\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/moyahost.ai\/nl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/moyahost.ai\/nl\/wp-json\/wp\/v2\/comments?post=256"}],"version-history":[{"count":7,"href":"https:\/\/moyahost.ai\/nl\/wp-json\/wp\/v2\/pages\/256\/revisions"}],"predecessor-version":[{"id":264,"href":"https:\/\/moyahost.ai\/nl\/wp-json\/wp\/v2\/pages\/256\/revisions\/264"}],"wp:attachment":[{"href":"https:\/\/moyahost.ai\/nl\/wp-json\/wp\/v2\/media?parent=256"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}