A known hospitality job
Begin with a recognizable purpose, then adapt the timing, information, communication and follow-through to the way your operation works.
StayAssist workflow orchestration
Custom Workflows
Your process does not have to fit a fixed template.
Define how a process should start, what information matters, what should change the path and when your team should become involved. Then reuse that workflow across the properties where it fits and adapt supported details where local operations differ.
Starts from
- Schedule
- Reservation event
- Operational signal
Configuration Your process
- 01Use context
- 02Apply conditions
- 03Set timing
- 04Choose follow-through
Reuse across
- Property
- Group
- Portfolio
Beyond a fixed catalogue
Start with a familiar workflow. Adapt beyond it.
Some operational jobs are common across hospitality. Others depend on how your properties, teams and processes actually work. StayAssist supports both without treating familiar workflows as rigid scripts.
Your particular process
Define a reusable path around the way your business operates when a familiar starting point is not enough. Supported rules, timing, communication and team involvement can shape what happens next.
The configuration model
Shape the path around what starts it and what happens next.
You define the operating logic. Guided setup brings together the triggers, information, rules and follow-through the process needs, using the capabilities available to your setup. Many business-specific paths use current capabilities rather than bespoke development.
- 01
Choose what starts it
Begin from a schedule, reservation event, incoming guest call, manual start or an event made available by a supported product or integration.
- 02
Bring in the information that matters
Use the guest, reservation, property, language, knowledge, timing and operational information available to the process.
- 03
Define what changes the path
Use rules and responses to change the route, wait, retry or stop when the process calls for it.
- 04
Set what happens next
Communicate with the guest, bring in the team, or continue into the next supported operational step.
A path can also include a relevant commercial branch or a supported follow-through step when the process requires it. Specific events, fields, message results and connected actions depend on provider data, permissions and the configured setup.
Explore Revenue Workflows Possible paths
Different operations can use the same orchestration ideas.
These examples show how the same StayAssist capabilities can support different operating needs. They are illustrative configurations, not defaults or promises that every provider exposes the same data and actions.
- 01
A recurring operational check
At a scheduled point, inspect an available status and continue only when attention is still required. The timing, recipient and follow-through can reflect the way that operation handles the check.
- 02
A property-specific exception
A supported reservation event or status can lead to different timing, recipients or follow-through for a particular property or group. The variation stays part of the reusable operating process.
- 03
A connected property signal
An event from StayControl, StayAlert, StayEco or a supported external system can begin a business-specific communication or team path. StayAssist coordinates the communication or team response while the originating product continues to handle its own monitoring or control role.
- 04
A conversation that changes the route
A guest-support path can answer the original question, introduce a relevant experience when it fits and carry the guest's response into the next step.
Build a process that fits the operation, can be repeated consistently and remains visible to the team.
Portfolio configuration
Define the process once. Adapt it where the operation differs.
Create one reusable operating definition and assign it to the properties or groups that share the process. Keep the common logic together, then adapt supported details where an individual operation differs.
Reusable definition
Keep the shared trigger, rules, timing and follow-through together.
Copy and reuse 02 03
Property and group assignment
Use the process across the parts of the portfolio that share the same job.
Local adaptation
Adjust property knowledge, recipients, windows or other supported details where the operation differs.
Consistency does not require every property to be identical.
People in the right place
Let the workflow carry the routine. Bring people in for the decisions.
A useful custom workflow is clear about which repeatable steps can continue and where judgment, approval or an exception needs a person.
The repeatable route
Supported starts, relevant communication, waits, retries, recipient changes and routine follow-through can continue through the defined path.
The decision that needs a person
Questions, exceptions, approvals or decisions outside the configured scope can move to the appropriate person with the relevant workflow context.
Execution visibility
See how your process actually ran.
See which route the workflow took, what happened during communication and where the process ended. Review waits or retries, team involvement and supported actions. Filter history by property, workflow, result or date for team handoff and later operational review.
- 01 Started
Scheduled operational check
- 02 Context
Property and available status
- 03 Decision
Follow-up required
- 04 Follow-through
No answer; wait completed and team path selected
- 05 Final state
Context carried forward and result recorded
Questions, answered
Practical details before defining a custom workflow.
What makes a StayAssist workflow custom?
A custom workflow brings supported starts, relevant information, rules, timing, communication and follow-through together around a process that is specific to your operation. It is not limited to one named workflow family or fixed script.
What can start a custom workflow?
A custom workflow can start from a schedule, reservation event, incoming guest call, supported API or integration event, or an event from StayControl, StayAlert or StayEco. Manual start can also be included where configured. The exact events and data available depend on the products and providers involved.
Can I use the same workflow across multiple properties?
Yes. StayAssist supports reusable definitions, copying, property groups and portfolio assignment, so a process can be used across the properties that share it.
Can different properties use different versions?
Yes. Property-specific configuration and overrides can adapt supported details such as knowledge, recipients, timing or other local requirements. Exact settings depend on the workflow and account configuration.
Can the team or another system become involved?
Yes. A path can include a live transfer, team contact or another supported continuation. Exact continuation depends on the available capability, provider data, permissions and configured setup.
Do I configure the workflow myself?
You define the operating logic, and StayAssist is configured through guided setup around the capabilities available to that process. It is not an unlimited self-service or drag-and-drop workflow builder.
Does Custom Workflows mean bespoke software development?
Not necessarily. Many business-specific paths can use existing StayAssist capabilities. If the process requires a new capability or unsupported integration, that would need to be scoped separately.
Start with the process you already run.
Tell us how the process works today, what should trigger it and where your team needs to stay involved. We can map it against the StayAssist capabilities and integrations available to your operation.