We would like the ability to send patient emails and text thru the API protocol. Right now, offices on E-services have their office phone as the text number and emails are saved on open dental. Please help to enable this.
The use cases are many for this. Patients who have missing medical history forms, send a specific reminder for patients to take medications for premed indicator, send emails/text follow up for planned appts, etc.
Email and text functions via API
Re: Email and text functions via API
Good afternoon,
You can currently use the API to retrieve the patient contact information (email address, phone number for texting) via the Patients GET (single/multiple) or Patients GET Simple methods. Your application can then send the email or text message to the intended recipient. See this post.
You can currently use the API to retrieve the patient contact information (email address, phone number for texting) via the Patients GET (single/multiple) or Patients GET Simple methods. Your application can then send the email or text message to the intended recipient. See this post.
-
akjain1@gmail.com
- Posts: 12
- Joined: Thu Feb 16, 2023 2:28 pm
Re: Email and text functions via API
Yes I do know that function. The issue is that the email does not show that open dental sent it. Also the most important part was the texting feature. Offices give their numbers to open dental via eServices text. So it would be helpful to use their feature to leverage the phone number
Re: Email and text functions via API
Could you please clarify what you mean? The linked post above explains that we could insert rows into the emailmessage table to show that your application sent an email. As far as texting, are you suggesting your application would send text messages but would require the office to pay for eServices and each text anyway?
-
akjain1@gmail.com
- Posts: 12
- Joined: Thu Feb 16, 2023 2:28 pm
Re: Email and text functions via API
To clarify my message, here goes.
For texting, we have clients who use eServices and Open Dental has ported their number to enable texting with their office numbers. We would like API to utilize Paid clients of eServices to send text thru the eServices platform. We are well aware that we can text from independent agencies and applications, but since Open Dental has the office number for integrating texting, it would help to utilize this service.
For texting, we have clients who use eServices and Open Dental has ported their number to enable texting with their office numbers. We would like API to utilize Paid clients of eServices to send text thru the eServices platform. We are well aware that we can text from independent agencies and applications, but since Open Dental has the office number for integrating texting, it would help to utilize this service.
Re: Email and text functions via API
Open Dental currently has no plan to create a feature to allow 3rd party services to send texts using our eServices texting service.
If we opened up our texting infrastructure to 3rd party use, it is highly unlikely that we would allow them to text using the numbers that we have registered with campaigns that we are using for our own eServices. There are many reasons why we would not do this, but the simplest one is that we do not want other services to restrict our ability to send texts through our own campaigns.
If we opened up our texting infrastructure to 3rd party use, it is highly unlikely that we would allow them to text using the numbers that we have registered with campaigns that we are using for our own eServices. There are many reasons why we would not do this, but the simplest one is that we do not want other services to restrict our ability to send texts through our own campaigns.