Wednesday Connection 03-13-24

FxMedSupport Wednesday Connection 03-13-24

In this video, I discuss various features of the Cerbo system, including manipulating items, editing recommended supplements, using the POS system, and navigating the legacy automator. I also highlight the importance of integrating Hint to Cerbo for seamless information transfer. No specific action is requested from viewers, but understanding these features can enhance workflow efficiency.

Quick recap

Kevin discussed updates and enhancements to their e-commerce platform, emphasizing a new integration for medical providers. He explained that this integration allows providers to have their own e-commerce store and benefit from wholesale pricing. Kevin also mentioned the system's compatibility with WooCommerce, Shopify, and Big Commerce, as well as ongoing work on integrating with Salesforce. Other topics included a new POS system, issues and updates related to the visual automator, the shift from hint to Cerbo for the client's automation process, the integration of a payment system, and the integration of a credit card refund system.

Summary

E-Commerce Platform Updates for Medical Providers

Kevin discussed the updates and enhancements to their e-commerce platform, with a focus on a new integration for medical providers. He explained that the integration allows providers to have their own e-commerce store and benefit from wholesale pricing. This integration is designed to be passive, with providers able to recommend products during encounters or by creating a schedule. Kevin also mentioned that the system integrates with WooCommerce, Shopify, and Big Commerce, with work on integrating with Salesforce underway. He also highlighted a custom integration with the WooCommerce Point of Sale system for hybrid practices, allowing recommended supplements from medical appointments to be automatically loaded into the system for easy transactions.

New POS System and Automator Issues Discussed

Kevin introduced a new POS system and its integration, highlighting the upcoming launch of the Multi branch. However, mpike raised a concern about the new automator system's inability to categorize subfolders, a feature that the visual automator had. Kevin confirmed this as a bug and assured that the development team would address it promptly. They also discussed other issues and updates related to the visual automator, with Kevin explaining the process and its similarities to the legacy automator. However, no clear resolution was provided for mpike's concern about the automation not triggering notifications if a tag is added later.

System Building and Scheduling Process

Kevin discussed the importance of proper system building and the need for checking and modifying schedules. He realized that he had forgotten a step in the process and corrected it in real time. He also discussed the issue of multiple locations and the need to add a tag identifying the location when an appointment goes from scheduled to checked in. Kevin emphasized that it was important for the system to be built correctly and that this was used as a training tool for their staff.

Shift From Hint to Cerbo for Automation Process

Kevin and mpike discussed the shift from hint to Cerbo for the client's automation process. Kevin proposed that the client should invest in the integration from hint to Cerbo to guarantee a smooth transition and eliminate the need for manual data relocation. He emphasized that this transition would necessitate financial, workflow, and training investments. Kevin also stressed the need for detailed information about the transition from hint to Cerbo to assist their development team. mpike acknowledged the logistical challenges and confirmed the intention to proceed with the plan. Additionally, mpike expressed interest in discussing something Kevin mentioned on the Facebook page.

Integration of Payment System Stacks With Cerbo

Kevin explained the integration of a payment system, 'Stacks' (previously known as Payment Depot), with their Cerbo system. He clarified that 'Stacks' is an authorized payment gateway that allows the system to connect with various payment systems like Square, Clover, and a private PayPal version. Kevin demonstrated that users can charge a patient a certain amount and allocate it accordingly. He further explained that users can select the corresponding button that corresponds to their payment system for processing a transaction. Kevin also mentioned that they can trigger the system one at a time as patients go through, or invite all their patients to the new payment system.

System Benefits Over Cerbo's Default

Kevin discussed the benefits of their system over Cerbo's default, emphasizing its ability to automatically send notifications when a payment fails and to handle pending transactions. He also explained the system's user-friendly approach to managing subscriptions, allowing patients to select and approve charges. Kevin highlighted the system's ability to create invoice templates, which can be sent to patients for approval. He concluded by expressing his preference for this system over others due to its efficiency and user-centric design.

Credit Card Refund System Integration in Cerbo

Kevin explained the integration of a credit card refund system in Cerbo, a medical software. He emphasized that the system allows users to view all recent charges and perform full or partial refunds, leaving notes on why the refund was given. Kevin also discussed the ability to check if a patient has a credit card on file and if they've ever added one. He mentioned that if the card is found to be invalid, a link can be sent to the patient to update their card information. mpike inquired if the card input process would look the same whether initiated by an email or a portal message, to which Kevin confirmed it would. However, Kevin clarified that the card information cannot be entered through the patient portal; it must be done through an email, text message, or a link sent from the portal.

