Post-purchase AI support

Keep every buyer supported after checkout.

BYC Growth Plan gives your store a private, context-aware AI chatbot. One tenant per account, real data answers, and no cross-access between customers.

Get the Growth Plan See how it works

Multi-tenant isolation
Answers from your data
Groq / OpenAI powered

BYC Support Assistant

Built for stores that care about retention.

Tenant isolation

Every account gets a unique tenant_id. RLS policies block any cross-account reads, period.

Context-aware answers

The AI retrieves your orders, policies, and FAQs before it replies, so answers are grounded in real data.

Unlimited team members

Add your support team under one tenant. Everyone sees the same history without sharing logins.

Persistent chat history

Conversations are stored per tenant and user, so context carries across sessions.

Model flexibility

Switch between Groq and OpenAI backends per message. Use the model that fits the question.

Secure by default

Server functions validate tenant membership before touching data. No client-side secrets.

Pricing

Growth Plan

₹999 per tenant. Unlock the AI chatbot, context retrieval, and team access.

₹999

one-time per tenant

Unlock access

Payment integration is a placeholder. Sign-up is free during preview.

Embed

Add the widget to any site.

Copy one script tag and set your tenant context with window.BYC_CONFIG. The widget renders a floating chat bubble in the bottom-right corner.

HTML / Next.js snippet

<script>
  window.BYC_CONFIG = {
    tenantId: "YOUR_TENANT_ID",
    tenantCode: "acme-store",
    userId: "USER_ID",
    email: "customer@example.com",
    name: "Riya",
    company: "Acme",
    growthPlan: "Growth Plan",
    position: "bottom-right",
    primaryColor: "#ea580c",
    open: false
  };
</script>
<script
  src="https://byc-growth-support.byc-support.poke.site/widget.js"
  async
></script>

For secure deployments, generate a signed JWT on your server and pass it as token instead of exposing tenantId/userId in HTML.

How context flows

1JWT token - preferred for production. Verifies identity on the server.
2URL params - useful for direct iframe embeds.
3window.BYC_CONFIG - easiest for script-tag installs.

The backend uses the provided context to set tenant isolation and include the user's name, company, and growth plan in every LLM prompt.

Onboarding

Push signup data automatically.

POST user details and an ElevenLabs call transcript to /api/onboard. The AI will remember them in every future chat for that tenant.

curl snippet

curl -X POST "https://byc-growth-support.byc-support.poke.site/api/onboard" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantId": "YOUR_TENANT_ID",
    "email": "riya@acme.example",
    "name": "Riya",
    "companyDetails": {
      "company": "Acme",
      "website": "acme.example",
      "plan": "Growth Plan"
    },
    "elevenLabsTranscript": "Customer wants AI support for post-purchase questions."
  }'

In production, protect this endpoint with an API key or signed secret. The current endpoint is open for preview so external sites can test the integration.