PMS integrations
Connect a practice management system, map its sites, review patient matches and bookings needing attention, and monitor automatic polling.
Use Settings → Integrations to connect a practice management system (PMS), request a planned integration, and monitor sync health. Dentally, CareStack and Open Dental support live data connections; every other listed PMS is request-only until its adapter and provider partnership are available.
The page has four tabs:
- Practice system — your PMS connection, the systems that sync today under Two-way sync, and the rest of the catalogue under Coming soon.
- Connected apps — Zapier, plus every app your practice authorised over OAuth.
- Inbound webhooks — the endpoints your own forms and systems post leads to (owners and managers only).
- Outbound webhooks — the endpoints Smileline delivers events to (owners and managers only).
A practice can run one active PMS connection at a time. If you are moving between systems, disconnect the old one before connecting the new one. While the old connection still holds money Smileline copied from it, Smileline refuses a connection to another account or another practice system until you contact Smileline — see Sync now, pause or disconnect.
For a single view of every external account Smileline is signed in to — ad platforms, Google, your inbox channels, your phone provider and this PMS connection — with the health of each, see Connections.
Owners and managers can create, pause, resume, map, and disconnect PMS connections. The front desk sees connection details read-only and can review suggested patient matches. Telesales see the same read-only connection details. Analysts do not have access to PMS connections.
Connect Dentally
Dentally is a UK practice management system. Go to Settings → Integrations, find Dentally under Two-way sync, and click Connect. Smileline asks how to connect, because Dentally offers three routes and each one syncs a different amount:
| Personal token | NexGen API (preview) | Partner app | |
|---|---|---|---|
| Patients and appointments | Imported; bookings, confirmations, cancellations and moves made in Smileline are written back, and a new patient's chart is created with their first booking | Imported hourly; Smileline's bookings sent to Dentally | As the personal token |
| Live updates | Yes | No — hourly sync | Yes |
| Book, move and cancel in the Dentally diary | Yes | Yes | Yes |
| Confirm appointments from Smileline | Yes | No — confirm in Dentally | Yes |
| Appointments move journey stages | Yes | Yes | Yes |
| Invoices on the lead | Yes | Yes | Yes |
| Payments and treatment plans | Yes | No | Yes |
| Available | Now — recommended | Now | Coming soon |
A personal access token connects Smileline to the same Dentally API the partner app will use, with every feature on. The token acts as the Dentally user who creates it, so create it from an account that stays with the practice.
In Smileline, choose Personal token and continue. The connection shows Awaiting credentials and the credentials form opens. Enter credentials on the card reopens it later.
In Dentally, open Settings → Developer → Personal Tokens and click Generate new token.

Describe what the token is for — for example, "Smileline syncs patients, appointments and invoices with Dentally for our practice" — enter Smileline as who will use it, and click Continue.

Tick these permissions, then click Save:
- user:read
- appointment:read, appointment:create and appointment:update
- financials:read and financials:create (or financials (all)) — Smileline adds a paid booking deposit to the patient's account, and its refund if the deposit is refunded, and writes the allocations you make of Dentally payments as payment explanations
- patient:read, patient:create and patient:update (or patient (all))
- practice (all) — Smileline registers its live-update webhook with this
- treatments

