SUPPORT

Every door a customer can knock on. One room behind them all.

Email, the chat widget, messaging apps, phone calls and web forms are just doorways. Whichever one a customer uses, the request lands in the same queue, on the same timeline, under the same rules.

OMNICHANNEL INBOX

Three conversations walk in.
One queue takes them.

Channels are doorways to the same work item. Email threads by Message-ID onto the same ticket, and WhatsApp Business and Telegram are wired for two-way conversations into the same agent inbox as the web widget.

One person, one timeline - identity merge joins the same customer across channels instead of splitting them into strangers.

  • A channel is a doorway: email, the chat widget, public forms, messaging apps and the API all land as the same kind of work item in the same queue - whichever door is used, the item behaves identically once it is in.
  • Email threading is by Message-ID: replies land on the same ticket; auto-responders are detected and dropped so two robots cannot ping-pong tickets.
  • The brand is determined from the address that was written to, never from the message body - mail cannot be spoofed into another brand.
  • Connect your own WhatsApp Business number or Telegram bot - configurable per deployment - and conversations flow into the same inbox. Provider webhooks are signature-verified; tokens are write-only, encrypted on save, never shown again.
  • A chat that ends becomes a ticket automatically, carrying the full transcript; agents can also Convert to ticket mid-conversation, keeping the transcript linked.

What happens to a request after it lands - clocks, escalation, history - is the Ticketing story.

THE DOORWAYS

Connect the doors your customers already use.

Every door leads to the same queue. Each one keeps its own guarantees at intake.

Email

Replies thread by Message-ID onto the same ticket, and auto-responders are detected and dropped.

The brand comes from the address that was written to, never from the message body. Outbound replies go from the brand's own address and display name, with DKIM/SPF status shown - and an unconfigured sender records the reply as pending, never lost.

Chat widget

Built visually, dropped on your site with one snippet. Your greeting, an optional ask-name-and-email step, an origin allow-list and key rotation that kills a leaked embed instantly. Rate-limited against abuse.

Sub-3-second delivery with a resilient polling fallback

Intake forms

A deliberately small, safe field set - text, paragraph, email, dropdown, number - each field validated against its declared type.

Honeypot and rate limiting are always on; CAPTCHA is two switches - a per-form toggle plus a server-side provider key.

WhatsApp & Telegram

per deployment

Connect your own WhatsApp Business number or Telegram bot - configurable per deployment - and conversations flow into the same inbox.

Provider webhooks are signature-verified; tokens are write-only, encrypted on save, never shown again.

Voice

per deployment

Connect your telephony provider (Voiso) - configurable per deployment. Inbound calls land in the same queue; call audio stays with your provider.

The caller is identified by number, and a missed call or voicemail automatically becomes a ticket covered by SLA, routing and automation.

Exclusion list

Some senders should never become tickets. Exact email, domain, pattern or IP/CIDR - silently dropped at intake across every channel and recorded in the audit log.

BUILT VISUALLY

The widget and the forms are built on a canvas,
not in a config file.

Palette, canvas, inspector. Drag a field in, tune it in place, watch the live preview follow - and drop the widget on your site with one snippet.

The widget loads only on domains you allow-list; a rotated key kills a leaked embed.

  • The chat widget is built visually and dropped on your site with one snippet.
  • Widget setup covers the essentials: your greeting, an optional ask-name-and-email step, an origin allow-list (the widget refuses to load anywhere else), and key rotation that kills a leaked embed instantly. Rate-limited against abuse.
  • Intake forms are built visually too - palette, canvas, inspector - from a deliberately small, safe field set: text, paragraph, email, dropdown, number (no file upload). Each field is validated against its declared type.
  • Form mapping builds the ticket: one field becomes the title, an email/name field finds-or-creates the contact, the rest map onto custom fields - the result is a normal ticket, filtered, routed and SLA-covered.
  • Form protection: honeypot and rate limiting always on; CAPTCHA is two switches - a per-form toggle plus a server-side provider key (both needed to enforce).
  • Every submission is listed under View submissions, each row linking to the work item it created.
SELF-SERVICE PORTAL

Customers answer their own "what is the status?"

A separate login for customers, scoped to the brand: their tickets, their replies, the help center - and nothing of yours.

  • The customer portal is a separate, brand-scoped login: customers see only their own tickets, reply on them (the reply lands on the very same work item), and browse the help center. Portal accounts can never reach the internal workspace.
  • Fully themed per brand - logo, colors, name, language - across the portal, forms and widget; the "Powered by" footer disappears when white-labeled.
  • The help center sits inside the portal: search, a language switcher and "Was this helpful?" feedback on every article.
SURVEYS · CSAT / NPS / CES

Measure the feeling, not just the closure.

A closed ticket is not the same thing as a happy customer. Surveys fire on resolve or close and come back as numbers you can steer by.

  • CSAT, NPS and CES, triggered on resolve or close; results show the average, the promoters / passives / detractors breakdown and recent ratings.
  • Each survey link is personal, securely signed and usable exactly once - ratings cannot be stuffed or replayed.
  • End-of-chat rating in the widget: thumbs, stars or a short form.
HELP CENTER

The articles do the night shift.

The best ticket is the one that never needed to exist. Each brand gets a public help center that answers the easy questions before they reach the queue.

  • Search, a language switcher and "Was this helpful?" feedback, per brand; articles are versioned and translatable.
  • Themed per brand, like the portal, forms and widget.
  • When switched on, the assistant answers first from the brand's published help articles, with citations; when unsure it hands to a human.

How answers stay grounded and human-approved is the AI story.

See it on your own screens.

Book a walkthrough