← Back to WorkflowSafe

Service & Support Policy

Last updated: September 6, 2026

This Service & Support Policy explains how WorkflowSafe handles customer support, automation incidents, monitoring, after-hours requests and service availability.

Specific customers may have different response commitments where a separate written proposal, service agreement, monitoring plan or support agreement applies.

1. Standard support

WorkflowSafe provides support for customers using its automation audit, troubleshooting, repair, monitoring and related services.

Support may include:

2. How to contact WorkflowSafe

The primary support contact is:

hello@workflowsafe.com

When contacting support, include enough non-sensitive information for us to identify the relevant system, request or incident.

Do not send passwords, API keys, private credentials or sensitive customer data through ordinary email.

3. Night and weekend response availability

WorkflowSafe may respond to requests during nights and weekends when team availability permits or when the customer's service arrangement includes after-hours support.

The statement “Night and weekend response available” means that WorkflowSafe may provide support outside normal daytime hours. It does not mean that a human team member is continuously available 24 hours a day, seven days a week.

Guaranteed after-hours response times must be expressly included in a written service agreement.

4. Automated monitoring

WorkflowSafe may provide automated monitoring for supported workflows and automation systems where monitoring is included in the customer's purchased service.

Automated monitoring may operate continuously, including outside normal working hours.

“24/7 automated monitoring” refers to automated systems or checks operating continuously. It does not mean 24/7 continuous human supervision or an immediate human response to every alert.

5. Monitoring limitations

Monitoring is designed to improve visibility into automation failures, but no monitoring system can guarantee detection of every possible problem.

Monitoring may be affected by:

6. Response priority

WorkflowSafe may prioritize requests based on their apparent business impact.

Examples of higher-priority issues may include:

Lower-impact configuration questions, improvements and non-urgent requests may be handled after active incidents.

7. No default response-time guarantee

Unless a specific response time is stated in a written agreement, WorkflowSafe does not guarantee that a request will receive a response within a particular number of minutes or hours.

Response time may depend on:

8. Emergency and priority arrangements

Customers who require guaranteed priority response, defined response targets or dedicated monitoring should arrange an appropriate WorkflowSafe support or monitoring agreement.

Any service-level commitment must be confirmed in writing.

9. What standard support does not automatically include

Unless specifically included in the purchased service, standard support does not automatically include:

10. Third-party systems

WorkflowSafe often supports automations involving third-party platforms such as GoHighLevel, Make, n8n, Zapier, Google Apps Script, CRMs, APIs and other services.

WorkflowSafe cannot guarantee the availability or performance of third-party systems and is not responsible for outages, account restrictions, API changes or other failures caused by those providers.

11. Customer cooperation

Timely support may depend on the customer providing accurate information, appropriate authorization and reasonable access to the affected systems.

Customers should avoid making unrelated changes to affected workflows while an incident is being investigated unless those changes are necessary to protect the business.

12. Secure access

When technical access is required, WorkflowSafe may arrange an appropriate access method separately.

Customers should provide the minimum permissions reasonably necessary and revoke temporary access when it is no longer required.

13. Scope changes

If investigation reveals that an issue requires work substantially outside the original service scope, WorkflowSafe may provide a separate recommendation, quote or service proposal before proceeding.

14. Service interruptions

WorkflowSafe may occasionally be unable to respond immediately because of technical outages, third-party failures, maintenance, security incidents or other circumstances outside reasonable control.

We will make reasonable efforts to restore normal service and communication when such interruptions occur.

15. Security or dangerous conditions

WorkflowSafe may pause work where continuing could create unreasonable security, privacy, financial or operational risk.

We may require additional authorization, backups, testing or customer approval before making significant changes to production systems.

16. Changes to this policy

WorkflowSafe may update this Service & Support Policy as services, monitoring capabilities and operational practices change.

The current version will be published on this page with an updated revision date.

17. Contact

For support or questions about this policy, contact:

WorkflowSafe
Email: hello@workflowsafe.com
Website: workflowsafe.com