On this page
Explore complete agent use cases
Follow three workflows from setup to release: order support, appointment booking and after-call automation. Each guide shows the flow, action contracts, failure paths and tests. Screenshots use synthetic data; endpoints at api.example.com represent services your team implements. Select an image to view it at full size.
Order support and refund review
Follow the complete support workflow. See how verification gates account access, documents supply approved policy, action responses drive branches, and an operator reconciles an uncertain refund before requesting another write.
Useful for: order support, account service, returns, billing questions and workflows where an operator must explain what happened to a business action.
Qualification and appointment booking
Follow the qualification and booking workflow. Capture the caller's needs, route the conversation, offer actual availability, request explicit confirmation and distinguish a confirmed reservation from a follow-up request.
Useful for: requested consultations, service intake, appointment scheduling and routing to a specialist. Your team owns contact eligibility, business criteria, calendar access and the authority to book.
After-call cloud operations
Follow the after-call operations workflow. Map selected fields from a phone run into a cloud task, reconcile the business outcome, update your system and return a structured result. Use a schedule for a separate review-queue path.
Useful for: CRM updates, exception queues, follow-up preparation and background work with its own version, run history and action receipts.
Inspect the operational result
Investigate a run: identify the publication, read the transcript, follow the node path, inspect action receipts and determine whether the business outcome was confirmed. A call ending successfully does not establish that a refund or booking completed.
Release a tested change
Release and operate an agent: compare publication changes, run repeatable cases against a candidate, inspect a regression against its baseline, promote the tested version and review real integration acceptance.
Setup responsibilities
| Your team supplies | Cumulus supplies |
|---|---|
| The verification, eligibility, qualification and escalation rules | The flow editor, reusable components, validation and published versions |
| Business endpoints, credentials and transactional/idempotency contracts | Named HTTP actions, permission checks, send attempts and receipts on each run |
| Approved knowledge and test acceptance criteria | Document pinning, scenarios, action mocks, trials and assertion evidence |
| Authorized phone targets and carrier configuration | The documented phone execution and review workflow |
| Downstream reconciliation and the decision to act on a result | Structured cloud execution, triggers, outputs and the same run model |
For a comparison of development and operating responsibilities, see Choose your platform.