EaseeBuy × FTEG AI Chat — go-live handoff

For the EaseeBuy engineering / ops team · FTEG shop is ready · Loading…

FTEG internal sign-off Try demo widget Print / PDF

Status update (2026-08-13): EaseeBuy rejected the AI Chat subscription. This handoff is retained for history only — do not treat as an active go-live request unless commercial is reopened. FTEG has cancelled the pilot subscription and disabled the shop widget.

Archived — FTEG host setup that was prepared before rejection. Shop erp-easeebuy had KB, templates, and AWS inbound ready. Steps below are kept only if the deal is revived.

Do not put Singpass passwords or OTPs through chat. Marketing / promo templates only send when the conversation has marketing consent. Meta WhatsApp conversation fees are billed by Meta separately from the FTEG AI Chat plan.

Your checklist (3 items)

Embed the widget on member / marketing pages (snippet below).
Wire AWS → FTEG inbound events with the Bearer secret from your FTEG portal / FTEG contact (not printed here).
Send us your outbound webhook URL (+ optional secret) so FTEG can push replies / template triggers back to EaseeBuy. Then connect Meta WhatsApp if needed.

1. Widget embed

Paste before `</body>` on pages that should show chat

Shop UUID is already provisioned for EaseeBuy.

<script src="https://ai-chat-apis-71649285.fteg.dev/api/widget/script"
  data-api="https://ai-chat-apis-71649285.fteg.dev"
  data-shop="3415c0e1-5208-486f-8349-b94f295de20f"
  async></script>

Preview (FTEG-hosted): open demo

2. AWS → FTEG (inbound)

Events

POST https://ai-chat-apis-71649285.fteg.dev/api/integrations/aws/3415c0e1-5208-486f-8349-b94f295de20f/events
Authorization: Bearer <inbound secret — ask FTEG / see portal BO Integrations>
Content-Type: application/json

Catalog (read)

GET https://ai-chat-apis-71649285.fteg.dev/api/integrations/aws/3415c0e1-5208-486f-8349-b94f295de20f/catalog

Inbound secret is already generated on the FTEG shop. Request it via your FTEG contact or Client Portal → My products → AI Chat → Integrations (SSO).

3. EaseeBuy → FTEG (outbound) + Meta

Reply to FTEG with

Outbound webhook URL (HTTPS) — where FTEG should POST events back to EaseeBuy
Outbound secret (optional) — if you want FTEG to send a shared Bearer / HMAC
Environments — stage vs production URLs if different
Meta WA — if using WhatsApp: confirm Cloud API WABA / phone number; FTEG will share the webhook callback URL for Channels

After we receive the outbound URL, FTEG will save it on the shop (BO Integrations) and confirm with a test ping.

Access you already have

FTEG Client Portal: fteg-client-83911523.fteg.dev/portal/login — use the owner account FTEG issued
AI Chat backoffice: open from Portal → My products (SSO)
Staging site (yours): stage.easeebuy.com.sg

Suggested email subject

EaseeBuy AI Chat — FTEG ready; need widget embed + outbound URL + Meta

Attach or link this page. Internal FTEG tracker: fteg-easeebuy-go-live.html

Your checklist (3 items)

1. Widget embed

Paste before </body> on pages that should show chat

2. AWS → FTEG (inbound)

Events

Catalog (read)

3. EaseeBuy → FTEG (outbound) + Meta

Reply to FTEG with

Access you already have

Suggested email subject

Paste before `</body>` on pages that should show chat