# AI Call Answering for Every Location on Your Denticon Instance > AI phone receptionist for Denticon DSOs. Answer every call 24/7 and book into the right office's Denticon schedule, without extra front-desk hires. **Canonical:** https://gethelpdesk.ai/integrations/denticon/ ## In short Denticon is Planet DDS's cloud practice management system for multi-location groups and DSOs, and it has a documented public developer portal whose Appointments resource covers reading the schedule, checking availability and booking, confirming or cancelling. Planet DDS's own DentalOS AI Agents, launched February 2026, are outbound only. ## Specifications | | | | --- | --- | | System | Denticon | | Vendor | Planet DDS | | Deployment | Cloud, multi-tenant, built for multi-location groups | | Best for | DSOs, emerging groups, multi-location practices and institutional dentistry | | How we connect | Vendor-approved API access, authorised by your admin in Denticon's Vendor API Settings | | Included in plans | All plans, at no additional cost | ## Overview Denticon is Planet DDS's cloud-based practice management platform, built from the ground up for multi-location groups rather than adapted to them. ## At a glance - **Every site** -- One AI front door across your whole organisation - **24/7** -- Answered at 2am as readily as at 2pm - **Per office** -- Booking rules and routing scoped to each location ## What the AI can do inside Denticon | Action | Supported | Notes | | --- | --- | --- | | Answer inbound calls for every office | Yes | Simultaneously, with no queue, across the whole organisation. | | Read schedule availability | Yes | The Appointments resource covers seeing the schedule and getting availability. | | Book, confirm or cancel an appointment | Yes | Documented in the Appointments resource and scoped per office. | | Route by location | Yes | Every request is scoped to a practice group and office ID. | | Writebacks to Denticon | Yes | Patient information, documents and appointment status can be written back where enabled. | | Event webhooks | Yes | Event-driven updates rather than polling, where your configuration supports it. | | Outbound confirmations and recall | Partial | We can do this, but Planet DDS's own Confirmation and Scheduling Agents may already cover it -- we would rather you did not pay twice. | | Clinical or RCM actions | No | Out of scope. The receptionist touches scheduling and patient contact only. | ## Why GetHelpdesk.AI for Denticon ### One standard across every location The same greeting, the same triage, the same booking discipline at every site -- instead of call handling that quietly varies with who was hired where. ### Scoped so cross-booking cannot happen Every request is scoped to a practice group and a specific office, and each phone number maps to one office. ### Covers the inbound half Planet DDS's agents handle outbound confirmations and recall outreach. New patients, emergencies and patient-initiated reschedules still need answering. ### Cost does not scale with sites Adding the eleventh office does not mean adding an eleventh receptionist. Every caller across every location is answered at once. ### Takes clicks off your coordinators Denticon users report a click-heavy interface and ticket-only software support. ### Admin-controlled and revocable Your Denticon administrator decides which offices and data domains the integration can reach, and can withdraw access from Vendor API Settings. ## How the integration works 1. **Security review and BAA** -- Your team reviews our handling of PHI, we sign a Business Associate Agreement, and we agree which data domains the integration needs. 2. **Authorise the connection** -- Your administrator approves the integration inside Denticon's Vendor API Settings, scoped to the practice group and the offices you nominate -- and it can be revoked from the same place. 3. **Map numbers to offices** -- Each phone number is bound to one office, with that office's providers, operatories, appointment types and block-outs. 4. **Pilot, review, then roll out** -- We go live on one region, read real transcripts with your operations team, tune routing and escalation, then extend site by site. ## Features - **Per-office booking rules** -- One site's block-outs and appointment-type durations never leak into another's schedule. - **Consistent handling across sites** -- The call experience stops depending on which office the patient happened to dial. - **Admin-scoped API access** -- Authorised, limited and revocable from inside Denticon by your own team. - **Transcript and summary per call** -- Routed to the right office's team, with organisation-wide visibility for operations. - **Unlimited simultaneous callers** -- A Monday morning spike across twenty sites does not create twenty hold queues. - **25+ languages, detected automatically** -- Consistent language coverage across every market you operate in. ## Use cases ### The acquisition that came with a phone problem Onboarding a new site A group acquires four practices and migrates them onto Denticon in a fortnight. The data lands cleanly; the phones do not. ### A Phoenix patient nearly booked in Tucson Cross-location scoping A caller who has been seen at two of your sites rings the Tucson line. ### Outbound automated, inbound still ringing After adopting DentalOS AI Agents The Confirmation and Scheduling Agents go live and outbound outreach improves immediately. Then the pattern becomes obvious -- confirmations are handled, and every new-patient enquiry still waits for a human. ## FAQ ### Does Denticon have an AI receptionist? Not for inbound calls. Planet DDS launched DentalOS AI Agents in February 2026 -- a Confirmation Agent and a Scheduling Agent -- but both are outbound: they call and text patients about confirmations, recall lists, waitlists and unscheduled treatment. ### Is this a real Denticon API integration or a screen-scraping workaround? A real API integration. Planet DDS runs a public developer portal with documented Appointments endpoints for reading the schedule, checking availability and booking, confirming or cancelling, plus webhooks and writebacks. ### We have 20+ locations on Denticon. Will the AI book a patient into the wrong office? No. Every Denticon API request is scoped to a practice group and a specific office, and each of your phone numbers maps to one office. A call to your Tucson line can only resolve against Tucson's providers and operatories. ### How does this compare to running a centralised call centre? A call centre still scales linearly with call volume, still goes home at 6pm, and still costs more per location every time you acquire one. ### What patient data does the AI touch, and is it HIPAA compliant? Only what is needed to identify a caller and book them: name, contact details, appointment history, availability and appointment type. ### Can we pilot on one region before rolling out to every site? That is how we recommend doing it. We go live on a single region, review real call transcripts with your operations team, tune routing and escalation rules against what actually came in, then extend site by site. ## Other practice management systems - [Dentrix Ascend](https://gethelpdesk.ai/integrations/dentrix-ascend/) -- AI receptionist for Dentrix Ascend - [Dentrix Enterprise](https://gethelpdesk.ai/integrations/dentrix-enterprise/) -- AI receptionist for Dentrix Enterprise - [athenahealth](https://gethelpdesk.ai/integrations/athenahealth/) -- AI receptionist for athenahealth - [Cloud 9](https://gethelpdesk.ai/integrations/cloud9/) -- AI receptionist for Cloud 9 ## Next steps - [Book a demo](https://gethelpdesk.ai/#schedule-demo) - [All integrations](https://gethelpdesk.ai/integrations/) - [Pricing](https://gethelpdesk.ai/pricing/)