Whoa Chat
Developers

Connect your app to the inbox

Whoa Chat talks to your app through a small connector you run on your own server. Your app signs the merchant in, posts what they did, and answers the inbox's questions about their store. Nothing reads your database directly.

Three things to wire up

  • Who is writing. A token signed with your app's secret names the store and the staff member, so identity never comes from the browser.
  • What they did. Installs, setup steps, plan changes and ratings go to the store's timeline.
  • What only your app knows. The inbox asks for a store's panel, your dashboard numbers or a store's status, and your app answers what it supports.
// Who is writing, signed with your app's secret.
const contact = contactToken(shop, { email, owner, timezone });

// What they did, for the team's timeline.
await postChatEvent(shop, {
  type: "setup",
  title: "Turned on the storefront widget",
  fields: [{ label: "Theme", value: themeName }],
});

// The inbox asking about a store, signed by Whoa Chat.
const req = verifyConnectorRequest(secret, token, rawBody);
if (req?.op === "storePanel") return { rows: [...] };

Built to stay out of your way

Every question is optional: your app answers the ones it supports, and the inbox leaves the rest out.

Signed both ways

Your app signs the merchant with its own secret. Whoa Chat signs every request it sends you with a secret issued to your workspace, with a hash of the body and a 60 second expiry.

Your data stays yours

The inbox shows what your app chooses to send, when it is asked. Nothing is copied out of your database.

Panels and dashboards as data

Store panels and dashboard charts are sent as simple blocks, so you add a number or a chart without waiting for us.

Good support is the cheapest way up the rankings

More reviews, a better rating and merchants who stay. Whoa Chat is built to move all three.