Small Business Intake Design
Intake is the front door of an AI operator system. If the request enters cleanly, Rocky can classify, summarize, route, and draft the next move.
When this matters
This page is for operators who want Rocky to produce usable work without turning the system into a mystery box. Use it when you need a practical path, a clear verification step, and a boundary between suggestion and action.
The operating pattern
- Choose entry points. Pick email, form, phone, SMS, chat, or a private portal.
- Ask only useful fields. Every field should support routing, response, quote, or follow-up.
- Normalize records. Convert messages into consistent request objects.
- Detect urgency. Tag deadlines, VIPs, refunds, safety, money, and legal issues.
- Create next action. Every request should land as draft, approval, or task.
Pre-flight checklist
- Customer can complete it quickly
- Private data is minimized
- Confirmation is sent or shown
- Duplicate requests are handled
- Follow-up owner is visible
Common failure modes
- Overlong forms: More fields can reduce completion and still not improve decisions.
- No receipt: Customers need to know the request arrived.
- Unclear routing: Intake without routing just creates a prettier inbox.
Verification
A page is not done because it was drafted. Verify the source, run the workflow, inspect the output, and record what changed. If a step touches money, customers, accounts, permissions, or private data, keep it behind an explicit human approval gate.