CS Pulse Community
Code of Conduct
CS Pulse Community. For every member, host, contributor and participant. Last updated 28 September 2026.
Why this exists
CS Pulse Community works because people share real things: real accounts, real mistakes and real opinions. That only happens when everyone trusts that what is shared stays with the people it was shared with.
Our Rooms are small by design, so a single broken confidence is felt by everyone in them. This Code of Conduct makes the standard explicit. It applies in Rooms, in our WhatsApp and Slack groups, on our member workspace, and at our events.
By joining the community or applying for a Room, you agree to follow it.
1. Keep it confidential
What is shared in the community stays in the community.
- Do not share account names, customer situations or company details from a Room or a group without the explicit permission of the person who shared them.
- Do not record, screenshot or run your own note-taker in a Room, and do not share screenshots of group conversations.
- Do not quote other members directly without their permission.
- Never pass on "I heard in a CS Pulse Room that [Company X] had this problem", in any form, to anyone.
How we take notes. We never record video in Rooms. The audio is transcribed by Granola or a similar botless note-taker, run by the moderator or another member everyone has agreed on, so we can write notes and resources for the community. Everyone is asked at the start of each Room, and anyone can say no. We never share or publish raw transcripts, and anything we share from a Room is anonymised. Our Privacy Policy has the details.
What you learn is yours. Frameworks, questions, mental models and approaches are yours to take, apply and share. The confidentiality rule covers people and situations, not ideas.
2. Bring your experience, not a product
Everyone here represents their own experience, never a product.
- Do not use Rooms, groups or messages to members to pitch a tool, service, consultancy or job.
- Sharing what worked for you is welcome: "what we saw work with our customers" is fine, "you should buy [Product]" is not.
- If you work for a CS vendor and take part as a practitioner, say so, and keep your contributions grounded in your own work.
This applies to hosts, contributors and members alike.
3. Contribute, don't just consume
CS Pulse Community is a group of practitioners who show up for each other, not a content feed.
- When a discussion touches your area, join in.
- When you get a seat in a Room, come ready to take part. If you can't make it, tell us at least 48 hours ahead so someone on the waitlist can take your place. Genuine emergencies are always understood.
- There is no minimum level of activity, but joining only to take and never to give isn't the spirit of the community.
4. Respect the room
Rooms are small and curated, so everyone's time matters.
- Read the brief and come prepared.
- Engage with other people's ideas, not only your own.
- Disagree with the idea, never the person.
- Back your views with your experience, not your seniority. "I've been in CS for fifteen years" is not an argument.
5. If something goes wrong
If something doesn't feel right, don't keep it to yourself. Email support@cspulse.com, or message a core team member you know. Reports are handled privately, with no public call-outs.
We look at every situation on its own facts. As a guide:
| Level | Examples | What happens |
|---|---|---|
| Minor, usually accidental | A takeaway shared outside with enough detail to identify someone. Missing a Room without notice. A drift toward promoting a product without realising it | A direct conversation and a reminder of the standard |
| Moderate | Naming a member and their situation outside the community. Pitching a product, service or consultancy in a Room. A personal attack instead of engaging with the idea | A direct conversation, and we may ask for an acknowledgement or a change in behaviour |
| Serious | Deliberately sharing a member's confidential details in a way that harms or exposes them. Repeated pitching after a warning. Using the community for personal gain without ever contributing back | We may ask for an apology where it happened, and may remove the person from the community |
Confidentiality breaches deserve a special word. Most problems can be put right with a conversation, but once something that identifies a member is out in the world, it can't be taken back. That is why the standard exists: to prevent harm, not only to respond to it.
Our aim is always to fix things, not to punish. But the standard is real, and the community only works because it is kept.
Why it matters here
A large, open community can run on light-touch rules. Small Rooms can't. The scenarios work because they are specific, the mistake autopsies work because they are honest, and the follow-ups work because people share what they actually learned.
All of that depends on everyone trusting that it's safe to be honest. This Code of Conduct is how we protect that trust.
Questions
Email support@cspulse.com.