Crisp Chat
Intercom
Tidio
tawk.to
Zendesk
LiveChat
Freshdesk
Drift
EchoRelay.dev
Paragon
Nango
Prismatic.io
Svix
Hookdeck
Companies have to deal with the increasing number of communications' channel that they have to handle in order to support their customers, furthermore, speed has become a key factor in generating a high satisfaction degree. Crisp has been built for SMB's in order to help them better scale their customers' relationship through a wide range of features:
Crisp offer the following features: * Shared Inbox * CRM * Live Chat * Knowledge Base * Chatbot * Drip campaigns (Email & InApp)
Used by more than 100 000 companies, Crisp offers a support 24/24 5 days a week to help every customer to scale their own customers relationship.
EchoRelay is a managed runtime for custom API integrations.
Describe one integration once: what comes in, the target system, credentials, the retry policy, and how the answer maps back. EchoRelay validates each inbound request, maps it, replies synchronously, passes streams through, fans out to multiple targets, or queues delivery with automatic retry, a dead-letter queue and replay.
Every configuration change is versioned. Preview, diff, dry run, schedule, publish and roll back. When a vendor changes their API or rotates a credential, you update the configuration and publish. Deploy nothing.
Build and operate each integration through the REST API, an MCP server so an AI agent can do the wiring, or the web panel. Free to start, no card required.
Docs: https://docs.echorelay.dev · Pricing: https://echorelay.dev/pricing
Crisp Chat EchoRelay.devEchoRelay.dev's answer:
What costs you money in an integration is not building it, it is the week a vendor renames a field. EchoRelay holds each integration as configuration instead of code you deploy: what comes in, where it goes, how it authenticates, what happens when the target is down, and how the answer maps back. Change any of it, preview the diff, publish, roll back if you were wrong. Deploy nothing. Every request leaves a delivery receipt, so when someone asks whether an order reached the warehouse, you answer from the record rather than from the logs.
EchoRelay.dev's answer:
Software teams that maintain a handful of custom integrations and have nobody whose job that is. There are developers, which is why they can run a runtime and read a mapping, but no integration team, so every vendor change competes with the product roadmap for the same people. Typically a shop wired into an ERP, a tax office, a fulfilment partner and a few marketing tools, or a product reselling a dozen vendor APIs behind one format of its own.
EchoRelay.dev's answer:
Most alternatives are one of two things: a catalogue of prebuilt connectors for popular products, or a workflow canvas. Neither helps with the adapter you had to write yourself, because the system on the other end is a customer's ERP or a partner's ordering API that nobody ships a connector for. EchoRelay is for that one. You describe it once and we operate it. The real comparison is the adapter service you would otherwise build and maintain in-house, and the difference is that a schema change becomes a mapping edit instead of a release.
EchoRelay.dev's answer:
It started from a pattern that shows up in almost every software team that talks to systems it does not control. The integrations that hurt are never the popular ones with a ready-made connector. They are the customer's ERP, the partner's ordering API, the tax office endpoint: one-off adapters somebody wrote once and now nobody wants to own.
The cost is not writing them. It is everything after. A vendor renames a field and someone edits adapter code, deploys it and hopes nothing else moved. A credential rotates and the adapter quietly breaks until a customer notices. The vendor has an outage and the retry logic you wrote yourself has to absorb it. Then someone asks whether an order actually arrived, and the honest answer is buried in logs.
EchoRelay was built to move that work out of application code. Describe the integration once as configuration: what comes in, where it goes, how it authenticates, what happens when the target is down, and how the answer maps back. When the vendor changes something, you change the mapping, preview the diff, publish, and roll back if you were wrong. Deploy nothing. Every request leaves a delivery receipt, so the question about that order has an answer you can point at.
EchoRelay.dev's answer:
Nothing you have to install or operate. From the outside EchoRelay is plain HTTP: a REST API, an MCP server so an AI agent can do the wiring, and a web panel. You send a request to an address and we handle the rest.
Based on our record, Crisp Chat seems to be more popular. It has been mentiond 13 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Some things just work. Our frontend is still Nuxt with Typescript and Tailwind (RIP). Our backend is still Go with Go-Gin. We still run on Hetzner bare-metal and use Firecracker for virtualization. Terraform still manages our infrastructure. Redis still handles caching. Crisp still powers customer support. AWS SES still sends our transactional emails. - Source: dev.to / 8 months ago
Importantly, in practice, most production "Chat" windows on websites were not fully automated. They were a blend of machine + human, where the chatbot handled basic queries and human agents stood by to take over for complex requests. This ensured customer satisfaction while keeping automation lightweight. A notable example, widely used today, is Crisp. I mention it here only because I consider it a competitor to... - Source: dev.to / about 1 year ago
It seems to be using https://crisp.chat/en/. - Source: Hacker News / about 1 year ago
Crisp - For users to reach out to me if there’s any problem via live chat. - Source: dev.to / over 1 year ago
Of course there are a bunch more tools that we use, some great, some not. Two notable ones are Crisp for customer support and AWS SES for sending out emails (we send out quite a lot of transactional emails!). - Source: dev.to / over 1 year ago
Intercom - Intercom is a customer relationship management and messaging tool for web businesses. Build relationships with users to create loyal customers.
Paragon - Paragon offers routing, scheduling, and transport logistics optimization software.
Tidio - Tidio is an AI customer support software suite. It merges help desk, live chat, chatbot, and AI agent features into one seamless platform. With Lyro, the customer service AI agent, businesses can resolve up to 67% of all tickets automatically.
Nango - The fastest way to ship integrations with 500+ APIs
tawk.to - tawk.to is a free live chat app that lets you monitor and chat with visitors on your website or from a free customizable page
Prismatic.io - The integration platform for B2B software companies.