What inputs does the Support Router workflow use?

The workflow uses Message, Order Id, Support Context. Required fields and their expected formats are listed on this page.

What resources are included in the Support Router blueprint?

The blueprint contains 4 AI agents, 0 functions, 1 MCP server. Its workflow pattern is Handoff.

Can I customize the Support Router blueprint in GraphN?

Yes. Open the blueprint in GraphN to customize its inputs, models, resources, and workflow behavior before deployment.

All blueprints Support AI workflow blueprint

AI customer support routing workflow blueprint

Classify each support request and route it to the right specialist for a ready-to-send reply

See where this blueprint fits in the production workflow lifecycle

Handoff

Support

Routing

E-Commerce

Multi Step

Use this blueprint

Pattern

Handoff

Agents

4

Functions

0

MCP servers

1

What the Support Router blueprint does

Suggested starting request
Describe the support issue; optionally include an order ID and trusted support context.

Inputs for the Support Router workflow

Provide the following information when starting this workflow. Required inputs are validated before the first workflow stage runs.

Message
Required
Customer message
Type: String
Order Id
Optional
Order ID if known
Type: String
Support Context
Optional
Optional order, tracking, return-policy, or product data supplied by the caller
Type: String

Input template

This request shape is generated from the blueprint's input schema. Angle-bracket values are placeholders; defaults and examples appear only when the source blueprint defines them.

{
  "message": "<required string>",
  "order_id": "<optional string>",
  "support_context": "<optional string>"
}

How the Support Router AI workflow works

This support blueprint uses a handoff workflow with 4 agents, 0 functions, and 1 MCP server. Open it in GraphN to customize the resources, inputs, and workflow behavior for your use case.

Router
Handoff Router

Blueprint resources and prerequisites

These are the actual agents, functions, and MCP servers declared by the blueprint. If an MCP server connects to an external system, configure the required connection and credentials in your GraphN workspace before running the workflow.

AI agent

Triage Agent

AI agent

Order Specialist

AI agent

Returns Specialist

AI agent

Product Advisor

MCP server

Store API

Tools: Lookup Order, Get Tracking, Check Return Eligibility, Search Products

Workflow output contract

The completed workflow makes the following output available to downstream steps, applications, or API clients:

Result

Frequently asked questions

What does the Support Router blueprint do?: Classify each support request and route it to the right specialist for a ready-to-send reply
What inputs does the Support Router workflow use?: The workflow uses Message, Order Id, Support Context. Required fields and their expected formats are listed on this page.
What resources are included in the Support Router blueprint?: The blueprint contains 4 AI agents, 0 functions, 1 MCP server. Its workflow pattern is Handoff.
Can I customize the Support Router blueprint in GraphN?: Yes. Open the blueprint in GraphN to customize its inputs, models, resources, and workflow behavior before deployment.

Related Support blueprints

View all customer support workflows

Support Knowledge Bot

Search across help docs and past tickets to surface answers for support agents

Escalation Detector

Monitor conversations for frustration signals and auto-escalate to a human manager

Multi-Language Support Router

Detect the customer's language, translate, route to a specialist, and translate the response back

Ticket Tagger & Prioritizer

Automatically classify, tag, and prioritize incoming support tickets