fteg-ai-chat Urgent I0–I3 live

FTEG AI Chat — Product Plan

Omnichannel AI customer service. Merchants subscribe via fteg-erp. One inbox replies across website live chat, WhatsApp, Facebook Messenger, Instagram — with AI assist and human handoff.

Decision (Jul 2026)
Product name: fteg-ai-chat · engine: package-ai-chat.
Same product pattern as Reservation / AI Review — standalone hosts + ERP subscribe.
I3 live — inbox + website widget + Meta webhooks (WA / Messenger / IG).
Business model → compete with Respond.io Growth (EaseeBuy anchor) on features + local price.

Hosts (I1 live)

RoleURL / path
Publicai-chat-71649283.fteg.dev — landing · /demo widget
Backofficeai-chat-bo-71649284.fteg.dev — inbox + shops
APIai-chat-apis-71649285.fteg.dev — widget + Meta webhooks
App path/srv/www/fteg-products/ai-chat
Engine/srv/www/package-ai-chat

1. Layers

LayerPath / role
Product app /srv/www/fteg-products/ai-chat — public widget host + BO inbox + API
Engine package /srv/www/package-ai-chat — conversations, channels, AI, handoff
Billing fteg-erp catalog (B8 / I5) → Fiuu → provision tenant
CMS / sites Embed live-chat widget only — no engine install in CMS

2. Channels (MVP)

ChannelNotes
Website live chatJS widget + websocket/poll API
WhatsAppWhatsApp Cloud API or BSP
Facebook MessengerMeta Messaging API
InstagramIG messaging (Meta)
Human handoffAgent takes over thread; AI pauses
Non-goals (v1) — full contact-center ACD, voice/phone, SMS blast marketing, rebuild WhatsApp Business Manager UI.
Market bar (EaseeBuy) — must match Respond.io Growth for WhatsApp + website chat + AI first reply + human takeover + multi-officer inbox. Meta WhatsApp fees stay separate. Pricing draft + parity table: fteg-ai-chat-business.html.

3. Rollout (Track I)

  1. I0 — Plan + ecosystem map (this doc) — done
  2. I1 — Product shell + unified inbox BO — done
  3. I2 — Website live-chat widget + webhook API — done
  4. I3 — WhatsApp + Messenger + Instagram adapters — done
  5. I4 — AI auto-reply + knowledge base + human handoff — done
  6. I5 — fteg-erp catalog + subscribe (with B8) — done
  7. I6 — Conversation-Led Growth foundation (lifecycle + campaign tags + pre-qual routing) — done
  8. I7 — Retain: templates + consent-aware segmented broadcasts — done
  9. I8 — AWS hooks (application / EaseeScore / EaseeCollect) — done

4. Suggested start (next chat)

EaseeBuy go-live checklist:
1. ERP portal: create EaseeBuy client → subscribe AI Chat Pilot
2. BO shop → AWS: enable + inbound secret + outbound URL to AWS CRM
3. AWS calls POST /api/integrations/aws/{shop}/events (application.*, payment.*, score.updated)
4. Embed widget on EaseeBuy AWS site + Meta WA webhooks
5. Seed Knowledge + Templates; demo /demo copy prompts
Safeguards: no Singpass OTP in chat; promo needs marketing_consent