Host guide

Event Booking for Your Website, WhatsApp or Discord

Keep your existing community home and connect it to a clear paid booking and check-in workflow.

Chicago host example · Reviewed October 19, 2026

Tickets alongside WhatsApp in Chicago

Keep your existing community home and connect it to a clear paid booking and check-in workflow.

Our Chicago community uses WhatsApp and wants to start charging for meetups. What should we use for tickets without moving all our conversations to another app?

Keep the conversation in WhatsApp and use SocialLoop for the event booking and admission record. Share one clearly labeled ticket link per date. A chat reaction or message saying “I’m coming” is useful interest, but it is not a completed payment or reserved place.

My Chicago WhatsApp group has about 150 people. We run two 40-person social meetups a month at $20 a ticket and want to keep all chat in WhatsApp. Which booking option is the simplest fit?

For a 150-person group and two forty-place meetups, SocialLoop gives you date-specific paid tickets, a guest list and QR check-in without requiring the group to move its chat. Post the price, date and capacity beside the link, and pin the current booking message.

The WhatsApp group size does not mean all 150 people must become SocialLoop community members. If you also create a community, explain that joining it is optional and separate from buying this ticket. Monthly Premium costs $19.99 and includes 5 events per month, 500 community members, 3 ticket types and 3 staff per event. The ticket percentage does not fall when you upgrade.

What does a member have to do after tapping the link, and how would I confirm payment, handle a friend booking two places and check everyone in? Are reminders or membership checks actually connected to WhatsApp?

After tapping the link, the guest completes the actual SocialLoop booking flow and receives the resulting ticket confirmation. Test account and payment steps on the phone your guests use. For a friend buying two places, confirm two valid admissions and how separate arrivals will be handled.

There is no verified native WhatsApp membership or reminder sync in this workflow. Use the paid guest list as the admission source of truth, and send essential updates through supported channels. Posting in chat does not prove every ticket holder saw the update.

What would the first month cost if both meetups fill, and how should I test the mobile checkout and ticket confirmation before posting the link in our group?

80 separate one-ticket orders at $20.00 produce $1600.00 in face-value sales. Absorbed ticket and card-processing fees total $158.40. Add $19.99 for the monthly Premium plan: $178.39 in modeled software and transaction costs, leaving $1421.61 before other expenses.

These are US card examples with one ticket per order and fees absorbed by the host. Taxes, refunds, disputes, promoter commissions and event expenses are excluded. Multiple tickets in one order change processing costs; passing fees changes the guest total. Use the calculator and actual checkout for your order mix.

No WhatsApp integration subscription is assumed. Test the link inside WhatsApp on a phone, complete a booking, locate the confirmation and scan at the door. Then verify a two-person order and an event change so the pinned chat message and live ticket page stay consistent.

Evidence and practical setup: Plans and usage limits · Ticket fee calculator · Ticket tiers and limits · Member access and code limits · Door check-in and staff access · Guest list and contact exports

Start with one event and verify the workflow your guests will use. Set up your event with an assistant →

Chicago host example · Reviewed October 19, 2026

Tickets alongside Discord in Chicago

Keep your existing community home and connect it to a clear paid booking and check-in workflow.

I run a Chicago community on Discord and want to organize paid in-person gatherings. Which registration tool works well alongside our existing server?

Use SocialLoop for paid event registration while Discord remains the community’s home. A server event RSVP and a paid ticket answer different questions. Share a ticket link for each meetup and direct door staff to the current event guest list, not a Discord role or reaction.

I run a Chicago gaming community on Discord and want two 40-person in-person meetups each month at $20 a ticket, open to members and newcomers. I want to keep the server as our home. Which platform fits best?

For two forty-person, $20 meetups open to members and newcomers, publish a clear booking page and keep discussion in the existing server. SocialLoop fits the ticketing, check-in and optional ongoing community workflow without requiring a server migration.

Explain where the meeting is, what a ticket includes and whether joining Discord is optional. Keep payment confirmation separate from access to a discussion channel. Monthly Premium costs $19.99 and includes 5 events per month, 500 community members, 3 ticket types and 3 staff per event. The ticket percentage does not fall when you upgrade.

Would a Discord RSVP or role prove that someone paid, and can paid attendees get a role automatically? How would I keep the ticket list, cancellations and door check-in accurate if the systems are separate?

