Members use the Loyalure PWA on their phones. Venue teams configure the business from a laptop or desktop; Door check-in may run on a registered tablet or computer.
Know which Loyalure product to open
Loyalure Member PWA: the guest's wallet, rewards, events, VIP requests, QR, inbox, preferences, and privacy controls.
Loyalure Door: registered-device QR check-in, physical age confirmation, reward handling, offline queue, and audit receipts.
Loyalure Media: sponsor inventory, creative approval, placements, signage, and proof of play.
Sponsor Portal: aggregate campaign delivery and private reports without member PII. Loyalure Control is for authorized Grayston platform staff.
Begin every shift safely
Use your own staff account, complete email-link sign-in and TOTP, and confirm the role shown in the workspace header.
Confirm the organization and venue selector before reading data or making a change.
Review launch/readiness warnings, provider status, open VIP requests, scheduled campaigns, and Door device health relevant to your role.
Do not continue if the venue context is wrong; sign out and contact your owner or Grayston support.
Questions answered
Where do members download Loyalure?
Native iPhone and Android apps are coming soon. During the pilot, members open the venue's Loyalure link in Safari or Chrome and use Add to Home Screen / Install app. The PWA is the complete member product.
Can I configure the venue from my phone?
No. Use a laptop or desktop for Venue, Media, Sponsor, and Control. Door may use a registered tablet or computer because it is a focused check-in workflow, not a configuration surface.
Why do I see fewer modules than another staff member?
Menus reflect role permissions and venue entitlements, but authorization is also enforced server-side. Ask the venue owner for the narrowest additional role genuinely required; do not share accounts.
Is the information in the dashboard live?
Production surfaces show tenant-scoped data and a generated-at timestamp. Some analytics are bounded rollups rather than instant counters; always read the metric definition and freshness label.
Loyalure uses secure email links and requires time-based authenticator MFA for business and platform roles. Every staff member must have an individual account.
Sign in
Open the Loyalure sign-in page on the workstation you intend to use.
Enter your invited email address and request a fresh secure link.
Open the newest link on the same device and browser; old or already-used links may be rejected.
Enter the current six-digit code from your authenticator app when prompted.
Confirm the workspace displays the expected venue and role before continuing.
Invite or remove staff
From Loyalure Venue, open Growth or Team access when your role includes staff management.
Invite the person's business email and select the narrowest role matching their actual duties.
Ask them to complete sign-in and MFA themselves; never scan their MFA QR or keep their secret.
Remove or suspend access immediately when a staff member leaves or changes responsibilities.
Review the audit receipt after any role change.
Questions answered
What if my magic link opens the landing page?
Return to sign-in, request a new link, and open the newest message in the same browser where you started. If it still fails, capture the time and safe screenshot and contact support without forwarding the link.
What if my authenticator code is rejected?
Confirm the phone's date/time is automatic, wait for a new code, and try once more. Repeated failure or a lost device requires the approved recovery process; do not ask another user for their code.
Can an owner see everything?
An organization owner has broad business permissions but still cannot bypass tenant isolation, platform-only controls, feature entitlements, provider approvals, or append-only histories.
What is read-only access for?
It is for people who need authorized visibility without mutation rights. Exports and sensitive guest detail may still require separate permissions.
Preview the public venue page and every launch event on a phone before sharing a QR.
Publish a simple loyalty version and confirm member-facing terms match the simulator.
Create at least one attainable reward with operational instructions and inventory.
Confirm VIP request acknowledgment, assigned owner, and response expectation.
Prepare the team and devices
Invite each required staff role and verify MFA.
Register the Door device and test camera permission, signed-key readiness, duplicate handling, and reconnection.
Print venue/source-specific QR codes only after the final production link is verified.
Run one test join, RSVP, VIP request, check-in, points award, and reward redemption before launch.
Questions answered
Does publishing the venue make it native-app eligible?
No. Web/PWA publication, plan entitlement, and native distribution are independent. Native apps are coming soon and native eligibility is a separate Grayston-controlled review.
Can we launch without online payments?
Yes. Request-only VIP is the production pilot default. A member submits interest; the venue follows up through its approved process. No 3% platform fee applies to requests or offline transactions.
How do we know the correct QR is printed?
Scan the final printed proof with a phone, confirm the exact venue page and source, complete a test join, then mark the artifact approved. Do not shorten or hand-edit Loyalure links.
State age requirements and material reward/event restrictions where the member acts.
Use discreet notification previews because members may receive them on a locked screen.
Questions answered
Can we use performer or adult imagery?
Use tasteful, approved venue/event creative and follow the Grayston brand-safety posture. The member product must remain discreet and suitable for browser installation and future store review; explicit imagery is not acceptable.
Can the venue use a custom domain?
Only when the entitlement, DNS ownership, certificate, canonical behavior, and production verification are complete. Until then, use the approved Loyalure URL.
What happens if two managers edit at once?
Versioned records reject stale updates. Reload, compare the newer value, and intentionally reapply your change rather than overwriting another manager's work.
Loyalty versions make earning rules predictable. Published member terms, operational cost, caps, and effective dates should agree before a program is activated.
Publish a loyalty version
Open Launch & loyalty and review the current version, points expiration, tiers, and effective date.
Define simple earning events such as RSVP, successful check-in, qualified weekday visit, referral milestone, or qualified VIP request.
Set daily/weekly/monthly caps, blackout conditions, one-award rules, and tier thresholds.
Run the simulator for ordinary, high-frequency, duplicate, and ineligible examples.
Publish a new effective-dated version; do not rewrite historical versions.
Correct a points mistake
Confirm the member, venue, original ledger item, business reason, and amount.
Use the authorized manual adjustment workflow and enter a clear reason.
Create an equal compensating entry where appropriate; never delete or edit the original ledger entry.
Verify the resulting balance equals the sum of valid ledger entries and review the audit receipt.
Questions answered
When are check-in points awarded?
Only after an authorized successful check-in transaction. Replaying the same token or idempotency key cannot create a second award.
Can points be transferred between venues?
Not by default. Points and terms are venue- or organization-specific according to the published program. A platform identity can hold separate memberships and balances.
Can points have cash value?
Do not describe points as cash unless qualified counsel and program terms specifically support it. Loyalure tracks a separate internal liability estimate; that is not a member cash balance.
How do tier changes work?
They follow the published qualification window and thresholds. Effective-dated rules govern upgrades/downgrades; staff should not manually relabel members to bypass them.
A reward is both a member promise and an operational inventory item. Configure what staff can actually recognize and fulfill.
Create or update a reward
Enter a clear public name/description and separate internal fulfillment instructions.
Set points cost, eligible tiers/segments, validity, blackout dates, venue restrictions, member/night limits, and inventory.
Choose whether staff approval is required and identify which role may approve/redeem.
Preview terms in the member PWA, then activate or schedule the reward.
Pause rather than delete a reward when fulfillment becomes temporarily unavailable.
Approve and redeem
Ask the member to open the reward from their own Loyalure wallet; do not accept a screenshot as proof.
Confirm the code/token, venue, status, expiration, inventory, and staff-approval requirement.
Approve and redeem once through the authorized workflow.
If fulfillment cannot occur, use the documented void/correction path with a reason instead of reusing the token.
Questions answered
Why is a member unable to reserve a reward?
Check points balance, tier/segment, validity, blackout, venue, per-member limit, per-night limit, inventory, and current reward state. The wallet should show the eligibility reason; do not override by changing the ledger casually.
Can staff redeem from a screenshot?
No. Require the live member wallet or approved secure code path. Screenshots can be stale or replayed.
What if inventory runs out after a member reserves?
Follow the published terms and venue service policy. Do not silently delete the reservation. Use an authorized void, replacement, or compensating resolution with an audit reason.
The CRM is a consented operational record, not a list to message indiscriminately. Access and exports are tenant-, role-, and purpose-scoped.
Find and understand a member
Open Guests & VIP and search only within the selected venue context.
Review venue membership, channel consent, points/tier, visits, RSVPs, VIP requests, referrals, reward history, and campaign history.
Use manager-only notes for necessary operational context; keep notes factual, minimal, and professional.
Do not copy member information into personal spreadsheets, texts, or unsupported systems.
Build a safe segment
Start with a business question such as inactive members, weekday visitors, upcoming birthdays, or RSVP non-attendees.
Build AND/OR criteria and inspect the estimated eligible count.
Apply channel consent, suppression, age/venue eligibility, quiet hours, and frequency caps at send time.
Save an understandable name and description; review small or surprising audiences before approval.
Import or export
For import, map fields, preview validation, resolve duplicates, and preserve known/unknown/revoked consent exactly.
For export, confirm role, purpose, minimum fields, tenant scope, and secure destination before requesting the job.
Download from the private authorized result, protect the file, and delete local copies when the purpose ends.
Review the import/export audit receipt and rollback report where applicable.
Questions answered
Does an email address mean the member opted into marketing?
No. Marketing requires valid channel-specific evidence. Unknown, revoked, or suppressed contacts remain ineligible even if they match the segment criteria.
Can we add private notes about a guest?
Only necessary, factual, professional operational notes accessible to authorized roles. Never enter sensitive speculation, protected-class data, passwords, payment data, or government-ID details.
Can a sponsor receive our member list?
No. Sponsor users receive their own campaign and aggregate delivery metrics only. Member PII is structurally isolated.
How are duplicate profiles handled?
Use the authorized merge workflow after verifying identity and tenant context. Preserve consent, ledger, visits, and audit histories; never merge solely because names look similar.
Published event data feeds the public page, member plans, RSVP capacity, reminders, Door context, and attribution. Accuracy matters everywhere at once.
Create and publish an event
Choose the correct venue, date/time/timezone, minimum age, capacity, waitlist, RSVP limit, and plus-one rules.
Preview mobile and desktop public pages and confirm calendar/timezone rendering.
Generate a source-specific link/QR for each placement or partner you need to measure.
Publish only after the event owner approves the facts and operational capacity.
Operate RSVPs
Monitor going, waitlisted, canceled, and checked-in states; do not treat RSVP as guaranteed entry unless venue policy explicitly says so.
Use the authorized waitlist promotion flow so capacity is released and claimed atomically.
Reconcile Door arrivals to RSVP status and investigate surprising conversion rather than editing counts.
Archive completed events after reporting needs are met; do not delete their attribution history.
Questions answered
Does an RSVP guarantee entry?
Only if the venue's published terms explicitly guarantee it. Otherwise it records intent and capacity status; physical age/ID, venue policies, and lawful entry decisions still apply.
What if the event time changes?
Update the event through the versioned workflow, review reminders/campaigns, and communicate materially affected members through an approved transactional path. Verify the public and member views afterward.
Can we reuse one QR everywhere?
You can, but source-specific links are strongly preferred for flyers, partners, tables, and campaigns because they preserve attribution and make bad artifacts easier to retire.
A VIP submission is a request until venue staff confirms it. Fast ownership, clear public updates, and disciplined private notes are more important than a complex pipeline.
Work a new request
Review requested date, arrival window, group size, occasion, package interest, budget range, contact preference, notes, and source.
Assign one host and make first contact within the venue's published response expectation.
Move the request through new, contacted, qualified, awaiting guest, offered, confirmed, arrived, completed, canceled, no-show, or lost as facts change.
Use public updates for information the guest can see and private notes only for necessary internal coordination.
Record a clear outcome/lost reason and next action.
Handle deposits during the pilot
Keep production in request-only mode unless Grayston confirms an approved processor capability.
Do not collect card numbers or sensitive payment data in Loyalure notes, email, or chat.
If the sandbox is used for training, label it clearly and reconcile signed webhook behavior exactly once.
The 3% demonstration rule applies only to eligible online VIP/package deposits processed through Loyalure, never to requests, cash, tips, door sales, or unrelated venue revenue.
Questions answered
Is a submitted VIP request confirmed?
No. It is a request until an authorized host moves it to confirmed and the venue communicates the applicable terms.
Can we quote a price in Loyalure?
Use approved package or range information and record quoted value in integer minor units where supported. Do not invent pricing, tax, availability, or processor promises.
What should be a private note?
Necessary internal assignment, factual follow-up, operational constraints, and outcome context. Never enter card data, government-ID data, protected-class information, or disparaging/speculative comments.
What if a guest asks for a refund?
In request-only mode there is no Loyalure payment to refund. For an enabled approved processor, use the provider-backed refund-request workflow and follow venue policy; never promise an outcome before reconciliation.
Pilot channels are in-app, push, and email. SMS is not available. Every marketing send must pass channel consent, suppression, age/venue eligibility, quiet hours, frequency caps, and approval.
Create and approve a campaign
Choose a business objective and an understandable saved segment.
Select only configured channels: in-app, Web/Expo Push, or email. Do not create or promise SMS delivery.
Write discreet content with safe personalization fallbacks and an accurate venue identity.
Review the estimated eligible count after consent, suppression, quiet-hour, frequency, and venue checks.
Send a test to authorized recipients, complete approval, schedule, and record the attribution window/control group.
Read results honestly
Separate queued, sent, delivered, failed, clicked, opted out, RSVP, VIP request, and check-in counts.
Use source links and the documented attribution priority; an attributed visit is not automatically causal lift.
Compare a control group when available and label modeled estimates separately from measured facts.
Investigate opt-outs, complaint signals, or provider failures before cloning the next campaign.
Questions answered
Can we send SMS?
No. SMS and phone OTP are outside Loyalure v1, the SMS feature key remains disabled, and no SMS UI or sending path is shipped.
Why is the eligible count lower than the saved segment?
A segment describes matching records. Send eligibility further removes invalid consent, suppressions, wrong venue/age, channel absence, quiet hours, frequency caps, control group, and provider restrictions.
Can adult-venue marketing email be activated?
Only after the configured provider explicitly approves that tenant category and all consent/content controls pass. Until then, keep it disabled and use in-app/member-owned paths.
What is a transactional message?
A necessary account or requested-service update such as sign-in, RSVP status, or VIP request status. Classification is purpose-based; calling promotional content transactional does not bypass consent rules.
Door is optimized for a registered tablet or computer, low light, minimal PII, and fast decisions. Physical age/ID responsibility always remains with trained venue staff.
Open the Door shift
Use the registered device and your own Door-authorized account with MFA.
Confirm the venue, device status, camera permission, network state, and venue public signing key before doors open.
Keep the device powered, time-synchronized, physically controlled, and on the approved network when possible.
Review the physical age-check requirement and the escalation path for denied or unclear entry.
Scan a member
Ask the member to open the live rotating QR from their Loyalure PWA; do not use a screenshot.
Scan the token and confirm the result belongs to the selected venue and is not expired, replayed, or denied.
Perform the venue's physical age/ID check and record only that verification occurred—never an ID image or number.
Accept the check-in once and show the member the success/points result when available.
Escalate denied, expired, duplicate, cross-venue, or unclear results rather than forcing a manual award.
Use offline mode
Offline mode accepts signed-token check-in only after the device loaded the venue public key online.
Phone/name lookup is unavailable offline because Loyalure does not cache member PII on the device.
Keep the encrypted pending count visible and reconnect within the authorized reconciliation window.
Sync once, review conflicts, and never clear browser/device storage before pending check-ins reconcile.
Questions answered
What if the QR will not scan?
Increase screen brightness, clean the camera, move out of glare, confirm camera permission, and ask the member to refresh the live QR. Use the approved online fallback only; do not photograph the code.
What does duplicate or replay mean?
The token or idempotency context was already used. Confirm recent accepted activity; do not scan repeatedly or award points manually unless an authorized manager completes a documented correction.
Can we look up a guest by phone while offline?
No. Offline mode intentionally stores no searchable phone/name PII. Restore connectivity or follow the venue's separate entry process without representing it as a Loyalure check-in.
Can Door store an ID photo or number?
No. Record only the authorized physical-verification flag. Loyalure does not require or store government-ID images, numbers, or biometrics by default.
What if the device is lost?
Notify the venue owner and Grayston immediately, revoke the Door device, remove staff access as needed, and follow the incident process. Do not wait for the next shift.
Loyalure Media proves scheduled and measured delivery without exposing member identity. Sponsor access is aggregate and scoped to the sponsor's own campaigns.
Launch a sponsor placement
Create or verify the sponsor organization and approved brand-safety category.
Reserve the correct venue inventory, flight dates, schedule, pricing model, and internal contract value.
Upload creative that meets dimensions/type/size requirements, then complete venue and platform approval.
Create the placement with the approved creative version, disclosure, target/schedule, and attribution link or QR.
Preview the public/PWA/signage destination and verify no member PII is available to sponsor users.
Operate signage and reports
Pair each signage device to the correct venue/screen group and publish an approved playlist.
Verify autoplay-safe playback, device health, local cache behavior, schedule, and proof-of-play timing.
Treat view opportunities as estimates unless technically measured; do not guarantee impressions.
Generate reports from immutable authorization-checked snapshots and confirm the no-PII assertion before sharing.
Questions answered
Can a sponsor upload anything directly to screens?
No. Creative requires the configured approval stages and only an approved version can be placed or published to signage.
What does proof of play prove?
It records that an approved creative was actually in a playable state on the registered device for the validated interval. It does not prove that a particular person watched it.
Can reports include names or contact details of members who scanned?
No. Sponsor reports use aggregate delivery and attribution measures. Member identity and contact information remain isolated.
What if a screen goes offline?
The player may use its approved cached playlist briefly. Investigate device health, reconnect, and confirm proof resumes. Do not fabricate plays for the outage period.
Reporting
Dashboards, definitions, and truthful interpretation
Loyalure metrics are definition-backed and tenant-scoped. Use them to make decisions, not to manufacture a success story.
Read a dashboard
Confirm venue, date window, timezone, data freshness, and whether demo/test records are included.
Open the metric definition before comparing a number to another system.
Drill into underlying authorized records when a KPI looks surprising.
Separate counts, conversion rates, contracted/invoiced/collected value, and modeled estimates.
Export only when necessary and protect the private result.
Use attribution responsibly
Read the configured source priority and attribution window.
Treat a click/scan followed by a visit as attributable under that definition, not proof that the campaign caused the visit.
Use control groups when you need genuine lift evidence.
Document seasonality, event changes, capacity, and other material context in decisions.
Questions answered
Why does Loyalure differ from a POS or door count?
Systems may measure different people, time windows, event states, or eligibility. Compare definitions and reconciliation records before labeling either number wrong.
What is repeat visit rate?
Members with at least two successful check-ins in the selected rolling window divided by members with at least one successful check-in in that same window.
Does attributed revenue mean Loyalure caused it?
No. Attribution associates an outcome under a documented rule. Causal lift requires an appropriate comparison/control and careful interpretation.
What is points liability?
Outstanding unexpired points multiplied by the venue's accounting estimate. It is labeled an estimate and is not a member cash balance.
Member requests are authenticated workflows. Consent, points, and audit histories remain append-only; privacy processing removes or anonymizes PII while preserving only what policy requires.
Handle a member request
Direct the member to the signed-in Privacy section of their Loyalure PWA whenever possible.
Do not accept a sensitive export/deletion request solely through an unverified email, DM, or verbal message.
Confirm the request is queued and do not promise immediate deletion before identity, retention, and legal checks complete.
Stop nonessential marketing through consent/suppression controls while required transactional notices may continue.
Escalate through the venue privacy owner and Grayston support without copying unnecessary PII.
Use member data appropriately
Access only the venue, purpose, and fields required for your role.
Never store government-ID images/numbers, biometrics, raw card data, passwords, authenticator codes, or access tokens in Loyalure notes.
Do not share member PII with sponsors or outside tools without an approved purpose and policy.
Respect revocation and suppression immediately; consent history itself is not erased or rewritten.
Questions answered
Can staff delete a member directly?
No ad hoc deletion. Use the verified privacy workflow so identity, tenant scope, retention, anonymization, and audit requirements are handled consistently.
Can we remove a consent record?
No. Consent history is append-only. Record revocation or a correction event; do not erase the historical evidence.
What remains after deletion?
Only minimally necessary anonymized or non-PII audit, financial, fraud, security, and integrity records allowed by the applicable policy. The exact result depends on the approved retention rules.
Can members leave one venue but keep Loyalure?
Yes. Platform identity and venue memberships are separate. Leaving a program should stop venue-specific access and marketing while preserving other valid memberships and required history.
Settings
Providers, payments, push, email, and entitlements
A visible module does not mean its external provider is approved. Entitlement, provider capability, consent, and role permission each remain independent gates.
Check capability before use
Open provider readiness and confirm configured, sandbox-ready, approved, disabled, or failing state.
Verify the venue entitlement and your permission for the requested action.
For messaging, confirm production keys/domain, provider category approval, consent, and a real-device canary.
For payments, remain request-only unless Grayston identifies the approved production adapter and reconciliation receipt.
Report a failing provider with time, venue, action, provider state, and correlation ID—never the secret itself.
Request a capability change
State the business need, venue, proposed users, data involved, provider, and launch date.
Have the venue owner approve the business/legal responsibility.
Grayston validates commercial scope, entitlement, provider policy, credentials, health check, rollback, and audit path.
Activate in a bounded canary before wider use.
Questions answered
Why is a feature visible but unavailable?
The interface may explain an entitled or upsell capability while the API still requires tenant entitlement, role permission, provider approval, and policy. Read the status and contact the named owner.
Can we enter our own API key?
Only through the approved secret-management and integration process. Never paste secrets into notes, normal forms, email, chat, source code, or screenshots.
When does the 3% fee apply?
Only to an eligible online VIP/package deposit processed through Loyalure under an enabled rule snapshot. It never applies to request-only VIP, cash, tips, door sales, food/bar revenue, or unrelated payments.
Can a rollout percentage turn on a paid feature?
No. Staged rollout controls exposure among already eligible tenants; it never creates a plan entitlement and explicit deny still wins.
Start with scope and evidence. Most recoveries are faster when support knows the venue, role, surface, time, exact action, and correlation ID.
Use the two-minute recovery check
Confirm internet access, system time, browser support, selected venue, staff role, and MFA state.
Reload once. Do not repeat a mutation such as check-in, redemption, send, or invoice entry until you know whether the first attempt succeeded.
Read the full status/error and copy the correlation ID without member data.
Check whether the issue affects one member, one device, one role, one venue, or every user.
Use the safe fallback: request-only VIP, pause the affected campaign, online Door fallback, or normal venue process as applicable.
Escalate effectively
Provide venue, surface, URL path, time/timezone, your role, expected result, actual result, and safe screenshot.
Include correlation ID, device/browser, network/offline state, and whether retry was attempted.
Mark urgent only for security/privacy, tenant boundary, widespread sign-in, active Door, duplicate ledger, live campaign, or material member impact.
Never send passwords, magic links, authenticator codes, access tokens, provider secrets, full card data, or government-ID data.
Questions answered
The page says access denied. Is it broken?
Usually it means your role, tenant context, or entitlement does not allow the action. Confirm the selected venue and ask the owner for the correct narrow role. Support should not bypass the API boundary.
The page is offline. What should I do?
Restore connectivity and retry the read. Only Door signed-token check-in has an encrypted offline queue; business configuration, phone/name lookup, exports, and campaigns require online access.
A button was clicked twice. What now?
Stop and inspect the resulting record/history before retrying. Loyalure uses idempotency for critical mutations, but support still needs the correlation/record status to resolve the user experience safely.
How do I report a suspected privacy or security issue?
Stop the affected action, preserve safe evidence, notify the venue owner and Grayston through the designated urgent channel, and avoid copying or further exposing the data. Do not attempt your own cross-tenant test in production.
What if this manual does not answer my question?
Send Grayston the venue, Loyalure product, your role, goal, exact steps, expected result, actual result, time/timezone, and correlation ID. That gives support enough context to answer without requesting broad access.
A light recurring rhythm keeps the venue current and prevents launch configuration from becoming stale.
Every operating day
Review provider/incident state, today's events, open VIP requests, scheduled campaigns, reward availability, and Door device health.
Assign every urgent VIP/member issue and confirm Door staff/device readiness before opening.
At close, review accepted/offline check-ins, pending reconciliation, reward issues, and unresolved guest follow-up.
Every week
Review member growth, repeat visits, RSVP conversion, VIP response/completion, reward utilization, opt-outs, and failed deliveries.
Retire outdated events/links, check reward inventory and economics, remove obsolete staff access, and review upcoming content.
Choose one measurable improvement for the next week rather than changing many rules at once.
Every month
Review program versions, points liability estimate, campaign frequency, sponsor delivery, data freshness, plan usage, and provider health.
Audit staff roles/devices, exports, privacy queue, open support access, incidents, and unresolved dead letters with Grayston as applicable.
Record the owner decision: continue, adjust one bounded program element, or request a scoped capability review.
Questions answered
Who should own the daily check?
A named venue manager with backup coverage. Door, VIP, and marketing specialists own their queues, but the manager confirms the whole night is staffed and recoverable.
How often should loyalty rules change?
Only when there is a clear member/business reason and enough time to measure the current version. Frequent changes confuse members, staff, liability reporting, and attribution.
What should be reviewed after every event?
Published facts, RSVP/waitlist, arrival reconciliation, source attribution, loyalty awards, VIP outcomes, sponsor delivery, member issues, and any corrective action with an owner.