Skip to main content
Tellescope Integration

Book More Appointments. Reduce No‑Shows.

An AI agent that calls and texts your patients in your practice's name, gets them booked and confirmed, and writes every outcome straight back to your Tellescope calendar.

BAA available
SMS on your Tellescope number
Consent + quiet hours
See it in action

Not a reminder.
A conversation.

One-way reminders get ignored, and a patient who ignores a reminder is a slot you lose. VisitConfirmed texts each patient from your practice's own Tellescope number, calls the ones who go quiet, answers what they ask, and gets the visit on the books.

  • Two-way over SMS and AI voice
  • Answers questions, day or night
  • Escalates only what needs staff
9:41
NF

Northside Family Health

Text message

Hi Maria, it's Northside Family Health. You have a visit with Dr. Lee on Tue at 2:00 PM. Reply YES to confirm.
9:41 AM
Do I need to fast beforehand?
9:41 AM
No fasting needed for this visit. Reply YES to confirm or RESCHEDULE for a new time.
9:42 AM
Yes
9:42 AM
You're confirmed for Tue at 2:00 PM. See you then!
9:42 AM
Text Message
Sent from your Tellescope number, so patients never see VisitConfirmed

Tellescope Runs the Workflow. VisitConfirmed Runs the Follow-Through.

Tellescope gives care teams journeys, messaging, and a calendar in one place. But a journey can send a reminder; it cannot pick up the phone, answer a question at 9pm, or talk a wavering patient onto the schedule. That gap is where visits get lost. We've written more about why appointment reminders aren't appointment confirmations and what it takes to close the loop.

Tellescope
  • Patient records and care journeys
  • The calendar and appointment templates
  • Your messaging number and inbox
VisitConfirmed
  • Two-way SMS confirmations
  • AI voice, inbound and outbound
  • Answers patient questions
  • Reschedules against your calendar
  • Status written back to the event
  • Human escalation

From Journey to Filled Slot, on Autopilot

Four steps, and no one on your team touches a phone.

01

A journey hands off the appointment

Add a Send Webhook step to the journey that should start confirmations. You choose which patients are enrolled, so nobody is contacted by surprise.

02

The agent texts, then calls

Texts go out through your own Tellescope number in your practice's name, and land in the patient's Tellescope conversation as usual. Patients who do not reply get a call.

03

The conversation adapts in real time

The agent answers patient questions, handles a "can't make it," and knows when to stop. No answer? Retry. Needs a person? Escalate.

04

The calendar event updates itself

Confirmed, cancelled, or moved to a new time, the outcome is written straight back to the Tellescope calendar event. Your team reads status where it already works.

SMS and voice work together. Texts go out over your existing Tellescope number, with no carrier registration to wait on. AI voice runs on a dedicated line we provision, so patients can call in and be called back.

Connect With One API Key

VisitConfirmed runs alongside Tellescope, not in place of it. Tellescope stays the source of truth; VisitConfirmed handles the outreach.

You generate a key. We do the rest.

Create an API key in Tellescope under Settings, then hand it to VisitConfirmed. We register the webhook, create the journey that forwards patient replies, and turn on calendar write-back. There is nothing to install and no server to run.

Tellescope
VisitConfirmed
SMS from your number

A journey step hands off the appointment → VisitConfirmed holds the conversation over your Tellescope number → the outcome is written back to the calendar event

Send Webhook journey step sms_messages calendar_events API key auth Signed webhooks

Optionally, VisitConfirmed can book reschedules against your Tellescope calendar, reading live availability from your own providers and templates rather than a separate schedule.

One Journey Step. The Iceberg Underneath Is Not.

Add one step to a journey. Get a full engagement engine underneath.

What you see

A Send Webhook step in the journey you already use to manage upcoming appointments.

What VisitConfirmed handles
  • An agent that handles real patient replies, not keyword matching
  • Retry cadence, then escalation when a person is needed
  • Cancellations and reschedules flow both directions
  • Timezone-aware quiet hours and consent management
  • White-label messaging that never names VisitConfirmed

What Your Team Gets

A Fuller Schedule

Patients get booked who would have drifted, and show up who would have quietly disappeared.

Less Manual Work

Free front-desk staff from repetitive reminder calls and routine follow-up.

Live in Days, Not Weeks

Texting rides your existing number, so there is no carrier registration to wait on. Connect the key and start.

One Conversation Thread

Messages and replies stay in the patient's Tellescope conversation, so staff never switch tools to see what was said.

Covered by a BAA

VisitConfirmed signs a BAA with your practice, and every webhook we receive is signature-verified.

Human-in-the-Loop

Automation handles routine work while your staff stays in control of exceptions.

Built for Practices Running on Tellescope

If your practice runs on Tellescope and missed appointments hurt revenue, utilization, or patient outcomes, VisitConfirmed is designed for you.

Virtual-first clinics

Practices already running patient engagement through Tellescope journeys.

High-volume care teams

Where confirming tomorrow's schedule is a daily job nobody wants.

Operations teams

Where a missed visit means lost revenue, delayed care, or wasted capacity.

Stop Losing Visits You Already Won

One API key, and the agent starts working your schedule.

Frequently Asked Questions

No. Tellescope stays your platform and source of truth. VisitConfirmed runs alongside it and handles the appointment conversation.
You generate an API key in Tellescope and provide it to VisitConfirmed. We register the webhook, create the journey that forwards patient replies, and enable calendar write-back. The only step inside Tellescope is adding a Send Webhook step to whichever journey should start confirmations, which is how you choose the patients to enroll.
Not for texting. Messages go out over the number you already use in Tellescope, so patients see a number they recognize and there is no carrier registration to wait on. That makes Tellescope the fastest of our integrations to get live. Voice is the exception: it runs on a separate line we provision, because Tellescope's calling cannot carry an AI agent.
VisitConfirmed subscribes to changes on the calendar event, so it stops chasing a visit the practice cancelled and picks up the new time when one is moved. A reconciliation poll runs behind that as a backstop, so a single dropped notification cannot leave the two systems out of step.
Yes, on a dedicated line rather than your Tellescope number. Tellescope's own calling runs on a softphone that a server-side AI agent cannot join, so voice runs on a line VisitConfirmed provisions, the same way other AI calling tools in Tellescope's catalog run on their own telephony. Patients can call it and speak with the agent, and we offer outbound confirmation calls for practices that want them. Tell us and we will set it up for your practice.
Practices running on Tellescope that want to reduce no-shows and cut front-desk phone tag without building a patient engagement system from scratch.