Integrating Authorized.net Payments in Cerbo

Kevin explained the process of integrating with the authorized.net system for payments in Cerbo. He clarified that failed charges would still be visible in Cerbo, allowing the use of all Cerbo billing features. Kevin emphasized that the first step upon a charge failure is to contact the patient directly. He also introduced a new feature that allows admins to be notified 18 hours after a charge fails, giving them time to reach out to the patient. Kevin expressed his belief in the patient's willingness to pay and the importance of giving them a day to rectify the situation.

Credit Card Processing System Discussion

Kevin expressed his mixed feelings about their credit card processing system, highlighting its strengths and areas for improvement. He emphasized that most practices do not require a third-party credit card system and suggested that users should learn to optimize their use of Cerbo. mpike, however, clarified that he was not involved in the billing aspect and would bring this information back to the Admin for consideration. Kevin agreed to a support appointment to further discuss the matter.

Kevin's Team Meeting Agenda

Kevin expressed his intention to learn more about the interests of the team he would meet with. He also mentioned he would try to find any new or exciting developments to share. Kevin then reviewed the topics covered, including WooCommerce POS integration, automated talks, and the Authorized.net third-party payment system. He concluded by reminding attendees about upcoming classes and support options. No new questions or issues were raised.

Words 

00:04 Good morning and welcome to Wednesday, March 13th, uh, Community Connection. Um, there's some people joining right now, so we'll go ahead and let them join and just wait a few minutes.

00:14 Very exciting. We are to talk about some of the updates that are currently live and then the others that are actually being pushed later today.

00:21 So, very excited about that. Um, and we'll just go ahead and wait a few minutes for those that are, um, to join in.

00:29 Um, if anybody has any topics or questions, please go ahead and do put them in the chat section. Um, so we'll just few minutes.

00:48 What I'm going to quickly do in the beginning part of the Wednesday Connection is talk about one of our new enhancements.

00:56 Um, very excited about this upgrade. This is to the e-commerce platform. So inside of Servo, we have uh. e-commerce integration so that medical providers can have their own e-commerce store and they can get the wholesale pricing and they can make the profits, not Fullscript or other large companies.

01:20 That supplement integration was always intended to be ah very passive so the cart can get filled through providers just recommending products in an encounter or filling up supplements here or simply by creating a supplement schedule.

01:35 You can go ahead and automatically create a patient's e-commerce cart and that cart can be completely manipulated from within Servo.

01:46 You can remove items, you can edit the quantity of the shopping cart, you have the whole history. This is currently a WooCommerce shopping cart.

01:57 We do integrate with WooCommerce, Shopify, BigCommerce. We are working on a Salesforce. We've been working on it for a while.

02:08 But uhm yeah, so I'm gonna go ahead and scroll back and just go ahead and show you uhm. I'm gonna go ahead and show you that what we're gonna do is we know that we can come here and we can update the cart we can log into the cart with our one-click check-in if we wanted to experience it as the the patient

02:38 or customer we can check out and so I'll just make the cart go to zero we can send the the customer patient an email letting them know that the the shopping carts ready for them to check out they can get a push notification in their mobile app but for those practices that are hybrid and maybe a practice

02:56 has a point-of-sale doesn't work if I already have it loaded the point-of-sale application for WooCommerce allows those practices that are that are in person and their patient walks out of that office and that you know they were just with a medical provider in an encounter that medical provider recommended

03:24 supplements and that supplement cart was loaded uh and now as that patient walks up to the front desk and they're using the POS system uh organically the WooCommerce POS system does not integrate with the patient shopping cart inside the system so we've built the um the custom integration and so you

03:46 simply just go ahead and put your patient slash customer email address first and last name works as well and we're going to go ahead and find that user and then it's going to organically or I shouldn't say organically it's going to then programmatically go and find that user's shopping cart and it's

04:02 going to load the items of the shopping cart into the WooCommerce POS system so that the items that were recommended from the medical appointment automatically get pulled into the POS system.

04:16 for a simple fast transaction. When you do check out and they hit pay, it will clear the shopping cart as well so that it is as if they logged into their own account and placed an order.

04:29 So just an introduction to the POS system brought to you, the POS integration, really excited about. Let's go jump into our servo system and pull up our application.

