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

The fix for the issue affecting emails with attachments sent from O365 has been deployed. Please reach out to our Customer Support team if you require further assistance; we will be happy to help.

A fix for this issue has been implemented. We are monitoring the results.

We are aware of an issue preventing Playbooks customers from manually sending emails that contain attachments when using Office365 as their email provider. We have identified the root cause of the problem and will be providing a fix for this.

The issue with ad-hoc email sending via Office365 has been confirmed as resolved. In case further issues are experienced, please reach out to the support team.

We have implemented a fix for the issue and are now monitoring the results. We sincerely apologize for the inconvenience.

We are aware of an issue preventing Playbooks customers from manually sending emails when using Office365 as their email provider. We have identified the root cause of the problem and will be deploying a fix before the end of the next week.

We have received confirmation that this issue has been successfully addressed, and it should no longer affect any users. As always, please feel free to raise a ticket with Customer Support if you are experiencing any unexpected behavior.

We are continuing to monitor for any further issues.

The intermittent log in issues appear to be fixed and we could confirm that customers didn't experience any failure to log in in the last 45 minutes. We will keep monitoring the situation and investigating the root cause until we are able to conclude that the incident is fully resolved. Please accept our apologies for the inconvenience during this short outage.

We are investigating an intermittent issue preventing users from login into the Playbooks app (Chrome plugin) and the Playbooks Manager Portal (https://playbooksmanager.insidesales.com). Users receive the following error: "Unable to log in: An error occurred, please try again.". We will provide further updates shortly and thank you for your patience and understanding.

This incident has been resolved.

After monitoring our systems, we are now confident to say that this issue is resolved. Thank you for your patience!

A fix for the issue was implemented and at this moment, we can see that the robots are running as intended for the affected tenants. The issue is under monitoring for the next hours. Please contact support if you encounter any further trouble. We apologize for any inconvenience or difficulty you may have experienced as a result of this issue.

We have identified an issue with enrollment robots that have been ongoing for a couple of hours. This issue is affecting the US-east zone and our team is working on a fix.

As of 18:51 UTC, we implemented a potential solution for the issue related to the Inbound and outbound calls. We have implemented a fix for an issue that was affecting the backend and thus, the ability to place and receive calls. At this moment, we can no longer reproduce the issue identified. We apologize for any inconvenience or difficulty you may have experienced as a result of this issue.

We are aware of an issue affecting some customers trying to place outbound calls. We also have reports of issues with inbound calls for some other customers. Our team is investigating the issue and will update this page as soon as we have more precisions on the scope.

Our infrastructure team has completed the investigation and updated the necessary values for the correct operation of the Teams Page.

At around 17:00 UTC on 31/March/2023 - It has come to our attention that a functionality of the Playbooks Teams Page might not be working as expected, as a result, we have engaged our infrastructure and development teams to investigate further.

All issues related to the synchronization of activities from the CRM are confirmed to be resolved. The root cause has been identified and a permanent fix is currently being implemented to prevent this from happening again. Please accept our apologies for any inconvenience or difficulty you may have experienced.

We are continuing to monitor for any further issues.

As of 16:10 UTC, we implemented a potential solution for the issue related to the synchronization of activities from the CRM. We have applied the fix to the affected components, and we can no longer reproduce the issue identified. We apologize for any inconvenience or difficulty you may have experienced as a result of this issue.

We are currently investigating the issue relating to the synchronization of activities from the CRM, and are working to identify the source of the issue reported. We highly appreciate your patience, and will provide further updates as they become available.

This incident has been resolved.

Our Infrastructure team has implemented a fix for the outbound calling issues reported. We are actively monitoring the situation, but we can no longer internally reproduce the issue identified.

We have identified an issue related to outbound calls, with certain North America customers reporting an “unable to connect” message. We are actively investigating the issue and will provide further updates as they become available.

We have rectified the issue with Microsoft and authentication between Salesforce and InsideSales has been restored. Users affected may need to reload their Playbooks UI page. Should you experience any other problem, please contact support in the normal way.

We continue to work with Microsoft to re-enable the interface to Salesforce and will continue to post updates here

We have an ongoing issue with Salesforce authentication not working, which impacts all customers using the Salesforce authentication. We continue working directly with Microsoft to restore the Salesforce authentication.

We have identified the root cause behind the Azure subscription issue that prevents Salesforce authentication from working. This issue impacts all customers using this Salesforce authentication. We are working directly with Microsoft to restore this authentication.

As of 07:00 UTC, we identified an issue with the Azure subscription that prevents Salesforce authentication from working. This issue impacts all customers using Salesforce authentication. We are investigating the issue and will provide further updates as they become available.

Our Infrastructures Team has verified that the issue has now been resolved. We will continue working to prevent the issue from reoccurring in the future. We once again thank you for your patience and apologize for the inconvenience.

After restarting the affected services, the product is working as expected. We will continue monitoring the behavior of the app to ensure the outage does not reoccur and address the underlying causes. Thank you for your continued patience.

We have been notified of an outage affecting some customers in the North America Region. We are working to diagnose the issue and will provide further updates as they become available. We apologize for any impact caused to your operations and thank you for your continued patience.

After monitoring our systems, we are now confident to say that this incident is resolved! Thank you for your patience!

A fix has been implemented and we are monitoring the results.

We are aware of an issue affecting certain users where it is not possible to advance between steps in Plays within the software. This is currently identified as only affecting Plays with hidden steps. We are working on identifying a solution and will provide you with further updates as they become available.

Dear Customer, After monitoring our systems, we are now confident to say that this incident is resolved! Thank you for your patience!

A permanent fix has been implemented for the present issue through an updated version of the Chrome extension and we're currently monitoring its behavior. We will post an update through this forum once the issue is confirmed to be resolved.

The implementation of a permanent fix for the present issue (being experienced by some North American customers) is in progress.  Some users may experience slowness as this is rolled out.  We will continue to post updates through this forum.

We are progressing on the implementation of a permanent fix for the present issue being experienced by some North American customers. Some users may experience slowness as this is rolled out. We will continue to post updates through this forum.

We have identified a workaround for the issue being experienced by some North American clients and are in the process of implementing it. Some users may experience slowness as this is rolled out. We will continue to post updates through this forum.

We have identified the cause of the issue. We are testing a resolution and will continue to post updates here.

We continue to investigate this issue and have identified some contributory elements. We will post further updates here as we mitigate the problems.

we are aware that some clients in North America may be experiencing issues with inbound and outbound calling. We are investigating the problem and will continue to post updates through this Status Page.

Dear Customer, After monitoring our systems, we are now confident to say that this incident is resolved! Thank you for your patience!

All users are advised to upgrade to the latest version (1.3071.14) of the extension following the article below: https://support.playbooks.aurea.com/hc/en-us/articles/7850579125522-How-to-verify-the-Playbooks-extension-is-updated As users move to the new version, we will see overall improved performance. Should you experience any further issues, please use the support portal to log a support ticket.

We have identified the issue to be affecting a limited number of users that are using the 1.3071.13 version of the Playbook Chrome extension. In order to resolve the issue, users are advised to upgrade to the latest version (1.3071.14) of the extension following the article below: https://support.playbooks.aurea.com/hc/en-us/articles/7850579125522-How-to-verify-the-Playbooks-extension-is-updated Should you experience any further issues, please use the support portal to log a support ticket.

We are aware that a limited number of users in North America may be experiencing issues accessing Playbooks. We have identified the problem and are implementing a resolution.

Our team has confirmed that the server had a temporary issue and is now working as expected. We've also been able to make calls and haven't observed any other issues so far. Please contact the Playbooks Support Team if you are still facing any issues.

Service returned to normal and we are monitoring the issue.

We are continuing to investigate this issue.

A small number of clients have reported a "Failed to start call" banner appearing when attempting to place an outbound call. We are investigating this issue and will report updates through the StatusPage

Our team has confirmed that the process of disposition calls is now working as intended. No further issues have been observed or reported. Please contact Playbooks Support Team if any other issue is identified.

As of 22:30 UTC, we implemented a solution for the issue related to call dispositions. Errors when saving the disposition will not be experienced, except on rare occasions when dispositioning ad-hoc calls. Please validate the fix on your end and notify us if you experience any further issues. We apologize for any inconvenience or difficulty you may have experienced as a result of this issue.

We are investigating reports that some users may not be able to disposition calls. At the moment, the Infrastructure Team is able to unblock any users experiencing the issue while it is investigated. If you are experiencing this issue, please reach out to Playbooks Support and provide the list of users experiencing the issue. We will update this page with additional information as it becomes available.

As of August 19th 20:15 UTC, we implemented a solution for the issue related to call synchronization. Call details are now appearing within the backend database. Please validate the fix on your end and notify us if you experience any further trouble. We apologize for any inconvenience or difficulty you may have experienced as a result of this issue.

As of 20:15 UTC, we implemented a solution for the issue related to call synchronization. Call details are now appearing within the backend database. Please validate the fix on your end and notify us if you experience any further trouble. We apologize for any inconvenience or difficulty you may have experienced as a result of this issue.

We are currently investigating reports of call synchronization and are working to identify the source of the issue reported. We will provide further updates as they become available.

Our team confirmed that the server had a temporary problem and is now working as intended. We were also able to make calls and we have not been able to detect any further issues at this time. Please contact Playbooks Support Team if any other issue is identified.

We are investigating reports that some users may not be able to make calls, log into Salesforce or save notes. We will update this page with additional information as it becomes available.

A Database issue impacted some Playbooks Services between 12pm and 12:20pm UTC. All services are back to normal now and the issue has been resolved. We thank you for your patience while we were solving the issue.

Our team confirmed that the server that places calls had a temporary problem, and is now working as intended. We also received positive results for inbound calls being performed effectively and we have not been able to detect any further issues at this time.

Our team has received positive results for inbound calls being performed effectively and we have not been able to detect any further issues at this time. We will continue to monitor the services to ensure all is working as expected.

We are aware that some users in North America may be experiencing issues with agents not being able to receive inbound calls. We are investigating the cause and will post further updates through this forum.

We have identified the issue that users on the CA1 pods were unable to connect calls as a result of a misconfiguration of DNS records, and are happy to report that the incident has been fully resolved, all systems are working as expected.

We are investigating reports that users on the CA1 pode are unable to connect calls. We will update this page as soon as further information is available.

Our team was able to track down the issue to a release that was published before scheduled. After rolling back the release we are able to see that all Playbooks services are back online. We will continue monitoring the system over the next few hours to ensure the issues have been completely resolved. All services are back online. Please confirm and let us know if you have any further issues. We apologize for the inconveniences.

Our team was able to track down the issue to a release that was published before scheduled. After rolling back the release we are able to see that all Playbooks services are back online. We will continue monitoring the system over the next few hours to ensure the issues have been completely resolved. All services are back online. Please confirm and let us know if you have any further issues. We apologize for the inconveniences.

Our team continues investigating the current Outage. We have narrowed down the possible causes and expect to find the root cause soon. We will provide further updates as soon as we get more information.

At around 19:46 UTC on 4/26/2022 we have received reports of an ongoing issue that is causing the integration user to be disconnected. Our team is actively investigating the root cause and will provide further updates as we get more information.

The incident has been confirmed as resolved. Thanks for your patience.

A fix has been implemented and you should be facing no more issues with your Import Record feature. Please clear your browser cache before attempting a new Record Import. We thank you for your patience while we were resolving the issue

We are aware of an ongoing incident on Playbooks Import Record feature. Our team is investigating the issue.

At this time we have identified the root cause of and fixed it. Calls are going through properly and we will keep monitoring the service for any residual issues. If you experience further issues please report them as usual through our normal support channel.

At this time we have identified the root cause of the interruption and taken steps to mitigate it with our telephony providers. Calls are going through properly and we are monitoring the situation for any residual issues.

At this time we have identified the reason that calls take long and sometimes fail to connect. We are actively working with our telephony providers to mitigate the symptoms and further, to eliminate the root cause of the problem.

We are investigating reports that calls are being dropped or disconnected. We will update this page as soon as further information is available.

We have monitored the performance for 2 hours, and everything is working as expected. We are now closing the incident. If you experience any other issues, please create a Support ticket with the details.

We have reviewed the system and the performance is back to normal. We will monitor for the next 2 hours. If you are still experiencing issues please create a Support ticket

We are experiencing performance degradation issues in the system. We are investigating what is affecting the issue.

All systems are operational, the incident has been resolved. Should you experience ongoing problems or issues of a different nature then please don't hesitate to log a ticket in the normal way.

We have implemented the fix and are monitoring the performance of Playbooks.

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

We are aware that some clients may be experiencing slow connection issues with Playbooks. We have identified the issue and are working on implementing a fix.

This incident has been resolved - Should you experience ongoing problems or issues of a different nature then please don't hesitate to log a ticket in the normal way.

We are aware of clients experiencing a number of issues when using Playbooks. We have found the root cause and fixed it, monitoring the situation

The calls issue is now resolved. You should be able to call without any problems. Please let us know if you are still experiencing issues.

The system performance is improving, you should be able to make calls now. We are still investigating the root cause, please let us know if you are experiencing issues.

At this time we identified the cause of the service disruptions that customers in North America experienced and implemented a fix. We are monitoring it for residual or further issues.

At this time some customers in North America experience a service disruption. We are investigating the cause and aim to fix it asap. Thank you.

Customers on pods US2 and US3 were affected by slow and, at times, stalled service. This problem has been diagnosed and mitigated. All services are now working as expected. If you experience any other service issues, please report these to our support team as usual. We appreciate your patience while we worked to resolve this issue.

We are investigating an issue some customers are experiencing while placing outbound calls. We will add further updates as more details become available.

This issue has been resolved.

A fix has been implemented to resolve all call issues that some users may have experienced. We continue to monitor performance and will update this forum should we become aware of any degradation in service. Should you experience issues outside of this scope then please report such problems via a support ticket as per the normal procedure.

At this time we have identified additional causes of the problem and are working to implement a fix for it. We will update this page and any active support tickets when this work is complete and keep monitoring the situation thereafter. Thank you again for your patience.

A fix has been implemented to resolve the inbound call issue that some users may have experienced. We continue to monitor performance and will update this forum should we become aware of any degradation in service. Should you experience issues outside of this scope then please raise a problem ticket in the normal way.

We are aware that some clients based within the US East 1a region may be experiencing issues with inbound calls. We are currently investigating this and will post further updates via this forum.

We have been monitoring the system status for more than 6 hours and it's stable. Some customers have confirmed the resolution too. We are now closing this incident.

The issue have been identified and fixed the root cause of the issue. Playbooks™ is now fully operational. We will continue monitoring the situation and if you experience any new problems, please raise a ticket in the normal way through the portal.

We are currently investigating an issue affecting Inside Sales Playbooks customers in the US region related to calls not connecting or timing out. We will provide updates as they become available.

At this time we have identified and fixed the root cause of the issue. Playbooks™ is now fully operational.

we are in the process of implementing a fix. The issue is related to the access user configuration of the impacted orgs.

We found the potential cause for the connectivity issue, we are working on a resolution.

We are aware of clients experiencing a number of issues when using Playbooks - We are investigating this issue and will continue to post updates.

This incident has been resolved.

AWS have resolved the majority of their issues and we are no longer seeing any impact on InsideSales clients, intermittent or otherwise. We will continue monitoring the situation and if you experience any new problems, please raise these in the normal way through the portal.

AWS continue to work on resolving their issues as tracked here: https://status.aws.amazon.com/ These continue to have an intermittent effect on InsideSales/Playbooks services.

Amazon Web Services are continuing to work on resolving their issues that are affecting some of our InsideSales clients. Progress can be tracked independently of these status page updates, here: https://status.aws.amazon.com/

We continue to work with AWS to mitigate the impact of the issues and fix them. We will post further updates as we progress towards resolution.

The root cause of the issue has been identified and we are working closely with Amazon Web Services to implement a permanent fix.

AWS monitoring on their availability can be tracked here: https://status.aws.amazon.com/

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

We are aware of an issue being experienced by Amazon Web Services AWS) that may affect InsideSales clients intermittently. We are working with AWS to mitigate these issues.

