How to unglue a client card with the AI Assistant
Sometimes two different clients end up on one card: for example, one card holds its own Telegram and someone else's Viber. The AI Assistant in "Agent" mode moves such a channel contact together with its conversations and messages to another card, without asking support. It first shows what exactly will move and acts only after you confirm.
When you need it
- A client complains that they get messages about someone else's order because a foreign contact sits on their card.
- Operators see the history of two different people on one card.
- A channel contact landed on the wrong card and has to move to the right one (or to a new card).
Good to know
- A channel contact is a client's Viber, Telegram, WhatsApp, etc. in one bot. Its conversations and messages move with it.
- The source card is where the contact is now; the target card is where it goes. The target can be an existing card or a new card.
- The source card does not disappear this way. The last contact of a card cannot be taken: that is a merge of cards, and support does it.
- A move to an existing card can be undone: ask the agent to move the contact back. A move to a new card cannot be undone by the agent (the contact is the new card's only one): support does it; the confirmation card warns about this.
- Support enables the feature for your instance; an administrator turns on the right in the role.
Before you start
Step by step
- Open the AI Assistant chat and choose the "Agent" mode.
- Say what to move. Example: "Move the Viber contact from card #1024 to card #2048" or "Move the Viber from Olena's card to a new card".
- The agent finds the contact on the card and shows a confirmation card:
- a title: from which card to which card;
- a What / Count table: contacts (for example, "Viber #123"), conversations (and how many are open), messages, how many contacts will stay on the source card;
- warnings when they apply: open conversations will move mid-conversation; the target card already has a contact of this channel; the contact id is taken by another card, so the new card gets a service id; for a new card, always: «This tool cannot remove the new card: only support can move the contact back».
- Check the numbers and press "Only this time", or "Reject" if something is wrong. There is no "for the whole conversation" button: every move is confirmed on its own.
- The agent reports the result: how many contacts, conversations and messages moved.
Limits
- Not the last contact. If the contact is the only one on the card, the agent refuses: that is a merge of cards.
- Only cards with a bot, and only within one bot. A card without a bot or a contact of another bot is a job for support.
- Up to 5 contacts at a time. For more, move them in parts.
- Up to 20 moves per hour per user. After the limit the agent tells you in how many minutes you can try again.
- Very large volumes (many thousands of conversations or messages) are not moved by the agent: contact support.
- If another operation is running on the card, or your previous move has not finished yet, the agent asks you to try again in a minute.
What happens next
The contact with its conversations and messages is on the target card; the other contacts stay on the source card. The move is recorded in the card operations journal and in Settings → Change log with the source "AI agent".
How to check it worked
- Open the target card: the moved contact is in the channels block, its conversations are in the history.
- Open the source card: the other contacts are still there.
- Check the record in Settings → Change log.
If something goes wrong
- The move failed (a red card). Nothing was changed, the reason is written under the card. The card can no longer be pressed: ask the agent again.
- A wrong move to an existing card. Ask the agent to move the contact back: from the target card to the source card.
- A wrong move to a new card. The agent cannot undo it: the contact is the new card's only one, and the agent never takes the last contact of a card. Contact support — they merge the cards.
- The agent has no such tool. The feature is not enabled for the instance, or your role lacks the right: contact support or the administrator.