04:56 I am told that multi-branch is getting pushed later today, so we're very excited about that. questions on any automations or any questions on any of our applications or on servo or something where we should start our class today?

05:20 I have a small question, Kevin. Um, in the new automator system, um, I've seen it on your automator system where you're able to categorize into subfolders, uh, with the visual automator.

05:34 And I'm wondering, for some reason, when I go to do that, it doesn't allow me to categorize them into subfolders that I create in the visual automator.

05:43 It only allows that in the legacy automator. Do you know what I could be doing wrong? I'm not understanding. So, can you can you click on the automator system?

06:00 Maybe it's easier to just show. How you have these subgroups where it says like push notifications. When I create those they don't stay and I can't ever in the legacy automator we used to be able to file things into groups, right?

06:21 So, are you saying that when you when you say that you create a group? Correct. It then shows up in the legacy automator and I found that out after having the titles.

06:32 Multiple titles that I had attempted to do in the visual automator were all duplicated in the legacy automator. And if I go ahead and just move.

06:49 Okay well yeah, oh there's definitely an error. Yeah it's not, oh I'll have the dev look at this right away.

06:54 Um. It's a small question, but I was like, I didn't ask that. But my folder's there, which, okay the folder's there.

07:02 And it is holding it, but it's not holding it where it should be. The question is, does it stay? And the fact that it showed error, but it also saved it.

07:12 It shows that our code's not right, but if I leave and come back, will testing 1, 2, 3 be there?

07:17 And testing 1, 2, 3 was made at the legacy. Now, there's a bug. We'll fix it. Okay, thank you so much.

07:23 You're so, so welcome. Yeah, oh my gosh. And so that is going to be our visual automation create groups is done.

07:44 Having a bug. I'll ask another question. Yes, that's okay. I know in the legacy automator. We're able to make campaigns.

08:02 Is that am I saying the right thing? Are we able to do that in the visual automator? It's it's the same thing.

08:08 So, um in the legacy We we used to call like that main automation you trigger like the main automation and then anything that it did after that was a campaign um okay like this so yeah you do one thing and then they would do ten other you really it's it's the same exact process just a different terminology

08:36 so if we just just open one up real quick this would be that main idea event and then this is technically the campaign I see okay thank you yeah yeah we are working on and there's a lot of the minor changes being made right now like the ability to hover and have information pop up that pertains to the

09:11 condition the the one that I'm just really excited about because it can't really move forward um is the multi-branch being able to say like because what it'll eventually do is you can should you want is have one automation per major servo event you might have others that do other things but you could

09:31 really just have one automation per event uhm and and it'd be pretty powerful but it needs to get pushed live first and apparently that gets that gets done later today the the automations we were working on for you and your practice how or how are those coming?

09:57 So I went through and tested them yesterday um um where we had combined one step to the beginning of step one.

10:10 Hopefully that makes sense to you. Um my only concern is if we add the tag um later on the notification doesn't trigger uh the notification that a few days later like we had hoped.

10:30 Um so that's something that I'm not following um the definitely not following but what I can say is off of just um a integration that we did for, did I press the wrong button, nope I got it, um we had an automation request, um and so we had one of our clients say hey can you just build us this and so

10:52 our team went in and built it for them and it just worked. It's an example of something very simple but it allows them to do something complex later and so what they have is when the schedule is modified and the schedule is modified to the status uh for the new patient appointment and it's in the uh

11:20 uhm the green wood. Ooh I forgot to do one. condition. Oops. I just figured out in real time I forgot I forgot something.

11:34 Scheduled modified. Oops. Let's fix this in real time for the client. Oh my gosh. I feel I realized I just forgot a step.

11:42 Because it's not just scheduled modified it's scheduled modified. Modified with check-in. Oh wow. You see even I forget sometimes. So we're gonna go to a Therbo community and No, we're not because that would show real data for the client.

11:58 Okay, so I'm gonna go to my bill and I need. Oh wow. I love it when I figured out something in real time.

12:05 Here is an appointment. We're gonna take this appointment, and we're gonna move it to scheduled checked in. That is the actual metadata piece that I need.

12:14 I'm gonna go into my system. Apologies if I make, if I'm confusing anybody right now, but I just realized that I didn't build it correctly.

12:24 We need the data appointment status as well to be checked in. So I am going to go here, I'm going to log back in, and fix that for the client.

12:41 Oh my gosh, how funny, funny, funny of me. And while I am editing this. I can tell you what we're doing.

