Hi, this is Roshan Agarkar. I'm VP of Product and Customer Success at Synup. Today I'm here to talk about one of the most commonly occurring use cases in our world when it comes to keeping all your location information consistent, up -to -date and accurate across the board. So for this conversation, I want to use a hypothetical example. The hypothetical example, imagine there is a business that has about 200 locations. It's a multi -location business that has 200 locations. A relatively decent sized marketing team where the marketing team is obviously primarily responsible for all the content that goes out that gets published on the website, on the listings and everywhere there is content published around that business. Now here is a use case. A digital marketer says that, hey, I just went in and updated hours of operation for these that are based out of the northeast zone. However, the descriptions are changed now. All these 40 locations are now showing old descriptions. How did that happen? I did not even touch the description field. It's a very common use case, more common than you would think. Here is really what happened. This digital marketer went in and used a bulk upload sheet to update hours of operation for those 40 odd locations. However, they used a previous version of the file where the new business descriptions were not populated. How can you avoid this? Or what can you really go and do to check what must have gone wrong here? Now, like I said, the marketing team owns the content, the business descriptions. They might have updated business descriptions, unique business descriptions for every single location. Imagine they have a special service at certain locations. They do not have certain services at special locations. They accept appointments on phone on certain locations. They accept appointments on via the web on certain locations. They might have certain locations that are located inside a mall. In the description, they have specifically mentioned how to go and find our location. All this information that was up to date is now erased at this point. However, the business is showing the latest hours of operation. Now, what can I go back and check here? The hours of operation are owned by the operations team. The business descriptions in this case are owned by the marketing team. One of my primary points of check would be to go back and check the approved business descriptions. One of the best practices is to always maintain up to date approved content, approved business location information file internally with date and time stamp. That would be my first place to go back and check. Were the hours when the file that was used to update hours of operation, did they have the latest description or not? That would be my number one place to go back and check. If that is the reason, then the answer is simple. But now begs the bigger question. Sure, I was able to go and fix the description over here. Was there any other piece of information that may be stale now? Any other old information that got updated? if the importer requires a full file, I would build the file from a fresh approved baseline, apply the intended changes, then compare the result against that baseline. Every unrelated field should remain consistent with its approved value. I would also check for edits made after the baseline was created so the preparation process doesn't accidentally miss newer work. One of the other things I would recommend is preview. If the tool that you are using provides one, followed by a small test batch, I would include representative cases such as location with recently revised wording. I would then check both the intended changes and the fields that should have stayed the same. To be clear, I haven't tested a specific importer for this walkthrough. This is the process I would use to verify the behavior. The successful test would support only the situations actually covered by that test or the use cases that are covered by that test. There can be more, more costlier versions of this problem. Imagine that old file still marks a permanently closed location as open. Depending on how the importer handles status changes or creates records, uploading that file could potentially reintroduce information the business had already retired. I would keep a controlled record of closed locations using stable location identifiers. Before every upload, I would check incoming rows against those records. Any attempted change from close to open should be held for explicit approval. I would also check the age and origin of the file. Like I said, one of the best practices is to maintain the date and time stamp. A recent upload doesn't make the information inside it recent. A human review deserves particular attention when a change affects whether customers should travel somewhere. Closures reopening address changes, normal hours, holiday hours. I would also review unexpected new locations, duplicate identifiers, cleared fields, unusually large batch of changes. AI could help summarize all these differences. Flag descriptions that appear to restore an outdated service or highlight unusual hours for review. I would use AI to direct attention with a person checking consequential changes against the approved records. Before the next upload, I would want a customer, a potential marketing team running into this issue to make three checks. First, is this file based on latest approved information? Check where it came from, when was it prepared, whether anything changed after that, pay particular attention to recently corrected descriptions or opened or closed locations. That would tell you the recent changes are going to tell you the kind of help you validate whether the file is accurate or not or the most recent or not. Second, be very focused on what changes this upload is going to make. Review every changed field, not just the column someone remembers editing. Confirm how the importer handles included values, missing columns, empty cells, location statuses. If there is a preview available, show changes nobody intended to resolve before uploading. Third one, decide who is going to check it. How are you going to confirm the result? Which locations they will inspect, what they will compare against, include any high risk changes and account for updates that may still be under review. Keep the approved file, upload record, uploaded record so that you can trace what happened and if something looks wrong. The central point is that successful submission and a correct published result are two different things. A success message may tell you that the file was accepted, processed, latest values have been synced. That does not mean the information that is reflected across all the publishers is accurate or up to date. It does not by itself establish that every intended value is now visible to customers. For me the job is complete when the published information matches what was approved and the important fields that were never intended to be changed still remain intact. Thank you for listening.