Respond.io is a customer conversation platform that keeps WhatsApp leads and new chat history with the business when sales staff leave. Agents reply from company-owned numbers connected to respond.io, and a departing employee's contacts and chat history can be taken over by a colleague.
When a departing employee's access to respond.io is revoked, every contact assigned to them can be reassigned to a colleague. If no one is chosen, those contacts are marked as unassigned and wait in the Unassigned inbox for the team to take over.
Revoking access removes the employee from the workspace, not the customer. The conversation history is stored with each contact, so the colleague who takes over can get full context from the thread before replying. The business keeps the customer, the thread and the sale in progress on the day the employee leaves.
Lifecycle, which tracks each contact by stage from first interaction to conversion, shows the colleague taking over which contacts are close to buying. Its default stages are New Lead, Hot Lead, Payment and Customer, with Cold Lead for contacts who stop responding.
Every stage change is logged in the contact's Activities tab with when and by whom it was made, and internal comments stay with the contact, visible across the workspace. This allows the colleague taking over to start with the hot leads and payments in progress instead of restarting every conversation.
The Agent role in respond.io has access to the Messages module only: agents reply to customers, but cannot open the Contacts module or export data. Agents can also be restricted to the contacts assigned to them or their team.
On the Advanced and Enterprise plans, respond.io can mask phone numbers and email addresses, so agents do not see a customer's number to save on their own phone. When an agent leaves, the customer list stays in the workspace, not in their phone's contacts.
Everything above applies to conversations that run through respond.io, so the requirement is moving the team's WhatsApp selling away from employee-owned WhatsApp accounts and into company-controlled channels connected to respond.io. A team can centralize on a single business number that every agent replies from, and a business with several branches can connect a number for each to respond.io. Each number is connected through the company's own Meta Business Manager, and agents who sell from their phones reply in the respond.io mobile app instead of their own WhatsApp.
WhatsApp calls run on the same business number: agents answer and place them from the respond.io Inbox, and each call is logged on the contact.
Customers who saved a rep's personal number may keep messaging it after the rep leaves. To inform the customer of the official business number so they can message it instead, send broadcasts from the business number. Srikandi replaced agents' personal numbers with one WhatsApp number for its 47 branches on respond.io, used broadcasts to move customers onto it, and saw conversations rise 125% and revenue 23%.
For mid-market B2C businesses where several agents sell on WhatsApp, this turns every lead into a company record rather than one employee's chat.
Respond.io allows businesses to store conversations in a central inbox from the day they run through it. It cannot bring back chats that already live in staff members' personal WhatsApp accounts: chat history from the WhatsApp app cannot be imported, and WhatsApp's own backups only restore history on another phone. Contact details can still be imported from a CSV file.
A WhatsApp Business App number connected through WhatsApp Coexistence keeps working in the app, but its past chats stay in the app and do not appear in respond.io. If the goal is to recover a former employee's past chats, respond.io is not the tool for it: those chats stay with that phone's WhatsApp account and its backup. If your business has only a a couple of people handling just dozens of inquiries on a company’s WhatsApp Business App account, the app is enough: the chats stay on the company's phone when one person leaves.