Seven things make SK Chat different. Here's each one, illustrated.
Channels share one brain — same knowledge, same rules, same memory. Adding a channel is a toggle, not a project.
Configure your agent once. It answers on your website, on your hosted chat link, on WhatsApp and Instagram, and inside your own app through the API — without five setups, five knowledge bases, or five bills to reconcile.
One snippet, any stack. Themed to your brand, loads async, remembers returning visitors.
Your own chat link — perfect as a QR on the storefront, the bill, the package. No website needed.
The channel India lives on — with Meta's per-conversation cost shown transparently, not hidden in a markup.
Comments aren't commerce — DMs are. Product questions answered and bookings made inside Instagram.
Bring your own surface — the full agent behind your app, kiosk, or product, over REST and webhooks.
Start on the website, continue on WhatsApp — one conversation, one history, never "as I said before…".
Every message is read three ways — what they want, what language they're in, how they feel — before a single word is generated.
Intent picks the path, language picks the words, sentiment picks the moment. The agent answers when it knows, uses a tool when it can act, and brings in your team when it should — never bluffing through what it doesn't know.
Detects per message, answers in kind — including the Tamil-English and Hindi-English mixing real customers type.
Sentiment is tracked across the conversation — rising frustration triggers help before the customer demands it.
Your catalog, your policies, your FAQs — not the open internet. When it doesn't know, it escalates instead of inventing.
Mid-chat, the agent searches your catalog, books real appointments into SK Calendar, and creates leads in SK CRM — through the same tool gateway our production voice agent uses.
One price per 24-hour conversation window with a 50k-token allowance — chatty threads don't punish you.
The AI is a team member, not a wall. Conversations flow to your people at the right moment — and flow back when the moment passes.
Every channel, one inbox. The AI handles the routine majority quietly; the conversations that need a person rise to the top with the full thread and an AI summary attached. Your customer never repeats themselves — that's the entire point.
While your agent owns the thread, the AI keeps drafting replies from your knowledge — send, edit, or ignore.
Escalation is a phase, not a one-way door — return the thread and the AI resumes the follow-ups.
Whoever picks up gets the whole story plus an AI summary — what they want, what's been tried, how it's going.
Persona, knowledge, hard limits — configured in plain language, with safe defaults from day one.
Name, tone, greeting, working hours, escalation posture — set in plain language, previewed before publishing.
FAQs, policies, services. Edit the knowledge and the agent changes with it — no retraining cycle.
Topics the agent must never handle — medical, legal, pricing exceptions — and exactly what it does instead.
One Softknack sign-in, one permission model — chat access follows the same roles as everything else.
Widget colors, launcher, position, welcome message — it should look like your site.
Meta charges for WhatsApp and Instagram conversations. Most vendors hide it inside a markup. We show you the receipt.
Load the wallet; channel charges draw down from it, each one visible per conversation in your dashboard. No month-end surprise, no overage shock — and your website channels keep working no matter what the wallet says.
SK Chat itself bills per conversation — and the free tier's 1,000/month is real business volume, not a teaser.
Evaluate on your real traffic. If the agent earns its keep, upgrade; if not, you've lost nothing.
INR is primary; USD and EUR fully supported for billing beyond India.
Because it does. India's DPDP Act is a design input here, and the isolation is in the database — not in a policy PDF.
Row-level security means a misbehaving query physically cannot read another tenant's data. Defense in depth — not a promise in a policy.
Consent capture, data export, and erasure flows with admin UIs — not a clause in a contract.
What customers ask, how well the agent handles it, when help is busiest — without making your customers the product.
The invariants most chat vendors don't publish. Technical buyers — this row is for you; the rest is on the Developers page.
Every write accepts an Idempotency-Key. Retries are safe by construction, platform-wide.
HMAC-SHA256 signatures, at-least-once delivery, exponential backoff, replayable dead-letter queue.
Chat capabilities exposed as MCP tools — the same gateway our production voice agent calls.
1,000 conversations a month, no card — evaluate it on your real traffic.
Start free For developers →