Is Sense Down Right Now? Check if there is a current outage ongoing.

Today we received multiple reports of users running into issues when logging in or resetting their password. After our team was able to review, we identified an issue starting at 9:30am PST causing intermittent issues in Sense, along with being able to send Test Emails through Engage, or sending out User Account Invites in the product and have deployed a fix as of 1:30pm PST. We have confirmed these issues have been resolved, but if you believe you’re still facing this issue, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

Today we received multiple reports of users running into issues when logging in or resetting their password. After our team was able to review, we identified an issue starting at 9:30am PST causing intermittent issues in Sense, along with being able to send Test Emails through Engage, or sending out User Account Invites in the product and have deployed a fix as of 1:30pm PST.We have confirmed these issues have been resolved, but if you believe you’re still facing this issue, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

After monitoring, we have confirmed that all broadcasts attempted during that time have been sent out, and all new broadcasts are sending out as expected once more. If you believe you're still facing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will investigate.

We have confirmed that the fix implemented has corrected the broadcast issue, and all scheduled broadcasts affected during that time have been sent as expected. We will monitor to ensure we don't see this recur, and all functionality continues to operate correctly. If you believe you're still facing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will investigate.

We have identified the underlying issue causing broadcasts to be stuck, and have implemented a fix to have any attempted broadcasts during this time send out as soon as possible. We will provide another update once we confirm when all broadcasts will be caught up and seeing stability in the function once more

We have received reports of Broadcast Messages not being able to be sent out as expected when attempting to send right away. Our team is actively investigating what maybe occurring and we'll provide updates as we find more information.

After monitoring, we have confirmed that all broadcasts attempted during that time have been sent out, and all new broadcasts are sending out as expected once more.If you believe you're still facing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will investigate.

We have confirmed that the fix implemented has corrected the broadcast issue, and all scheduled broadcasts affected during that time have been sent as expected.We will monitor to ensure we don't see this recur, and all functionality continues to operate correctly. If you believe you're still facing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will investigate.

We have identified the underlying issue causing broadcasts to be stuck, and have implemented a fix to have any attempted broadcasts during this time send out as soon as possible. We will provide another update once we confirm when all broadcasts will be caught up and seeing stability in the function once more

We have received reports of Broadcast Messages not being able to be sent out as expected when attempting to send right away. Our team is actively investigating what maybe occurring and we'll provide updates as we find more information.

Our team discovered a service disruption that impacted CSV data uploads via the Sense SFTP integration and related API processing on May 6, 2025, from 3:00am PST to 7:20am PST (or 10:00 UTC to 14:20 UTC). During this time window, files uploaded via SFTP were not processed, and some data updates submitted through the Sense API may not have been successfully applied. Affected requests would have returned a 400 or 500 error. This has been caught by our team and corrected from persisting. At this time, all services are now fully operational. A full post-mortem is underway to prevent recurrence and strengthen deployment and alerting practices. If you uploaded files or pushed updates on May 6, 2025, between 3:00am PST to 7:20am PST, please reprocess or retry those updates. If you need support with identifying failed updates or require assistance, please contact us at support@sensehq.com. We sincerely apologize for the inconvenience and appreciate your understanding and partnership.

After monitoring, our team has confirmed that the fix put in place did resolve the issues we were seeing with Workflow events not processing intermittently. We will continue to monitor and ensure this does not recur in the future. If you believe you are still experiencing issues, please reach out to our Support Team and submit a ticket here https://support.sensehq.co/hc/en-us/requests/new for us to investigate further.

Our team has identified the issue and has put in a fix to resolve these events from not sending out. We are showing stability across the platform once more, and will continue to monitor all Workflows to ensure we don't see this recur. If you believe you are still experiencing issues, please reach out to our Support Team and submit a ticket here https://support.sensehq.co/hc/en-us/requests/new for us to investigate further.

We have received reports of Workflow Events not sending out as expected for intermittent nodes. Our team is actively investigating this issue and working to have this functioning as expected for all workflows once more. This issue is only impacting Workflows, and we have confirmed Journey events are processing as expected. We'll continue to provide updates here as we learn more.

After monitoring, we are showing successful API returns and receiving confirmation of users able to access their Sense numbers and messaging history as expected once more. Our team will review and put measures in place to prevent this from recurring in the future. If you believe you are still facing issues please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will review as received.

We have received reports of users running into API errors when navigating in Sense or unable to access their Sense number when using the platform or extension. Our team has identified the root cause and have deployed a fix to correct this. We are actively monitoring to ensure we don't see this recur and we will provide an update once confirmed fully resolved. If you believe you are still facing issues please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new.

Our team has identified an error on the Sense API from April 16th, 5:00pm PST through April 17th 8:00am PST. During this time, any customers using Sense API for their ATS connections may have seen missing writebacks or data not populating as expected. This has been corrected and all data is in the process of backfilling. If you believe you are still seeing errors in the data, please submit a support ticket to https://support.sensehq.co/hc/en-us/requests/new for investigation