12:50 So they have multiple locations, and they want that, I can't believe I forgot to do this, wow. So they want it so that when their appointment goes from scheduled, modified for this particular appointment.

13:01 That, um, they add a tag so they know what location, um, the users are American. Oh my gosh, and let's save changes.

13:23 And so since we built two of them yesterday, I neglectedly add, forgot to add, not just the schedule modified, because that means, oh my gosh, every time it's modified.

13:32 We want it modified when it goes to checked in. To add that tag. There is no patient connection with this, so it's not like you're gonna, you know, ping your patient, but it's really important that it's built properly.

13:49 And so appointment status. I just realized I didn't build it right. And it's kind of just a example of Even I make mistakes.

14:05 There we go. Aw, I'm so happy. Now I saved it and it's updated. And we actually use this as a training for our staff.

14:14 So when this automation request came in, we actually use the request from the client as a training session. So, the other reason I bring this up, and I'm sorry I went on a tangent, but I realized I wanted to fix it for the client as soon as I could, uhm, is that your automation, if you're trying to do

14:36 an event and it's not triggering what you want, we want to step back. and figure out if the previous step is, you know, the hindersome, or, I'm trying to think of a better way to put it, uhm, from what we went through yesterday.

14:52 Let me clarify as well, because the automation we built, functions properly. It functions properly that, that trigger, when the patient is created in servo, it goes through those steps.

15:04 Where we have to discuss is, we aren't having our patients created in servo yet, because we're still using Hint, and so that's something that needs to be discussed if we need to create like another temporary automation that we use as we, because the whole point of what we're creating is, we're starting

15:24 a new onboarding process with our, with our members, and it's temporary as we transition out of Hint, and so maybe that helps clarify that it functions properly as if we're doing everything out of Servo, which is exactly where we intend to be, but we have to figure out in the interim when we start our

15:44 onboarding process, how do we get it to run smoothly with patients being created in Hint technically. I would believe to make your life easy in the transition, you would come to our website, you got to support and do a request for development.

16:00 And you should let us know exactly what is going on from Hint to Servo and your company in my honest humble opinion should invest in the integration from Hint to Servo so that it programmatically can do what you need and know that in this Because the commitment from moving from leaving Hint to go to

16:20 Serbo is a huge commitment. It's both a financial investment, it's a workflow investment, it's a training investment, it's a pain in the butt to your patients.

16:29 So we know that your patients are probably going to have to enter new credit card information system at some point.

16:33 Like it's a big process. I believe that acknowledging that it's a large process and investing in the integration so that you don't have to manually move information, you make it so that when something happens in Hint, it actually creates the information you want in Servo so that eventually your Servo

16:56 is caught up to where your Hint used to be and you can turn Hint off. That is how a true integration.

17:04 and you know a migration of leaving one application to another should work. Most practices manually do it and try to piece it together.

17:14 Ultimately, you're going to spend more time, energy, and money not doing it through an integration. If you're not going to be on Hint long term, we wouldn't build a very powerful integration.

17:31 Or I would say we wouldn't build a very, you know, integration with lots of bells and whistles and switches. We're going to build the integration that serves your function because your goal is to leave Hint.

17:41 If you were going to be on Hint forever, well we'd probably build you an integration that had fun, cool features and, you know, worked back and forth together.

17:48 Um, but honestly, that's the best, uh, uhm, solution. Uhm, because then you don't have to manually do anything. It's, it's a program, it's a workflow.

17:59 It's if this then that, go to Serbo, start creating the user in Serbo. Uhm, the more you do, when you have one Serbo system, one other, you know, application that you're using, that your patients are using, and now if we're then bringing those users from this system into Serbo, but we're not actually

18:21 creating them as a patient, we're, we're technically creating a third system. So it's a lot that you and your admin will have to manage, and I believe ultimately if you invested in just the integration to solve your purpose, it'd be a lot easier.

18:41 Because the goal is to leave Hint, right? You're not trying to straddle Hint forever. The goal is to streamline and leave Hint, correct?

18:56 Yeah. Uhm, Uhm, can I ask you a question though about something on the Facebook page that you had mentioned about a, I think it was a processing system?

19:09 You can ask questions about anything. Stacks Payments, I think that's what it's called, uhm, yeah. Yeah. What do you know about that?

19:20 Can you just explain that? I mean, we've looked into it, but it sounds like you know a little bit more about it.

