US Data Store resources

Route service requests with useful context.

Define the inquiry type, receiving team and fallback before handing a B2B service request to another department.

1. Try a planning tool

Map service-request routing →

Use your own operating assumptions. A planning result is a discussion aid, not a live configuration or a performance guarantee.

3. Work through an example

Read the full worked example: sample intake, decisions and exception paths →

Fictional planning example—not a customer result. An existing customer calls about a billing question and a separate service issue.

Capture both requests and the permitted account reference. Identify the owner for each, avoid disclosing protected account information without the approved checks, and define who coordinates follow-up if a transfer is unavailable.

Write down the information to collect, the next-step owner and the unavailable-recipient fallback. Bring those choices to a setup discussion.

Bring your next-step plan.

Tell us which scenario you worked through, the questions you need answered and who should receive the handoff.

Discuss your workflow →