Skip to content

Your first week

A suggested order. Nothing here is mandatory, but teams that follow it stop fighting the tool by about day three.


  1. Connect your Telegram accountguide. Wait for the first sync to finish before judging the table.
  2. Exclude the noise. Personal chats, bots, dead groups — right-click a row and choose Exclude chat, or bulk-select and use Exclude selected chats. Excluded chats disappear from the CRM and from analytics and contact syncing. See Excluded chats.
  3. Hide the columns you don’t use. Open Columns in the table toolbar and switch off everything that isn’t load-bearing.
  1. Create your custom columns. Start with three, not thirteen: something like Stage (Select), Owner (Select), Next step (Date). Add more once you know they’re needed. See Columns & custom fields.
  2. Tag 20 real chats by hand. This is the step people skip. It tells you within ten minutes whether your field design survives contact with reality.
  3. Save a view. Filter to what you actually work on each morning, then Save current view and give it a name. See Views, filters & sorting.
  1. Write your top 5 templates and give each a /command shortcut so you can insert them by typing in the composer. See Templates.
  2. Set reminders on anything waiting on you. The reminder bot pings you in Telegram when one is due. See Reminders.
  1. Buy seats and invite teammatesSettings → Workspace → Members. Each invite link is good for 24 hours.
  2. Decide the account model per person:
    • Sales / outreach → each teammate connects their own Telegram.
    • Support → everyone connects the same Telegram and shares one inbox. You can mix both in one workspace.
  3. Set your privacy toggles before anyone starts working — Permissions & privacy settings. At minimum decide: can members see all analytics, can members edit/delete Telegram messages, can members manage excluded chats.
  1. Open Analytics and read your baseline. Response times, heatmaps and top chats fill in automatically once your accounts are connected (Pro, or a Pro seat). See Analytics overview.
  2. Enable tickets if you handle inbound work, and set a Global SLA in hours under Settings → Workspace → Privacy & Settings. See SLA.
  3. Share a view with the workspace so the team starts from the same screen.
  • Run your first broadcast to a small, filtered segment — 20 recipients, variables checked in the preview. Broadcasts.
  • Check Custom fields analytics for coverage gaps: fields under 25% coverage are either unnecessary or unenforced.
  • Connect an AI agent over MCP and let it do the bulk edits for you. MCP connectors.

  • Too many custom columns on day one. Coverage collapses and analytics turns useless.
  • Leaving every chat in the CRM. The table becomes noise and your analytics baselines are meaningless. Exclude aggressively.
  • Blasting a big list on day one. Start with a small batch, check the preview per recipient, and let the send delay do its job.