How to Migrate From DelightChat to Tenashi
DelightChat built a focused product: WhatsApp and multi-channel support for D2C brands on Shopify and WooCommerce, with order data surfaced in the same interface where agents are replying. If you're a direct-to-consumer brand where agents spend most of their day answering "where's my order?" across WhatsApp and Instagram, DelightChat handles that well.
The gaps show if your business doesn't match the D2C e-commerce mould, or if you want more than a support inbox. There's no sales pipeline for teams managing leads, no built-in CRM for contact history beyond support context, and the WhatsApp Business API overhead means both a verification step and per-conversation billing.
Here's the practical migration from DelightChat to Tenashi.
Why teams look past DelightChat
DelightChat is well-designed for its intended use case. The mismatch appears when:
- You're not an e-commerce brand. DelightChat's integrations, automation logic and product framing are built around Shopify and WooCommerce merchants. A services business, an agency, a real estate team — the platform's core value doesn't apply.
- You need sales tracking alongside support. A team that manages both inbound sales leads and support tickets on WhatsApp needs a pipeline. DelightChat doesn't provide one.
- API overhead adds up. Per-conversation billing on the WhatsApp Business API underneath DelightChat is a cost that scales with how much you talk to customers.
What changes when you switch to Tenashi
| On DelightChat (WhatsApp API) | On Tenashi | |
|---|---|---|
| Your number | Registered on the API | Linked by QR — stays yours |
| Platform requirement | Shopify / WooCommerce focus | Any business |
| Built-in sales pipeline | Not included | Yes |
| CRM with contact records | Limited | Full CRM |
| Support tickets with SLA | Limited | Yes |
| Per-conversation billing | Yes | No — flat pricing |
| WhatsApp groups | No | Yes |
Honest note: DelightChat's Shopify and WooCommerce order integration is its distinctive feature — pulling order history into the support thread so agents see order context without switching tabs. If that's central to how your support team works, Tenashi doesn't provide that. Tenashi's strength is a complete sales-and-support workspace for any business type.
Step-by-step: migrating from DelightChat to Tenashi
1. Export contacts and support data
From DelightChat, export your contact list (CSV) and any customer notes, tags or segmentation you've applied. Note common support response templates — you'll rebuild these as canned replies. Chat history won't transfer, so note any ongoing issues that need context.
2. Decide on your number
- Same number. The number on DelightChat is registered on the WhatsApp Business API. To reuse it in Tenashi, release it from the API first (step 3), then link it by QR.
- New number. Link a different existing WhatsApp number to Tenashi now and migrate customer contacts gradually.
3. Release the number from the WhatsApp Business API
DelightChat runs on the official WhatsApp Business API. A number on the API cannot simultaneously be used as a linked device. Deregister the number through Meta Business Manager (WhatsApp Accounts → delete or migrate). You may also be able to request the release through DelightChat support. Do this in a quiet window — it's the only timing-sensitive step.
4. Connect to Tenashi
Start your Tenashi trial and scan the QR code with the WhatsApp app on the phone holding your number. Done in under a minute. Your WhatsApp groups now appear in the shared inbox — something the API blocked.
5. Import contacts and set up your workspace
Upload the CSV. Then build out what DelightChat didn't provide:
- Sales pipeline — create stages for inbound leads alongside the support workflow.
- CRM fields — business type, segment, contact source, deal value.
- Support ticket settings — SLA targets, issue categories, agent queues.
- Canned replies — the support answers your team sends most often.
- Automations — routing rules, keyword assignment, after-hours messages.
- Broadcasts — proactive outreach campaigns with ban-protection.
6. Move your team in
Invite your agents, assign open support conversations, and test the end-to-end flow: handle an inbound message, raise a ticket, push a lead through the sales pipeline. Once the setup is validated, cancel DelightChat.
Where Tenashi fits
Tenashi is built for any business that uses WhatsApp seriously — not just for D2C e-commerce support. Whether you're running sales and support from the same inbox, handling leads alongside customer service tickets, or working a WhatsApp channel without Shopify in the picture, Tenashi covers the full lifecycle:
- Shared inbox with claim, assign, internal notes.
- Full CRM — contact records, company history, custom fields.
- Sales pipeline — so leads from WhatsApp become tracked deals, not lost threads.
- Support tickets with SLA — so issues have owners and resolution timelines.
- Flat pricing — no per-conversation meter.
Pricing: Starter $18/mo, Growth $27/mo, Scale $56/mo, 3-day Growth trial, no card.
Start your free trial → · See every feature
FAQ
Can I keep my WhatsApp number from DelightChat?
Yes. Deregister the number from the WhatsApp Business API through Meta Business Manager, then scan the QR code in Tenashi with the WhatsApp app. Same number, same contact threads.
Does Tenashi work for non-Shopify businesses?
Yes. Tenashi works for any business with a WhatsApp number — there's no e-commerce platform dependency. Whether you're a service business, agency, or B2B team, the shared inbox, CRM and pipeline work the same way.
What do I lose by leaving DelightChat?
Primarily the Shopify and WooCommerce order-context integration. If your support agents need to see order history inside the chat thread without switching tabs, that's DelightChat's specific value. Tenashi offers a broader sales-and-support workspace without that e-commerce order data layer.
Can Tenashi access WhatsApp groups?
Yes. Because Tenashi links your real number as a linked device, your WhatsApp groups appear in the inbox. The official WhatsApp Business API that DelightChat uses cannot read or send to groups — it's a structural limitation.
Does the migration cause downtime?
Very little. The only timing-sensitive moment is releasing the number from the API — a window of a few minutes while the number transitions. The QR link itself takes under a minute.
Not a Shopify brand — or need more than just support? Start a free trial and move to a WhatsApp workspace that covers sales, support and CRM for any business, not just e-commerce.