After monitoring, we have confirmed rolling back the MFA settings did correct this issue we were seeing with users logging in. We will continue to review the MFA settings to see why this occurred, but we can confirm users can log in as expected once more. If you believe you are still running into issues logging in, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will review.

“We have received reports of users unable to login to Sense using Multi Factor Authentication, or having issues when attempting to use the One Time Password this morning when prompted. This may have affected those who did not have Multi Factor Authentication enabled previously, and was pushed through Sense March 31st. Our team has rolled back these changes to ensure all users can login as expected once more. We are monitoring currently to ensure we don’t see this recur, and our team will be reviewing the MFA push to determine why this was caused. We will follow up once we have full confirmation login is working as expected once more. If you believe you are still running into issues logging in, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will review.”

After monitoring, we are seeing the People Tab and Audience list loading successfully for the users. Our team will continue to watch through out the day to ensure we don't see this recur. If you believe you are still seeing issues while logging in please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

Our team has identified the issue and a fix has been implemented, resulting in stability across the platform. We are seeing People tab and Audience List in Journeys loading successfully for users. We'll continue to monitor to ensure we do not see this recur on our end. If you believe you are still seeing issues with People Tab please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

We are seeing reports of the People Tab and Audience List in Journeys not loading for users intermittently. Our team is actively investigating and we will provide updates once we have more information

After monitoring, we are continuing to see successful login attempts when using the One Time Passwords for MultiFactor Authentication for users. Our team will continue watch throughout the day to ensure we don't see this recur. If you believe you are still seeing issues while logging in please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

Our team has identified the issue in the MultiFactor Authentication, and has deployed a quick fix to resolve this issue. We are seeing successful login attempts once more across users, and the one time passwords being accepted as expected. We’ll continue to monitor to ensure we do not see this recur on our end. If you believe you are still seeing issues while logging in please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

We are seeing reports of the One Time Password not being allowed when using MultiFactor Authentication intermittently for users, not allowing them to login to Sense via webportal, extension, or mobile app. Our team is actively investigating and we will provide updates once we have more information

After monitoring the stability and usage of the Learning Center, we have confirmed that everything is working as expected for all users. We will continue to make improvements internally to ensure we don't see this recur in the future. If you believe you are still facing errors attempting to access the learning center, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

After working with our downstream vendors, our team has restored functionality to the Sense Learning Center. All courses and available knowledge material are accessible for all users once more. We will continue to monitor over the next few hours to ensure we don't see any new reports or issues with the Learning Center and will provide another update once confirmed no new issues arise. If you believe you are still facing errors attempting to access the learning center, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

Our team has identified the root cause and is continuing to work with our downstream vendor on having the Sense Learning Center restored for all users. No Sense products are impacted during this downtime of the Learning Center. We'll continue to provide updates as we receive them

We have received reports of the Sense Learning Center being unavailable to users at this time. We have engaged our downstream vendor to determine the root cause and get this up and running for all users once more. This does not affect any functionality of the Sense product. We'll continue to provide updates as we receive them

After monitoring, we have confirmed that we are seeing standard network traffic across Sense, and successful logins from all affected users. If you believe you are still experiencing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

Our team has identified and corrected the issue that was preventing some users from logging into Sense or navigating through pages. We are currently monitoring to ensure we don't see this recur, and will update here after seeing success across all users, or any other information we receive. If you believe you are still experiencing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

Our team has received reports on being unable to log into the Sense webpage, or unable to navigate between pages intermittently for some users. We are actively investigating this issue and will provide updates as we receive them.

After monitoring, we are continuing to see stability on platforms across the entire Sense server and all products working as expected. Any missed messages during this time will populate in the inbox as expected once the user is logged in. If you believe you are still experiencing issues with the platform related to this issue, please submit a ticket to our support team to check on a case by case basis at https://support.sensehq.co/hc/en-us/requests/new

A fix has been implemented and we are seeing stability across all pages and products once more in Sense. Our team will continue to monitor to ensure this does not recur and work with those who submitted tickets to ensure we are not seeing other reports We will provide another update after we confirm this has been resolved permanently after monitoring further. If you believe you are still experiencing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

Our team has identified the cause of the server spike and actively implementing a fix. Once deployed we'll monitor to ensure we see the spike in latency decrease and stability across the platform. We'll provide more updates as soon as they are available

We are receiving reports of a spike in latency on the Sense servers, causing extended loading times in pages or not loading all the data expected. Our teams are actively investigating the cause and working to have a fix in place as soon as possible. We’ll provide more updates as we receive them

After monitoring we are still seeing successful received messages in Sense from all carriers as expected. We will continue to work with our SMS partners and make sure we don’t see this issue recur in the future. If you believe a recipient is still facing these errors, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will take a further look.

