StayAssist workflow follow-through
Carry workflow results into the next operational step.
Follow-Through is what happens after a workflow reaches a result. It carries that result into the next step for the guest, the team, a supported system or another workflow. Connected-system actions depend on the integration.
Workflow result Early check-in requested
Follow-Through
Operational continuity
A useful result still needs somewhere to go.
The guest asked for help. An early check-in was requested. An experience was accepted. A reminder is still unresolved. In each case, someone still has to pick up the result and make the next thing happen. Follow-Through carries it into the next step instead of leaving the team to reconstruct and move it manually.
- 01
Workflow result
The answer, contact outcome, selected branch or operational status produced by the source workflow.
- 02
Next step
The next step chosen for that result. Different results can continue differently.
- 03
Where it continues
The guest, team, owned task, connected operation or next workflow that receives it.
A useful result should not stop at the end of the conversation.
People in the right place
Continue with the guest, or bring in the team.
Some results need another guest contact. Others need someone to decide or act. Follow-Through keeps those paths distinct.
- 01Guest continuation
Continue with the guest
Place another outbound call or message when the result calls for a guest-facing next step. OTA/PMS messaging is available only where the connected provider supports it.
- 02Live team transfer
Connect now
Keep the guest in the active call and transfer it to the relevant team destination where the setup supports it.
- 03Later team contact
Continue with the team later
Place a separate outbound team call after the guest conversation when the next step does not need to happen in the active call.
- 04Owned follow-up
Create owned follow-up
Create or assign an operational task when someone needs to own what happens next.
Contact, transfer, message delivery, task completion and team availability are not guaranteed.
Supported connected actions
Carry the result into the connected operation.
When the next step belongs in another operational system, Follow-Through can use an available action from the connected PMS, CRM or other supported destination.
- 01
Keep the operational status aligned
Update the relevant operational status when the workflow reaches the right result.
- 02
Keep connected information up to date
Update available PMS, CRM or operational information when the connected integration provides that action.
- 03
Continue through a webhook or API action
Send the result to a defined destination when the receiving system and connection support it.
Structured post-call extractionA separate usage-based add-on can extract structured information from a completed call for supported follow-through. Destination support still applies.
Explore integrationsConnected-system follow-through depends on the data, actions and permissions supported by each provider and configured integration.
Purpose-specific paths
Continue into another workflow when the next step needs its own path.
One workflow can finish the job it owns and pass its result into another configured workflow. This keeps arrival, assistance, reminders, commercial conversations and other operational paths focused while the wider operation continues.
Across StayAssist workflows
Different results need different next steps.
Follow-Through works across StayAssist workflows. These examples begin with the result and show a possible next step, not a fixed default.
Workflow resultOne meaningful outcome
Workflow Follow-ThroughConfigured continuation
One appropriate destination
Guest
- Outbound call or message
- Another guest-facing workflow
Team
- Connect now
- Continue with the team later
Connected operation
- Supported update
- Owned operational task
Next workflow
- Another configured workflow
- Purpose-specific next path
- 01Team
Guest needs a person
Connect the active call now or continue with the team later.
- 02Team or connected operation
Boat experience accepted
Carry the result to the appropriate team or an available connected-system action.
- 03Team or supported continuation
Early check-in requested
Send the request to the team for a decision, then continue through an available system action or another workflow.
- 04Next workflow or team
Required step remains outstanding
Continue to the next reminder, team contact or workflow path.
- 05Owned task, operation or workflow
Configured branch reached
Create an operational task, use an available connected-system action or continue into another workflow.
A commercial acceptance is not automatically a sale, order, payment or reservation change.
Operational visibility
See where the result went.
StayAssist can show the result, the next step selected and the available outcome from that continuation. The team can use that context for handoff and later operational review.
- 01
Result
The workflow reaches a useful result.
- 02
Next step selected
The configured continuation determines what follows.
- 03
Where it went
The guest, team, operation or next workflow receives it.
- 04
Available outcome
The destination result is shown where available.
This view shows how the result continued. It does not guarantee that a person acted, a guest complied, a task was completed or a real-world issue was resolved.
Questions, answered
Practical details about what happens next.
The next step depends on the workflow result, the chosen path and what the destination supports.
What kinds of workflow results can continue?
A next step can begin from a contact result, guest response, selected branch, outstanding status, commercial response or another result available to the workflow. What can happen next depends on the source workflow and destination.
What is the difference between a live transfer and later team contact?
A live transfer keeps the guest in the active call while it connects to the relevant team destination. Later team contact is a separate outbound team call after the guest conversation. Neither action guarantees that the team answers or resolves the request.
Can Workflow Follow-Through update my PMS or CRM?
It can update an available PMS, CRM or operational field when the connected integration provides that action. It does not provide unrestricted access to every field or a generic ability to modify any reservation, create an order or register every accepted offer as a sale.
Can it create a task or send a webhook or API action?
Yes. Follow-Through can create or assign an operational task and can send an outbound webhook or API action to a defined destination. Available details, authentication and what the receiving system reports back depend on the setup. Delivery, processing and task completion are not guaranteed.
Can one workflow start another?
Yes. The result of one workflow can start another configured workflow. A subflow may also be used where appropriate. Custom Workflows explains how the wider business-specific path is configured and reused.
Does every action work with every integration?
No. Connected-system follow-through depends on the data, actions and permissions supported by each provider and configured integration.
Is structured post-call data included with every call?
No. Structured post-call extraction is a separate usage-based add-on. It can provide agreed information from a completed call for supported follow-through, but destination support and action permissions still apply.
Plan the continuation
Give each important result a clear next step.
Tell us which StayAssist results matter to your operation and which guest, team, system or workflow step should follow.