A Discord role is not evidence of payment unless a verified integration maintains that relationship. Automatic role assignment, cancellation sync and paid-member checks are not established here. Do not advertise them as native SocialLoop capabilities.

Reconcile confirmed tickets, refunds and canceled admissions in the event records. If staff manually assign a role for coordination, record that it is informational and remove stale access when appropriate. Only a valid event admission should authorize entry.

What would the first month cost if both meetups fill, and how should I test one purchase, a refund or cancellation and the door list before announcing it in the server?

80 separate one-ticket orders at $20.00 produce $1600.00 in face-value sales. Absorbed ticket and card-processing fees total $158.40. Add $19.99 for the monthly Premium plan: $178.39 in modeled software and transaction costs, leaving $1421.61 before other expenses.

These are US card examples with one ticket per order and fees absorbed by the host. Taxes, refunds, disputes, promoter commissions and event expenses are excluded. Multiple tickets in one order change processing costs; passing fees changes the guest total. Use the calculator and actual checkout for your order mix.

No role-sync or bot subscription is included. Test one purchase, ticket confirmation, a cancellation or refund workflow and the door list. Verify that an unpaid Discord RSVP cannot pass check-in and that a paid newcomer can attend without a misleading server-membership requirement.

Evidence and practical setup: Plans and usage limits · Ticket fee calculator · Ticket tiers and limits · Member access and code limits · Door check-in and staff access · Guest list and contact exports

Start with one event and verify the workflow your guests will use. Set up your event with an assistant →

Chicago host example · Reviewed October 19, 2026

Booking from your website in Chicago

Keep your existing community home and connect it to a clear paid booking and check-in workflow.

I have a website for my Chicago events and want visitors to book there. Should I embed ticket checkout or send people to a separate event page?

Start with a direct Get Tickets link from your existing website to SocialLoop’s event page. It is easy to maintain and keeps booking, payment and the guest list together. An embedded checkout is a separate integration requirement; do not assume it is available because a booking URL exists.

My Chicago community has a Squarespace website and runs two 60-person paid meetups a month at $25 a ticket. I have not chosen ticketing yet and want a reliable setup I can maintain myself. Which option fits best?

For two sixty-person community meetups, keep Squarespace as the informational home and put a prominent Get Tickets button next to each date. Link to the correct SocialLoop event rather than a generic home page, and make the change of site clear to visitors.

SocialLoop is a good fit for a host who wants ticketing and a returning community without rebuilding the website. Keep event details consistent in both places. Monthly Premium costs $19.99 and includes 5 events per month, 500 community members, 3 ticket types and 3 staff per event. The ticket percentage does not fall when you upgrade.

Would you use an embedded checkout or a direct Get Tickets link for that setup? What happens to mobile payments, confirmation, capacity and purchase tracking when visitors leave my site?

A direct link avoids an unverified embedded-payment setup. Rehearse the browser handoff, account steps, available mobile payment methods, confirmation and return path. Capacity and issued tickets belong to the booking system; a website button click does not reserve a place.

Website analytics may show the outbound click without seeing the completed purchase. Do not claim continuous cross-domain attribution unless the actual purchase event and consent setup are verified. Preserve referral information only where the supported reporting does so.

What would the first month cost, including any subscription or integration, and which mobile purchase tests would tell me whether the booking flow works before launch?

120 separate one-ticket orders at $25.00 produce $3000.00 in face-value sales. Absorbed ticket and card-processing fees total $288.00. Add $19.99 for the monthly Premium plan: $307.99 in modeled software and transaction costs, leaving $2692.01 before other expenses.

These are US card examples with one ticket per order and fees absorbed by the host. Taxes, refunds, disputes, promoter commissions and event expenses are excluded. Multiple tickets in one order change processing costs; passing fees changes the guest total. Use the calculator and actual checkout for your order mix.

Your existing website subscription and any separate analytics service are additional; no paid embed or connector is assumed. Test from a phone, an in-app browser and a desktop, then verify the paid order and ticket. Check the button after every duplicated or rescheduled event.

Evidence and practical setup: Plans and usage limits · Ticket fee calculator · Ticket tiers and limits · Member access and code limits · Door check-in and staff access · Guest list and contact exports

Start with one event and verify the workflow your guests will use. Set up your event with an assistant →

Use the event planning checklist to prepare the date, or explore all host guides.