We are seeing messages received successfully from all carriers once more and our SMS partners are reporting the same from their end. We are continuing to monitor to ensure we don’t see this recur. If you believe a recipient is still facing these errors, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will take a further look

We are continuing to work on a fix for this issue.

We have received reports of T-Mobile users receiving “Service Not Available” when attempting to message Sense Numbers. Our SMS partners have confirmed this issue is isolated to the T-Mobile services, and are actively working with the downstream providers to correct this error. We are actively working with our vendors for updates as soon as possible, and will post updates as they are received

After monitoring, our team has confirmed the note writeback queue has stabilized and we’re seeing all notes populate in the expected time once more. If you believe you are still experiencing delays, please reach out to our support team to submit a ticket at https://support.sensehq.co/hc/en-us/requests/new and we will review on a case by case basis

We are continuing to see the backfill of any missed writebacks decrease, and the queue stabilize to allow any new writebacks to populate in the expected timeframe once more. We will continue to monitor to ensure we don’t see the queue increase once more, but do expect to be fully caught up within the next hour and a half. We will provide an update once we are seeing this caught up, or if we see this recur.

After review, our team was able to identify the root cause on the AWS server and have started to reprocess all missed writebacks. We have confirmed no notes will be missed during this delay and all notes should populate over the next few hours. We will ensure the note writeback queue is running as expected, and will update as we are seeing the flow stabilize once more

We have received reports that Messaging Note Writebacks are not recording into the respective ATS records. Our team is actively investigating the cause and working to have any missed messages backfilled as soon as possible

Our team has identified an instance that affected intermittent customers in our note writeback processor which caused duplicate messaging note writebacks to populate in the ATS record on August 29th, between 08:30am to 10:30am PST. Our team was able to isolate the anomaly and correct this to prevent any other duplicates from populating. We are currently working to remove any duplicate notes that appeared during this time, and will work with all ATS partners affected to ensure this can be corrected. Please don’t hesitate to reach out to our Support team for any questions or concerns you may have at https://support.sensehq.co/hc/en-us/requests/new

After monitoring, we are continuing to see stability across the platform and no longer seeing errors on products. We are continuing to monitor and check with reporters on a case by case basis. If you believe you are still facing these errors, please submit a support ticket to our team at https://support.sensehq.co/hc/en-us/requests/new

The fix has been deployed by our team, and we are seeing stability across all products once more. Our team will continue to monitor to ensure we don’t see these errors recur and will provide an update once we are confident that this has been fully resolved or if we see any other issues arise. If you believe you are still facing these errors, please submit a support ticket to our team at https://support.sensehq.co/hc/en-us/requests/new

We have been able to identify the root cause for these intermittent errors across the platform and are actively implementing a fix to correct these. Once the fix has been deployed, our team will confirm that we are seeing all products work as expected and continue to monitor the platform to ensure we don’t see this recur. We’ll provide more details once the next steps are completed

Our team has identified a few instances within Sense that are producing errors or unable to access the page. Currently we are seeing this within Drag and Drop editor templates when attempting to create or adjust, when attempting to view Chatbot Transcripts analytics, as well as intermittent scheduler links. Our team is actively investigating these errors and we will continue to provide updates as soon as we have them

This morning our team performed a last minute needed database update that caused 500 errors while attempting to login or navigate through Sense intermittently for users. This started roughly around 5am PST and lasted for less than 30 minutes. As of 5:30 am PST we confirmed these errors are no longer appearing and all users should be able to use Sense as expected once more. If you believe you are still experiencing issues please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new for our team to review

Our team has further monitored and we are continuing to see success in deliverability overall. If you believe you are still experiencing issues please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new for review

After further testing and updates we are seeing continuing success in deliverability overall. 

 Our team will continue to monitor on the backend, but if you believe you are still experiencing issues please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new for our team to review

As we continue to monitor, we are still seeing a higher level of unsuccessful deliveries. Our team is taking more action to work with our partners to determine next steps and we’ll ensure to provide updates as we receive them

We have made updates to alleviate these failed deliverability instances and are seeing normal deliverability rates in the system. Our team will continue to monitor deliverability rates and will be in communication with our SMS vendors to ensure we do not see this recur. If you believe you are still experiencing issues please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will take a deeper dive.

Our team has identified the cause for these intermittent deliverability failures and are taking action to get these restored. We are actively working with our carriers as well for any other underlying issues as well and will continue to provide updates as we receive them.

We have received notice from our SMS carriers that we are seeing an increase in deliverability failures and carrier filtering notices intermittently among users. We have escalated this with our partners and they are actively investigating the cause and working towards a resolution with the recipient carrier networks. We will continue to update this page as we receive more information

