Clean up and next steps

Put the demo environment back the way you found it, and a routine worth taking into real work.

Put the environment back

The demo instance is shared, so leaving it as you found it is the difference between the next person having a working workshop and a confusing one.

  1. Undo the exercises. The welcome prompt, the routing reference on the experience, transferType back to queue, the default language, and the closure switch if you turned it on. The closure matters most, because leaving it on shuts every demo line, not just yours.

  2. Delete what you created. The <your initials> Announcements entity, its child Urgent, and the items in both. Delete the child first: an entity with children cannot be removed.

  3. Set yourself offline in the softphone so you are not routed a call later.

If something is left in a strange state

The demo environment has a scripted reset that puts the entities, items and flows back to their known-good state. Ask the workshop host to run it rather than trying to repair things by hand.

A routine worth keeping

DFC changes are fast to make, which is exactly why they deserve a habit. The short version of everything in this workshop:

  1. Check the blast radius. Open the item and see what references it. Shared items are normal — surprises are not.

  2. Change the value, not the schema. Editing an item is routine. Renaming or removing a field changes the contract every flow depends on, and a flow reading a field that no longer exists gets a blank rather than an error.

  3. Place a test call. It is the only step that proves a flow is reading what you think it is reading.

  4. Read the flow log if anything looks wrong. It records the path that was asked for, the whole response, and the exact text and voice of every prompt.

DFC change checklistThe four steps above, plus the specific traps, in one page you can paste into a change template — MD · 2.4 KB

Where to go next

Three directions, roughly in order of usefulness:

  • Move something real into DFC. Take a flow you own and find one hard-coded value in it — a prompt, a queue, a threshold. Model it, point the flow at it, and delete the hard-coded copy. One value at a time, with a test call after each.

  • Model an experience from scratch. The demo’s Contact Source and Experience Config pair is a pattern rather than a rule. Build the equivalent for a line you know, and notice which fields you wanted that the demo does not have.

  • Look at how changes get approved. Everything in this workshop took effect the moment you hit save. Where that is too loose, DFC edits can be routed through change requests and an audit log instead, which is a separate module and a separate workshop.

What this workshop deliberately left out

Two things you will meet in real work and not here. Evaluating a schedule — deciding whether you are open right now — is not something a contact flow can do on its own, and the demo sidesteps it with the closure switch instead. And bulk editing across many items at once is its own module. Neither changes anything you learned about the model.