Mar 20, 2024 12:25 PM
As our company and product evolves, we’ve adopted terminology to reference different concepts. This is a living guide to ensure that our users have a good understanding of our product and our team is using consistent terminology as we grow.
A person who is an employee, but has been turned into a team admin or super admin. Their primary interaction with Epoch is creating and managing events. They can access the Dashboard.
A custom Slack message with event blocks sent to selected Slack channels. The goal is to increase registrations for selected events.
An event guest that showed up in a Zoom meeting generated by our integration or was marked as attended through in-person check-in.
An invitation sent through Google Calendar or Outlook Calendar that includes a hold in guests’ calendars and a default invitation email.
The action to RSVP as not attending when a guest already responded to an event.
A guest who either declined or cancelled their spot.
The noun used to refer to our in-person check-in process.
The action of checking into an event.
A page on our dashboard used for event announcements via Slack. This space is meant to scale for email announcements and non-event announcements in the future.
A guest who confirmed and filled out the event questionnaire.
A page used to share links with employees, such as event recordings, articles, or podcasts.
An event’s photo that appears on the event page, Discover page, Slack, and email.
A dashboard on our web app for admins to create, manage, and announce events.
The homepage on our web app for employees to discover company events.
A distribution list that is synced into Epoch through a customer’s distrolist directory. When the directory is synced, people who were added or removed from a distrolist will be updated for events in Epoch and calendar.
The action to RSVP as not attending when a guest hasn’t responded to an event yet.
A person who is in the company’ HRIS. Their primary interaction with Epoch is attending events. They can access the Discover page, but not the Dashboard.
An admin on the Epoch team who has full access to the Dashboard. They have access to Epoch integrations.
An event card is used to showcase an event on the Discover page. It shows basic event information.
A page on our web app that shows an event’s information, guest list, and buttons to RSVP for the event.
A custom survey that is sent to confirmed guests for an event.
A person who isn’t in the company’s HRIS, but attends an event or is invited to an event through calendar.
A custom survey that is sent to guests who attended an event.
An employee who is part of an event. This includes any guest who is invited, pending, confirmed, incomplete, maybe, cancelled, waitlisted, and attended.
A guest who confirmed, but did not fill out an event questionnaire with required questions.
A message sent through Slack or calendar to invited guests. Once the message is sent, the guest’s status will become invited.
The action of inviting someone to an event or content.
A guest who responded as maybe. They will be added to the calendar event as maybe, but their spot is not guaranteed for the event (i.e. doesn’t count toward the capacity limit).
A survey question where more than 1 option can be selected. The question must have a minimum of 1 option.
An event series that has different sessions related to a similar topic.
A guest who previously had an RSVP for an event, but the event's start time was updated.
An event that is only visible to invited guests. Private events cannot be unfurled, they don’t appear in the Discover page to those not invited, and they appear as “busy” in Google Calendar to those not invited.
An event that is visible to everyone in the company across the platform. Public events can be unfurled in Slack if the link is in a message.
An event that has similar sessions that occur at regular intervals.
A custom message sent through Slack or email to guests for an event. These are often used to relay important information to guests or remind guests to register before an event.
A survey question where only 1 option can be selected. The question must have a minimum of 2 options.
A Slack Connect Channel is a kind of Workspace channel that is shared with an external Workspace.
An automated message with an event block sent through Slack to invited guests.
A Slack Organization has dashboard tools that allow Slack admins to centrally manage an organization’s Slack Workspaces. A Slack Organization can contain different Slack Workspaces. It can also be called Slack Enterprise or Slack Grid.
An organization-wide channel is a channel that is tied to a Slack Organization rather than a Slack Workspace.
A Slack Workspace is made up of channels. It can also be called a Slack Team.
An admin who has full access to the Dashboard. The only thing they don’t have access to is Epoch integrations.
A template that is created in the Dashboard for an event questionnaire or feedback form. Admins can select these templates to pre-populate questions for an event or content.
A tag is a short string used to categorize events and content. They’re created in the database and associated with a Discover tab by CX. Multiple tags can be selected for an event or content.
A group that is created within Epoch to represent a subset of people in a company who host events. Examples: “LGBTQ+@ ERG”, Epoch San Francisco”
An admin who has partial access to the Dashboard for specific teams. They can only see events for the teams that they have permissions for. They also don’t have access to employee settings, team settings, and company integrations.
A guest who joined the waitlist for an event that has reached its capacity limit. They will automatically be confirmed into the event when a spot opens up on a first-come, first-serve basis.
Thanks for your feedback!
Get in touch with our customer experience team. We'll reach out with next steps.
Contact us© 2024 Epoch Inc. All rights reserved.
