MapMyStaff glossary
A shared vocabulary for understanding product decisions.
Find the terms used across product pages, the Help Centre, trust flows, and methodology. Each definition stays within the documented scope.
Reference
Bilingual glossaryOne term, one definition, one page to consult
01
Planning and capacityDefinitions linked to documented pages
Review02
Customers and bookingDefinitions linked to documented pages
Review03
Surveys, recovery, and referralsDefinitions linked to documented pages
Review04
Data, security, and measurementDefinitions linked to documented pages
Review01Planning and capacity
Understand the rules that shape a workday.
These terms describe how available information contributes to appointment proposals and field operations.
- Capacity
- An operational reading of what the team can cover based on employees, schedules, absences, territories, and available settings. See Employees and capacity →
- Availability
- A calculated state based on available information and rules to determine whether an appointment can be proposed at a given time. See availability calculation →
- One-hour time slot
- A scheduling model where the day is structured around hourly slots; the module distinguishes it from more flexible period-based planning. See one-hour slots →
- Territory
- A documented coverage perimeter used with address information in flows where that rule applies. See appointment booking →
- Field day
- The operational context that brings together the agenda, schedules, absences, appointments and, when available, estimated travel. See Staff management →
02Customers and booking
Connect the request to the customer record.
Customer terminology distinguishes booking, recorded data, and the historical readings that are available.
- Customer Directory
- The module that brings together the customer record, activity markers, and appointment history when those data are available. See the Customer Directory →
- Customer record
- The set of recorded information accessible for a customer according to available data and access rights. Open the module →
- Appointment history
- Recorded appointments that can be reviewed from the customer record when those data are available. See an example →
- Lifetime value
- A marker shown in the Directory from recorded customer data; its interpretation depends on the available scope. See the methodology →
- Package
- A service configuration that may group price, duration, options, and applicable rules according to the documented workflow. See packages →
03Surveys, recovery, and referrals
Distinguish a signal, an action, and a result.
These terms help avoid confusing recorded information, a workflow state, and an actually observed result.
- Survey
- A configurable questionnaire sent according to the documented workflow to collect customer feedback. See surveys →
- Signal
- Information from a survey or workflow used to prioritize a reading or action; by itself it is not proof of an outcome. Qualify signals →
- Customer recovery
- A follow-up workflow used to qualify a signal, prioritize an intervention, and document handling status. See customer recovery →
- Referral
- A workflow where a code may connect a booking to a referral; the referred-customer discount and referrer reward remain distinct decisions. See referrals →
- Referral reward
- A state distinct from the discount applied to the referred customer; eligibility and payment follow the documented program rules. See validation →
04Data, security, and measurement
Name controls and indicators precisely.
These definitions summarize vocabulary used on trust and methodology pages without expanding the documented guarantees.
- Firebase Authentication
- A service that may manage accounts and session state on protected flows that use it. See trust architecture →
- App Check
- An application token and anti-abuse signal that may protect configured functions; it does not replace server-side validation. See the controls →
- Group access
- A control where some flows read the group associated with the user document; the documented administrator group is group 1. See Security and data →
- Server-side validation
- A check performed on the server before accepting or recording certain actions; it complements interface controls. See validations →
- KPI
- A documented indicator with its scope, calculation method, and interpretation limits. See KPI methodology →
- Observed reference
- A value derived from historical data available within the documented scope. Understand the method →
- Simulated scenario
- A value calculated from assumptions; it is not an observed customer result. See the limits →
Next step
Explore MapMyStaffLooking for a term that is not defined yet?
Use Explore to find the relevant page or the Help Centre to start from a concrete problem.