19:25 Yeah, so first I'm going to go to our Servo Integration page. So Stacks just happens to be the one that we're like, I don't know, quote-unquote friends with, but only because they used to be Payment Depot and Stacks Purchase Payment Depot.

19:42 So we're here in our enterprise interface. Payment Depot So we should upgrade that so that it says stacks, and it's actually stacks.

19:54 In all honesty, they're all the same. And when I say they're all the same, Payment Depot. U.S. pay, um, there's like five others, we don't list them all.

20:04 Because in the end, they leverage the authorized.net payment gateway. So if, whatever payment system you use, could connect to this.

20:16 We can connect your servo to that payment system. Now we do connect to other payment systems like Square, Clover, um.

20:26 We have a private PayPal one. Um, it's not, we aren't able to release it, but we do have a PayPal one.

20:32 Um, and so when we can connect to a payment system using APIs and web hooks, we can still accomplish everything that you can do inside servo.

20:38 We just do it a little different. So we can when you're inside here, inside here being the billing box, Mr.

20:52 Please always talk um as specific as possible not talking specific. So you see that we pulled the billing box. We can go ahead and say, you know, we want the patient to be charged, I guess let's do 450.

21:04 and we sp we're gonna allocate it here. You historically, and you may not be historically because you're in hint, but eventually you would come in the servo, your servo integrated credit card, you press this button and you add payment or and it would process the transaction.

21:21 When you are using our integrated system, you would just simply select the button that corresponds to your payment system. Now, we servo kind of refreshes ours because we have we've you know, so they don't continue to make more buttons for us.

21:39 They eventually just remove one of our old, um, because we can still trigger them other ways. So, if you theoretically went to one of our payment system, authorize.net.

21:52 In a depot square, it runs almost identical as the servo system. Just, it triggers your outside payment system. You can leverage that payment system by opening up our application.

22:05 And depending on what system you have, you simply, you know, you can go to it, and you can open it up.

22:13 They all have the how-to instructions. Um, but just to give you a little overview. So, our system works first by allowing you to umm to either invite all of your patients to the new payment system, umm, or you can trigger it one at a time as they're going through.

22:32 Umm, and so in our credentials tab is where you would have like the welcome email, and this is like the hey welcome to our system, or you have the email that that you would send, and it's not really an email, it's notification, because it can get sent via portal, or an email, umm, it's the notification

22:51 that they get when the payment failed. So that's one of the items that makes our system different than servo default, is in servo default, if a credit card or payment fails, you get the decline message, umm, I know that's not the decline message, but you get the decline message, and then you as an admin

23:11 , or as a medical practice, now- have to come up here, and you've got to send a message, and you've got to say, hey patient, please log in to servo, umm, the credit card you had on file did not work, and you'd have to do a process, umm, yes you can build an automation that when credit card de- Clines

23:29 we see it, and then we can send an automation, but our systems built that intuitively, if the system detects that the card failed, or there is no card on file, we just automatically send them the notification with a link that says add the card info and go here, and when they add the card info, it automatically

23:47 grabs a transaction that is pending. If they have seven pending transactions because they're really, really bad, and they've got a subscription that has been running for seven months, and for some reason you didn't turn it off, you just let it keep going.

24:00 Even though they haven't paid you, if they eventually come back in the system, we will capture all seven payments because you technically never, you never cancel the subscription, so in essence they owe you it.

24:10 So it's just a more intuitive way to talk to a patient about transactions is saying, main. Hey, your payment failed is just automatically.

24:19 We have other ways to use the system where when you press the button inside servo for the charge, it doesn't charge them automatically, it can trigger it.

24:27 Invoice this, send them, I don't like this. Umm to me this is, this is not how- a medical practice should run.

24:34 You have presented the services you want to offer and when somebody comes in and has accepted those services and you provided them, you don't then say here's what we did pay us.

24:43 You take your money because you already provided those services. Umm and it's not looking- car like they already left. Umm and so we I think we do subscriptions a lot easier because we just make it really easy.

24:58 You simply just log in on your- you know you're on your patience page. Simply select what- charge you want or charges.

25:06 How often do you want it to run? When do you want it to start? Number of payments and you create the subscription.

25:12 See the subscription list of all your active subscriptions. Umm. This is something I really like so we get- give you the ability to create invoice templates.

25:22 Umm. And invoice- and so our- the payment system we're looking at works for all of our third party integrated payment systems.

