Skip to main content
All CollectionsLocalMed Online Scheduling
LocalMed: Fix Pending Appointments when LocalMed is Out-of-Sync
LocalMed: Fix Pending Appointments when LocalMed is Out-of-Sync

Learn how to update pending appointments in LocalMed

Grace Richards avatar
Written by Grace Richards
Updated over a week ago

Got an email saying you have pending appointments? No problem! Pending appointments are appointments that have been booked but have not yet been entered into your practice management software (ie, Dentrix, Open Dental, Eaglesoft).

In order to get these appointments added to your practice management software, you just need to restart LocalMed on the computer that LocalMed is installed on. This computer will have a red cross icon on the desktop that reads "LocalMed Connect."

Helpful tip: If you are receiving LocalMed email notifications but they are being filtered to your spam inbox by your email provider, please reach out to your office's IT to adjust your email settings or reach out to your email provider's support team.


Before you begin the procedure to re-sync to LocalMed, please check to ensure that you have set up the following in the LocalMed portal:

  1. Providers, IDs, and operatories have been added to LocalMed

  2. Provider availability and schedule is current in LocalMed

  3. Appointment types are available in LocalMed

Check out our Getting Setup collection for guides on best practices and step-by-step instructions so that you can make sure your LocalMed account is fully set up.

Method 1: Restart LocalMed from the Services Panel

Once you've checked your LocalMed portal and have confirmed that providers, schedules, and appointment types are active and correct, please follow the steps below to restart LocalMed from your server computer.

Important note: LocalMed may be installed on your server computer. This is most likely a computer found in a back room in your office that is not used every day. If you have an IT Group that maintains your server computer, please share this article with them.

  1. Click Start (the windows icon in the bottom left hand corner) on your desktop

  2. Type Services, this will pop up with a search section

  3. Click on the Services App (gear icon)

  4. Find and right-click LocalMed Connect

  5. Click Restart

Method 2: Restart LocalMed from the Admin Console

If the first method doesn't successfully resolve pending LocalMed appointments, please follow the steps below to restart LocalMed from your server computer.

  1. Find the LocalMed icon in the tray. The tray is found in the bottom right of your desktop

  2. Right-click on the LocalMed icon

  3. Click Admin Client

  4. Select the Services tab (if this tab does not appear right away, click anywhere in the Admin Console window)

  5. Right-click on LocalMed Connect Service

  6. Click Restart Service

  7. After clicking to restart, click on the Status tab and check to ensure that the sync is in progress

  8. If you do not see a sync progress bar, please click on the refresh icon to begin the sync

Resolved: Updated Appointment Status

After the LocalMed restart is completed, the previously pending appointment status(es) will be updated to show as either Scheduled, Rejected, or Conflicted.


Scheduled means the appointment has been inserted into the Practice Management Software calendar. No action is required if it updates to this status. A confirmation email will be sent to the patient:


If a patient who is Black-Listed attempts to schedule an appointment it will be
marked as Rejected. If the status reflects this, we will send an email to the patient
with the following notice:


Conflicted means the appointment could not be scheduling due to a conflict in the Practice Management Software's calendar. If the status reflects this, we will send an email notification to the patient with the following notice:

If after troubleshooting and/or trying to re-sync you are still unable to resolve the pending appointments, please contact our support team by signing in here and contacting us via chat. They’d be happy to troubleshoot the issue for you!

Did this answer your question?