As of 9:30am PST Sense saw instances of incoming messages being delayed when appearing on the Sense UI or Apps for up to 30 minutes or more. Our team was able to identify the root cause and implement a fix to ensure all messages are being received on time once more. We have confirmed stability in the platform as of 12:30pm PST and will continue to monitor for any other delays.

We have confirmed we are seeing successful broadcast sends and stability across all products once more. Any broadcast that was scheduled or failed during that time will be automatically resent from Sense. We identified delays in note write backs during this fix as well, and have confirmed that any missed notes during this time will be backfilled. Our team will continue to watch for any other spikes or concerns, and if you believe you are still experiencing these issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

After review, we have been able to deploy a fix that has all broadcasts sending on time as expected. We are continuing to monitor performance to ensure we don't see this recur, and will provide any updates that we receive. If you believe you are still experiencing these issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

We have uncovered an issue within the UI where scheduled broadcasts are not sending as expected and showing scheduled within the UI. Our team is actively working on a fix and we will keep you updated on our progress.

Our team discovered an error on the Sense API this morning around 6:00am CST that caused the Sense UI not to load correctly, or products became unavailable during that time. We have since been able to identify and correct the error, and we are showing stability across the platform as of 7:30am CST. Our team will continue to monitor throughout the day

Our team has monitored and we're continuing to see stability across all platforms. We will continue to review throughout the day, but please reach out to our Support team at https://support.sensehq.co/hc/en-us/requests/new if you believe you are still seeing this occur for any user

After reviewing our team found the cause for the delays and we are now seeing stability across all products. Our team will continue to monitor to ensure we do not see this recur. If you believe you are still experiencing delays within the UI, please submit a ticket with our Support team at https://support.sensehq.co/hc/en-us/requests/new

We have received reports of users facing intermittent delays when attempting to navigate and use the messaging product within the UI and Extension. Our team is actively investigating and we’ll provide updates as soon as we learn the cause

After monitoring, we have confirmed we are seeing stability across all Sense Chatbots as expected. If you believe you are still experiencing this issue, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us

We have confirmed that we are seeing all chatbots affected load correctly once more. Our team is continuing to monitor to ensure this does not recur. If any issues persist, please report to our support team at https://support.sensehq.co/hc/en-us

We have received reports of issues with Sense Chatbots failing to load. Our team is actively investigating and will provide updates as soon as we have more information

Our team found there was an issue with the bulk cleanup function within our Engage product that caused cleanups scheduled between October 12th through October 18th to not run during that time frame. We have since identified the root cause of this and any active cleanup that did not run has since been backfilled and completed If you believe you have any issues due to this downtime, please reach out to Sense support at https://support.sensehq.co/hc/en-us/requests/new

After monitoring the affected components, we are seeing everything operational, and all products functioning as expected. If you believe you are still experiencing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new or support@sensehq.com

Our team has reported Sense AI and Chatbot issues have subsided. We expect systems should be fully functional at this point. This outage is now being moved to the “monitoring” stage to confirm the recent changes before officially declaring as resolved.

Our team has reported Sense AI and Chatbot issues have subsided. We expect systems should be fully functional at this point. This outage is now being moved to the “monitoring” stage to confirm the recent changes before officially declaring as resolved.

Our team is still actively investigating this error when attempting to generate AI messages through Sense products We'll provide an update as soon as we receive more information

We are currently seeing increased reports of the Sense AI app is giving an error when attempting to generate a message for intermittent users. Our team is actively investigating this and we'll provide updates as we receive them

After monitoring deliverability traffic and confirming with our downstream partners, we are seeing successful deliveries once more to all carriers. Any message that failed during this time will not be resent automatically and will need to be resent manually as needed If you believe you are still experiencing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new or support@sensehq.com

We received confirmation from our downstream vendors that they were able to identify and mitigate the issue with the affected carriers, and we’re seeing successful traffic once more. Any message that failed during this time will not be resent automatically and will need to be resent manually as needed Our team is continuing monitor the traffic for all numbers and continuing to work with our vendors incase of a recurrence. If you believe you are still experiencing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new or support@sensehq.com

We are receiving reports of some users receiving an error message when attempting to send messages stating "Possible Carrier Filtering". We’ve received confirmation from our downstream vendors that there is a current blocker that is causing messages to not be delivered intermittently, specifically to AT&T and Verizon carriers. We are working with our downstream vendors to resolve this blocker, and we will continue to provide updates as we receive them

Our team has continued to monitor and confirmed we’re seeing all products function as expected once more. We will continually monitor the servers on the backend and review to see the full scope of the effects and will communicate this once confirmed. If you believe you are still experiencing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new or support@sensehq.com

As our team continues to monitor the AWS outage, we are seeing a decrease in load failures within Sense pages and components. We are still seeing some failures, mainly on our Chatbot product, that is still causing users to not be able to load or view pages, and will continue to monitor these statuses. We’ll provide more updates as we receive them