25:30 Umm this is one that I really like because it allows you to- to create templates Let's, based off of charges so let's say that we want to create an email and in this email it has you know maybe umm maybe a lab umm and so you would do a one lab charge and maybe it has a supplement system.

25:53 You have the ability to create invoices that get sent to your patient that allow your patient to umm is there anything here.

26:05 It allows your patients to select what the charges they want. Umm they also can execute on it. When is this a really good idea?

26:13 Umm Patient came in, they saw you for uh you know hormones and you recommended a Dutch hormone test as soon as that Dutch hormone test got into the encounter you can automatically They automatically send them the invoice that says do you approve it?

26:28 Now why is that different than automatically charging for like an appointment? Well because your patient agreed to the appointment they're in the appointment and that's a non argumentative charge.

26:39 But as a provider for your recommending services. And so usually how it goes is patient comes in, we recommend a bunch of stuff by sending a message.

26:49 Patient then gets the message. They then send us back an edited message of what they approve. We then send back the new message.

26:55 and most likely we're using uh servo umm estimate system. Which is a great system. This kind of just speeds it up because it says this is what's recommended.

27:07 And it gives them the option to just manually choose. So we if you show them you know something with ten items umm I know I keep pulling up templates with with just one.

27:18 Umm if you pull if you give them a template with oh no there is multiple items. Umm they can say yes I approve this charge, yes I approve this charge and I don't do this charge.

27:28 Umm and so I really really like it because for ordinary charges you can just have it your patient just gets a link and they click it umm and it's automatically charged from what you recommended.

27:40 Umm really fun just like any credit card umm integration. Your patient's email, it'll pull up all the recent charges and you can do full refunds, partial refunds, leave notes on why you're doing it.

27:51 Umm. We really try to make it so you don't ever have to leave servo when you're inside our system so we can give you the entire charge list just because you have every transaction that was ever attempted in the system regardless of its status.

28:05 This is one that I really like. At the end we're starting to get into where it becomes very intuitive. Now remember this works within the application as well for the umm for umm The patient, not so much the ability to add their credit card but when you start sending them portal messages umm an email

28:23 and they have the app. Umm but this gives you all of your patience in your practice. It shows you if they have a credit card on file and if they- I've ever added one so umm right now like I don't have one and I've never had one or I shouldn't say I, this user.

28:39 It could show false and update meaning they once had one the card on file is currently bad and we need them to update it.

28:47 So you can simply click Update card umm and it would send a link you can automatically or copy the link sorry I would copy the link to my clipboard or I can automatically just send a portal message or an email to this patient saying hey please umm please upload your credit.

29:04 Umm, this is one of those pages that I also really like. It allows it so when that patient is in the office and they hand you the card you simply can go and find their account and you can simply hit update card or add card and it will load the screen.

29:20 In of the bank umm in and so I can simply just hit this and it's actually going to take us umm to an encrypted page.

29:28 It looks like it's your website and we're staring at the patient's credit card screen so that you can enter it for your patients.

29:35 Go ahead and click. Back. So if the patient is entering their card information like through the initiation of an email or portal message umm it would look the same as what you just showed.

29:46 Is that correct? Yeah so if I go open my email and. I don't know if it's come in yet. My internet's quite slow today.

30:02 Umm the e-mail that we see right here. Is the e-mail that that you get. If it's never been for a new card and for an updated card you'd get this one.

30:15 Umm we could, well actually how do I even have it sent. Umm. It. It's a patient account. So I've just sent a portal message to this patient since.

30:40 sense. My email might take a long time and let's log in. So you can imagine this coming many different routes of travel and remember um oh wow my notes really slow.

31:03 I mean it can come many routes of travel and umm jimma caught. Whenever your patients open up that screen you are looking at the bank you're not okay you're not so when it when they get the email and they click that email and it takes you right here now it obviously it says fx meds work because it's

31:25 our account umm now this will be r-u-r-l an encrypted key but it'll be your logo we do it just so it looks like you but you're actually staring straight at the bank so none of this information is being saved anywhere locally in our system or your system or servo system It's straight into the bank umm

31:47 and- Would function the same if they put their card information in their patient portal as well? No. No, so this- they have to enter it through this particular- They would enter it through an email.

32:00 Umm, a text message, I don't recommend. Umm, just cause text is inherently never the safest. Umm, they would- you can get the message from the portal and that message would, you know, I'm sure I have one, some in here.

32:13 This is not the- the best patient in the world for examples because we use them so much for testing and I think we might need a new testing patient.

