Book a demoBook

    Popular searches

    Go to

    PricingFrom $137 a monthTemplatesThe designs we build onServicesWhat we are asked for most

    Case study 20 · Approvals and handover

    New patient appointments documentation the team can actually use

    When it comes to new patient appointments, the team holds a usable operating reference from day one after launch. A colleague covering an absence can find the right person and follow documented steps without reconstructing the project's history.

    Book a demoAll case studies

    The story

    Whereitstarted,andwhat we changed

    Three stations, in the order the practice lived them. The first two are the practice's description of the old way; the third is the build.

    1. Station 01

      Starting point

      The previous site's knowledge left with its designer. Updating new patient appointments information meant guessing or waiting.

    2. Station 02

      The problem

      With new patient appointments, nobody internally knew the procedures: who approves, how to request, what to check. Ordinary maintenance waited on one person's diary.

    3. Station 03

      What we built

      The handover packages a page inventory, update instructions and a contact list, plus a short guided check of the route to an appointment callback from the reception team. Ownership of new patient information and reception hours sits with a named person and a named backup.

    Features used

    5partsofthepackage,put to work

    Each one links to the page that explains how it works on every site we build.

    Timeline

    25 working days, counted from content approval

    25 working days after content approval, including staff review and handover.

    Across all 20 case studies, builds ran from 10 to 25 working days after approval. The bar is drawn to that scale.

    Live demo

    Want this fixed on your own site?

    A 30-minute walk-through of the site you would get, with the approvals and handover set up the way your front desk works.

    Book a demo

    What changed

    When it comes to new patient appointments, the team holds a usable operating reference from day one after launch. A colleague covering an absence can find the right person and follow documented steps without reconstructing the project's history.

    I judge a project by what happens after launch. The new patient appointments documentation means the site survives my vacation.
    Nisha DeshpandeTreatment coordinatorPrivate dental practice, Stamford, Connecticut

    Answers

    Questionsaboutthis case study

    How long did this project take for the private dental practice?

    25 working days after content approval, including staff review and handover. The clock starts when the practice approves the content, so the build never waits on a draft nobody has signed off.

    Which parts of the build did this case use?

    Page inventory, Maintenance notes, Backup reviewer, Form check instructions, Support contacts. Each one is listed above with a link to the part of the package that carries it.

    Why is the practice not named?

    The practice agreed to share the work and their words on the condition that the business stays anonymous. You see the practice type, the region and the team size, and the quote is attributed to Nisha Deshpande, treatment coordinator, by name and role.

    Could our practice get the same thing?

    Very likely, because this is the kind of work every plan is built around. Plans start at $137 a month with the $797 build fee invoiced only after launch. Book a demo and we show you how it would look and route on your own site before you commit to anything.

    More answers on the full FAQ page, or email us and a person replies within one working day.

    Next step

    Seewhatyour first messagecouldlooklike.

    From $137 a month, live in 7 days, and nobody at the practice ever logs into anything.

    Book a demohello@getdentalwebsite.com