Read an order status after identity checks.
Payments & Orders
Order Workflows for voice workflows
Connect order status or approved order actions through a business API.
Layer
Payments & Orders
Focus 01
Order status
Focus 02
Customer context
Focus 03
API actions
The role
What Order Workflows brings to a call
Order actions are business-specific API workflows. Keep the agent's scope narrow so it can answer a status question without changing an order unexpectedly.
In the voice stack
Payments & Orders
Payments and orders require a precise scope. Account billing, customer payment collection, and order actions are different workflows with different permissions.
Use cases
Where teams use Order Workflows
Record a delivery exception for staff review.
Update an order only after caller confirmation.
Implementation
From setup to a real call
Define the outcome
Choose the call scenario and decide which of Order Workflows's capabilities the agent needs.
Configure the path
Expose only the order fields and actions the agent needs through a scoped API tool.
Test before launch
Verify caller identity before sharing order details or making a change.
Frequently asked questions
Order Workflows questions
What does Order Workflows add to a Vozon workflow?+
Order actions are business-specific API workflows. Keep the agent's scope narrow so it can answer a status question without changing an order unexpectedly.
How do I set up Order Workflows?+
Expose only the order fields and actions the agent needs through a scoped API tool.
What should I verify before launch?+
Verify caller identity before sharing order details or making a change.
More in Payments & Orders
Build your workflow
Put Order Workflows to work in the right call flow.
Tell us what your agent needs to hear, say, read, or update. We'll help map the connection and test it with your call scenarios.
Plan this integration