We are currently seeing issues due to an AWS outage. You may be experiencing intermittent load failures across various pages and components. Furthermore, some inbound messages and delivery analytics may be delayed or missing as a result. Our team is conducting a thorough impact analysis to better understand the situation and determine the best course of action. We apologize for any inconvenience caused and appreciate your patience as we work to resolve this issue

After monitoring the affected components, we are seeing everything operational, and all products functioning as expected. If you believe you are still experiencing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new or support@sensehq.com

We have identified the root cause and rolled out a fix to correct this. We are seeing the Discover Product and Field Writebacks function as expected once more. Any missed writebacks during this time are currently reprocessing and we should see this all catch up shortly. Our team will continue to monitor to ensure we don’t see this revert, and we’ll provide more information once we have it. If you believe you are still experiencing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new or support@sensehq.com

Our team has found an issue with our Discover Product in Sense, and is actively investigating the root cause for a fix. In addition we are seeing the use for Field Writebacks are not showing available or recording back to the candidate record. We did confirm any missed data will be caught up once we implement a fix. We'll continue to provide updates as we receive them

Our team has confirmed we're seeing all systems operate as expected once more, and all users are able to navigate the portal as expected. If you believe you are still experiencing issues, please reach out to our support team at https://support.sensehq.co/hc/en-us/requests/new to submit a ticket for further investigation.

Our team has identified the root cause of the API error, and has implemented a fix. We are seeing servers stabilize for all users once more, and are continuing to monitor to ensure all fixes have taken correctly. If you believe you are still experiencing issues, please reach out to our support team at https://support.sensehq.co/hc/en-us/requests/new to submit a ticket for further investigation.

We are seeing increased reports of users receiving an API error when attempting to send messages through Sense or navigating through the portal. Our team is actively investigating the root cause and working to get all systems operational once more. We’ll be sure to provide updates as we receive them”

We have received confirmation that this issue has been resolved. If you continue to see any issues, please reach out to Support@sensehq.com.

Our downstream vendor has confirmed they are once again seeing latency reduced to normal levels, and all functions stabilized. We will continue to monitor this with them and provide updates as we receive them

We have received an update from our downstream vendor that they have made an update to their server and are seeing latency decrease. They are continuing to make this update and monitoring the status as this is implemented. We’ll continue to provide updates as we receive them

Our downstream vendor is still actively investigating the cause for the increased latency on the server. We are working with them and will be sure to continue provide updates as we receive them

There has been reports that the fix implemented did not take as expected and our downstream vendor is seeing latency pick back up causing errors to come through once more. We’ll continue to work with them for updates and provide what we have here as we receive them

We have received reports that our downstream vendor has put in a fix and are seeing their servers working as expected once more. Sense is seeing the product function as expected once more for users as well, but will continue to monitor the progress. If you believe you are still experiencing issues, please reach out to our support team at https://support.sensehq.co/hc/en-us/requests/new to submit a ticket for further investigation.

We have received notification from our downstream scheduler service that they are seeing increased latency on their servers, causing appointments to not be able to be booked or throwing errors for intermittent recipients. They have confirmed they are actively investigating this and we will provide updates as soon as we receive them

We have confirmed we are continuing to see all note writebacks process as expected throughout today after monitoring the fix. We will still continue to backfill the writebacks that were delayed during this time and provide updates on a case by case basis. If you believe you are not seeing new note writebacks process correctly, please reach out to our support team at https://support.sensehq.co/hc/en-us/requests/new to submit a ticket for further investigation.

After monitoring, we can confirm all note writebacks are processing as expected for today’s notes. We are still in the process of backfilling all other missed writebacks and will continue to monitor on our end they continue processing. We will continue to provide updates on the backfill as we receive them. If you believe you are not seeing new note writebacks process correctly, please reach out to our support team at https://support.sensehq.co/hc/en-us/requests/new to submit a ticket for further investigation.

Our team has confirmed that we are seeing all Note Writebacks process in realtime once more. We are continuing to reprocess any that may have been missed during this time as well. We will continue to monitor the status of these and provide updates as we receive them If you believe you are not seeing new note writebacks process correctly, please reach out to our support team at https://support.sensehq.co/hc/en-us/requests/new to submit a ticket for further investigation.

Our team has discovered a delay in Note Writebacks being posted from the Messaging product. The cause has already been identified and a solution has been implemented. We will continue to monitor as the delayed Writebacks are being processed and provide updates once that is complete.

We are seeing normal deliverability rates for all networks once more. We will continue to monitor delivery traffic to ensure we do not see any spikes recur. If you believe you are still experiencing failures please reach out to our support team at https://support.sensehq.co/hc/en-us/requests/new to submit a ticket for further investigation.

