Make the next step part of the work.
A request should not disappear after the first answer. In the same workspace where you shape a digital worker, you can build the route that carries context forward, branches on a decision, and gives a person the right moment to take over.
- Start
Choose the signal
A form submission, inbound conversation, scheduled event, or other configured trigger can start a flow. This journey begins with a planning request.
- Understand
Put a digital worker to work
Give the worker approved knowledge and a specific job: gather missing context and prepare the request without inventing an answer.
- Decide
Branch on what is known
A decision node can route a complete request toward a booking option while sending an exception to staff for review.
- Act
Keep a person in control
The workflow can create a staff task with the original context attached. A person checks availability and decides what to confirm.
- Inspect
See the path it took
Test in the simulator, then use runs and activity to inspect the transitions, timing, and next owner.
From a signal to a decision you can see.
The flow below follows one planning request through the actual shape of the Agents & Workflows workspace: its trigger, digital worker, decision branch, staff action, and run history.
Use approved service knowledge to prepare the request for the next step.
- ✓KnowledgePlanning services
- ✓OutputRequest summary
- ✓GuardrailDo not confirm availability
Check configured availability
Ask team to resolve details
Room preference missingJordan asked for a team planning session for eight. The preferred date is October 24. Room preference still needs confirmation.
- SourcePlanning request form
- Prepared byService guide
- Next decisionCheck rooms and follow up
- Jordan Taylor · Planning requestInspect
Test run · Needs review · 4 steps
- Alex Rivera · Planning requestBooking path
Test run · Booking path · 4 steps
Trace the path and inspect the result before activating a workflow.
- ✓Form submittedPlanning request received
- ✓Service guideContext prepared from approved knowledge
- ✓Details complete?No · Room preference missing
- ✓Create staff taskMaya · Events team · Open
Maya reviews and chooses the follow-up.
- 01Give the request a starting point.
A form submission starts this flow. The contact and answers travel with it, so nobody has to start again.
- 02Gather what the team needs.
The service guide checks approved knowledge and prepares a summary of the requested date, group size, and purpose.
- 03Let the route change with the facts.
A complete request can move toward a bookable option. Missing details take the staff-review branch instead.
- 04Put the decision with a person.
A task carries the original request and reason for review. The team decides what to offer or confirm.
- 05See the path before it goes live.
The simulator and run view show which nodes fired, which branch was taken, and where ownership landed.
The experience carries the context.
Jordan and Maya are fictional people in this planning-request journey. It follows a configured form trigger through a digital worker, a decision, a staff review task, and a test run. The actual triggers, permissions, messages, booking rules, and handoffs are set and tested during implementation.
See forms and bookingBuild the right version for your work.
We’ll map your existing tools, choose the experiences that matter, and help your team put them to use.
Book a guided demo