This incident has been resolved.

As you may have seen from the AWS status page, power has been restored to the affected sub-zone within the region and normal service is resuming. We will continue to monitor the situation and, as mentioned, the incident can be directly tracked here: https://status.aws.amazon.com/

We are aware of an issue with Amazon Web Services affecting their US East 1a Region. This may have intermittent effects on Playbooks clients but we are working to mitigate any negative impact. The recovery of AWS can be tracked here: https://status.aws.amazon.com/ (North America). We will continue to post updates here.

This incident has been resolved - Should you experience ongoing problems or issues of a different nature then please don't hesitate to log a ticket in the normal way.

A fix has been implemented and we are monitoring the service performance. Where clients have been experiencing synchronization issues, these have now caught up. If you experience additional issues then please raise this in the normal way.

We are continuing to work on this issue which is focused on the US3 region. However, there may be knock on effects for calls beyond this area which we are continuing to mitigate.

We are aware of issues that have resurfaced for clients using US3 whereby they are unable to make outbound calls. We are actively investigating this issue and will continue to update you.

All issues relating to inbound and outbound calling, synchronization, monitoring and call recording have been resolved and normal service has been resumed. We will continue to monitor the resolution implemented and if you experience other issues, please report these in the normal way.

Issues with outbound calls for all clients are now resolved. Issues with inbound calls for US2 and EU1 are resolved and we are working on the remaining clusters.