We have received confirmation that our vendor was able to work with the downstream carrier and reduce the amount of SMS filtering with the T-Mobile network. We are now seeing normal delivery rates to all carriers once more. We are continuing to monitor all outbound traffic to ensure we don’t see another spike in filtering. If you believe you are still experiencing failures please reach out to our support team at https://support.sensehq.co/hc/en-us/requests/new to submit a ticket for further investigation. We’ll provide more information as we continue to monitor.

We are still seeing higher than normal SMS filtering by the T-Mobile Network for intermittent numbers. Our team is actively engaged with our partners on the cause of these errors and we’ll continue to share updates as we receive them.

We are getting reports of higher than normal SMS filtering by the T-Mobile network for intermittent numbers. We are working with our partners on this for those affected and will provide updates as we find more

After monitoring the results of the fix deployed, we are seeing all services function correctly once more. Any end user that may have faced this issue can re-engage the bot to finish any conversation initiated. If you believe end users are still experiencing issues when interacting with conversation bots, please reach out to support team at https://support.sensehq.co/hc/en-us/requests/new to submit a ticket for further investigation

We have deployed the fix and are seeing all services restore once more. We will continue to review chatbot conversation status and will provide updates as we monitor. If you believe end users are still experiencing issues when interacting with conversation bots, please reach out to support team at https://support.sensehq.co/hc/en-us/requests/new to submit a ticket for further investigation.

Our team has found Sense Chatbot conversations are experiencing errors when attempting to be interacted with end users. We have identified the error on the API and are actively working on a fix to be deployed. We will provide updates as we have new information.

We have confirmed we’re seeing all users able to connect their calendars correctly once more. Any user that was disconnected during this time will need to re-connect directly in Sense once more. For information on how to do so, please see the below support article for assistance. https://support.sensehq.co/hc/en-us/articles/13981726944013-Sense-Scheduling-Setup-Guide#h_01GVG68ND94WTZBNQP2H0YTZR4 If you believe you are still having connection errors when attempting, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new for further review

Our team has identified the root cause to the disconnection of MS 0365 calendars, and have updated the configurations on the backend to correct the error when reconnecting. We are seeing calendars connect correctly once more. Any users that were experiencing this will need to reconnect their calendars in the Sense instance directly. For more information on connecting your calendar, please review the below support article on how to do so: https://support.sensehq.co/hc/en-us/articles/13981726944013-Sense-Scheduling-Setup-Guide#h_01GVG68ND94WTZBNQP2H0YTZR4 We will continue to monitor this on our end to confirm no other users are seeing issues when reconnecting. If you believe you are still having issues please submit a support ticket to our team at https://support.sensehq.co/hc/en-us/requests/new

We are receiving reports of intermittent users being disconnected from their calendars within Sense Meetings, and unable to reconnect due to a server error. It appears to be affecting users using Microsoft 365 calendars at this time Our team is actively investigating the root cause of the disconnections and we will provide updates as soon as we learn more information

After monitoring, we have confirmed all systems are connecting correctly and we’re seeing the product function as expected once more. If you believe you are still experiencing any connection issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

Our team has found the root cause and was able to implement a fix to ensure all systems are connecting correctly once more. We did confirm there will be no missed messages within the product, however live updates did not occur during this time. If users are not seeing any new messages, please ensure the user refreshes their browser or extension and all messages will appear. We will continue to monitor for any recurrences and if you believe you are still seeing an issue please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

We have received reports about a connection issue popup that is displaying on the Messaging tab within the Sense UI and the Sense Messaging Extension. Our team is actively investigating this and working to find the root cause and overall impact. We will be sure to provide updates as we discover new information on this

All Sense pages are loading correctly once more and we can confirm we are no longer seeing the error recur. If you believe you are still experiencing this issue please submit a ticket to https://support.sensehq.co/hc/en-us/requests/new for our support team to review, and we’ll provide further updates after review

We are continuing to monitor for any further issues.

We have updated the configurations affecting this and we are seeing pages loading successful once more. We will continue to monitor after this update to make sure this does not recur. If you believe you are still experiencing this issue please submit a ticket to https://support.sensehq.co/hc/en-us/requests/new for our support team to review, and we’ll provide further updates after review

Our team has identified a configuration update that is causing runtime errors intermittently for some users while navigating through the Sense Platform. We are currently working on updating this and having the product load pages correctly. We'll follow up as we receive more information here.

This incident has been resolved.

We have confirmed the bug fix that was deployed did take successfully and we're seeing the affected pages load correctly. We are still spot checking for the remaining data points missed to be updated, but will continue to handle these on a case by case basis. If you believe you are still experiencing this issue please submit a ticket to https://support.sensehq.co/hc/en-us/requests/new for our support team to review.

Bug fix has been deployed and we are seeing the analytics page load correctly across the platform. There are still minor data points that maybe missing, but our team has identified these and are handling them on a case by case basis. We will continue to monitor this and provide further updates as we receive them. If you believe you are still experiencing this issue please submit a ticket to https://support.sensehq.co/hc/en-us/requests/new for our support team to review

