The user’s card

The user’s card holds everything we know about them: how to reach them, where they came from, what labels they carry and what they will get next. It is the same card wherever you open it from — a conversation in Chats or the Contacts section.

“About this contact”

A short summary right inside the conversation:

• Channel — Telegram or Instagram;
• Account — which of your bots is writing to them;
• Replies — “Bot” or “You”;
• Time left to reply — for Instagram. “Instagram gives you 24 hours to reply after the user’s last message. Once they write again, the countdown restarts.” In Telegram it says “No limit”.

What the card holds

• Name — you can change it: Edit, then Save.
• Channel, Account, Phone, Email — whatever the bot has learned.
• Activity: Last seen — when they last wrote; In the base since — when they first appeared.
• Tags — everything you have labelled the user with: by hand here, with an “Add a label” button in a message, or with the “Save to the card” step in a bot. The row opens the list of that user’s tags, where you take them off with the cross and add new ones: pick a tag your users already carry or type a new one in your own words and tap Add. No tags yet? The page says so: “No tags yet. Add your own — later you can select users by it in filters and folders.” In the browser the tags sit right on the card: the cross next to a tag removes it, and the field beside Add a tag adds a new one (Enter does the same). You can tag someone whose conversation has only just started — the user’s card is created for you.
• Data — what the bot saved with the “Save to the card” step: a city, a size, an answer to a question.
• Open chat — when you opened the card from Contacts and a conversation with the user already exists.
• Delete contact — at the bottom, with a “Really delete?” confirmation.

Where the user came from

There is no separate “source” field — their path shows in the conversation itself:

• “Came from link «profile bio»” — your link trigger fired, and the source name is the one you gave it in the trigger settings;
• “Came from link «…» — invited by Ivan” — an invitation from another user;
• “Came from an Instagram link”, “Came from an Instagram ad”;
• “Comment on a post” or “Comment on a reel” above a message — they came from the comments;
• events in the conversation — “finished the bot”, “tapped a button”: they show what exactly the user went through.

Stopping the bot for this user

That is done in the conversation itself, with Turn automation off: the bot stops replying and you take over. See Inbox.

Separately from that, the card sometimes carries a note: “This user stopped the bot on 3 September — new messages will not reach them, and they are left out of mailings. The note clears itself if they start the bot again.” That one is the user’s own doing, not yours.

“Do not message”

The Messages and broadcasts group holds the Do not message switch: “The user asked not to be disturbed: chain messages and broadcasts will not reach them.”

Turning it on takes the user off all of your chains at once and leaves them out of broadcast audiences. You can turn it back off here too, but that alone does not put them back into the chains — that is done one at a time (below).

The Unsubscribe button under a chain message does the same thing, by the user’s own hand.

Chains on the card

If chain messages are coming to this person, the card shows them — both in the browser and in the app.

In the app it is the What comes next group: one row per upcoming message — “Chain name · Message 3” with the date it goes out. Nothing scheduled — the line reads “No chain messages are scheduled.” If the conditions will drop the person earlier, it says so underneath: “After message 3 they leave the chain: has the label «bought»”.

Tapping a row opens that message’s page:

• Chain — which one it belongs to;
• When — the date and time;
• Conditions — who it goes to (“No conditions” when there are none);
• the Skip this message button — that message will not go out, the rest keep their schedule. If it has already gone, we say so: “The message has already gone out or been cancelled”;
• the Remove from this chain button — the person leaves the chain entirely and everything scheduled is cancelled.

In the browser the same thing is laid out in blocks:

• Upcoming messages · «Name» — the list of upcoming messages with their dates, each with a Skip button. What you skip is marked “skipped by you” and is never scheduled again. The last row of the block is Remove from the chain.
• If the person is waiting for a conversation with another bot to end, the dates are replaced by the line “Waiting for the conversation with the bot “…” to end — messages start after it”.
• Message history — what has already happened: “sent”, “not delivered”, “scheduled”, “skipped: the condition did not match”, “skipped: while the bot was off”, “skipped: the chain ended”, “skipped by you”.

“Taken off chains”

A list of the chains the user dropped out of, with the reason. It is there both in the browser and in the app:

• “no longer matches the conditions”;
• “‘Do not message’ is on”;
• “tapped ‘Do not message me’”;
• “moved to another chain”;
• “the message could not be sent”;
• “you removed them”.

Every row has a Put back button. Putting someone back returns them to that chain and the pauses start counting from that moment; nothing they already received comes again. If they were taken off because a message could not be sent, that very message comes back with them.

This is the only way to return a user to a chain: on its own, a chain never takes anyone twice (see How a chain behaves).