Support ticket lifecycle · Data Modeling scenario

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You are modeling the core of HelpLoop, a B2B support desk. Tickets move through states and change owners, and the business reports on SLAs — so status and ownership must be history, not columns, and any past moment must be reconstructable.

your ERD must answer

01What is a ticket’s full status history — every transition, in order, with when and by whom?
02Who owned a ticket at any point in time — and who owns it right now?
03The SLA timestamps: first response and resolution.

out of scopeKnowledge base · CSAT · billing · staffing

This exercise’s brief could not be loaded.The guided questions and their model answers come from the review service. It looks like it is not reachable — start it with pnpm dev:api and reload.The canvas below still works, so you can model now and run the review once the service is up.

Build starts here

The brief becomes the left drawer. The canvas stays the build surface.Study is done above. Build the tables here, hit review to validate, then use follow-ups to defend the model.

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

68%

You built the model in the Studio. Now defend it.Support ticket lifecycle

Design review

The reviewer reads your model.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You are modeling the core of HelpLoop, a B2B support desk. Tickets move through states and change owners, and the business reports on SLAs — so status and ownership must be history, not columns, and any past moment must be reconstructable.

your ERD must answer

01What is a ticket’s full status history — every transition, in order, with when and by whom?
02Who owned a ticket at any point in time — and who owns it right now?
03The SLA timestamps: first response and resolution.

out of scopeKnowledge base · CSAT · billing · staffing

This exercise’s brief could not be loaded.The guided questions and their model answers come from the review service. It looks like it is not reachable — start it with pnpm dev:api and reload.The canvas below still works, so you can model now and run the review once the service is up.

Build starts here

The brief becomes the left drawer. The canvas stays the build surface.Study is done above. Build the tables here, hit review to validate, then use follow-ups to defend the model.

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

68%

You built the model in the Studio. Now defend it.Support ticket lifecycle

Design review

The reviewer reads your model.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules