# Support triage flow

Create an editable Visio support flowchart with an investigation loop and a requester-acceptance decision. Download the diagram, previews and C# source.

Visio · C# walkthrough

Show how a request returns to investigation when the outcome is not accepted.

[Build this report](#example-code)[Download VSDX](/downloads/showcase/workflows/visio-triage-flow/example.vsdx)

**Start with**

Support states and acceptance decision

**Generate**

VSDX

[!\[Generated Visio example: Support triage flow\](/downloads/showcase/workflows/visio-triage-flow/preview.webp)](/downloads/showcase/workflows/visio-triage-flow/preview.png)

Generated diagram · Generated by the example below

## How it works

1. ### Order the supported path
  
  Start at intake and finish with a recorded outcome.
2. ### Make the loop visible
  
  Route a No decision back to investigation.
3. ### Fit the page
  
  Keep branch routing and content within the exported diagram.

## The C# source

The example below shows the document API and layout used for this report. Follow the Visio guide for package setup in your own project.

```csharp
using OfficeIMO.Visio;
using OfficeIMO.Visio.Diagrams;

namespace OfficeIMO.Examples.Showcase.Workflows {
    /// <summary>Maps a support request from intake through verification, including the investigation loop.</summary>
    internal static class TriageFlow {
        internal static void Create(string folder) {
            var document = VisioDocument.Create(Path.Combine(folder, "example.vsdx"))
                .Flowchart("Support triage", flow => flow
                    .Theme(VisioStyleTheme.Process()).RouteBranches(laneSpacing: 0.6)
                    .Start("received", "Request received")
                    .Step("classify", "Confirm scope and impact")
                    .Step("investigate", "Assign owner and investigate")
                    .Step("verify", "Verify with requester")
                    .Decision("resolved", "Outcome accepted?")
                    .End("closed", "Record result and close")
                    .Branch("resolved", "No / investigate further", "investigate"));
            document.Pages[0].FitToContent(0.7, 0.6);
            document.Save();
        }
    }
}
```

[Open the C# source file](/downloads/showcase/workflows/visio-triage-flow/TriageFlow.cs.txt)

## API used in this example

- [`VisioDocument`](/api/visio/officeimo-visio-visiodocument/)
- [`VisioStyleTheme`](/api/visio/officeimo-visio-visiostyletheme/)

## Use this in your project

Adapt the states and escalation rules to the service; the diagram does not execute tickets or changes.

The [Visio guide](/docs/visio/) explains package setup and related document APIs.

## Documents and scope

### What the preview shows

The C# source generates the downloadable file. The runner validates the diagram and exports native PNG and SVG previews.

### What to keep in mind

Adapt the states and escalation rules to the service; the diagram does not execute tickets or changes.

[Visio API reference](/api/visio/) · [Artifact hashes and provenance](/downloads/showcase/manifest.json)

## Continue with another example

- [Visio**Purchase approval swimlane**](/showcase/visio-approval-swimlane/)
- [Visio**Organisation chart with team vacancies**](/showcase/visio-team-organisation/)

<!-- PowerForge markdown artifact sha256:F112D8251FF6D8F1C6857FAD9295DB86E4230C77681872D1423EFF76149351B9 -->