Fix is applied to load data points. There are few data points missing which the team has encountered, will continue working. Recommendation is to downgrade the outage to MINOR

We have tested the fix for the failing scenario, doing final smoke testing. Going to start the production deployment in some time.

Our team is actively working to have the bug fix deployed as soon as possible, and continuing to test. We will continue to work overnight and provide more updates in the morning or if they become available before then.

We are still processing the bug fix to deploy and correct the current issue we’re seeing when attempting to load analytic data on some pages. We will continue to test and confirm when ready to deploy We will provide updates as we receive more information on a resolution

Our team is continuing to work on the fix for this issue. Once we have this ready, we'll deploy it and monitor for results We'll continue to provide updates as we receive them

Our team has identified an ongoing issue with loading journey and touch point summary data on the analytics overview dashboard. We have identified the root cause and are working on deploying a fix. We will continue to provide updates as we find new information

We have confirmed that all writebacks are processing correctly for all ATS partners. Any missed writebacks during this time will be backfilled before the end of the day. If you believe you are still seeing missed writebacks before end of today, please submit a ticket at https://support.sensehq.co/hc/en-us/requests/new and our support team will review

Our team confirmed that the fix deployed for Sense API customers worked as expected and we’re seeing all missed writebacks backfill correctly for those that may have experienced this delay. We are seeing most already processed and the remaining in the queue to be completed today. We will continue to monitor the remaining progress to ensure there are no other misses and we’ll provide and findings we have. If you believe you are still seeing missed writebacks before end of today, please submit a ticket at https://support.sensehq.co/hc/en-us/requests/new and our support team will review

Our team discovered Sense API customer’s writebacks stopped sending to their ATSs as early as Tuesday morning at 12pm PST. We have identified the issue and have deployed a fix. Missing writebacks have begun processing and will catch up within the next few hours. We have confirmed there will be no data loss. We will monitor the backfill process and provide updates as systems are caught up.

We have confirmed that we are seeing expected traffic to all carriers once more. If you are still experiencing any deliverability issues please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new to investigate further

We have received confirmation from our vendor that they are seeing successful traffic to T-Mobile once more for affected numbers. Our team is continuing to monitor to ensure we are seeing the same delivery rates. If you believe you are still experiencing issues please submit a ticket with our support team at https://support.sensehq.co/hc/en-us/requests/new

We have received an update from one of our providers for SMS services that we are seeing an increased failure rate to T-Mobile recipients for some users. They have confirmed this error did not originate on their servers and are in contact with the downstream carriers to resolve this as soon as possible. We will continue to provide updates as we receive them.

This incident has been resolved.

Our team has identified the issue and deployed a fix for it. The issue has been resolve now. All the components are working fine now.

Our team is still working to determine the root cause for the analytics page to fail loading. We will be working continuously overnight to narrow down this issue, and provide any information we find

We are still troubleshooting what maybe causing the error when loading analytics for some users in Sense. Our team is actively working to find the root cause as soon as possible and we’ll continue to provide updates when received.

Our team is still investigating the root cause for the analytics not loading correctly for some users. We will continue to provide any updates as the information becomes available on this issue.

Our team has confirmed there is an ongoing issue causing our analytics to not load results intermittently for some users. Our team is actively investigating the root cause and we’ll provide updates as we receive them

The database maintenance has been completed, The entire system is now operational.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We have confirmed the fix implemented has been successful and we're seeing stable loading times across the board. If you believe you're still experiencing issues, please submit a ticket at https://support.sensehq.co/hc/en-us/requests/new and our Support team will investigate further"

Our team has implemented the fix and seeing our servers stabilize across the board. We'll continue to monitor as this takes place and provide updates as we receive them. If you believe you are still seeing issues, please submit a support ticket at https://support.sensehq.co/hc/en-us/requests/new

Our team is still working to deploy the fix after identifying the block. We'll continue to provide updates as we receive them

Our team has identified the block on the backend server and working to deploy a fix that will improve the loading time across the platform. We will provide an update once the fix has been deployed and we will monitor the status.

We are still investigating the root cause of the increased load times. We will continue to provide updates as we receive them

Our team is continuing to investigate the root cause for the slowness of the platform and working to correct the issue as soon as possible. We do not have an estimated correction time just yet, but will be sure to share this information once we're able to and will provide updates when possible"

Our team is still investigating the cause for the increased loading times and working to return to the service back to operational. We'll continue to provide updates as we receive them

Sense is experiencing a significant spike in loading times in the portal due to an issue with a backend server. We are actively investigating and will provide an update as soon as possible

We have confirmed the fix implemented has corrected the incoming message delay we were seeing with intermittent users, and our logs are showing the system has been stabilized. We can confirm all incoming messages were delivered and there was no loss of data. If you believe you are still experiencing this issue, or have any questions, please submit a ticket with our Support Team at https://support.sensehq.co/hc/en-us/requests/new

