Group Bookings and Event Ticket Transfers

Choose the booking workflow around individual admissions, even when one friend pays. SocialLoop brings ticket sales, guest records and QR check-in into the same event workspace. Keep the buyer, the order and each person who may enter separate in your records; a four-person purchase must not become one ambiguous name at the door.

Your two events have 120 admissions and $3,000 in face-value sales. SocialLoop can support the event and community workflow, but your mandatory four-person order with separate arrivals needs a specific rehearsal. Confirm the number of issued tickets, the names staff can see and whether each guest receives a usable ticket before choosing it for this requirement.

Until individual assignment and separate arrival are demonstrated, use individual purchases or a host-reconciled roster with one admission per person. Do not promise buyer self-service name changes or transfers from the existence of a plus-one field.

Renaming a guest-list entry is not the same as transferring a purchased ticket. SocialLoop’s documented agent guest-edit operation excludes purchased tickets. A name correction must preserve the original order reference and a clear admission record; a transfer additionally needs an ownership and old-ticket validity rule.

For two staff members, test scanning one ticket twice on connected devices, then rehearse the loss of connectivity. The web scanner needs internet. The iOS scanner can preload tickets and queue offline check-ins, but disconnected devices cannot be assumed to share a real-time duplicate decision. Use one exception owner.

30 separate orders at $100.00 produce $3000.00 in face-value sales. Absorbed ticket and card-processing fees total $261.00. Add $19.99 for the monthly Premium plan: $280.99 in modeled software and transaction costs, leaving $2719.01 before other expenses.

This models thirty four-person orders across the month, each totaling $100, with host-absorbed fees and monthly Premium. If everyone buys separately, processing costs differ; compare the actual order mix before quoting a margin.

Run one four-person order from checkout through two separate arrivals. Verify names, four admission records, remaining inventory and duplicate rejection, then export the list. If the paid-ticket assignment requirement is not demonstrated, keep that selection decision open.

A ticket transfer must change who holds the admission and define what happens to the original code. Changing a guest’s name or forwarding a screenshot is not equivalent. SocialLoop supports ticket sales, guest lists and check-in, but a complete buyer self-service transfer workflow has not been verified for the requirement below.

For two 80-person events, SocialLoop is worth considering for the broader host workflow. However, if guests must independently transfer one purchased ticket out of a group order, make that a selection gate. Do not replace a mandatory self-service requirement with a promise that the host can edit a guest list.

A host-assisted alternative must identify the original order, the particular admission, recipient acceptance and which code remains valid. Only use it once the supported paid-ticket process is confirmed; do not improvise by issuing a second admission and leaving the first active.

Define pending, accepted, canceled and already-used transfers separately. After acceptance, test the original ticket and the recipient’s ticket on two connected devices. Only the intended valid admission should succeed. A correct attendee name alone does not prove that the old code was revoked.

SocialLoop’s agent edit_guest operation handles guest-list entries, not purchased-ticket transfers. Offline scanning introduces another constraint: a disconnected device may not have the latest ownership change. Keep transfer exceptions with the host and verify current status before admitting either person.

160 separate one-ticket orders at $25.00 produce $4000.00 in face-value sales. Absorbed ticket and card-processing fees total $384.00. Add $19.99 for the monthly Premium plan: $403.99 in modeled software and transaction costs, leaving $3596.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.

This is a ticketing budget, not proof that the required transfer flow exists. Before opening sales, demonstrate one-ticket transfer out of a group order, rejection or expiry, recipient acceptance, original-code invalidation, duplicate scanning and loss of connectivity. Keep the requirement open if any case cannot be demonstrated.