Copy the token Dentally shows — it is shown only once — paste it into Personal access token in Smileline and save. Smileline reads the token's permissions before storing it and names any that are missing. It then starts the import and turns on live updates.
Map the Dentally site to a Smileline location on the connection card. Appointments for an unmapped site wait until you map it.
While the first import runs, the connection card says First import from Dentally and the connection shows as connecting. It brings in practitioners, surgeries and appointment types first, then patients, then the diary and the rest of the history. Until it finishes, Leads asks for the date and time you booked in Dentally instead of booking there for you; once it finishes, bookings go to Dentally from Smileline. A large practice's first import can take more than a week; it carries on for as long as it keeps bringing records in, for up to three months. An import still not done by then stops, and the card offers Replace token: replacing it carries the import on from where it stopped.
Smileline brings in the whole of your Dentally history, not just recent months: patients, appointments, treatment plans, invoices and every payment back to your first day in Dentally. On a practice connected before payments came in this way, the older payments arrive by themselves in the background after the next hourly sync. They don't send anything to anyone.
For reports that match Dentally's, Smileline also reads each invoice's lines, each treatment plan item and your recalls. On a practice connected before reports read these, Smileline reads your patients, invoices and payments once more in the background after its older payments are in, then those lines, items and recalls back to your first day in Dentally. Nothing is sent to anyone, and nothing changes in Dentally. Until it finishes, reports that need them can show older months short.
Payments taken, changed or deleted in Dentally reach Smileline straight away with live updates; a payment deleted there is removed here too. Dentally sends no live updates for invoices, so after that background read Smileline asks Dentally about each invoice it no longer lists: one Dentally deleted is removed here too, with its charges, and one it still has is kept.
The card warns if that can't finish:
- Smileline stopped bringing in your older Dentally payments — it carries on by itself within a week, or straight away when you replace the token.
- Dentally wouldn't list every payment taken on… — Dentally lists at most 9,900 payments for one request, and those days, or a day beside them, had more. Their payments come in with Dentally's full export when you switch from Dentally.
- Treatment history import stopped — Smileline reads your older treatment items one patient at a time, including items that aren't on a treatment plan, and stops on a patient when Dentally won't list every item they have after three tries, or when the import fails. Until it carries on, treatment reports can show older months short. Click Retry to carry on from that patient; otherwise it tries again by itself within a week, for up to three months after it began.
Replace the token before it expires
Dentally personal tokens stop working 90 days after you create them, or after 14 days without use. Smileline uses the token every hour, so the 90 days is the one to watch.
From 14 days before the token expires, the Dentally card shows when it expires and a Replace token button, and the practice gets one notification. Create a new token in Dentally with the same permissions, click Replace token and paste it. Smileline swaps the token without restarting anything: the import, the hourly sync and any bookings on their way to Dentally carry on. Then delete the old token in Dentally.
If a token has already expired, the card says the token expired or was revoked. Replace token fixes it the same way — an import that stopped because of the token carries on from where it stopped.
Deposits and notes in Dentally
With a personal token, Smileline also writes to the patient's Dentally record:
- Paid deposits. A booking deposit paid through Smileline is added to the patient's account as a card payment. If the deposit is refunded in full, Smileline adds the refund beside it as a payment of minus the deposit; the deposit's payment stays. A partial refund is left for you to adjust in Dentally. See The deposit in Dentally.
- Allocations. Allocating a payment that came from Dentally to one of its invoices, from the patient's Account tab, adds a payment explanation to that payment for that invoice — Dentally's own Allocate to invoice — with your note and a smileline-alloc: marker in its comments, so Smileline can find it again. Smileline never deletes an explanation: unallocate it in Dentally. See Money from your practice system.
- Notes. Two kinds go on the patient's Notes in Dentally, each titled Smileline · … so Smileline can find it again: the deposit — its amount, the proof link and the staff refund link — once its payment is added; and, for a consultation booked from Leads on a call with Call AI, the call's transcript up to the moment you booked, once Dentally confirms the booking. Smileline never edits or deletes these notes. A transcript too long for Dentally stays in Smileline, and one that expired before the booking was confirmed isn't written.
Nothing is ever written twice: if Dentally's answer is lost, Smileline looks for the payment, explanation or note before doing anything else. These writes count towards the hourly request limit like the sync does, so on a busy hour they wait for the next one. A deposit that needs a person shows on its deposit card; an allocation on its payment's row on the Account tab; a transcript note under Bookings needing attention.
If you disconnect, nothing is moved to another connection: a deposit not yet added reads Not added to your practice system, saying the connection was removed, and one that was added and is refunded later reads Adjust in your practice system, until someone dismisses it. An allocation not sent yet is dropped; one already sent reads Needs a look in your practice system until someone checks it in Dentally and marks it resolved, and the practice can't move to another practice system until then.
A deposit that never got into Dentally before you connected again stays Not added to your practice system: Smileline doesn't send it again. If someone types it into Dentally by hand, Smileline holds that payment instead of counting it, and asks Is this the Smileline deposit? in the review queue — see Is this the Smileline deposit?.
A token or NexGen access belongs to one Dentally practice. Replacing it with credentials from a different practice is refused — disconnect first. After you disconnect, delete the personal token or the NexGen access in Dentally; Smileline removes its own webhook but cannot revoke credentials Dentally issued.
Dentally's rota and blocked time in your diary
On a personal-token connection, Smileline keeps a read-only copy of Dentally's rota for each mapped site: when each dentist works, with their breaks taken out, for the next 26 weeks. The coming week is read again every hour, and the weeks after it over the next day or two. On a day the copy covers, the diary and the free slots on Leads use Dentally's hours for that dentist instead of Smileline's — even outside the site's opening hours — and a day Dentally has them off is grey. Closures you set in Smileline still close the day. A dentist Dentally's rota never lists, and days more than 26 weeks ahead, keep Smileline's own hours. Nothing is written back: change a rota in Dentally. If you map a Dentally site to another location, Smileline reads its rota again there and its blocked time moves with it. A site you switch off shows no rota or blocked time until you switch it back on.
Blocked time in Dentally — an appointment with no patient, such as Other — Not working or annual leave — shows on the dentist's column as a hatched band with its label, and that time is never offered as free. It follows Dentally: moved, cancelled or deleted there, it moves or goes here. Blocked time or a visit with no length in Dentally (it ends when it starts, or before) has nothing to show, so it comes off the diary, like an appointment taken off Dentally's diary, instead of going to the review queue.
The card warns when the copy can't be kept up to date:
- Dentally doesn't share its rota with Smileline — the token or the practice gives Smileline no access to the rota, so the diary uses Smileline's hours. Smileline asks again every day.
- Smileline couldn't read Dentally's rota just now — the diary keeps the last copy and may be out of date. Smileline tries again within the hour, and the warning stays until the days it couldn't read have been read again.
Reading the rota counts towards the hourly request limit: about three requests an hour for a site with 20 dentists.
NexGen booking reasons
Dentally needs a reason on every appointment it books and every one it cancels, chosen from the practice's own reasons. A NexGen connection card has a Booking reasons section with two choices:
- Book Smileline appointments as — one of your active appointment reasons in Dentally.
- Cancel Smileline appointments as — one of your active cancellation reasons. Only reasons that record a cancellation are listed; a did-not-attend reason records a no-show instead.
The lists are read from Dentally when you open the section, so a reason you add in Dentally appears the next time you open it. Owners and managers choose them; other roles see the section read-only.
Until both are chosen, the card warns Choose how Smileline books and cancels in Dentally, with Choose reasons to open the section. Meanwhile new bookings wait under Bookings needing attention and send by themselves once you choose a booking reason, and a cancellation is refused with that reason. If a reason was switched off in Dentally while you were choosing, Smileline says so and refreshes the list.
Bookings sent to Dentally
The card of every system Smileline books into has a Bookings sent to Dentally section (named after the system). It holds the layout of the booking note: the note every appointment Smileline books there carries, whoever booked it — the booked step on Leads and on the patient record, the calendar's booking card, online booking, the AI receptionist, AI replies booking in a chat, and Book appointment in Dentally… on the patient record. You don't need Smileline Voice for it.
Write one line per item. A line with a tag is filled by Smileline:
{{lead.source}}— where the lead came from, such as Facebook.{{user.name}}— who booked: the teammate, or Online booking, AI receptionist or AI replies.{{booking.consultation}}— the consultation's day, time and dentist, such as Mon 4 Jan, 09:00 with Yasser El Ali, in the site's time zone.{{call.transcriptLink}}— a link to the call's transcript in Smileline.
A line that ends after its label — Problem: — is for your team to fill when they book. On a call with Call AI, Call AI fills it when it heard the answer, and leaves it empty when it didn't. A booking nobody writes a note for — online, the AI receptionist, AI replies, Book appointment in Dentally… — gets Smileline's lines and leaves the others empty.
When the lead has a booking deposit, its amount, proof-of-payment link and the link staff use to refund it always come first, so the template doesn't need a line for them.
The default layout is Problem, Treatment, Job, Finance, Source, Time frame, Booked by, Consultation and Call transcript. Click Save after a change, or Reset to go back to the default. The template can be about 1,000 characters long. Anyone who can change the practice's settings edits it; everyone else sees it read-only.
Medical history forms for Dentally visits
Dentally's one-tap medical history links ([patient_medical_link] in Dentally's own templates) can only be created inside Dentally: its API can't make or read them. To ask Dentally patients for their medical history from Smileline's booking messages, enter your Dentally Portal page as each site's Medical history form address under Settings → Locations. Patients sign in to the Portal there, and the medical history they fill in goes straight into Dentally.
Connect CareStack
CareStack needs credentials from your practice, so the connection has one extra step. Smileline connects to CareStack accounts in the US (yourpractice.carestack.com) and the UK (yourpractice.carestack.uk). Ask CareStack support for your API details before you start:
- your CareStack address — the one your practice signs in at
- an Account Key
- an Account ID, or, if CareStack registered your practice for API access itself, your practice's own vendor key, client ID and client secret
Go to Settings → Integrations, find CareStack under Two-way sync, and click Connect.
Enter your CareStack address and Account Key, plus either the Account ID or your practice's own developer keys under Your practice's own CareStack developer keys, then click Save credentials. Smileline checks the credentials against CareStack before saving them.
Map each CareStack location to a Smileline location. Appointments for an unmapped location wait until you map it.
Open Sync detail on the connection and check Clinicians. CareStack has no directory of its providers, so Smileline learns them from the appointments it imports and adds each one as an inactive practitioner named after its CareStack id.
Go to Settings → Practitioners, give each of those a real name, and make them active.
An unnamed clinician is not bookable. Their CareStack appointments still import and still block that column of the diary, so you cannot double-book them — but they will not be offered for new bookings until you name and activate them.
A client ID and client secret work only with a UK (.carestack.uk) address. To move the connection to a different CareStack address, disconnect it first: records already synced belong to the old account.
You can replace expired keys for the same CareStack address while keeping your imported records linked, including a connection originally set up with a US practice subdomain.
What CareStack syncs
The connection imports patients, appointments, surgeries, and appointment types, and it writes new bookings, cancellations, and confirmations back to CareStack.
It does not import treatment plans, invoices, or payments, and CareStack does not send Smileline live updates — changes arrive on an hourly poll rather than instantly. Availability always comes from your Smileline rota, not from the CareStack diary, so keep your practitioner rotas accurate.
Bookings Smileline sends to CareStack carry a short reference tag in the appointment notes. It is how Smileline recognises its own bookings if a request is interrupted. Leave it in place; removing it means a booking may need manual review.
Connect Open Dental
Open Dental needs one credential from your practice: the customer API key Smileline issues for it. Set up Open Dental first, with the key Smileline gave you:
On the practice's server — the computer that is always on — open eServices → eConnector Service in Open Dental. If the eConnector isn't installed, click Install and allow the changes when Windows asks. Current eConnector Service Status should read Working. A practice that already uses another Open Dental eService has the eConnector installed.

