Glossary
Plain definitions for the terms you will meet in these docs, from staff confirm and direct booking to included minutes and the words compliance reviewers look for. Older names you may still see are here too.
At a glance
- One place for the vocabulary used throughout the docs, in plain words.
- Grouped by topic: platform, booking, billing, trust, and dental terms.
- Each term links on to the guide that covers it in depth.
Platform and channels
- AI front desk
- The SpiderLabs product: an AI receptionist that answers, takes down, and follows up on calls and chats for businesses that run on appointments, so a missed call does not become a lost customer.
- Business that runs on appointments
- Any business where booked time is the revenue: dental and medical practices, med spas, law firms, home services, salons, and restaurants that take reservations. Staff confirm coverage works for all of them; dental is our deepest vertical, proven in production.
- No vendor names on your screens
- Everything your staff and customers see carries SpiderLabs and your brand, with no other company’s names or links. Transcripts and recordings open through audited SpiderLabs access. You may have seen this called provider neutral.
- Your business details
- What the receptionist knows about your business: the services you do and do not offer, your hours, your staff, and the answers to common questions. You give them to us at launch, and they live in your Knowledge Base. You may have seen this called ground truth.
- Intent
- The reason for a call, tagged automatically: booking, hours, a service question, billing, and so on. Intents roll up in Analytics to show what people call about most.
Booking and workflow
- Staff confirm
- The mode every business starts in. The receptionist handles the conversation and the intake, and anything that needs a person, appointment requests included, becomes a callback your staff confirm. Your front desk keeps the final say over the calendar.
- Direct booking
- When the receptionist books an appointment straight into your connected schedule during the call, instead of taking a request. Proven today with Open Dental, and turned on only after a booking test passes. See Booking modes.
- Callback
- A follow up the receptionist creates when a caller leaves a message, needs a person, reaches voicemail, or ends a call unresolved. Callbacks are prioritized and worked from the queue.
- Requested appointment
- A booking the receptionist took that still needs a staff member or your schedule to finalize. It shows as Needs confirmation. In staff confirm every booking is requested by design; with direct booking it is the safety net when a schedule is briefly out of reach.
- Launch gates
- The checks every business passes before taking a single live call: a signed agreement, a signed BAA, a passing test call, a passing test booking, working staff alerts, and a checked dashboard. Nothing goes live until every gate has passed; see Getting started.
- Callback first (older name)
- An older name for staff confirm.
- Write mode (older name)
- An older name for direct booking.
- Mirror Mode (older name)
- An older name for a staff confirm launch with no vendor names on your screens. These docs now use those plainer words.
Plans and billing
- Included minutes
- The monthly pool of AI voice minutes built into your base plan. Your order form states how many. See Plans & billing.
- Usage meter
- The view in your dashboard of how many included minutes you have used this cycle and how many remain, so the end of the month holds no surprises.
- Overage
- The flat rate per minute charged only if a busy month takes you past your included minutes. It is agreed in your order form before you sign, never a surprise tier.
Trust and compliance
- PHI (protected health information)
- Health information tied to a person who can be identified: the sensitive data a healthcare front desk handles. SpiderLabs keeps it to the minimum needed and handles it under a signed BAA.
- BAA (business associate agreement)
- The HIPAA contract that governs how SpiderLabs handles patient data for you. A signed BAA is required before a practice goes live; see Security & compliance and HIPAA & BAA.
- Audited access
- Reading a transcript or playing a recording is a logged event, recorded with who viewed it and when, so there is an accountable trail over patient content.
- Account isolation
- Each business is its own account, and its data is kept apart from every other account by row level security in our database.
- Live patient data gate
- The point at which live patient data is switched on for a new customer: only after the BAA is signed and the compliant data environment is active and verified. Until then a business launches in staff confirm. See Security & compliance.
For dental practices
- Open Dental
- The dental practice management system SpiderLabs works with most deeply. When connected, the receptionist can read your schedule and, after a booking test, book appointments into it. See Connecting Open Dental.
- CustomerKey
- The key for your practice that lets SpiderLabs work with your Open Dental data. We create it; you paste it into the Open Dental API setup and turn it on.
- eConnector
- A small Open Dental service running at your office that carries the connection to your practice. If bookings suddenly stop, check first that it is running and up to date.
Was this page helpful?
Keep exploring
Booking modesStaff confirm, where your team confirms each requested time, or direct booking into your schedule, proven today with Open Dental. Plus what requested means.Security & complianceWhat a compliance reviewer needs: the BAA process, audited access to patient data, how we handle data, and the gate before live patient data flows.Frequently asked questionsAnswers to the questions we hear most from the businesses we serve, from partners, and from compliance reviewers, with links to the details.

