Real customer workflows are more than question and answer. A warranty claim needs a photo of the rating plate. An insurance quote needs a document read and a system called. Flows in Rylvo can now do that work themselves.
Actions on every step
A flow step can wait for a file, read it, call a connector, set a tracked detail, reply, hand off to a person or go to another step. Actions work on every channel and with any bot.
Reading profiles
A reading profile tells the agent what to pull from a photo or document, such as a model number, an amount or a date. It handles photos from phones (HEIC included) and scanned PDFs, within a per-conversation photo budget.
Run your own code
When a step needs logic of its own, write it. The code editor includes packages, a Simulate button that runs the step against a sample conversation, and a Code tab on the flow. Architect and MCP can write and test code steps too.
Measured and testable
- Flow analytics show what each action did.
- Saved tests can send photos and expect tracked details and a flow step.
- A tracked detail that changes during a conversation can be written to your own database through Conversation Storage.
- Test destinations let a flow in Test call a test system instead of a live one.
