Documents / Integrations / Clientish Team Notifications: Slack, Microsoft Teams, Discord and Telegram

Clientish Team Notifications: Slack, Microsoft Teams, Discord and Telegram

5 min read

The five updates your team chat can receive, where each chat app is connected, and how to check that messages really arrive.

In Clientish, you can post short updates to the chat app your team already lives in: Slack, Microsoft Teams, Discord or Telegram. A new lead, order or ticket, a paid invoice or a call brief shows up in the channel with a link that opens the record in your workspace.

Applies to: every plan (Solo, Starter, Growth, Pro and Enterprise). Meeting briefs need Calendly or Cal.com, which turn booked calls into leads.
Who can do it: the owner and co-admins, and team members whose role has the General Integrations permission

Where Do You Connect Slack, Teams, Discord and Telegram in Clientish?

Each chat app has its own card under Integrations, on the Communication tab. You can connect one of them or all four; each card has its own settings.

Integrations page filtered to the four team chat cards: Telegram, Discord, Slack and Microsoft Teams, each with a Connect button
Chat appWhat you paste into ClientishWhere the updates go
SlackA webhook URL from your Slack app (it starts with https://hooks.slack.com/services/)The Slack channel you picked for that webhook
Microsoft TeamsA workflow URL from the Teams template “Post to a channel when a webhook request is received”The Teams channel the workflow posts to
DiscordA webhook URL from the channel settings (it starts with https://discord.com/api/webhooks/)That Discord channel
TelegramA bot token from @BotFather and the chat to post inA group, a channel or a private chat with your bot

Which Updates Can Clientish Post to Your Team Chat?

There are five kinds of update, and you check which ones each chat gets. All five are checked when you first open a card.

UpdateWhen it is postedWhat the message says
New leadsA lead is added, from any source: a form, an import, a booking or manually“New lead”, the person’s name and company, and an Open the lead link
New ordersAn order is created“New order”, the order number, and Open the order
New ticketsA support ticket is opened in your workspace“New support ticket”, the subject, and Open the ticket
Paid invoicesAn invoice changes to paid. Saving a paid invoice again doesn’t post a second time“Invoice paid”, the invoice number and amount, and Open the invoice
Meeting briefsBefore a call booked in Calendly or Cal.com, at the time set on that cardWho is coming and when, what they want and where they came from, with a link to the lead

Uncheck what a chat doesn’t need. For example, a finance channel can get only paid invoices while the sales channel gets new leads and meeting briefs.

How to Set Up Team Chat Notifications in Clientish

Setup takes one link or one bot token from the chat app, pasted into its card. The short version:

  1. Get the link or token

    Create an incoming webhook in Slack or Discord, a workflow in Teams, or a bot in Telegram.

  2. Paste it into the card

    Open the card on the Communication tab, paste the value, and check the updates under Send these updates.

  3. Save and test it

    Click Save & test. A test message lands in the chat if everything is right.

Full steps for each app, with screenshots, are in How to Connect Slack, Microsoft Teams, Discord or Telegram in Clientish.

How to Test a Slack, Teams, Discord or Telegram Connection

Click Save & test on the card: Clientish saves what is on screen and posts a real test message into the chat. It reads “Test message: Clientish is connected. The updates you ticked will appear here.” with an Open Clientish link.

  • When it arrives, Clientish shows “Test message sent. Check the Slack chat.” (or the name of your app).
  • When the chat app refuses it, the reason appears instead, for example that the URL wasn’t accepted. The fixes are below.
  • You can click it again anytime, for instance after someone changes the channel in Slack.

How to Pause Team Chat Notifications

Turn the card off on the Integrations page. The link or token stays saved, nothing is posted while it is off, and updates already waiting are dropped rather than sent late. To stop only one kind of update, uncheck it on the card instead.

Team Chat Notifications Not Arriving? Common Fixes

The test says the URL wasn’t accepted⌄
The webhook or workflow was probably deleted or changed in the chat app. Make a new one there, paste it into the card and test again. Clientish never shows the saved URL, so a blank box on save keeps the old one.
The Telegram test says “Telegram refused to post there”⌄
The bot isn’t in that chat or may not write there. Add the bot to the group, or make it an admin of the channel, then test again.
The test works, but an update never came⌄
Open the card and check that this kind of update is checked and that the card is turned on. If the chat app was down, Clientish tries again a minute later, three tries in all, and then gives up on that message.
No meeting briefs arrive⌄
Briefs need a connected Calendly or Cal.com card with a brief time set and Slack / Teams / Discord / Telegram checked there, plus Meeting briefs checked on the chat card.

Related

Related Articles

How to Connect Slack, Microsoft Teams, Discord or Telegram in ClientishClientish Accounting Sync: QuickBooks and Xero Invoices