Policies used for retrieval and citations

FlowZint offers workflow automation subscriptions for growing teams. Standard plans include workspace setup, dashboard access, ticket workflow rules, and basic support. Enterprise onboarding can include custom integrations, security review, admin training, and priority escalation.

Refund requests should be checked against the customer's billing cycle, usage state, and original contract terms. If the customer reports duplicate billing or service outage impact, mark the ticket as high priority and send it to finance operations for review.

New customers should receive a workspace invite, admin configuration checklist, data import guide, and a 30-minute onboarding call. If an onboarding issue blocks first workflow activation, route it to customer success within one business day.

Product support tickets related to failed automations, dashboard sync delays, or integration errors should include the workspace ID, reproduction steps, error timestamp, and affected workflow. Integration outages and repeated automation failures should be escalated to engineering.

High priority support issues should receive a first response within four business hours. Escalated integration failures should be assigned to a support lead and reviewed by engineering when multiple customers or repeated workflow failures are involved.

Customer complaints involving repeated delays, billing disputes, or loss of trust should be acknowledged clearly, assigned an owner, and tracked until closure. High-risk customers should be flagged when churn risk or executive escalation is mentioned.

Sales inquiries should capture company size, current support volume, workflow tools in use, integration requirements, and expected launch timeline. Qualified enterprise inquiries should be routed to sales with context from the original message.