Our team has implemented a fix to decrease the load on the system and correct the speed of the incoming message display in Sense. We should start seeing messages receive at standard rate, and are monitoring our logs to ensure this does not recur. If you still see this recur, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and we'll investigate further

We have been notified of delayed messages being received by Sense users. We have found a strain on the system that is causing these messages to appear later than received. We can confirm all messages are being successfully received in Sense through our downstream carriers and will populate in the UI over time. Our team is working to reduce the strain on the system to have messages come through in real time once more. We'll continue to provide updates as we receive them.

We have received confirmation that this has been resolved and all services should be working as expected. If you're still experiencing issues, please submit a ticket with our support team for further investigation at https://support.sensehq.co/hc/en-us/requests/new

We have received reports that our downstream vendor for our Meetings Product is experiencing downgraded performance, causing longer loading times or errors when attempting to book meetings. They have identified the issue and put a fix in place to correct this issue and we're currently monitoring the results alongside. We'll provide an update once confirmed this service has been corrected

After monitoring the fix, we have confirmed that all users are still showing stable connections, and we are no longer receiving reports of error pages. We appreciate your patience as our team worked to correct this If you’re still facing issues, please submit a ticket to https://support.sensehq.co/hc/en-us/requests/new and our support team will investigate further.

We have confirmed that the fix has been implemented successfully, and we’re showing stable results for all users. We’ll continue to monitor to ensure this does not recur and check with users that have reported this issue If you’re still facing issues, please submit a ticket to https://support.sensehq.co/hc/en-us/requests/new and our support team will investigate further.

Our team has found the root cause of the issue, and has implemented a fix for pages to load correctly once more. We are monitoring the results and expect full functionality within the next hour for all users. We’ll follow up with more information as we continue to monitor the results

We have received reports of users intermittently receiving an error page when attempting to load and navigate Sense through web browsers. Our team is actively investigating the root cause and working to implement a solution as soon as possible We will follow up with more information in 2 hours if not sooner. We appreciate your patience as our team investigates

We have confirmed that we are no longer seeing instances of runtime errors occur, and all Sense functions should be operating as expected once more. If you are still experiencing a runtime error page, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

Our team has confirmed that the fix deployed has been successful and we’re no longer showing run time errors displaying in Sense. We’ll continue to monitor on our end to ensure the fix stays in place, and we’ll follow up with an update after confirming this. If you are still experiencing a runtime error page, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new

The fix implemented is currently in deployment for all users, and we are still monitoring it's process. We are seeing this error decrease for more users as the deployment continues. We will continue to monitor this deployment and provide updates as we receive more information

We have received reports of intermittent users receiving a Runtime Error page when navigating through Sense at random intervals. We believe we have identified the cause and have implemented a fix that is being deployed currently. We will monitor the status over the next hour as the fix takes place and provide an update once completed.

The fix implemented to correct the extended loading periods has been confirmed successful and we are showing expected behavior once more for the messaging page. If you believe you are still experiencing any issues around this, please submit a ticket to our support team: https://support.sensehq.co/hc/en-us

We have identified an issue causing some users to see extended loading times when using the Messaging Page in the Sense UI. A fix has been deployed to correct this and users should see expected loading times once more shortly. We'll continue to monitor to ensure this fix takes place for all users.

Our team has monitored the loading times for all pages and have confirmed functional across all products once more. If you believe you still are experiencing any issues, please submit a ticket to our support team to investigate further - https://support.sensehq.co/hc/en-us/requests/new

We are continuing to monitor for any further issues.

A fix has been deployed and we are seeing stability throughout all products. We'll continue to monitor to ensure this doesn't recur and provide updates on our findings. If you still are experiencing any issues, please submit a ticket to our support team through - https://support.sensehq.co/hc/en-us/requests/new

During our investigation we have found this increased loading time is affecting multiple Sense functions, including: Login, Messaging and Chatbot from the Sense platform. We have identified the root cause and are actively deploying remediation measures.

We have received reports of the Sense system taking long times to load some web pages and send messages, as well as templates not to populate for some users. Our team is actively investigating the root cause of these delays, and we will provide updates as we receive them

We have confirmed that AWS services have stabilized and we're seeing Sense services fully operational once more. If you believe you are still experiencing any issues still, please submit a ticket with our Support Team - https://support.sensehq.co/hc/en-us/requests/new

We are receiving reports that AWS services are stabilizing and we're seeing Sense services operational once more. We'll continue to monitor for any issues and provide updates as we receive them.

We are experiencing a degradation in service due to an outage with Amazon Web Services starting from 12pm CST. This may impact the following services for some users: - Some data sync events from Avionte may be delayed - Incoming SMS may be delayed for some customers - Analytics email delivery dashboards are delayed We will continue to monitor the status of the AWS downtime and provide updates on the status as we receive them