Some clients on the US East 1a region continue to experience issues with both inbound and outbound calls - We have identified the issue and are working on deploying a fix, for those affected clients. Performance for EU clients is resolved and synchronization should be complete in the next hour if not already.

We are continuing to work on a resolution on outbound calls for clients using US East 1a and for inbound calls for some clients in the EU. We will continue to post updates here.

CRM synchronization has been resolved for all regions but it may take up to 4 hours for all sync tasks to complete across all components. Outbound calls for US1, US2, US3, and EU1 have been resolved, however, we are still working on a resolution for USEast 1a. We continue to work on resolving an issue affecting some clients' inbound calls in the EU.

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

We have resolved issues in the US1, US3 and EU1 regions, however, outbound calling in US2 and US East 1a is still being worked on by the teams.

We are aware that some EU users are still experiencing issues with inbound calls and synchronizing call activity. We are working on a fix for this issue while continuing to enable the US region.

We continue to resolve the issue region by region. Both the EU and Asia Pacific regions are resolved and we are now working on the US.

We have identified the issue and are implementing the fix region by region. We will continue to keep you informed of updates.

We are continuing to investigate this issue which is also affecting inbound calls. We will post additional updates as we remediate the problem.

We are aware of clients experiencing a number of issues when using Playbooks - We are investigating this issue and will continue to post updates.

