Customer Support Request Form Workflow

How is this workflow audited?

Every status change, priority determination, assignment, and communication sent within the workflow is recorded as part of the request record inside assess.one. This creates a timestamped history that teams can review for quality assurance, compliance reporting, or internal audit purposes. Because the workflow runs natively in the platform, there is no need to reconcile logs across separate systems.

Who has access to support request records and priority decisions?

Access is controlled through role-based permissions configured directly in assess.one, so only designated support owners, team leads, or administrators can view or act on specific requests. Organisations can restrict who is able to manually confirm priority or amend resolution notes, supporting separation of duties. Permission settings can be adjusted at any time without disrupting active requests.

How does this integrate with existing email and SMS systems?

Email and SMS notifications, such as confirmation and closure messages, are configured within assess.one's built-in integration settings rather than through external development work. Teams connect their preferred email or messaging channel once, and the workflow uses that connection for all subsequent confirmations, closures, and feedback requests. This keeps communication consistent without requiring IT involvement for each change.

How long does implementation take?

This template is ready to use and can be published in minutes, after which the support team can begin running live requests immediately. There is no lengthy implementation project or external setup required. Any refinements to steps, roles, or notifications can be made directly in the platform as the process runs.

What happens when priority confidence is low?

When the AI-determined priority falls below a set confidence threshold, the workflow routes the request for manual confirmation rather than proceeding automatically. A designated reviewer confirms or adjusts the priority, and that decision is saved to the record alongside the original AI suggestion. This checkpoint helps maintain accuracy for edge cases while still allowing high-confidence requests to move through faster.

Can the workflow be customised for different support teams or SLAs?

Yes, steps, assignment rules, notification templates, and approval logic can all be adjusted directly within assess.one to reflect different SLAs, escalation paths, or team structures. Organisations with multiple support queues can adapt the same base template rather than building separate processes from scratch. Changes take effect immediately without requiring redeployment.

Who should have access to this workflow within a larger organisation?

Typically, front-line support agents, team leads responsible for assignment and priority confirmation, and administrators managing notification and integration settings should have access. Larger organisations may also grant read-only access to quality or compliance reviewers for oversight purposes. Access levels are configured per role inside assess.one to match internal governance requirements.

What compliance or approval considerations apply to closure and feedback steps?

Closure requires resolution notes to be saved before the closure confirmation email is triggered, supporting a documented rationale for how each request was resolved. The feedback request step runs on a fixed one-day delay after closure and can be disabled or reconfigured for organisations with specific customer communication policies. Both steps are logged within the request record for later review.

How does the workflow handle requests without a mobile number?

If no mobile number is provided, the workflow branches to skip the SMS confirmation step and proceeds directly with the email confirmation and subsequent triage steps. This conditional logic is built into the workflow and requires no manual intervention. Support teams can adjust this branching behaviour within assess.one if SMS requirements change.