LoginSign Up
← Back to all sparks
C

Chatway

SUPPORT
Velocity6.3

Live chat widget and customer messaging tool for websites

chatway.app ↗

Chatway's bot learned to read the store; now the store can listen back

live-chatai-agentsecommercewoocommerceintegrationsself-service
◆Current state
Chatway is a live chat widget for small e-commerce sites, weighted toward WooCommerce and Shopify, with an AI support agent attached. The last three weeks added the two things that decide when and where the agent operates: webhooks that push conversation, contact, assignment and resolution events out to external tools from the existing Developer Tools panel, with per-event subscriptions and delivery logs; and AI Availability settings that schedule the agent by weekly time range, timezone and special dates rather than leaving it always on. Underneath, self-service and routing shipped earlier in August.
◆Where it's heading
The product keeps widening from a widget into a support stack, and the recent work is about control and connection rather than new answering ability. The August spark grounded the AI agent in live store data; since then Chatway has added the Help Center it can point to, routing that decides who takes a conversation, an outbound event stream so other systems can react, and now a schedule that says when the AI is allowed to be the one responding. The consistent thread is that merchants are being given switches over an agent they were first given a reason to trust.
◆Prediction
With events flowing out and a schedule governing the agent, the obvious next gap is inbound control — triggering Chatway actions from outside, or handing off to a human on a rule rather than a reply. The entries do not indicate which, and no API beyond webhooks is mentioned.

◆Recent moves

  1. 2d ago

    Connect Chatway to other tools with Webhooks

    Webhooks push Chatway events — new conversations and messages, contact updates, agent assignments, resolutions, automation triggers — into external tools, managed from the existing Developer Tools panel with per-event subscriptions and delivery logs. It makes Chatway a component other systems can react to rather than a closed widget, though it extends a developer surface that was already there.

    View source ↗
  2. 5d ago

    More control over AI agent availability

    AI Availability settings let merchants keep the agent always on or give it a weekly schedule with multiple time ranges, a timezone and special dates for holidays. After spending August making the AI agent more capable, Chatway is now handing merchants the switch that decides when it answers at all.

    View source ↗
  3. 9d ago

    Introducing the Chatway Affiliate Program

    A referral program paying 20% of successful payments including renewals, upgrades and AI credit purchases, with a dashboard and a $100 payout threshold. It is distribution work rather than product, and the inclusion of AI credits in the commission base says where the revenue is expected to come from.

    View source ↗
  4. 13d ago

    Route chats based on visitor replies

    Chat Routing sends conversations to a specific agent based on which of up to four quick replies a visitor picks, with an optional automatic acknowledgement, and can route to the AI agent where enabled. It is the first piece of the stack that arbitrates between the human and AI paths the rest of the month built out.

    View source ↗
  5. 21d ago

    Create your own Help Center

    A hosted, customizable Help Center on a chatway.help subdomain with categorized articles, rich media and the chat widget embedded in it. This is the self-service layer of the support stack, giving the widget somewhere to send people instead of answering everything in the conversation.

    View source ↗
  6. 23d ago

    Your AI agent can now access WordPress & WooCommerce data

    ⚡ SPARK

    The release the rest of this window depends on: grounding the AI agent in live WordPress and WooCommerce data. Everything since has been scaffolding around it — where to send people, who handles a chat, when the agent is on, and now where its events go.

    View source ↗