How to Migrate From Verloop to Tenashi
Verloop was designed for a specific challenge: handling large volumes of customer support queries automatically before a human agent ever needs to touch them. AI-first bot deflection across WhatsApp and other channels is its core value proposition. If you're an enterprise with thousands of repetitive tier-1 queries per day, that's a real use case.
Teams that start looking elsewhere are typically ones where the bot-to-human handoff turns out to be the moment that matters most, and it's not going smoothly. When a customer with a real problem finally gets to an agent, the agent has lost context from the bot conversation, the shared inbox experience is secondary to the bot platform, and there's no CRM or pipeline to capture the relationship.
If your team's value is in what human agents do — building customer relationships, closing deals, resolving complex support issues — this is the migration path from Verloop to a workspace designed around them.
What Verloop is genuinely good at
Upfront honesty: Verloop's AI automation for high-volume tier-1 support is its genuine strength. If you're deflecting 50-70% of support queries before they reach a human, and your support cost metrics are driving that decision, Verloop is built for exactly that. Tenashi isn't a replacement for enterprise bot deflection infrastructure.
The cases where the switch makes sense:
- Bot deflection isn't the bottleneck. Your support volume isn't so high that automation before the agent is a cost imperative. Most queries need a human, and you want those humans to have a great shared workspace.
- Agents need context and structure. When a conversation reaches an agent, they need a clean inbox, full history, internal notes, and CRM context — not a handoff from a bot that drops them into a bare chat thread.
- Sales and support live together. You want leads tracked through a pipeline alongside support tickets, in the same inbox, with the same team.
What changes when you switch to Tenashi
| On Verloop (WhatsApp API) | On Tenashi | |
|---|---|---|
| Your number | Registered on the API | Linked by QR — stays yours |
| Primary model | Bot-first AI deflection | Human-first shared inbox |
| Built-in CRM + pipeline | Not included | Yes |
| Support tickets with SLA | Limited | Yes |
| Agent shared inbox | Secondary to bot | Primary surface |
| API approval | Required | Not required |
| WhatsApp groups | No | Yes |
Step-by-step: migrating from Verloop to Tenashi
1. Document your bot flows and export contacts
Before the switch, export your contact list (CSV) from Verloop. More importantly, document the key conversation flows your bot handles: the common questions, the decision branches, what triggers a handoff to a human. You'll translate some of this into Tenashi's routing automations and canned replies — the rest simply becomes agent work.
2. Decide on your number
- Same number. Your Verloop number is registered on the WhatsApp Business API. Release it from the API first (step 3), then link it to Tenashi by QR scan.
- New number. Link a different existing WhatsApp number to Tenashi now and run both in parallel during the handover period.
3. Release the number from the WhatsApp Business API
Verloop uses the official WhatsApp Business API. A number on the API cannot simultaneously be used as a linked device. Deregister the number through your Meta Business Manager (WhatsApp Accounts → delete or migrate the number), or work with Verloop support on the release process. Plan for a quiet window — the deregistration is the only moment of real downtime.
4. Connect to Tenashi
Start your Tenashi trial and scan the QR code with the WhatsApp app on the phone holding your number. Your number is live in the shared inbox within a minute. WhatsApp groups that were invisible in Verloop now appear.
5. Import contacts and build the agent workspace
Upload the contacts CSV. Then build the agent-first structure:
- CRM contact records — add custom fields for the context agents need: product, account tier, issue category, source.
- Sales pipeline — if any conversations are sales-related, set up deal stages.
- Support ticket settings — SLA targets, issue categories, assignment queues.
- Canned replies — turn the most common bot answers into quick replies for agents.
- Automations — routing rules that handle what the bot was doing: keyword-based routing, new-contact auto-assign, away messages.
6. Transition your team
Invite agents, assign open conversations, and do a real run-through: receive an inbound message, claim it in the inbox, reply, raise a ticket, add a CRM note. The first week on a human-first inbox after a bot-first platform often feels faster in daily use once the routing is configured.
Where Tenashi fits
Tenashi is the answer when human agents are doing the valuable work and they need a proper shared workspace to do it well. The product is designed around the agent — not around automating the agent away:
- A structured shared inbox where every conversation has an owner.
- Full CRM context — contact history, company record, deal stage — right next to the chat.
- Support tickets with SLA so issues don't get lost after the conversation ends.
- Sales pipeline for teams that are doing sales and support from the same inbox.
- No bot training setup — your agents are live on the same day you link your number.
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 Verloop?
Yes. Deregister the number from the WhatsApp Business API via Meta Business Manager or Verloop support, then link it to Tenashi by scanning the QR code. Same number, same contact threads.
Does Tenashi have any automation for handling WhatsApp conversations?
Yes. Tenashi has automations for conversation routing, keyword-based assignment and canned replies. These support your human agents rather than replacing them. The design assumption is that agents add value to most conversations — Tenashi makes those agents as effective as possible.
What do I lose by leaving Verloop?
The AI bot deflection capability. If you were successfully deflecting a large share of tier-1 queries before they reached an agent, and that deflection was meaningfully reducing support costs, that's real value Tenashi doesn't replicate. For teams where most conversations needed a human anyway, the loss is smaller.
Can Tenashi access WhatsApp groups?
Yes. Tenashi links your real number as a device, so your WhatsApp groups appear in the shared inbox. The official WhatsApp Business API that Verloop uses cannot read or send to groups.
How long does it take for agents to get up to speed on Tenashi?
Most agents adapt within a day. The shared inbox model is familiar — it works like an email inbox or a helpdesk, not like operating a bot platform. The setup overhead is mostly in configuring canned replies and routing automations, not in training the team on the tool itself.
Ready to put your agents at the center of the WhatsApp workflow? Start a free trial and move to a shared inbox where every conversation has context, every lead has a stage, and every support issue has an SLA.