Once the eConnector has started, allow a few minutes before Smileline can reach Open Dental.
Open Setup → Advanced Setup → API. In the API Setup window, click Add Key, paste the customer API key Smileline gave you, and tick Enabled.
In the same window, set Process subscription interval in minutes to 1. Left blank, it switches live updates off, and changes in Open Dental reach Smileline only with the hourly sync.
Set Default payment type for created payments to your practice's card payment type, such as Credit Card. Smileline adds paid booking deposits to the patient's account as card payments — see Deposits and notes in Open Dental.
Click Save.

Then connect in Smileline:
Go to Settings → Integrations, find Open Dental under Two-way sync, click Connect, then Continue. Smileline creates the connection, shows Awaiting credentials, and opens the credentials form. If you do not have your customer API key yet, close the form — Smileline issues the key for your practice and passes it to you, and Enter credentials on the card reopens the form later.
Paste the Customer API key and, if you want live updates sent from one machine only, the Open Dental workstation name (the Windows computer name of the machine running OpenDental.exe or OpenDentalAPIService.exe). Click Save credentials. Smileline checks the key with Open Dental before saving it. If it says Open Dental could not be reached, the eConnector may still be starting: wait a few minutes and save again.
If your practice uses Open Dental's Clinics feature, map each clinic to a Smileline location. A practice without clinics gets one site called Practice; map it to your location. Appointments for an unmapped site wait until you map it.
Open Dental sends live updates from the workstation you name, so that machine must be running Open Dental (or the Open Dental API service) for changes to arrive between polls — a workstation that is switched off sends nothing, and Smileline cannot tell that apart from "no changes". Leave the name blank if you are unsure: every workstation then sends updates, and the connection works either way because changes also arrive on the hourly poll. If live updates could not be switched on, the card warns Live updates are off: changes in Open Dental then reach Smileline every hour instead. Smileline checks them at each hourly sync and tries again until they are on.
What Open Dental syncs
The connection imports patients, appointments, providers, operatories and appointment types, and copies the money on each patient's account (see Open Dental's money in Smileline). Both the dentist and the hygienist on an appointment are carried across, so each one's column is blocked in the Smileline diary. It writes new bookings, confirmations and cancellations back to Open Dental, and when your team moves a booking in Smileline the new time is written to Open Dental too. A cancellation sends the appointment to Open Dental's unscheduled list, and Smileline never adds a missed- or cancelled-appointment fee procedure to the patient's account.
Availability comes from Open Dental's own diary: Smileline asks Open Dental for free slots, so keep your provider schedules in Open Dental accurate. Live updates are delivered by Open Dental as changes happen; a full poll runs every hour as well.
- Bookings sent to Open Dental carry your own Open Dental appointment type when the visit's appointment type came from Open Dental, or its treatment's appointment type did. A first visit is marked as a new patient's when Smileline opened the chart, and a new chart is filed at the clinic of the location booked.
- Free times online at a location are only in that location's own operatories. A location with no active operatory from Open Dental offers no times. A time Smileline already holds for the provider is not offered either: a booking made a moment ago, or one still waiting for your team.
- Changes your front desk made first. Before Smileline confirms, cancels or moves a visit, it reads that visit in Open Dental. If that read shows the front desk has moved it, checked the patient in or completed it since Smileline last read it, nothing is sent: the change waits under Bookings needing attention with the reason. A visit already cancelled in Open Dental needs nothing sent, and Smileline's cancellation is done.
- Confirmed is the status your practice chose in Open Dental for an accepted eConfirmation. Smileline reads that choice again every hour.
- Appointment types take their length from Open Dental when they are first imported. They start not bookable online: switch them on under Choose what's bookable.
- Provider schedules show in the diary, and place each provider at their locations — see Open Dental's schedules in your diary.
- Recalls and the ASAP list feed the Recalls, Recall effectiveness and Waiting lists reports. Recalls are read once a day, the ASAP list every hour. Each patient's dentist and the day their chart was created feed the patient reports.
It does not import treatment plans or clinical records, and it does not update patient details in Open Dental. Smileline opens a chart there only when a booking is for someone who has no chart yet, after checking by email and phone that they do not already have one, or when your team creates one from the patient record.
Open Dental records a missed appointment and a cancelled one the same way from Smileline's point of view, so both appear as Cancelled here. Record no-shows in Open Dental itself. Times are read in the Practice timezone set under Settings → Practice details; check it is right before connecting.
The customer API key belongs to one Open Dental database. To connect a different practice, disconnect first — reusing the connection with another practice's key would attach its records to the wrong charts. If a connection has stopped with an error and you enter a different key from the one it was using, nothing connects until Smileline has confirmed the new key opens the same database: the card shows Waiting for Smileline, as it does when you connect the same database again. Bookings Smileline sends carry the same short reference tag in the appointment note as CareStack bookings do; leave it in place.
Open Dental's schedules in your diary
Smileline keeps a read-only copy of Open Dental's provider schedules for each mapped location, for the next 26 weeks. The coming week is read again every hour, and the weeks after it in turn. On a day the copy covers, the diary shades that provider's column by their Open Dental hours instead of Smileline's, as it does with Dentally's rota. Nothing is written back: change a schedule in Open Dental.
- Blockouts are taken out of the provider's working time in the operatories they cover, whatever their type. That time shows as not worked, with no label.
- Practice holidays are not read: Open Dental's API doesn't say which days are holidays.
- Locations. A provider Open Dental schedules at a location is assigned to that location in Smileline automatically, so you don't assign each dentist by hand before they can be booked online. An assignment your team ended is never brought back.
- Online times still come from Open Dental's own free-slot search, not from this copy.
If the schedules can't be read, the card says Smileline couldn't read Open Dental's schedules just now. The diary may be out of date until Smileline reads them again, which it tries within the hour.
Open Dental's money in Smileline
Smileline copies each patient's account from Open Dental into their ledger, one patient at a time. The copy writes nothing to Open Dental: the only money Smileline writes there is a paid booking deposit and its refund (see Deposits and notes in Open Dental).
- Charges — each completed procedure is a charge on the patient's account. A procedure deleted in Open Dental, or no longer completed, has its charge taken off again.
- Payments, refunds and adjustments — each one lands on the patient it belongs to in Open Dental, attached to the procedure Open Dental attaches it to. Insurance payments and write-offs arrive the same way.
- Waiting for insurance — Open Dental's own estimate for claims sent and not yet paid; see Waiting for insurance.
Each patient shows their own money. Where Open Dental bills a family through a guarantor, every member still has their own account here, and the Patient accounts report names the guarantor under Billed to.
The first copy takes a while. The diary and bookings work as soon as the first import finishes; the money follows in the background, patient by patient, and takes longer the more patients you have. Until that first copy has ended, the money reports that read it say Smileline is still bringing in payments and balances from your practice system, so these figures aren't complete yet. The dashboard and the Revenue summary keep showing your leads' values as revenue until then, and the money taken from then on.
How fresh the figures are. A procedure, a payment or an insurance claim added or changed in Open Dental usually reaches Smileline within about an hour. A change Open Dental doesn't announce, such as an adjustment or a payment moved to another procedure, shows when Smileline next reads the whole account, which it does for every patient at least once a week. The Patient accounts report says when each account was last read, under Figures as of.
When an account doesn't match. After reading an account, Smileline adds up what it copied and compares it with the balance Open Dental gives for that patient. If the two differ, the patient's Account tab says so with Open Dental's figure (see When the figures don't match your practice system), and the Open Dental card counts them: 3 patient accounts don't match Open Dental's balance. Smileline reads each of those accounts again within a week. There is no review item for each patient.
When an account couldn't be read. If reading a patient's account fails three times in a row — Open Dental didn't answer, say — Smileline stops asking for it for a week, and the Open Dental card counts it: 2 patient accounts couldn't be read from Open Dental. The account keeps the figures from its last good read meanwhile.
Archived patients. Open Dental doesn't give out the payments of a patient whose chart is archived. Smileline leaves that patient's account as it was last read and goes on with everyone else's. An archived account isn't counted as one that couldn't be read. If its last read didn't match Open Dental's balance, it still counts as not matching, and Retry still has it read again. Smileline asks again a week later, or sooner when a procedure, payment or claim of theirs changes, so once you take the chart out of the archive the account is read again.
Retry. Both rows have Retry for owners and managers. It has every account the card counts read again: those that couldn't be read get their three tries back. The rows then say Queued to be read again until the page next refreshes. Smileline doesn't read them at that moment: if it is already reading accounts, it takes them next; if not, it starts at the connection's next hourly sync, or straight away when you choose Sync now from the card's menu. An account that still doesn't match after it has been read again stays counted: check it in Open Dental.
What isn't copied:
- Payment plans. A payment plan's schedule in Open Dental is not copied, so an account on a plan shows its full balance here.
- Allocations made in Smileline. Smileline shows a payment against the procedure Open Dental attaches it to, and sends no allocation back. Attach payments in Open Dental.
Deposits and notes in Open Dental
Smileline also writes to the patient's Open Dental chart:
- Paid deposits. A booking deposit paid through Smileline is added to the patient's account as a prepayment, for the front desk to attach to a treatment. Its note starts with a smileline-deposit: marker, so Smileline can find it again. If the deposit is refunded in full, Smileline adds the refund beside it as a payment of minus the deposit, its note starting smileline-refund:; the deposit's payment stays. A partial refund is left for you to adjust in Open Dental. Open Dental takes deposits in US dollars only. See The deposit in Open Dental.
- Notes. Two kinds go on the patient's chart as commlogs, each starting Smileline · … so Smileline can find it again: the deposit — its amount, the proof link and the staff refund link — once its payment is added; and, for a consultation booked from Leads on a call with Call AI, the call's transcript up to the moment you booked, once Open Dental confirms the booking. Smileline never edits or deletes these notes. A transcript too long to write stays in Smileline, and one that expired before the booking was confirmed isn't written.
Leave the marker at the start of a deposit's payment note as it is: text you add around it changes nothing, but Smileline knows its payment by it.
Nothing is ever written twice: if Open Dental's answer is lost, Smileline looks through the patient's recent payments, or commlogs, before doing anything else. When that look can't settle it — one names the deposit or note without being it, two could be it, or the patient has 100 or more of them, more than Open Dental shows in one answer — a person decides: a deposit on its deposit card, a transcript note under Bookings needing attention. If Open Dental answers that Smileline isn't allowed to add payments there yet, the deposit card says so: there's nothing for you to change, so contact Smileline support, then Retry.
When Smileline reads the patient's account (see Open Dental's money in Smileline), it recognises its own deposit coming back, so the money is counted once: the deposit is already on the patient's account in Smileline, and the check against Open Dental's balance counts it once too.
- Attached to a treatment. When the front desk attaches the deposit's payment to a procedure in Open Dental, Smileline attaches the deposit to that procedure's charge the same way, so the treatment shows as paid from the deposit. A refunded deposit is attached to nothing, whatever Open Dental still shows.
- Split across the family. A part the front desk puts on a family member's account is money moved within the family, not new money: a transfer in on their account and a transfer out on the account of the patient who paid the deposit.
- Not sure it's Smileline's. A payment that might be a Smileline deposit's but can't be told for sure waits in the review queue as a Practice-management record instead of being counted as cash: one whose note has Smileline's marker edited, run into other text or there twice, or that names a deposit without being for its amount and patient; a refund made with Open Dental's own refund on a Smileline deposit; and money given back on a family member's account for the same amount as an open deposit, until Smileline next reads the account of the patient who paid that deposit — it is counted then, unless that account shows the payment with a Smileline deposit's note. One that waited only because Open Dental's answer about a deposit was lost settles by itself once Smileline finds that deposit's payment.
If you disconnect, a deposit not yet added reads Not added to your practice system, saying the connection was removed, and one that was added and is refunded later reads Adjust in your practice system, until someone dismisses it.
A deposit that never got into Open Dental before you connected again stays Not added to your practice system: Smileline doesn't send it again. If someone types it into Open Dental by hand, Smileline holds that payment instead of counting it, and asks Is this the Smileline deposit? in the review queue — see Is this the Smileline deposit?.
Recognising a patient without a date of birth
Open Dental opens a chart without a date of birth, so the booking page asks for none at an Open Dental location. A booking that gives a first name, a last name and a mobile number, and no date of birth, uses an existing chart when exactly one active chart in Open Dental has that number and the same first and last name.
- Capitals, accents, spaces, hyphens and apostrophes are ignored, and the chart's preferred name counts as its first name.
- A relative's chart on the same number under another name is left alone.
- If the number is only on charts that aren't plainly this person — a relative's, an inactive or archived chart, another name — or two charts match, the booking waits under Bookings needing attention for your team to pick the chart. The patient sees We've got your request.
- An email address alone never picks a chart: a chart that shares only the email waits for your team too.
- Where the patient's record and the chart both hold a date of birth, the dates and the names must agree, as with every other system. A chart with that number and name but a different date of birth is never used for an online booking, and no second chart is opened beside it: it waits for your team, because the booking itself gave no date of birth.
- A patient who is already linked is checked the same way on each online booking: if a second active chart with their number and name has appeared in Open Dental, the booking waits for your team.
- When two charts match, link the right one from the waiting booking. Choosing the chart the patient is already linked to confirms it as your choice, and Smileline stops asking for that patient.
The patient's Record history shows that the chart was matched by name and mobile number. If it is the wrong chart, ⋯ → Open Dental → Unlink from Open Dental on the patient record removes the link. A visit already sent to Open Dental stays on that chart: move it in Open Dental. Smileline never links an unlinked patient again by itself; link the right chart from the same menu.
Request another PMS
Coming soon lists the most widely used systems for UK and US practices. Use the market filter on the section rule to narrow it, then click Request on your PMS and confirm with Request. Smileline records one request per PMS for the whole practice and marks that tile Requested. Click Cancel if the practice no longer needs it.
Requesting a PMS does not start a data connection or grant Smileline access to the provider. It stays a request until an adapter has passed the same activation, security, and reliability checks as a live integration.
PMS not listed is for any other system, whatever market the filter shows: click Request, type its name under PMS name, and click Request. The tile then shows that name. To correct it, click Cancel and request it again.
While a requested PMS covers the practice — or a connection is still waiting to activate — Leads cannot book into its diary. When a lead books a consultation, the booked step asks for the date and time you booked in your PMS instead; see If they booked.
Leads uses one PMS per site. A live connection comes first; otherwise it is the PMS you requested first. That PMS moves up under Your connection with the line Leads records the date and time you book in name, followed by the sites it applies to when it is only some of them. Other requests stay under Coming soon as Requested. To make Leads use a different requested PMS, click Cancel on the one under Your connection.
A Dentally personal-token connection imports patients, appointments, treatment-plan summaries, invoices, and payments from Dentally; a NexGen connection imports patients, appointments, practitioners and invoices. You can also book against the Dentally diary from a linked patient record, and open a new patient's chart in Dentally from the same link dialog — see practice management system actions.
The initial historical import is silent to outbound webhook endpoints. It builds the Smileline record without sending one integration event for every historical patient, appointment, treatment plan, invoice, or payment. After activation, live provider changes and polling updates can emit the configured events. Exact provider retries are ignored. If only the provider's revision timestamp changes, Smileline advances that marker without rewriting the record or sending another event. A conflicting change at the same revision, or one without a usable revision, is held in the review queue instead of overwriting the existing record. A deletion is the exception: practice software keeps the record's revision when it deletes it, so a deletion at the current revision is applied, and a copy of that revision arriving after it is ignored.
A £0 payment in the practice software moves no money, so Smileline posts nothing for it and it never waits in the review queue. A payment edited to £0 is undone in Smileline, as if it had been deleted.
PMS financial and clinical mirrors remain read-only in Smileline. Two-way patient conflict resolution remains design-only and is not an enabled product mode.
For an appointment the PMS owns, cancelling it in Smileline is sent on to the provider so both diaries agree. Chairside outcomes — arrived, in chair, attended, no-show — are recorded in the PMS instead: Smileline cannot send them, and setting one locally would contradict the provider's own record. If the two views do disagree, the incoming record is held for review rather than overwriting what staff recorded.
A confirmation or cancellation the practice system can't take right now is refused with the reason, and nothing changes in Smileline:
- A Dentally NexGen booking can't be confirmed from Smileline — confirm it in Dentally. Mark confirmed isn't offered for it.
- While the connection isn't active — paused, still connecting, or showing an error — neither can be sent: make the change in the practice system, or try again once the connection is back.
- A booking that hasn't reached the practice system yet can't be confirmed or cancelled until it has. Resolve it under Bookings needing attention if it is waiting there.
Webhook receipts
Every signed webhook the provider delivers is recorded as a receipt, and its
raw body is captured before Smileline reads it — on the successful path as
well as on failures. The API lists a connection's receipts newest first
(GET /settings/pms/connections/{id}/receipts) and can replay a completed
one from its captured body
(POST /settings/pms/connections/{id}/receipts/{receiptId}/replay): the
events are re-parsed and re-staged (rows that still exist are left alone)
and processing runs again. Receipts that were held or refused are replayed
from the review queue instead.
Review appointment corrections
When a provider update would move an appointment backwards or replace a completed, cancelled or no-show fact, the connection card shows a banner naming how many appointment corrections are waiting, with a Review button. Smileline keeps the local appointment unchanged and stops any reminder that reaches its final provider boundary while that correction is pending.
Open the review sheet to compare the current and provider status, time, location, status timestamp and note. The provider side also lists the clinicians it proposes, which may be more than one where the PMS records a combined visit. A team member with appointment-edit permission can then choose:
- Keep Smileline — retain the local fact and resume each interrupted reminder that is still relevant.
- Use PMS correction — apply the reviewed PMS projection, recompute time-anchored reminders and create an urgent follow-up task. The task asks staff to check patient messages, deposits and other external effects that may already have happened. Smileline does not invent a retrospective booking, move, cancellation or no-show message from this decision.
One correction immediately releases at most twenty due reminders. If recompute produces more, the remaining reminders stay durably scheduled for the next bounded reminder sweep instead of blocking the correction decision.
The decision is version-fenced. If the appointment changed after the sheet was opened, reload and compare it again. Repeating the same completed decision is a write-free replay. If a later provider update resolves the contradiction on its own, Smileline supersedes the pending review. A live webhook or poll re-arms each still-relevant interrupted reminder. A historical backfill remains silent: it marks that frozen occurrence as not sent but leaves its ledger eligible for a later live appointment change. While a correction is still pending, a newer provider revision carrying the same material is re-evaluated if the local appointment changes. The stale review is then superseded by one tied to the new appointment version.
Appointments taken off the Dentally diary
Dentally can hold an appointment with no time: one waiting to be booked, or one taken off the diary to be moved. Smileline never treats that as a cancellation. An appointment it has never seen is noted and nothing is added to your calendar until Dentally gives it a time. A visit still to come becomes an appointment correction marked Taken off the Dentally diary: nothing is cancelled and nothing is sent to the patient, and its reminders wait. When Dentally books it again as an ordinary booking, the correction clears by itself and the visit moves to its new time. If it comes back in a way that needs a decision — for example a confirmed visit returning as pending, or one you already cancelled here — a new correction asks for it instead. If it stays off the diary, choose Use PMS correction to cancel it here (still without a message) or Keep Smileline. A visit that already happened, or was already cancelled, stays as it is.
If Dentally sends a visit back with no patient — turned into blocked time — Smileline doesn't turn it into blocked time here either. Unless it is already cancelled, it becomes an appointment correction, whatever happened at the visit: Use PMS correction cancels it here without a message, and Keep Smileline keeps it as it is, attended or missed included.
A patient the PMS marks as declining marketing is opted out in Smileline, and a patient it marks inactive is archived. Neither is reversed by a later provider update: an opt-out or an archive recorded in Smileline is never lifted automatically. Patients who have declined SMS or email in the PMS are not contacted on that channel, including by appointment reminders.
Bookings needing attention
When Smileline can't send something to your practice management system — a new booking, a move, a confirmation or a cancellation — it doesn't drop it or guess. The connection card says how many are waiting, for example 2 bookings need attention — Smileline couldn't send them to Dentally., with a Review button. Anyone who can see appointments can open the list; acting on it needs permission to edit appointments.
Each row shows the patient, the location and the visit's time — for a move, also the time it was asked to move to — and what it is: New booking, Move, Confirmation or Cancellation. The reason is in plain words, for example:
- the location isn't mapped to a practice-system site;
- the practice system needs more details before it can open the patient's chart, with the missing ones named (Missing: Title, Postcode.) — the row shows those fields, filled in from the patient's record, and Save and retry saves them on the patient and sends the booking again (Sent to Dentally again);
- the practice system has a chart that may be this patient, but Smileline can't be sure it is the same person — link the right chart, then retry;
- more than one chart in the practice system matches the patient's email or phone — link the right one, then retry (for Open Dental, see Recognising a patient without a date of birth);
- no "book as" reason is chosen yet (Dentally NexGen — see NexGen booking reasons);
- the practice system refused it, followed by its own words.
When the practice system may already hold the booking, the row says … may already have this booking — check there first.
Only the actions that are safe for that row are offered:
- Retry sends it again, once you've fixed the cause. A booking the practice system may already hold is checked there first, never sent twice.
- Keep in Smileline only (new bookings) keeps the booking in Smileline's diary and never sends it. It is offered only while nothing has reached the practice system.
- Cancel booking (new bookings and moves) cancels the visit. It asks for a second click, Yes, cancel booking. For a move it first asks for the Reason for cancelling, from your cancellation reasons, as cancelling a visit does everywhere else; Keep it closes the question and leaves the visit. A new booking can be cancelled here only while nothing has reached the practice system; cancelling a moved visit sends the cancellation to the practice system the normal way.
- Dismiss (moves, confirmations and cancellations) drops the change and leaves the visit as it is; make the change in the practice system yourself.
A Call transcript row is a booking Dentally confirmed whose call transcript couldn't be added to the patient's notes there — for example Dentally refused it, the transcript was too long, or Smileline can't tell whether Dentally has it. Open the transcript shows it in Smileline. Retry tries again (a note that may already be in Dentally is looked for first, never written twice); Dismiss leaves it.
Filling in a patient's details here needs permission to edit patients as well. The same fix shows where staff meet the booking — on Leads, the patient record and the calendar's visit panel (see A booking still on its way). A booking your team makes asks for a new patient's details before it goes, but online booking and the AI receptionist never turn a patient away over missing details: their bookings wait here instead.
If the row changed after you opened the list — someone else acted on it, or the booking reached the practice system meanwhile — Smileline says so and refreshes the list instead of acting.
An online booking waiting here is never released on a timer: the slot stays held until your team acts, and the patient has been told the practice will confirm. A booking whose deposit is already paid counts as paid and awaiting the practice, not as a lost slot, so no Deposit paid but the slot was lost task is opened; once you retry it or keep it in Smileline, the booking completes. A hold whose deposit was never paid still lapses as usual. See How bookings work.
Map provider sites
Provider sites appear under the active connection. Map each site to one Smileline location so imported records land in the correct practice context.
- Select Not mapped when a site isn't ready.
- Click Park to stop processing a site temporarily, then Resume when it should participate again.
- Records from unmapped or parked sites wait; Smileline does not guess a location or discard them.
Waiting records keep waiting until you act: there is no retry limit and no expiry, so nothing the practice management system sent is ever discarded on a timer. Map or resume the site, or resolve the record from the review queue, to have it processed.
An appointment can arrive before the clinician it names has been imported — Dentally sends no practitioner event, so a new clinician is picked up on the next hourly poll. Smileline records that appointment against a placeholder clinician straight away so the time is still counted as busy and cannot be double-booked online, then renames it automatically once the real practitioner arrives. The placeholder is inactive, so it is never offered to patients.
An appointment, treatment plan, invoice or payment can also arrive before the patient it belongs to. It waits, and is processed on its own as soon as Smileline imports or links that patient — nobody needs to act. A treatment plan, invoice or payment that names no patient at all has nothing to wait for, so it goes to the review queue instead.
Review patient matches
When an imported PMS patient resembles an existing Smileline patient, the connection card shows a banner naming how many matches are waiting, with a Review button.
Open the review sheet and compare the name, date of birth, email, and phone on both sides. Choose Link to link the records or Not the same to keep them separate. A suggested match never authorizes a link or provider write by itself.
When someone and their family member share an email or mobile, a record arriving on that contact is linked to the one of them its name and date of birth fit. If it fits neither, or more than one of them (two people with the same name, or a record with no name), it is not linked by a guess: it waits here with every likely person in that family offered, and none already linked to another record in your practice system is offered. A record that fits nobody well enough to offer becomes a new patient.
Until you decide, the record's appointments are not in Smileline yet. The diary still shows each one as busy time on its practitioner's column, labelled PMS visit · patient match pending, so nobody books over it. If you can review matches, click it to open this review. An appointment whose patient has not linked for another reason reads PMS visit · patient not linked yet.
A Smileline patient already linked to another record in your practice software is never suggested, nor linked automatically. Two records there — the same person entered twice, or a relative sharing a phone or email — become two Smileline patients, so every appointment shows. Link on a suggestion whose patient has since been linked to another record is refused: choose Not the same.
A suggestion whose Smileline patient has since been erased stays in the review without them: the Smileline side reads Erased patient and Link is gone. Not the same works as before, so a PMS record with no suggestion left becomes a new patient. If that record is the erased person, erase them in your practice software rather than choosing Not the same.
Monitor automatic polling
Dentally has a provider-managed polling cadence of 60 minutes. On a personal-token connection each hourly sync also checks Smileline's webhook in Dentally: if it was deleted it is registered again, and if Dentally switched it off after failed deliveries the card says so — switch it back on under Settings → Developer → Webhooks in Dentally. Until the webhook is registered, the card says live updates are not on yet and changes arrive with the hourly sync. Open Sync detail on the connection card for the cadence and its read-only scheduling diagnostics:
- Next due — when the connection is eligible for its next poll.
- Poll claimed until — another worker currently owns the bounded poll lease.
- Last started and Last completed — the most recent poll timestamps.
- Starts after the first import — the connection is still on its first import; hourly polling begins when it finishes.
- Waiting for activation — polling will begin after the connection becomes active.
Dentally limits how many requests a practice's tokens can make each hour (currently 3,600, shared by every token at the practice). Smileline reads the limit from Dentally and paces itself: the hourly sync and the first import use at most 60% of each hour, keeping the rest for free-time lookups and bookings made while you are on a call. If the import reaches its share, it waits for the next hour and carries on — nothing is lost or skipped.
Dentally's hourly sync also reads cancelled and did-not-attend appointments, so a cancellation whose live update was lost still arrives within the hour.
Smileline also consumes provider webhooks when available. Polling closes gaps without starting overlapping work: a claimed poll carries a fenced lease, and a stale worker cannot complete over a newer claim.
Sync now, pause or disconnect
Syncing now, pausing, disconnecting and replacing credentials live in the ⋯ menu on the connection card.
- Sync now starts the next sync straight away instead of at its scheduled time, for example after fixing something in your practice system. It is paced by the same provider allowance as the scheduled sync. If a sync is already running, it carries on and nothing is restarted.
- Pause syncing stops new sync work while keeping the connection, mappings, links, and history. Click Resume syncing to schedule it again. Use Pause for a temporary stop — it is fully reversible.
- Disconnect ends the connection. In-flight bookings and pending writes for that connection stop and are marked for review rather than left hanging. Existing CRM records and imported history remain available.
- Cancel connection removes a connection that is still waiting for provider activation.
Disconnecting stops the connection, not its history. If you later connect the same account again — the same Dentally practice, or the same Open Dental database — Smileline brings the earlier connection back, with its record links, the money it copied and its history, instead of importing everything again. The card shows the import while Smileline reads every record again; changes made in your practice system while it was disconnected apply as history, and balances stay right. With Dentally this happens by itself: Smileline recognises the practice from the token. With Open Dental, when the earlier connection still holds money Smileline copied, Smileline first confirms it is the same database: once you save the customer API key, the card shows Waiting for Smileline and says Smileline needs to confirm this key opens the same Open Dental database as your earlier connection. Nothing is copied until Smileline confirms. Nothing syncs meanwhile. Once Smileline has confirmed, the card says Smileline confirmed this is the same Open Dental database as your earlier connection. Enter the key again to connect.: click Enter credentials and save the same key. If Smileline couldn't confirm it, the card says Contact Smileline. If Smileline is still finishing the earlier connection's clean-up with your practice system, saving says so and nothing is saved: try again in a minute. Otherwise, a new connection imports again: patients converge onto their existing CRM records, and recent appointments that are unchanged reconnect to the same entries.
While an earlier connection still holds money Smileline copied from it, connecting a different account — another Dentally practice, another Open Dental database — or another practice system is refused, and nothing is saved: the form says Your earlier practice system connection still holds money Smileline copied from it, so this can't be connected and nothing was saved. Contact Smileline. If more than one earlier connection could be the account you're connecting, it says More than one earlier connection could be this account, so nothing was connected. Contact Smileline.
Notifications your practice system sends while it's disconnected — Dentally's webhooks, Open Dental's live updates — are kept. If you connect the same account again, Smileline applies them then; otherwise they wait in the review queue for someone to delete them.
If the provider needs clean-up on its side (Open Dental webhook subscriptions), the disconnected connection stays visible in the list until that clean-up completes, with any error shown on it.
If a connection reports an error, inspect its message and the affected patient. Failed PMS writes are called out on the connection and patient record instead of being hidden.
System of record
The System of record card at the top of the tab says which system holds the clinical record: Smileline, or the connected practice system while the practice still charts there. Moving the record to Smileline is an adoption — a series of recorded steps, never a switch:
- Start — an owner or manager opens the adoption against the active connection. One adoption at a time.
- Freeze provider writes — nothing new is sent to the practice system. A confirmation, cancellation or booking that would reach it is refused with a clear message until the adoption completes or is aborted.
- Approve as owner — the practice owner approves, entering their password again.
- Drain in-flight work and Reconcile — outstanding sync work finishes and the two records are compared. The drain step is refused, with the counts, while any provider write or booking operation is still outstanding.
- Complete adoption — Smileline becomes the system of record and every signed-in member is refreshed. Any provider work still carrying the old authority generation parks for review instead of posting.
Abort ends an adoption that has not completed; nothing already flipped is undone. Every step is kept in the audit trail.
Connected apps
The Connected apps tab lists each app as a card, starting with Zapier; select one to expand its detail. Zapier's shows what it can trigger on, what it can create, and where a connection starts. Once the Smileline integration is listed in Zapier's App Directory, owners and managers also get Zapier's builder there and create, edit and switch Zaps without leaving the page; expanding it passes their name and email address to Zapier so it can sign them in. See the Zapier guide.
Beneath it, Authorised connections lists what already holds access.
A PMS connection is one kind of integration. The other is an app your practice connects itself — Zapier, or anything built on Smileline's OAuth connections. These hold a credential that belongs to the practice rather than a personal API key, which is what makes them listable and revocable in one place.
- Only owners and managers can authorise a connection, and each one is bound to a single practice. Connect again for each practice you run.
- An app that Smileline has not reviewed yet says so on the consent screen, and can be connected to at most 25 practices per region until it is approved. You can still connect it; the notice tells you the app is new rather than vetted.
- An app may bring its own webhook endpoint with it. It appears under Outbound webhooks as read-only; disconnecting the app removes it.
- A connection acts as the person who authorised it: it can see and change exactly what their role allows, and its changes appear in the activity log under their name with an API key marker.
- Every role that can open Settings → Integrations can see the Connected apps tab. Owners and managers can remove any of them; anyone can remove a connection they authorised themselves.
- Disconnecting takes effect on that app's very next request, not when its token would have expired. It also switches off the webhook endpoints the connection created, releasing their share of the practice's 20 endpoints.
- Disconnecting removes access, not data. Records the app created stay; anything already copied into that app has to be deleted there.
Connected apps are listed with GET /connected-apps and removed with DELETE /connected-apps/{id} — see the Connected apps group in the API reference.
Inbound webhooks
The Inbound webhooks tab lists every Custom endpoint form: the URLs your own quizzes, forms, backends or third-party tools post leads to. Each row shows the endpoint path, whether it accepts a public browser form or signed JSON, its status and when its last lead arrived; click a row to open the form's page.
New inbound webhook starts the three-step setup (basics, one test submission, confirm the mapping). The steps, the two delivery modes and how to post are covered in Custom integrations. Forms built in Smileline and forms detected on your website stay under Settings → Website.
Outbound webhooks
The Outbound webhooks tab lists the endpoints Smileline delivers events to. Owners and managers see the tab; other roles do not.
Each endpoint shows its name, the host it delivers to, how many event types it carries, whether it is active, paused or not delivering, and when it last succeeded or failed. Only the host is shown in the list, never the full address, because a subscriber's URL often carries its own secret in the path. The full URL is visible when you edit the endpoint.
Create an endpoint
Click New endpoint. Give it a Name, an HTTPS URL, and tick the Events it should receive. Each group has its own tick box to select every event in it.
Save the signing secret from Save the signing secret. Smileline shows it once and never again. Your endpoint uses it to check the X-SmileLine-Signature header on every delivery (see Verify the signature).
Click Send test. Smileline posts a test delivery and watches for the response. When it succeeds the endpoint switches on by itself. If it fails, the card shows the HTTP status and error so you can fix the receiver and send another test.
A new endpoint stays Not delivering until one test succeeds. Real events are not queued while an endpoint is off or paused.
Manage an endpoint
- Edit changes the name, URL or events. Changing the URL clears verification and stops delivery until a new test succeeds.
- Copy for AI puts a ready-made brief on your clipboard for ChatGPT, Claude, Cursor or the developer building the receiver: the full URL, the subscribed events, the envelope, the signature check, the retry ladder and the idempotency rules from the webhook reference.
- Pause holds real deliveries; Resume switches them back on. Smileline also pauses an endpoint by itself after 20 failures in a row and says why on the card.
- Rotate secret issues a new signing secret and shows it once. The previous secret keeps working for 24 hours so you can deploy the new one; click Revoke previous as soon as your receiver has switched over.
- Deliveries opens the delivery log: every event sent to the endpoint with its status, attempts, HTTP status and any error. Replay queues the same payload again as a fresh delivery. When a patient is erased, the deliveries about them lose their payload and response and keep only these details: one not sent yet fails with Patient erased, and none of them can be replayed.
- Remove stops delivery and frees the endpoint's place among the practice's 20.
The same lifecycle is available through the webhooks API for teams that automate their setup.
An endpoint a connected app created is managed by that app: it cannot be edited, paused, rotated or removed here (the API answers APP_MANAGED_ENDPOINT), and it still counts towards the practice's 20. To stop it, disconnect the app under Connected apps or turn the trigger off in the app itself.