What suppy.chat is
suppy.chat gives a business one place to talk to the people using its website or app. Visitors open a chat bubble, write a message and stay on the page they were reading. Their conversation appears in a dashboard where the support team answers, assigns and closes it. The same conversation can be handled by an AI assistant first and by a person afterwards, without the customer having to repeat themselves or move to another channel.
The product is a hosted web service. A site owner adds one script tag to their pages (installation guide), configures the project in the dashboard, and invites the colleagues who should answer. There is nothing to run on your own servers, and the embed code contains a public project identifier rather than a secret key.
Who it is for
It is built for small and mid-sized teams that answer their own customers: online shops, service providers, SaaS products and mobile apps that need a support channel on the page rather than an email address at the bottom of it. Teams that already run support in several languages, or that want an assistant to take the repetitive questions before a person joins, are the clearest fit.
- Websites that want live chat with a real inbox behind it, not a contact form.
- Teams whose customers write in several languages and expect an answer in their own.
- Products that want AI answers grounded in their own documented knowledge, with a person a click away.
- Mobile apps that embed the same chat in a web view alongside their website.
How the product works
The widget loads asynchronously from suppy.chat and opens a conversation for the visitor. Messages are delivered live to the dashboard, where operators see who is on the site, what page a visitor started from and the history of the conversation. Optional modules extend that core: an AI assistant grounded in your knowledge base and uploaded knowledge files, live translation between the customer and the operator, voice messages, file attachments, email follow-up, NPS surveys and notification channels.
Handoff is explicit. The assistant is instructed to ask for a person when your knowledge does not cover the question, and an operator can take over any conversation from the dashboard, which switches that chat to human handling. Taking over does not delete the earlier messages: the customer keeps one thread.
What it costs
Pricing is built from two parts: seats for the people who answer, and modules for the capabilities a project switches on. A number of seats is included at no cost, additional seats are billed per seat, and each paid module is priced separately with a discount for projects on a paid plan. Current prices, included allowances and trial lengths are published on the plans page and in the machine-readable catalog at /api/pricing, which is the source both of them read.
Who runs it
suppy.chat is built and operated by the Vignette ID team - the people behind e-vignettes.eu - from Bratislava, Slovakia. Support, sales and security questions all go to support@suppy.chat, or through the chat widget on this site, which reaches the same inbox. The contact page lists every route, including the ones built for software agents.
The service runs on managed cloud infrastructure: Vercel for the application, Supabase (PostgreSQL and object storage) for the data. Our privacy page lists every subprocessor and what each one receives. A public status endpoint at /api/health reports whether the API can reach its database, and is the same check our own alerting watches.