<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://routme.io/</id>
  <title>RoutMe guides and blog</title>
  <subtitle>Answer-first guides and engineering notes on AI agents for customer conversations.</subtitle>
  <link rel="self" type="application/atom+xml" href="https://routme.io/feed.xml"/>
  <link rel="alternate" type="text/html" href="https://routme.io/"/>
  <updated>2026-11-20T00:00:00.000Z</updated>
  <author><name>RoutMe team</name></author>
  <entry>
    <id>https://routme.io/learn/ai-chatbot-for-banking-and-fintech</id>
    <title>AI chatbot for banking and fintech: what to allow</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/ai-chatbot-for-banking-and-fintech"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Buyer guide"/>
    <summary>A careful guide to AI chat in banking and fintech: informational answers only, strict verification, no advice, auditable tool calls and fast handoff.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/ai-chatbot-for-clinics-and-appointments</id>
    <title>AI chatbot for clinics and appointments</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/ai-chatbot-for-clinics-and-appointments"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Buyer guide"/>
    <summary>What an AI chatbot can safely do for a clinic: show real availability, answer preparation questions, hand clinical questions to staff. No medical advice.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/ai-chatbot-for-real-estate</id>
    <title>AI chatbot for real estate agencies</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/ai-chatbot-for-real-estate"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Buyer guide"/>
    <summary>Answer listing questions, arrange viewings and capture enquiry details with an AI chatbot, while offers and contracts stay with a person.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/ai-chatbot-for-saas-support</id>
    <title>AI chatbot for SaaS support: setup and limits</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/ai-chatbot-for-saas-support"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbook"/>
    <summary>How a SaaS team can use an AI chatbot for plan, usage and how-to questions, using account lookups and help docs, with bugs and billing routed to people.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/ai-chatbot-for-travel-businesses</id>
    <title>AI chatbot for travel and hospitality businesses</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/ai-chatbot-for-travel-businesses"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Buyer guide"/>
    <summary>How hotels, tour operators and travel agencies can use an AI chatbot on WhatsApp and web chat: booking status, policies, check-in and clean handoff.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/how-to-add-an-ai-chat-widget-to-your-online-store</id>
    <title>How to add an AI chat widget to your online store</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/how-to-add-an-ai-chat-widget-to-your-online-store"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbook"/>
    <summary>Add an AI chat widget by placing one script on each storefront page and connecting read-only data. Steps for Shopify, WooCommerce, Wix and more.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/how-to-connect-a-database-to-an-ai-agent-safely</id>
    <title>How to connect a database to an AI agent safely</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/how-to-connect-a-database-to-an-ai-agent-safely"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbook"/>
    <summary>Use a read-only role, views with only needed columns, row scoping, query validation and timeouts so an AI agent can read your data without risk.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/how-to-connect-your-rest-api-to-an-ai-agent</id>
    <title>How to connect your REST API to an AI agent</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/how-to-connect-your-rest-api-to-an-ai-agent"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="How it works"/>
    <summary>Turn an existing REST API into safe AI agent tools: pick read-only endpoints from your OpenAPI spec, scope credentials, describe each tool and test.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/how-to-measure-ai-support-quality</id>
    <title>How to measure AI support quality</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/how-to-measure-ai-support-quality"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbook"/>
    <summary>Define deflection, resolution, containment and handoff rate precisely, then add sampling and customer signals to judge AI support without benchmarks.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/how-to-migrate-from-a-rule-based-chatbot</id>
    <title>How to migrate from a rule-based chatbot</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/how-to-migrate-from-a-rule-based-chatbot"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbook"/>
    <summary>Move from a decision-tree chatbot to an AI agent in stages: audit old flows, reuse content, connect live data, run both in parallel and keep a fallback.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/how-whatsapp-business-api-pricing-works</id>
    <title>How WhatsApp Business API pricing works</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/how-whatsapp-business-api-pricing-works"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Buyer guide"/>
    <summary>WhatsApp Business API pricing is based on message categories and conversation rules, not a flat seat fee. Learn the model and what else adds to the bill.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/mcp-vs-rest-api-vs-rag-for-support</id>
    <title>MCP vs REST API vs RAG for customer support</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/mcp-vs-rest-api-vs-rag-for-support"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="How it works"/>
    <summary>How MCP, a plain REST API and RAG differ, what each is good for in customer support, and how they combine instead of competing.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/prompt-injection-and-read-only-tools</id>
    <title>Prompt injection and how read-only tools limit it</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/prompt-injection-and-read-only-tools"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="How it works"/>
    <summary>What prompt injection is, why customer-facing AI agents are exposed to it, and how read-only tools, scoped credentials and handoff rules limit the damage.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/whatsapp-24-hour-customer-service-window</id>
    <title>The WhatsApp 24-hour customer service window</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/whatsapp-24-hour-customer-service-window"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Fundamentals"/>
    <summary>The 24-hour window lets a business reply freely after a customer writes. Learn when it opens, what resets it and what to do once it closes.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/what-is-grounding-and-how-to-test-it</id>
    <title>What is grounding in AI support, and how to test it</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/what-is-grounding-and-how-to-test-it"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Fundamentals"/>
    <summary>Grounding means every claim an AI agent makes traces to a document or a live lookup. Learn how to build a test set that catches invented answers.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/what-to-put-in-an-ai-agents-instructions</id>
    <title>What to put in an AI agent's instructions</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/what-to-put-in-an-ai-agents-instructions"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbook"/>
    <summary>A practical template for AI support agent instructions: role, scope, tone, tools, refusals, handoff rules and examples, plus how to test and revise them.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/whatsapp-business-app-vs-api</id>
    <title>WhatsApp Business App vs WhatsApp Business API</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/whatsapp-business-app-vs-api"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Buyer guide"/>
    <summary>The Business App suits small teams answering chats by hand, while the API powers automation, AI agents and shared inboxes. Learn the real trade-offs.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/whatsapp-message-templates-and-approval</id>
    <title>WhatsApp message templates and approval</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/whatsapp-message-templates-and-approval"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="How it works"/>
    <summary>WhatsApp templates are pre-approved messages for reaching customers outside the 24-hour window. See the categories, how review works and why they fail.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/whatsapp-opt-in-rules-for-businesses</id>
    <title>WhatsApp opt-in rules for businesses</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/whatsapp-opt-in-rules-for-businesses"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbook"/>
    <summary>WhatsApp requires a business to get clear permission before sending messages. Learn what counts as valid opt-in, how to record it and how to honor opt-outs.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/when-an-ai-agent-should-hand-off-to-a-human</id>
    <title>When an AI agent should hand off to a human</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/when-an-ai-agent-should-hand-off-to-a-human"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbook"/>
    <summary>Which situations should always go to a person, which can wait one more attempt, and how to write those triggers as rules instead of hoping a model decides.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/move-customer-support-workflow-from-n8n-to-routme</id>
    <title>How to move a customer support workflow from n8n to RoutMe</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/move-customer-support-workflow-from-n8n-to-routme"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbooks"/>
    <summary>A step-by-step migration of a WhatsApp support workflow from n8n to RoutMe Flows: node mapping, the agent step, connectors and a checklist to cut over safely.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/n8n-vs-routme-for-customer-conversations</id>
    <title>n8n vs RoutMe for customer conversations: when to use which</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/n8n-vs-routme-for-customer-conversations"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Product"/>
    <summary>n8n is a general workflow engine and RoutMe is built for customer conversations. Here is when each is the right tool, and how teams use both together.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/do-you-still-need-zapier-for-whatsapp-customer-support</id>
    <title>Do you still need Zapier for WhatsApp customer support?</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/do-you-still-need-zapier-for-whatsapp-customer-support"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbooks"/>
    <summary>Probably not for the support part. See what a Zap does in a WhatsApp support setup, what RoutMe Flows cover instead, and where Zapier is still the right tool.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/whatsapp-without-twilio-cloud-api-connection-explained</id>
    <title>WhatsApp without Twilio: how the Cloud API connection works</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/whatsapp-without-twilio-cloud-api-connection-explained"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="WhatsApp"/>
    <summary>You can run WhatsApp support without your own Twilio account. Learn how Embedded Signup connects the Cloud API directly, and what a BSP adds that you may not need.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/twilio-whatsapp-alternatives-cloud-api-bsp-managed-agent</id>
    <title>Twilio WhatsApp alternatives: Cloud API, BSP or managed agent</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/twilio-whatsapp-alternatives-cloud-api-bsp-managed-agent"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="WhatsApp"/>
    <summary>Three ways to run WhatsApp support besides your own Twilio build: the direct Cloud API, another BSP, or a managed agent platform. Pros, cons and who each suits.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/replace-the-zap-where-is-my-order-automation</id>
    <title>Replace the Zap: a where-is-my-order automation, no glue code</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/replace-the-zap-where-is-my-order-automation"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbooks"/>
    <summary>Build a where-is-my-order WhatsApp flow without Zapier or glue code. Trigger, order lookup tool, reply, and a fallback to a person, step by step in RoutMe Flows.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/hidden-maintenance-cost-self-hosted-n8n-whatsapp-bot</id>
    <title>The hidden maintenance cost of a self-hosted n8n WhatsApp bot</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/hidden-maintenance-cost-self-hosted-n8n-whatsapp-bot"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Engineering"/>
    <summary>A self-hosted n8n WhatsApp bot works on day one. Here is the ongoing work it creates: hosting, upgrades, webhooks, templates, retries, monitoring and prompt safety.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/appointment-reminders-and-follow-ups-without-zapier</id>
    <title>Appointment reminders and follow-ups without Zapier</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/appointment-reminders-and-follow-ups-without-zapier"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbooks"/>
    <summary>Send WhatsApp appointment reminders and follow-ups with RoutMe Flows: an external event trigger, an approved template, wait steps and a reply path. No Zapier needed.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/from-diy-chatbot-stack-to-managed-agent-openai-n8n-twilio-checklist</id>
    <title>From DIY chatbot stack to managed agent: a migration checklist</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/from-diy-chatbot-stack-to-managed-agent-openai-n8n-twilio-checklist"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbooks"/>
    <summary>Moving off an OpenAI, n8n and Twilio chatbot stack? This checklist covers inventory, WhatsApp number, templates, data access, prompts, handoff, testing and cutover.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/connect-systems-without-glue-code-mcp-apis-read-only-databases</id>
    <title>Connect your systems without glue code: MCP, APIs, databases</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/connect-systems-without-glue-code-mcp-apis-read-only-databases"/>
    <published>2026-11-20T00:00:00.000Z</published>
    <updated>2026-11-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Engineering"/>
    <summary>How RoutMe reaches your data without glue code: MCP servers, your own APIs and read-only database views. What each is, when to use it and how to keep it safe.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/ai-chatbot-for-shopify-what-to-look-for</id>
    <title>AI chatbot for Shopify: what to look for</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/ai-chatbot-for-shopify-what-to-look-for"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Buyer guide"/>
    <summary>A practical checklist for choosing an AI chatbot for a Shopify store, from theme install and data access to read-only tools, handoff and honest roadmaps.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/how-an-ai-agent-looks-up-order-status-safely</id>
    <title>How an AI agent looks up order status safely</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/how-an-ai-agent-looks-up-order-status-safely"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="How it works"/>
    <summary>A safe order lookup verifies the customer, calls a narrow read-only tool, returns only needed fields and logs the call. See the design step by step.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/how-to-automate-returns-safely</id>
    <title>How to automate returns safely</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/how-to-automate-returns-safely"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbook"/>
    <summary>Automate returns by letting an AI assistant check eligibility against policy and purchase date, explain steps, and route the request, with approval left to rules or people.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/how-to-choose-an-ai-customer-support-agent</id>
    <title>How to choose an AI customer support agent</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/how-to-choose-an-ai-customer-support-agent"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Buyer guide"/>
    <summary>A neutral buyer's guide with an evaluation checklist for AI customer support agents: data access, grounding, safety, handoff, channels, pricing and proof.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/how-to-reduce-wismo-tickets</id>
    <title>How to reduce WISMO tickets</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/how-to-reduce-wismo-tickets"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbook"/>
    <summary>WISMO tickets are where-is-my-order questions. Reduce them with proactive updates, self-serve tracking and a read-only assistant that answers from order data.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/human-handoff-best-practices</id>
    <title>Human handoff best practices for AI support</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/human-handoff-best-practices"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbook"/>
    <summary>Design the handoff from an AI assistant to a person: clear triggers, full context, a warm message and a measured queue so customers never repeat themselves.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/rag-vs-tools-for-customer-support</id>
    <title>RAG vs tools for customer support</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/rag-vs-tools-for-customer-support"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="How it works"/>
    <summary>RAG retrieves passages from documents; tools call live systems. Learn when to use each for customer support answers and why most stores need both.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/what-are-ag-ui-and-a2ui</id>
    <title>What are AG-UI and A2UI? Generative UI protocols</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/what-are-ag-ui-and-a2ui"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Fundamentals"/>
    <summary>AG-UI streams events between an AI agent and an app, and A2UI describes interface components the agent can ask for. Here is how they fit together.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/what-does-read-only-ai-mean</id>
    <title>What does read-only AI mean, and why use it?</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/what-does-read-only-ai-mean"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Fundamentals"/>
    <summary>Read-only AI can look up and show information but cannot change it. Learn how read-only is enforced for a support assistant and what it protects against.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/what-is-an-ai-shopping-assistant</id>
    <title>What is an AI shopping assistant?</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/what-is-an-ai-shopping-assistant"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Fundamentals"/>
    <summary>An AI shopping assistant answers shopper questions in chat using a store's own catalog, orders and policies. Here is how it works and where it stops.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/what-is-mcp-and-why-it-matters-for-customer-support</id>
    <title>What is MCP and why it matters for customer support</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/what-is-mcp-and-why-it-matters-for-customer-support"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Fundamentals"/>
    <summary>The Model Context Protocol lets an AI assistant call tools on your own systems. Learn what MCP is and why it suits customer support, with read-only limits.</summary>
  </entry>
  <entry>
    <id>https://routme.io/learn/whatsapp-vs-website-chat-for-stores</id>
    <title>WhatsApp vs website chat for stores</title>
    <link rel="alternate" type="text/html" href="https://routme.io/learn/whatsapp-vs-website-chat-for-stores"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Comparison"/>
    <summary>Compare WhatsApp and website chat for ecommerce support, covering reach, rules like the 24-hour window, costs, identity and when a store needs both.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/wismo-is-a-lookup-problem</id>
    <title>Where-is-my-order is a lookup problem, not a conversation</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/wismo-is-a-lookup-problem"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbooks"/>
    <summary>Most where-is-my-order tickets ask for a fact that already exists in a system. That makes them the best first job for an AI assistant, if the lookup is safe.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/read-only-is-a-property-of-credentials</id>
    <title>Read-only is a property of credentials, not of prompts</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/read-only-is-a-property-of-credentials"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Engineering"/>
    <summary>Telling a model not to change anything is a request. Giving it credentials that cannot change anything is a guarantee. Here is how to build the second.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/ai-chat-on-shopify-without-an-app</id>
    <title>Adding AI chat to a Shopify store without an app</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/ai-chat-on-shopify-without-an-app"/>
    <published>2026-11-19T00:00:00.000Z</published>
    <updated>2026-11-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Product"/>
    <summary>RoutMe has no Shopify app, so the pattern is a script snippet in your theme plus your own read-only tools. Here is what that involves and what it does not.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/whatsapp-per-message-pricing-explained</id>
    <title>WhatsApp per-message pricing, explained without the spin</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/whatsapp-per-message-pricing-explained"/>
    <published>2026-08-12T00:00:00.000Z</published>
    <updated>2026-10-20T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="WhatsApp"/>
    <summary>Meta bills WhatsApp per message, not per conversation. Here is what that changed, what became chargeable in October 2026, and how to estimate a bill before you send anything.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/why-scripted-chatbots-fail</id>
    <title>Decision trees don't survive contact with customers</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/why-scripted-chatbots-fail"/>
    <published>2026-08-05T00:00:00.000Z</published>
    <updated>2026-08-05T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbooks"/>
    <summary>Every scripted bot works in the demo and falls over in production. The failure is structural, not a matter of adding more branches, and the fix is narrower than replacing the whole thing with an LLM.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/mcp-safe-data-access-for-support-agents</id>
    <title>Giving a support agent your data without giving it your database</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/mcp-safe-data-access-for-support-agents"/>
    <published>2026-07-28T00:00:00.000Z</published>
    <updated>2026-07-28T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Engineering"/>
    <summary>An agent that cannot read your systems can only apologise. Here is how to expose real data through MCP tools with a boundary you can actually defend in a security review.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/whatsapp-template-rejections</id>
    <title>Why your WhatsApp templates keep getting rejected</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/whatsapp-template-rejections"/>
    <published>2026-07-19T00:00:00.000Z</published>
    <updated>2026-07-19T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="WhatsApp"/>
    <summary>Template review failures are boringly predictable. The same handful of mistakes account for most of them, and all are fixable before you submit.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/designing-the-handoff-to-a-human</id>
    <title>The handoff is the part everyone gets wrong</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/designing-the-handoff-to-a-human"/>
    <published>2026-07-08T00:00:00.000Z</published>
    <updated>2026-07-08T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Playbooks"/>
    <summary>Most AI support deployments are judged on the conversations the agent could not finish. A good handoff is a design problem, not a fallback.</summary>
  </entry>
  <entry>
    <id>https://routme.io/blog/webhooks-retries-and-idempotency</id>
    <title>Your webhook will be delivered twice. Plan for it.</title>
    <link rel="alternate" type="text/html" href="https://routme.io/blog/webhooks-retries-and-idempotency"/>
    <published>2026-06-24T00:00:00.000Z</published>
    <updated>2026-06-24T00:00:00.000Z</updated>
    <author><name>RoutMe team</name></author>
    <category term="Engineering"/>
    <summary>Duplicate deliveries, out-of-order events, and the 20-second timeout are not edge cases on the WhatsApp Cloud API. They are Tuesday. Here is the handling that keeps them boring.</summary>
  </entry>
</feed>
