paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-10-31 12:03:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

corporate: Rename stream->channel in Semsee case study.

Browse Source
This commit is contained in:
Sayam Samal
2024-05-07 03:40:34 +05:30
committed by Tim Abbott
parent 5f5d4457b9
commit ecfb271a09
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
templates/corporate/case-studies/semsee-case-study.md
View File

@@ -56,7 +56,7 @@ rarely used for internal communications. For jumping on a call, Zulip’s native
call integration is an easy starting point. System monitoring and software
development processes are integrated with Zulip via the API. For example, a
custom integration sends logging data from Semsee’s product into Zulip, with a
stream and topic configured based on the deployed environment.
channel and topic configured based on the deployed environment.
New employees adapt easily to Zulip’s organized conversations. By reading
ongoing discussions, they quickly get an intuition for when to start a new
@@ -66,7 +66,7 @@ With conversations organized by topic, “people don’t have to scroll through
cherry-pick out the messages they need to read,” James says.
Semsee invites customers to join the company Zulip chat as guests. “Our
customers just see one stream with one or two topics, so it’s very easy for
customers just see one channel with one or two topics, so it’s very easy for
them,” James explains. On the flip side, when Semsee employees are invited to
join customers’ Slack chats, they miss Zulip. “I don’t like going back to Slack
now. It’s just not as efficient a way to organize communication,” says James. “A