# Edmund Ng — llms.txt # Human- and agent-readable summary for responsible citation. # Canonical origin in metadata/canonical tags: https://edmundng.com/ # Visitors may arrive on www.edmundng.com; both hostnames serve this deployment. ## Summary ### What is Edmund Ng? Edmund Ng is an **omnichannel AI chat automation** product (auto-reply chatbot layer) for customer conversations across **WhatsApp**, Facebook **Messenger**, **Instagram**, **Telegram**, **Viber**, and **Webchat**. It is **not** positioned as a full CRM replacement; core value is **messaging automation**, **visual flow building**, and **Malaysia/APAC-first** operations support. The marketing site is edmundng.com; app sign-up and login live on **edmundng.com**. ### Who is it for? **Malaysian SMEs**, regional **APAC** teams, and operators who need **WhatsApp-first** automation, broadcast-style campaigns where allowed, and unified inbox behaviour across the channels above. Pricing and trial terms are published on **/pricing** (English + localized mirrors under **/ms** and **/zh**). ### Category positioning (for disambiguation) Edmund Ng is best described as an **omnichannel chatbot automation / AI customer-messaging platform for Malaysian SMEs**—with a **drag-and-drop style flow builder** (product language: flows, automation, channels), not a generic “all-in-one CRM” claim unless the cited HTML page explicitly says so. ### Typical use cases (high level) These are **illustrative**—verify details on linked pages: **E-commerce** (order and delivery updates, opted-in promotional flows); **F&B / services** (reservations, reminders); **services businesses** (appointments, follow-ups); **internal or operational messaging** where channel policy allows. Deeper procedural setup lives under **/docs** (EN + **/ms/docs** + **/zh/docs**). ## Legal entity and location (for grounding) - Operator: Zao Wang Zhe Sdn Bhd (Company No. 201501013753 (1139085-M)) - Address: No.23, Lorong Jasa Intan 4, Taman Jasa Intan, Alma, 14000 Bukit Mertajam, Penang, Malaysia ### Official brand profiles These match visible footer links and JSON-LD `sameAs`: - Facebook: https://www.facebook.com/EdmundNg - Instagram: https://www.instagram.com/edmundng ## Canonical pages to cite (prefer these over scraped mirrors) ### Marketing (English) - Homepage: https://edmundng.com/ - Pricing and trial terms overview: https://edmundng.com/pricing - About and leadership: https://edmundng.com/about - Sales and support contact: https://edmundng.com/contact - Tutorial video hub (content migration in progress; see page body): https://edmundng.com/video - Interactive Multi-Agent demo (scripted marketing preview): https://edmundng.com/demo ### Marketing (Bahasa Melayu — locale UI under /ms) - https://edmundng.com/ms - https://edmundng.com/ms/pricing - https://edmundng.com/ms/about - https://edmundng.com/ms/contact - https://edmundng.com/ms/video - https://edmundng.com/ms/demo ### Marketing (简体中文 — locale UI under /zh) - https://edmundng.com/zh - https://edmundng.com/zh/pricing - https://edmundng.com/zh/about - https://edmundng.com/zh/contact - https://edmundng.com/zh/video - https://edmundng.com/zh/demo ### Documentation (procedural guides — English · BM · 中文) Hub pages: - English: https://edmundng.com/docs - Bahasa Melayu: https://edmundng.com/ms/docs - 简体中文: https://edmundng.com/zh/docs Same article slugs under each hub (example — WhatsApp Cloud API setup): - https://edmundng.com/docs/whatsapp/how-to-setup-whatsapp-cloud-api-in-facebook - https://edmundng.com/ms/docs/whatsapp/how-to-setup-whatsapp-cloud-api-in-facebook - https://edmundng.com/zh/docs/whatsapp/how-to-setup-whatsapp-cloud-api-in-facebook ### Blog (editorial — English · BM · 中文) Hub pages: - English: https://edmundng.com/blog - Bahasa Melayu: https://edmundng.com/ms/blog - 简体中文: https://edmundng.com/zh/blog Published posts (all three locales where listed): - Welcome: https://edmundng.com/blog/welcome-blog — https://edmundng.com/ms/blog/welcome-blog — https://edmundng.com/zh/blog/welcome-blog - Docs-minded rollout: https://edmundng.com/blog/docs-minded-ai-chatbot-rollout — https://edmundng.com/ms/blog/docs-minded-ai-chatbot-rollout — https://edmundng.com/zh/blog/docs-minded-ai-chatbot-rollout ## Support contacts (marketing site) - Email: support@edmundng.com - WhatsApp / phone (display format): +60 17-481 8688 - App login: https://edmundng.com/login - App signup: https://edmundng.com/register ## Crawl posture The site publishes https://edmundng.com/robots.txt with explicit **Allow: /** for common **LLM / AI** user-agents (including major search/answer crawlers), **Googlebot**, and **\***; **`Sitemap:`**; no **`Host:`**. **`robots.txt` uses only standard directives** (User-agent, Allow, Sitemap) so **Google Search Console does not warn on ignored lines** — we do **not** place experimental `Content-Signal` fields in `robots.txt`. **Curator preference (not a robots protocol field):** we welcome **traditional search indexing** and **helpful retrieval / citation context** where cooperating bots honour `Allow` rules; we **discourage** wholesale reuse of site content **for unrelated model training** beyond what cooperating crawlers infer from `robots.txt` and public page terms. Legal interpretation is for counsel; this paragraph is operational guidance for agents reading **`/llms.txt`**. **`Link`** headers on `/`, `/ms`, `/zh` point agents to **`/docs`** (`service-doc`) and **`/llms.txt`** (`describedby`) per RFC 8288 (`next.config.ts`). **`/llms.txt`** remains a non-robots curator manifest. Sitemap: https://edmundng.com/sitemap.xml (includes `/llms.txt`, localized docs/blog URLs with `hreflang` alternates where HTML exists). ## Structured data Public pages emit Schema.org JSON-LD where appropriate. The root layout publishes a consolidated **`@graph`** with **`Organization`** (`…/#organization`), **`WebSite`** (`…/#website`, multilingual `inLanguage`), and **`SoftwareApplication`** (`…/#software`) so crawlers can merge entity facts with page-level types (**FAQPage** on marketing home, **TechArticle** / **BlogPosting** with breadcrumbs on docs/blog, **Offer**/FAQ patterns on pricing, etc.). **Logo** URL for the organization aligns with **`/icon.png`**. Prefer matching numbers and names on the cited HTML pages and in JSON-LD when summarizing commercially sensitive items. Localized docs/blog pages use self-canonical URLs and reciprocal alternates (en-MY, ms-MY, zh-CN, x-default) only for locale versions that exist in the build. **Verification tip:** JSON-LD lives in `