Workflow Naming Guide
Tropikal is workflow-first. A workflow describes the customer or owner job being handled end to end: answering a visitor, qualifying a lead, drafting content, reviewing email, preparing a booking request, or handing work to an owner.
Use this language in customer docs:
| Term | Use it for |
|---|---|
| Workflow | The end-to-end job Tropikal is helping run. |
| Persona | The AI role inside a workflow: tone, behavior, boundaries, and escalation rules. |
| Knowledge | Approved sources the persona can use when answering or drafting. |
| Capabilities | Approved actions, integrations, and tools the workflow may use. |
| Channels | Places where the workflow starts or hands off, such as website chat, email, Telegram, or dashboard review. |
| Handoff | The owner-ready result: lead details, summary, draft reply, booking request, or next action. |
Agent language
Use agent only when it is the actual product surface, URL, API path, or legacy dashboard label. For customer-facing explanation, prefer workflow and persona.
Examples:
| Prefer | Avoid |
|---|---|
| AI Front Desk workflow | AI Front Desk agent as the main concept |
| Configure the persona | Write the soul |
| Knowledge & capabilities | Operating map |
| Website Embed workflow | Public agent bubble as the whole product |
| Owner handoff | Agent output |
What belongs where
The workflow owns the job, inputs, outputs, and handoffs. The persona owns how the AI should behave while performing that job. Knowledge and capabilities define what the persona can safely use.
Do not put changing business facts into the persona. Put approved facts in Knowledge. Do not describe broad system powers in the persona. Add only the capabilities the workflow needs.
Stable technical names
Some stable technical names still include agent, including agent.tropikal.ai, existing dashboard routes, install snippets, and API paths. Keep those names when accuracy matters, but explain the customer behavior as a workflow using a persona, knowledge, and capabilities.