32:23 Umm, but let me try to find one. Here's my comprehension. Do do do do do do do do do Umm, maybe, have I not I wonder this user in a long time.

32:53 Here we go. So kind of something like this. You know it's very default and then we're gonna say click here and then they'll click here and they'll come straight to this page.

33:00 And if it was an email it'd be the same exact thing just in a prettier form. from added email. Umm.

33:08 Because we are connecting straight to your authorized.net system. And then when you come here and you are inside turbo and you're adding a payment when you, Select your, your associated connection.

33:23 We're connecting. We're using that webhook to say, hey grab this information. Go talk to this patient's banking account. You know so that's, that's how it's working.

33:33 Umm, is there a way to attract like outstanding payments for patients within the integration at all? Well you'd still be able, because those charges would be in servo.

33:43 You'd still be able to use all servo, billing, all servo, reports. Umm, correct. Okay. Okay. Now there is one caveat.

33:51 If I subscribe The portion fails, we'll back out the charge because it doesn't work. If a, if you come in here and a charge fails, we can't actually, we don't come in here and edit and make it a red charge and say it was uh declined, servos and other APIs.

34:07 eyes. We would, we would first thing we do is go and talk to the patient, right? So if a credit card fails, I don't need to talk to you as an admin right away.

34:18 Okay, good. It failed, thanks for letting me know. The very first thing we do is go talk to the patient and say.

34:24 The credit card we had on file failed or you never had a credit card on file and we just ran umm we just did something and we expect a card you know we expect payment so please pay us.

34:36 That happens automatically because that's really the next piece in the in the process. Now what we do because we don't have the ability to say hey it didn't work you didn't you're not getting your money what we do is we give you the ability to say.

34:56 Umm right here. Notify me umm and I thought we had a number okay so it's not in this update it's the next one coming.

35:05 So right now it's 18 hours umm we're getting ready to allow you to do to choose. I did a- 18 hours umm because I figured if you ran a charge on Thursday at 5 o'clock you're now at Friday at 5 o'clock if we did 24 hours well that doesn't give you enough time to reach out to the patient and say hey the

35:27 charge yesterday failed we know you got the email and the text message that said give us payment you know what's the status you're leaving for Friday so we did default 18 hours because that gives you the ability to push back and sometime about noon or one o'clock what happens is is.

35:44 The admin you choose will get a task that with all of the charge information that says this charge actually didn't go through um patient's been notified um and you should be aware that the charge isn't good um when that patient makes payment it all disappears because we remove it all but so we give you

36:09 you know a day or I should say we give the patient a day to make it right I really live in the world that most patients are like not scam artists they really want to give you money usually you're asking for it in a way that makes them have to stop their day and do something kind of like servo in order

36:28 to get servo the credit card you've got to stop exactly what you're doing and log into the servo system and you know then go to a certain place and enter certain information I'm not saying it's bad I'm just saying this is the servo process and so you umm you have to do that when you're patient gets an

36:49 email inflow umm that just says hey please upload your credit card well they're going to click the button they're going to upload the credit card and move on umm so there's our items that I really really love about our credit card processing system and there are items I don't umm whenever somebody tries

37:11 to onboard with us at a credit card I will actually try to talk you out of it I would try to find the reasons in why you're not using servo correctly how you can use servo correctly with whatever credit card system you're using and leverage our automator to get like good messages umm in my real opinion

37:33 there's only a few use cases on why you truly need a third party credit card system most practices really really don't umm and I will try to talk you out of it because umm anything that could be done inside servo equivalent Level it.

37:52 Should be done inside servo equivalent I think you only should go to fx med support when we make it better and I can't really say we make it better other than right when a transaction fails we notify a patient and give the patient the link to make it better.

38:09 With our automator system we can make it so that when a transaction fails we notify the patient. No we cannot make it so that they just get a link and make it better umm but I don't believe that truly fx med support.

38:24 warrants leaving an entire servo payment system umm because the number one thing you just said is when a patient logs into the patient portal can they enter their credit card and since the answer is no that's why servo's better.

38:43 Umm and and it just is. Umm I don't ever plan on having the ability to put our system here but it's not needed.

38:49 Umm so what are some of the use cases that a third party credit card system works and then I'll kind of ask you why you guys are going to interested in it.

38:57 Umm the olden days of subscriptions. Subscriptions and memberships used to be really hard. Umm if you're selling products that someone deems not appropriate or approved.

