What is the #launchpass Channel? | LaunchPass Help Center

Overview

What It Is

The #launchpass channel is your admin control center inside Discord.

When you set up LaunchPass with Discord, the LaunchPass bot can post important notifications and respond to commands in a private channel you create.

Key purposes:

✅ Notify you when new members join
✅ Alert you when members cancel
✅ Look up member information
✅ Update member details
✅ Configure bot behavior
✅ Everything in one place

Why You Need It

Without the #launchpass channel:

You might miss member alerts
No easy way to look up member info
Can't update member details easily
Harder to manage your community

With the #launchpass channel:

Get notifications immediately
Quick member lookups
Easy email updates
Control bot behavior
Stay informed

Setting Up the #launchpass Channel

Creating the Channel

Step 1: Create a new channel

Go to your Discord server
Right-click in channel list
Select "Create Channel"
Name it: #launchpass (lowercase, no spaces)
Choose "Text Channel"
Click "Create"

Making It Private

Step 2: Make it private and admin-only

Right-click the #launchpass channel
Select "Edit Channel"
Go to "Permissions"
Click "Add a permission"
Select everyone role (@everyone)
Turn OFF all permissions (view, send, read)
Add your admin role and grant VIEW + READ permissions
Click "Save"

Result: Only admins can see #launchpass

Giving LaunchPass Bot Access

Step 3: Add LaunchPass bot permissions

In channel permissions
Add LaunchPass bot (search for it)
Grant permissions:
- ✅ View channel
- ✅ Read message history
- ✅ Send messages
- ✅ Read reactions (optional)
Save

The bot now has access to the channel.

Verification

Test that it's working:

Go to #launchpass
You should see a welcome message from LaunchPass bot
Or send a test command (see below)
Bot responds = it's working ✅

What The Bot Posts

New Member Notifications

When someone signs up and pays:

✅ NEW MEMBER ACTIVATED Name: John Doe Email: [email protected] Subscription: Monthly ($29/month) Joined: Today at 3:45 PM Tier: Standard

What you learn:

Who joined
Their email
What they paid for
When they joined

Why it matters:

Immediate notification
Know who your newest members are
Plan your welcome/onboarding

Member Cancellation Alerts

When a member cancels their subscription:

⚠️ MEMBER CANCELLED Name: Jane Smith Email: [email protected] Subscription: Monthly ($29/month) Cancelled: Today at 2:15 PM Reason: Not provided

What you learn:

Who canceled
When they canceled
Which subscription they had

Why it matters:

Know immediately
Potential to save them
Understand churn patterns

Member Left Without Canceling

When a member leaves Discord without canceling:

⚠️ MEMBER LEFT (No cancellation) Name: Bob Johnson Email: [email protected] Subscription: Monthly ($29/month) Left Discord: Today at 4:30 PM Status: Still paying, not in Discord Action: May want to reach out

What you learn:

They left Discord but didn't cancel
They might still be paying
You might save them

Why it matters:

Opportunity to retain
Understand if they left intentionally or by accident
Chance to re-engage

Using Bot Commands

Command 1: Look Up Member Info (whois)

Find detailed information about any member.

Command syntax:

whois [email or username or Discord ID]

Examples:

Look up by email:

whois [email protected]

Look up by Discord username:

whois JohnDoe#1234

Look up by Discord ID:

whois 123456789012345

Bot responds with:

User: John Doe Email: [email protected] Discord ID: 123456789012345 Discord Username: JohnDoe#1234 Subscription: Monthly ($29/month) Status: Active Joined: January 15, 2024 Next Billing: February 15, 2024 Payment Method: •••• 1234 Stripe ID: cus_ABC123DEF456

What you learn:

All their account details
Subscription status
Billing information
Discord information

When to use:

Troubleshooting access issues
Verifying member information
Checking payment status
Finding member details quickly

Command 2: Update Member Email (updateUserEmail)

Change a member's email address.

Why you might do this:

Member gave wrong email
Member changed email
Member's email was typo
Need to correct records

Command syntax:

updateUserEmail [old-email] [new-email]

Example:

updateUserEmail [email protected] [email protected]

Bot responds:

✅ Email updated successfully Old email: [email protected] New email: [email protected] Updated in: LaunchPass database + Stripe

Important notes:

Updates in BOTH LaunchPass AND Stripe
Email must be valid
New email can't already be used by another member
Takes effect immediately

What it affects:

Billing notifications go to new email
Password resets sent to new email
Any future communications use new email

Command 3: Don't Kick on Cancel (dontKickOnCancel)

Change what happens when a member cancels.

Default behavior:

Member cancels → Removed from Discord server (kicked)

Alternative behavior:

Member cancels → Keeps role, doesn't get kicked

When to use this:

