Skip to main content

Events

Scoutello's event tooling covers scheduling, participation, operational controls, commerce-oriented ticket structures, and guest-facing landing experiences for discovery and interaction.

Events sit between CRM, guest web apps, and commerce. They can be used for conferences, workshops, hospitality events, member gatherings, destination programming, internal sessions, or public experiences.

Core concepts​

  • Organization event: The tenant-scoped event record managed from /organizations/:id/events.
  • Participants: Attendee or invitee records tied to a specific event and optionally linked to CRM customers.
  • Customers: The broader CRM contact records that can carry history beyond one event.
  • Landing pages and tiles: Guest-facing event pages, agendas, site plans, chats, raffles, voting, networking, and other interaction modules.
  • Orders and payments: Commerce records created by ticketing or checkout flows.
  • Mail templates and newsletters: Communication surfaces for confirmations, reminders, updates, and follow-up.

Typical event workflow​

  1. Create the event inside the active organization.
  2. Add dates, place/address context, tags, descriptions, and responsible staff.
  3. Configure participant groups, registration settings, ticketing, or access rules when relevant.
  4. Attach or create a landing page for guest-facing information and event tiles.
  5. Prepare mail templates, newsletters, widgets, or QR links for promotion.
  6. During the event, monitor participants, check-in, questions, networking, or engagement modules.
  7. After the event, connect follow-up tasks, protocols, documents, and customer history in CRM.

Guest engagement​

Events work best when the operational record and guest web app use the same source of truth. A public landing page can surface:

  • Schedule and location information.
  • Site plans and places.
  • Contact forms and FAQs.
  • Networking, voting, quiz, raffle, chatroom, or media gallery tiles.
  • Offers and sponsor content.
  • Ticketing or checkout entry points.

Guests stay in a browser-first journey, while the team keeps participant, content, and follow-up context in the dashboard.

Support Checks​

When troubleshooting events, identify whether the issue belongs to the organization event record, guest landing page, participant/customer link, mail delivery, or checkout. For example, a person can have an event participant record without the expected CRM customer link, and an order can exist while event access still needs investigation.

Related concepts: Use case: events, Dashboard: events.