CushLabs Messenger

One Cloudflare Worker serves every connected Page. Each inbound webhook is routed by page_id to that tenant's own system prompt, per-Page access token, structured business facts, and tenant-scoped vector index — so onboarding a client is a config and content operation, not a deploy. A two-layer router sends pleasantries to Claude Haiku and real questions to Claude Sonnet with RAG context. Hard facts (hours, pricing, address, booking URL) live as structured records injected verbatim and marked authoritative, so a price change is a one-field edit that is live on the next message with no re-embed. When a customer wants a person, the bot goes quiet and alerts the operator, who replies from the Page Inbox.

Key Features

• Answers customer questions in under 5 seconds, 24/7 — nights, weekends, holidays
• English and Spanish automatically, following whatever the customer writes, with no manual switching
• Answers come from the client's own approved content — it never invents a price or makes up a promise
• Hours and pricing come back exact every time, because they are stored as data, not as prose the AI has to interpret
• Hands off to a person with full context when a customer asks, alerts the owner, then resumes on its own
• One Worker, many client Pages — a new client onboards as configuration, with no code change and no Meta re-review