What Flow needs
- A connected business phone line
- Business information for answering common questions
- Booking availability when appointment scheduling is enabled
AI receptionist for small business
Cassius handles customer conversations through Flow: inbound and outbound calls, qualification, booking, follow-up, and the CRM record that should exist when the call ends.
Who this is for
The operating problem
A missed call can become a missed customer. Even answered calls create follow-up work when the details never make it back to the business.
A workflow from instruction to outcome
A customer calls your business line, any time, day or night.
The receptionist answers and gathers the reason for the call.
Details are captured and the request is qualified against your rules.
An appointment gets booked, or a message is prepared for follow-up.
The full call transcript lands in chat and stays connected to the CRM record.
Illustrative example — fictional prompt, response, names, and metrics; not customer results.

From context to controlled action
Flow keeps the conversation close to the records and work it can use. The owner remains the decision point where the workflow requires approval.
What Flow needs
What Flow creates
Where you approve
What to expect
Call handling depends on your configuration and the information the receptionist has. Complex, emergency, regulated, or sensitive conversations should be escalated to a person.
Frequently asked questions
Start with the core
The workspace is free for one person and one organization. Hire an employee only when you want more capacity.