Everything included in a ChairsideWeb site
Ten features, each explained for a group with more than one front desk. Most are on every plan; the two engines sit on the larger ones.
Pages that open instantly
Hand-built static pages served from the edge, 90+ PageSpeed guaranteed on every office page.
Why speed is the first feature for a group site
A group site has more pages than a single practice, and every one of them is a front door for a different office. A slow hub punishes all of them at once. We hand-build every page, ship almost no JavaScript, and serve each one as a static file from Cloudflare's edge, so the downtown location page opens as fast as the home page. Patients searching between appointments on a phone get the office, the hours and the request button before they think about leaving. We guarantee a 90+ PageSpeed score on mobile and desktop, and we fix any page that drops below it because of our work at no charge.
What we leave out on purpose
No page-builder plugins, no third-party sliders, no chat bubbles that load before the content, no tracking scripts you did not ask for. Fonts load with swap, images are sized for the slot they sit in, and the finder is a small vanilla script rather than a framework. The result is a site that stays fast after launch rather than one that passed an audit once and then slowed as widgets piled up. When the AI Engine chat is enabled on a plan, it loads after the page is interactive, so the score holds.
Location pages, hub or standalone
One page per office with its own address, hours, providers, services and schema, on a hub or on its own domain.
One page per office, never one page for all of them
Each office in your group gets its own page: street address, map link, parking and entrance notes, opening hours per day, the providers who work there, the services offered at that office, the insurance plans it accepts and a booking request that goes to that office's front desk. Search engines rank office pages, not a group page with a list of addresses, and patients trust a page that names the clinician they will see. Every location page carries its own Dentist schema so each office can appear on its own in local results.
Hub and spoke, or one site per location
On a hub, location pages live under one domain and one brand, so reviews, articles and authority pool while each office keeps its own page. With one site per location, each office gets its own domain and its own site, which suits groups whose offices trade under different names or may be sold separately. We build both, explain the trade-offs on the demo, and keep the same finder and routing whichever you pick. Groups that later change their mind can move between the two structures with redirects rather than a rebuild.
Kept accurate week by week
Location details are the facts most likely to go stale in a group: a Saturday clinic that stopped, a provider who moved offices, a new suite number after a relocation. Weekly detail updates exist for exactly this. Email the change from any office manager and it is live within the week, without a revision being used and without anyone at your group logging in. Hours on the page, hours in schema and hours in the finder always match, because they come from the same record.
Service and provider pages
A page for every service you offer and every clinician who offers it, linked to the offices where it happens.
Service pages that know which offices offer them
A service page on a group site does two jobs: it explains the service in plain language and it tells the patient where to get it. Each service page lists the offices that offer it and the providers who perform it, and the finder is embedded on the page pre-set to that service. Content is general information written for patients, never a diagnosis or treatment plan, and it is written once at group level with office-specific notes where they differ, so the pages do not compete with each other in search.
Provider pages patients actually read
Patients look up the person before they book the chair. Each provider page carries the clinician's photo, the offices and days they work, the services they offer, a plain-language bio you supply and approve, education and memberships as you state them, and a booking request that goes to the office the patient chooses. Provider pages are linked from every location and service page they belong to, and each carries Person schema tied to the office, so a search for a clinician by name finds the right page.
Location and provider finder
A patient picks a service and a town and gets the nearest office, its providers, its hours and a booking request routed to that front desk.
From a service and a town to the right chair
The finder is the niche tool built into every ChairsideWeb site. A patient chooses what they need, for example clear aligners or a dental implant consultation, types a town or zip, and sees the nearest offices that offer that service, with distance, today's hours, the providers who perform it there and a request button. It lives on the home page, on every service page pre-set to that service, and on the hub's locations page. No app, no account, no map that has to load before anything appears.
Every request goes to the office that will see the patient
When the patient sends a booking request from the finder, it is tagged with the office, the provider if they picked one, and the service, and delivered to that office's front desk system or your group CRM by API, Zapier or Make. Nothing lands in a shared inbox. A confirmation goes to the patient with the office address, and the front desk gets a note with everything they need to call back. If an office changes its CRM, the routing changes for that office only.
Configured per practice type
The finder is set up for the way your specialty is booked. An orthodontic group lists free consultations by office; an oral surgery practice adds a referring-dentist field and asks for the referral slip; a pediatric group asks for the child's age and the parent's preferred contact; an implant center offers consultation and second-opinion requests separately. The practice type pages on this site describe the setup for each, and we adjust it on the onboarding call.
Booking requests into your front desk system
Every form, finder request and call note lands in the right office's CRM or practice system, by API, Zapier or Make.
Routing by office, not by group
A group site generates requests for many front desks, so the first rule is that each request reaches the office it belongs to. Forms on location pages, requests from the finder and, on plans with the AI Engine, bookings taken by phone or chat all carry the office, the service and the provider. We connect each office to its own destination, whether that is the practice management system's web form, a group CRM with an office field, or a shared system with per-office pipelines. If two offices share a desk, they share a destination.
Short forms that ask only what the desk needs
Forms ask for a name, a phone number, the preferred office, the service and a preferred time. Insurance details, medical history and anything clinical are left for the front desk to collect on the call or through your own patient intake, so patients finish the form and you stay clear of collecting health information on a marketing site. Every submission gets a confirmation to the patient, a notification to the office, and a copy in the CRM with the page it came from, so you can see which office pages and articles produce requests.
Weekly detail updates
Hours, providers, insurance plans, closures and office notes applied every week across all offices, without using revisions.
The small facts that go wrong across many offices
The most common complaint about a group site is not the design, it is that one office's Thursday hours are wrong and a patient turned up to a locked door. Weekly detail updates are our answer. Every week we apply the changes your offices send: opening hours, holiday closures, a new hygienist, a provider now at two offices, an insurance plan you stopped accepting, a new suite number. They are applied to the page, the schema and the finder together. They do not count against your revisions.
How offices send them
Any office manager can email a change to us directly, or your operations lead can send one list for the group. We confirm what we applied each week so the group has a record. If you prefer, we run a short monthly call to gather changes from every office at once. There is no portal to learn and nobody at your group logs in to anything. Larger changes, such as a new service page or a redesigned location page, are revisions, and five of those are included every month.
Researched articles for patients
Two researched articles a week on Chairside and Operatory Suite, three a week on Group, each 2,500 to 3,200 words with cited sources.
Articles that answer what patients actually type
Patients search for what a procedure involves, what it costs in general terms, how to prepare, what recovery is like and how to choose a provider. Our editorial team writes long-form, answer-first articles on those questions, each 2,500 to 3,200 words, researched from real sources and citing them on the page. Every article is general information for patients and families, says so, and points readers to your providers for anything about their own care. It never gives dental or medical advice and never makes a clinical claim on your behalf.
Scoped to an office or a specialty
An article can be about a specialty across the group, such as a guide to dental implants for people with missing molars, or about one office, such as what to expect at your pediatric location's first visit. Each article links to the relevant service page, the providers who offer it and the finder pre-set to that service, so the article sends the reader somewhere useful. Two articles a week on Chairside and Operatory Suite, three a week on Group, and you can review any article before or after it goes live.
Managed hosting and domain
Cloudflare hosting, SSL, backups, monitoring and a domain in your name, all inside the monthly fee with nothing itemized.
Nothing for your group to maintain
Hosting is on Cloudflare as static pages served from the edge. SSL, backups, monitoring and the caching that keeps every office page fast are included and never appear as a separate line. There is no server to patch, no plugin to update and no login for anyone at your group. If a page ever falls below the guaranteed PageSpeed score because of our work, we fix it at no charge. Fully managed means we run the site; you run the practices.
Domains stay yours
We register a domain in your group's name at no extra charge, or point the one you already own. Existing office domains can redirect to their location page on the hub, or stay as standalone sites if you choose one site per location. On cancellation the domain is transferred to you on request and you receive an export of your content and articles within 14 days, so nothing you paid to have written is lost.
AI Engine
An AI receptionist, site chat, SMS, Messenger and Instagram replies, per-office booking and a call-analysis PDF, with A2P 10DLC filed for you.
Every front desk answered, even the one that is busy
On Operatory Suite and Group, the AI Engine answers calls a front desk cannot get to, answers chat on the site, and replies over SMS, Messenger and Instagram. It knows each office's hours, providers, services and accepted insurance, takes booking requests and sends each to the office the patient chose. It is configured per office, so a flagship can keep its own desk answering first while a satellite routes everything after hours. It never gives dental advice and hands anything clinical to a person.
What you see and what is filed for you
A call-analysis PDF shows what patients asked, which office they wanted and where calls were missed, so you can staff around the pattern. Text messaging to patients requires carrier registration, known as A2P 10DLC; we file it for you and pass carrier fees through at cost. AI usage, meaning the minutes and messages your offices actually consume, is billed monthly in arrears at cost, with no minimum and no bundle to guess at. You review every script before it goes live.
Content Engine
Three articles a week, three social image posts a week, two reels a week and your Google Business Profiles managed, per office.
A content stream that runs office by office
Group adds the Content Engine: three researched articles a week instead of two, three social image posts a week, two short reels a week and managed Google Business Profiles for every office. Posts and reels are built from your approved photos and the articles we already write, so they say the same thing the site says, and each is tagged to the office it is about. Nothing clinical, nothing that promises an outcome, nothing you have not approved the style of on the onboarding call.
Google Business Profiles that match the site
Each office's Google Business Profile is kept in step with its location page: hours, services, providers, photos and posts, so a patient who finds the office on a map sees the same facts as the one who finds it on the site. Weekly detail updates feed both. Reviews are monitored and you are told when one needs a reply from the office; we draft replies for you to approve but we never post on a clinical matter without you.
See the features on your own offices.
A demo walks through a site built for your kind of group. Plans from $137 a month; the build fee is invoiced after launch.