This incident has been resolved.

A fix has been implemented for this issue and we are monitoring the performance of the system.

We have implemented an automation to prevent long-running queries from blocking normal activities and are monitoring the system performance. We are aware that some users may still be experiencing a degree of latency on calls and this is part of our current focus for remediation.

We have identified the issue and are implementing further mitigation and fix strategies.

We are aware of slow-running queries on the database affecting the US Cluster, our team is developing a solution to deploy.

Our team identified a problem with calls and have implemented a fix. We are currently monitoring the status of the service and will continue to update you through this medium.

A fix was deployed during the maintenance window and we are now monitoring the performance of Playbooks. We will continue to update you through this medium.

We have identified and implemented a temporary fix for this issue. We will be deploying a permanent fix between 0300-0400 UTC on December 2nd 2021 and will post further updates through this forum after this deployment.

We continue to investigate the issue and have identified the particular problem.

We are aware of ongoing issues that are affected both inbound and outbound calls made through Playbooks. We are investigating the specific cause and will continue to update you through this medium.

This incident has been resolved - Should you experience any other issues, please report the issue in the normal way.

We have identified a fix for the issue and are in the process of implementing it. We will continue to post updates here.

We are currently investigating intermittent connectivity issues for some clients in North America. We will continue to post updates through this forum.