39:09 Umm cannabis supplements. Umm b****** medical hormone. Like there's a lot of weird random rules and weird random states that eventually a credit card processor tells a medical practice that's doing everything ethical.

39:22 They can't use that credit card system inside servo. Okay well then you know that's an example. Umm. You're trying, you're running services.

39:32 And you acknowledge that servo is amazing for slow onboarding for integrative functional medicine. But when you're, when you want to just say welcome to our website and go straight to a shopping cart and a chair, not the best.

39:48 Umm. And no slight to servo. But you know for fast services, maybe it makes sense to have an e-commerce store and they purchase it.

39:58 Umm you know three IVs or something. I don't know. There are, there are use cases where the third party credit card processor makes sense.

40:06 Umm. Most of the time it is learning how to truly use servo just a little bit better and umm. And.

40:16 More optimized. What is your reason to want to use a third party credit card processor now? I'll be frank. I am not the person to make that decision or answer that question.

40:29 We just heard you mention it on the Facebook page. Oh. And we didn't know about it. I would, this is information that I all need to bring back to admin because it was just something we heard you mention.

40:42 Um, and we had an heart of it. So, yeah. No, I mean, so we, we have a lot of them.

40:50 Um, where's our little part? I also, for the most part, am not, I'm not involved in the billing aspect of things, at least not at this point.

41:01 So, I'm not the person to, to the answer. I would, whoever that person is, I would love to talk to them and figure out who, if you know, if you're leaving hit, you're obviously going to a new credit card processor and servo, who are you using?

41:16 Why are you using them? They all have their advantages and disadvantages. Umm, and I would not be looking at the per click or per transaction.

41:26 Umm, charge, as much as there's other features that make some of them a lot more advantage than others. Umm, and so.

41:36 Umm, yeah. Would you recommend we just set up a support appointment to talk more about this if that's something they're interested in?

41:43 Yeah, and again, but I'm gonna try to talk them out of it. It's going to be a support appointment where I'm showing you the other servo options and why I believe He If like in my opinion stripes the best I haven't looked into propeller very much yet just cuz I haven't busy but in my opinion stripe is

42:00 the best because you can put the stripe credit card um. Registry you can put on your registration form Umm you can put the stripe umm credit card form so when your patients are onboarding they're forced to put you know they're forced to enter their credit card umm.

42:17 For some reason they won't put it on the embedded scheduling system that makes it a little bit more difficult umm but.

42:24 They all have their purses and minuses and if you use servo very efficiently you don't need another one in my opinion unless you're one of those other groups selling cannabis selling supplements heavily umm.

42:40 See you somebody says you know we went to your website and you look more of uhh this than an actual traditional provider there's a lot of reasons they you know you lose your account umm some are justified some are not but yeah so you just go and go to our website and have them make a support appointment

42:59 love to talk to them love to learn about the use case scenario umm yeah awesome thank you you've been very helpful coming oh thank you I'm glad it's the whole goal of umm.

43:12 this umm is to just learn because I learn as well umm and when I meet with your team I'm gonna learn gonna learn what what interests them umm and not using the servo default one umm and how we can show them how to.

43:28 Umm yeah yeah. I don't have any other questions. Oh so let me try to think is there anything in any way shape or form new or exciting or any anything that I can let you know about um I'm really it's just really really funny I don't I don't know if um.

44:00 I don't know if the client knew that I I had to fix that fast. That's funny. If he pays attention he's gonna see that it was last edited today though.

44:09 Um. So that's funny. Um. I really have nothing else to talk. I can always just waste time. Let me do one last load of the system see if there's anything new that I'd want to talk about and then if not maybe just call it an early day if nobody has any questions.

44:34 Yeah, I don't I don't really have anything new to this if there's if nobody has any questions I would just say thank you all so much for coming.

44:41 Umm. Today we went over some WooCommerce, POS integration. We went over so. Some automated talk. We did a random talk about our authorized.net third party payment system that works for for a lot of payment systems.

44:57 Umm. Yeah, so thank you all for coming. It was such a pleasure to connect with you all. Look forward to answering any questions.

45:04 Is that anybody else has? Please do remember from our website our support page it lists all of our weekly classes so yes we have a class tomorrow and we have a class Friday.

45:14 And we have umm our support videos umm as well as all of the options that you have in order to get hold of our customer support team.

45:24 Thank you all so much. Have an amazing rest of your Wednesday and we'll see you out in the internet.