You want canceled members to still see archived content
You want to keep them in Discord but deny access to member channels
You're using role-based permissions instead of server removal

Command:

dontKickOnCancel

Bot responds:

true

What "true" means:

Feature is now ON
Canceled members will NOT be kicked
They'll keep the member role
You should manually manage channel access

How it works:

Member cancels subscription
They stay in Discord server
They keep their member role
But you can restrict their channel access manually
Use role permissions to deny access to paid content

To turn it back OFF:

dontKickOnCancel

Bot responds:

false

Now it's back to:

Member cancels → Gets kicked automatically

Practical Examples

Example 1: New Member Joins

Scenario: Someone just signed up

In #launchpass you see:

✅ NEW MEMBER ACTIVATED Name: Sarah Mitchell Email: [email protected] Subscription: Annual ($290/year) Joined: Today at 10:15 AM Tier: Premium

What you do:

See the notification
Welcome them personally
Send them resources
Set expectations
Help them get started

Why it helps:

You know immediately
Can personalize welcome
Build better relationships
Set tone for their membership

Example 2: Member Is Experiencing Issues

Scenario: Member says "I can't see the member channel"

What you do:

Type in #launchpass:

   whois [email protected]

Bot responds with all details
You check:
- Is subscription active? (yes)
- Is payment current? (yes)
- Do they have the role? (check Discord)
- Channel permissions set? (yes)
Troubleshoot based on findings
Fix the issue

Why it helps:

Quick access to all info
Diagnose problems faster
Help members immediately

Example 3: Updating Wrong Email

Scenario: Member signed up with typo in email

What happened:

They signed up: [email protected] (missing 'h')
Should be: [email protected]
Their bills going to wrong email
Causing issues

What you do:

They contact you about wrong email
You type in #launchpass:

   updateUserEmail [email protected] [email protected]

Bot confirms update
Email is changed everywhere
Future notifications go to correct email

Why it helps:

Fix mistakes immediately
Prevents billing issues
Updates across all systems
No manual work needed

Example 4: Member Cancels

Scenario: Important member cancels

In #launchpass you see:

⚠️ MEMBER CANCELLED Name: Mike Thompson Email: [email protected] Subscription: Monthly ($29/month) Cancelled: Today at 2:00 PM Status: Removed from server

What you might do:

See the alert
Reach out to Mike personally
Ask why they canceled
Offer solutions
Try to save the relationship
Learn from feedback

Why it helps:

Immediate alert
Chance to retain
Understand churn reasons
Improve your offering

Best Practices

Channel Security

✅ Keep it private - Only admins should see

✅ Restrict permissions - Turn off view for everyone except admins

✅ Archive old notifications - Keep channel clean

✅ Don't share commands publicly - They're for admins

✅ Protect member info - Don't screenshot emails publicly

✅ Be careful with commands - They make permanent changes

Using Commands Safely

✅ Double-check emails before updating

✅ Verify member identity before changes

✅ Communicate with member if making changes

✅ Test commands on yourself first if unsure

✅ Document changes (optional but helpful)

✅ Contact support if you make a mistake

Notification Management

✅ Check regularly - Don't miss new member alerts

✅ Act on cancellations - Try to save them

✅ Welcome new members - Set good first impression

✅ Keep it organized - Archive old notifications

✅ Export for records - Keep backup of important alerts

Organizing the Channel

Optional: Pin important information

Pin the welcome message
Pin bot command examples
Keep for quick reference
Update as needed

Troubleshooting

"LaunchPass Bot Isn't in My #launchpass Channel"

Why this happens:

Bot doesn't have permissions
Channel wasn't set up correctly
Bot wasn't authorized

What to do:

Check permissions:
- Right-click #launchpass
- Go to Permissions
- Look for LaunchPass bot
- If missing: Add it
Check bot permissions:
- Should have: View, Read, Send Messages
- If missing: Add them
Verify bot is authorized:
- Go to Server Settings → Integrations
- Look for LaunchPass
- Make sure it's there and enabled
If still not working:
- Try kicking bot and re-inviting
- Contact [email protected]

"Bot Isn't Responding to Commands"

Why this happens:

Commands misspelled
Channel permissions wrong
Bot doesn't see message
Command format incorrect

What to do:

Check command spelling:
- whois (not who is)
- updateUserEmail (exact spelling)
- dontKickOnCancel (exact spelling)
Check syntax:
- Make sure spacing is right
- Make sure email format is correct
- Example: whois [email protected]
Check permissions:
- Bot has permission to read messages? (yes)
- Bot has permission to send messages? (yes)
Try again:
- Retype command carefully
- Double-check formatting
- Press Enter
If still fails:
- Contact [email protected]
- Include the command you used
- Include exact error message (if any)