The same message journey as the map, written out as every single action, one per row: from the chat window opening, through sorting, the queue, the loop, the reply, to what happens out of sight after the turn and before the next release. 78 steps in 14 parts. This table is read live from the Series, so it always matches.
Goes in A customer opening the chat window
What happens 78 small actions, each saying where it runs and whether it is built
Comes out A reply, a record, and a better next release
JOURNEY 1 · ARRIVE AND SORT Before the customer typ… steps 1–5 The customer acts steps 6–9 Arriving at our server steps 10–15 Sorting the message steps 16–20 Fixed flow (no agent) steps 21–23 JOURNEY 2 · QUEUE AND THE LOOP Queueing the work steps 24–27 Before the loop steps 28–32 Inside the loop: the mo… steps 33–46 Inside the loop: a tool steps 47–53 Inside the loop: when t… steps 54–56 JOURNEY 3 · REPLY, AND AFTER After the loop: the reply steps 57–62 When a person is needed steps 63–66 After the turn (out of sight) steps 67–74 Before the next release steps 75–78
Each part has its own table below, with a link to the page that draws it.
Status says whether each step is built in the claims assistant today, is an Azure feature we configure, or is still to build. The design pages and real flows show what actually ran.
Journey 1 · Arrive and sort Before the customer types · drawn on One block # Step Runs in What happens, in plain English Status 1 Chat window opens Browser The claims app shows the chat window inside the page the customer is already signed in to. Proposed 2 Who they are Browser The window already knows who the customer is from the portal sign-in. Proposed 3 Past messages Browser → API The window asks for this customer's open conversation and shows the earlier messages. Proposed 4 Status card API If a claim is open, the window shows its current status before the customer asks. Proposed 5 Live connection Browser ↔ Web PubSub or Chatwoot The window opens a live connection, so a reply can arrive from any server. Proposed
The customer acts · drawn on Front door # Step Runs in What happens, in plain English Status 6 Types or taps Browser The customer types a message, or taps a button such as "Check my claim". 7 Message ID Browser The window gives the message a unique ID and keeps it if it has to resend. Built 8 Send Browser → Front Door The window sends the message, the sign-in token and the ID. Built 9 Waiting Browser The window shows the message as sent and a "thinking" indicator. Proposed
Arriving at our server · drawn on Front door # Step Runs in What happens, in plain English Status 10 Front Door Azure Front Door Front Door filters attacks and passes the request to any healthy server. No sticky sessions. Azure 11 Received API server (Python) Our Python server receives the message. Built 12 Check identity API server It checks the sign-in token and works out who the customer is and what they may do. Built 13 Load conversation API → PostgreSQL It loads the customer's latest conversation. Built 14 Duplicate check API → PostgreSQL It looks up the message ID. A repeat gets the earlier answer instead of a second run. Built 15 Shared record API → Chatwoot It adds the message to the customer's conversation in the desk, so staff can see it. Built (Chatwoot adapter)
Sorting the message · drawn on Router # Step Runs in What happens, in plain English Status 16 Rules first API server Buttons, the conversation's state (a form in progress) and simple patterns decide the route when they can. Proposed 17 Local classifier API server Otherwise a small classifier inside our server labels the message, with a confidence score. Proposed 18 Small model API → gateway → Foundry If the classifier isn't sure, a small model picks the label. Proposed 19 Several asks API server A message with several asks is split into parts, each routed on its own. Proposed 20 Route chosen API server The message goes to a fixed flow, policy search, the agent, a person, or a polite refusal. Built (routes)
Fixed flow (no agent) · drawn on The direct path # Step Runs in What happens, in plain English Status 21 Look up API → MCP → claims system The flow fetches the facts it needs from the claims system. Built 22 Fill the template API server It fills an approved reply template. No model writes the answer. Built 23 Go to the reply checks API server The reply joins the same checks as every other reply (stage after the loop). Built
Journey 2 · Queue and the loop # Step Runs in What happens, in plain English Status 24 Into the queue API → Service Bus Agent and search turns go into a queue with a priority and a deadline. To build 25 Picked up Worker Any free worker takes the turn and holds a lease, so no other worker runs it. To build 26 One at a time Worker → PostgreSQL Only one turn per conversation runs at once; a second message waits its turn. To build 27 Too late? Worker A turn past its deadline isn't started; the customer is told when to expect a reply. To build
# Step Runs in What happens, in plain English Status 28 Start the run Worker The agent starts a run with limits on steps, time and cost. Built 29 Allowed tools Worker → MCP It lists only the tools this customer may use. Built 30 Build what the model sees Worker It puts together the instructions, tools, history and new message, always in the same order. Built 31 Mark untrusted text Worker Anything that came from outside, such as document text, is marked as data, not instructions. Built 32 Keep it short enough Worker If the history is too long, older exchanges in the middle are trimmed. Built
Inside the loop: the model · drawn on Model call # Step Runs in What happens, in plain English Status 33 Our input check Worker Our rules check what's about to go to the model, such as an injection attempt. Built 34 Into the gateway Worker → APIM The request goes to our AI gateway, never straight to a model. Built (adapter) 35 Gateway: sign in APIM The gateway signs in to Foundry with its managed identity; the agent holds no model key. Azure 36 Gateway: allowed models APIM It checks this agent may use the model it asked for. Azure 37 Gateway: token limit APIM It checks the agent's and customer tier's tokens per minute; over the limit gets a polite 429. Azure 38 Gateway: edge screen APIM → Content Safety Optionally, it screens the request with Content Safety at the edge. Azure (optional) 39 Gateway: pick a backend APIM It sends the call to the first healthy backend: provisioned first, then pay-as-you-go, then a second region. Azure 40 Azure input check Foundry guardrail Azure screens the input for harm and jailbreaks. Azure 41 The model answers Foundry model The model reads the request and writes its response. Azure 42 Azure output check Foundry guardrail Azure screens what the model wrote. Azure 43 Gateway: count tokens APIM → Azure Monitor On the way back, the gateway records tokens by agent, model and tier. Azure 44 Gateway: not used APIM Semantic cache and full prompt logging stay off: answers are personal, and our own redacted record is the log. 45 Count the cost Worker The call's cost is added to the run's spend. Past the ceiling, the run stops. Built 46 Answer or tool? Worker The model either gives an answer or asks for a tool. Built
Inside the loop: a tool · drawn on Tool call # Step Runs in What happens, in plain English Status 47 Is it allowed? Worker Before a tool runs, our rules check it's permitted and that the customer asked for it. Built 48 Needs a person? Worker → DBOS If the action needs approval, such as a payout, the run pauses and asks an adjuster. To build 49 Gateway for tools APIM → MCP server The gateway checks the token and rate limit before the MCP server sees the call. Azure 50 Call the tool Worker → MCP → claims system The tool is called with a key that stops a retry from acting twice. Built 51 Check the result Worker The result is size-capped, checked for hidden instructions, and marked as data. Built 52 Azure tool check Foundry agent guardrail For Foundry agents, Azure can also screen tool calls and results. Azure (preview) 53 Save progress Worker → PostgreSQL Progress is saved, so a crash resumes from here, not from the start. Built
Inside the loop: when to stop · drawn on When it stops # Step Runs in What happens, in plain English Status 54 Limits Worker If steps, time or cost run out, the loop stops. Built 55 No progress Worker If the model keeps repeating itself, the loop stops. Built 56 Repeat Worker Otherwise the loop goes back to the model with the new information. Built
Journey 3 · Reply, and after # Step Runs in What happens, in plain English Status 57 Our reply rules Worker Our rules check the draft reply: no made-up claim numbers, dates, offers or personal data. Built 58 Promise check Worker Any promise, such as "we'll call you", must be backed by a real task, or the turn escalates. Built 59 Safe fallback Worker If a rule blocks, the reply becomes a safe message or a hand-off to a person. Built 60 Save together Worker → PostgreSQL The conversation and the reply are saved in one step, so neither exists without the other. Built (state) · outbox to build 61 Deliver Sender → Web PubSub or Chatwoot The reply is sent to whichever window or channel is open. Proposed 62 Shown Browser The customer sees the reply. A refreshed or new window loads it too. Proposed
When a person is needed · drawn on DBOS # Step Runs in What happens, in plain English Status 63 Hand-off ticket Worker → Chatwoot The question, what the agent found, and what's missing go to the human desk. To build 64 Bot steps back Chatwoot The conversation moves to a person, who sees the full history. To build 65 Waits DBOS on PostgreSQL Approvals and hand-offs wait as saved records with timers; any server resumes them. To build 66 Decision returns API → DBOS The adjuster's decision or the desk's resolution resumes the waiting work exactly once. To build
After the turn (out of sight) · drawn on Eval # Step Runs in What happens, in plain English Status 67 Trace Worker → Application Insights Every step is recorded, with personal data removed. Built 68 Counters Worker → Managed Prometheus Counters update: turns, refusals, steps, cost. Built 69 Online rules Scheduled job A job reads finished turns, runs the same rules again, and stores findings. Built on Langfuse · Azure to build 70 Sampled judges Foundry continuous evaluation A sample of turns is scored by evaluators such as groundedness and task adherence. To adopt 71 Alerts Managed Prometheus Rules watch windows of turns and alert on spikes, such as refusals or cost. Built 72 Daily cost Scheduled job The cost engine explains yesterday's spend and suggests fixes. v0 73 Canary Scheduled job Synthetic customers run real cases on a schedule, to catch breakage early. Built 74 Dashboards Managed Grafana People see health, quality, safety and cost for each agent. Built (template)
Before the next release · drawn on Offline # Step Runs in What happens, in plain English Status 75 Golden cases CI The new version answers the golden cases inside a simulated world (AgentTwin). Built 76 Red team CI Attacks are run against it; their success rate must stay low. Partial 77 Report CI The eval report compares results with the last release and explains any change. To build 78 Gate CI If anything got worse, the release is blocked. Built
Want every detail? The long version is in the Series: the journey overview .