Customers and tags

Members is GramBase’s record of every Telegram contact connected to your team — anyone who has messaged your bot, joined one of your groups, or logged into your Mini App. Each contact is one profile shared across orders, subscriptions, groups, and support, whatever bot or channel first brought them in.

Customer profiles

Open a member from the list to see their profile: display name, username, language, when they were first seen and when they were last active, and a private note only your team can see.

Below that, four tabs cover their history — Orders, Subscriptions, Groups, and Tickets — each loading its own data so a slow one never blocks the rest of the page. The Statistics section totals their spend, order count, active subscriptions, groups joined, and support tickets. The Orders tab lists every order with payment and delivery status; opening one shows the same order detail available from Orders. Subscriptions splits into active and inactive: an active subscription can be extended by a number of days, have its group invite link regenerated, or be removed (which also attempts to remove the buyer from the group). Groups lists every chat the contact has joined, with their role and join date. Tickets links straight into Inbox for each conversation.

A member’s profile is also reachable as a side drawer from the Members list and other screens that reference a contact, showing a condensed version of the same sections.

Tags

Tags (Members → Manage Tags, or Tags in the sidebar) is a single screen for both member tags and group tags, switched with a tab. A tag is a name and a color, nothing more — create one with Create Tag, which asks for a name and a color swatch. Editing a tag also offers Merge into another tag: picking a target moves every assignment to that tag, dedupes any overlap, and deletes the tag you merged away. Deleting a tag removes it from every member it was assigned to; the members themselves, their orders, notes, and support records are untouched.

From a member’s profile, add or remove tags directly through the tag editor in the Tags section — start typing to search existing tags or create a new one on the spot. From the Members list, the Manage Tags button and the tag filter both work the same tag pool.

Tags are the only customer grouping you can see or act on today — there is no automatic segmentation (no churn risk, lifetime value, or VIP score) yet.

Reachability

Telegram only lets a bot message someone who has started a private chat with it. GramBase tracks this per contact as reachability, shown as a badge next to each member:

• Reachable — the contact has a private chat open with at least one of your bots; a broadcast can reach them.
• Group only — the contact is known only from a group or channel they joined. They have never messaged a bot privately, so Telegram blocks any direct message to them until they do.
• Blocked — the contact previously had a reachable state but has since blocked the bot.

The Members list has a reachability filter alongside the tag filter, and the same states drive the checkbox when selecting members for a broadcast: a non-reachable member’s checkbox is disabled, with a tooltip explaining why, rather than letting you pick someone a send can never reach.

Banning a customer

A member’s profile shows a Ban user button inside the Overview card. Banning asks for a reason — spam or flooding, harassment or abuse, fraud or misuse, or other (which requires a note) — plus an optional note visible only to your team, and takes effect within a minute. A banned user can no longer use any of your team’s bot features: messages, commands, buttons, and payments are all blocked. You can still message them from Inbox, and existing orders and subscriptions are never touched by a ban.

A banned member shows a red Banned status card above their profile, with the reason, who banned them, and when, plus an Unban button that restores full access immediately. The Members list marks banned rows with the same badge next to their name.

A ban you see that nobody on your team issued may have come from GramBase itself, enforcing platform-wide policy — ban and unban work identically either way, and the status card always shows who issued it.