Product Naming Guide
TROPIKAL distinguishes Website Components from Jobs. A Component is a feature installed on one Website. A Job is an owner-authored automation that handles work end to end.
The public authenticated app host is app.tropikal.ai. ops.tropikal.ai is
retired and must not be used for browser or API traffic.
Use this language in customer docs:
| Term | Use it for |
|---|---|
| Website Component | A Website-owned visitor feature such as Website Chat or Calendar Booking. |
| Job | The end-to-end work TROPIKAL is helping run. |
| Run | One execution of a job. |
| Work-step instructions | Versioned AI behavior inside a Job: task, tone, boundaries, and escalation rules. |
| Function | An approved action a job can run. |
| Knowledge | Approved sources a job can use when answering or drafting. |
| Capabilities | Approved actions, integrations, and tools the job may use. |
| Connected Data | Approved business objects synced from a connected website. |
| Channels | Supported places where a customer Job starts or hands off, such as email, Telegram, or dashboard review. |
| Handoff | The owner-ready result: lead details, summary, draft reply, booking request, or next action. |
| Website publish destination | A job output that sends reviewed content to a connected website. |
Legacy technical labels
Some older database identifiers, file paths, and code symbols still use historical labels. Treat those as migration-history strings, not as the product category. For customer-facing explanation, use Job and work-step instructions.
Examples:
| Prefer | Avoid |
|---|---|
| AI Front Desk job | AI Front Desk as a standalone bot product |
| Configure work-step instructions | Write the soul |
| Knowledge & capabilities | Operating map |
| Website Chat Component | Website Embed Job, Chat Job, or backing Job |
| Owner handoff | Raw AI output |
What belongs where
The Job version owns the automation’s Trigger, work-step instructions, Conditions, workload package, outputs, and handoffs. Knowledge and capabilities define what the Job may safely use.
The Website page owns Component setup. Never instruct an owner to locate a hidden Component record in Jobs. Website Chat may start customer Jobs only when the owner explicitly adds them as Component tools.
Do not put changing business facts into work-step instructions. Put approved facts in Knowledge. Add only the capabilities the Job needs.
Configure where a Job starts in the Trigger node and where it ends in the Output node. Configure Website Chat and Calendar Booking from the Website’s component gallery instead.
Compatibility references
Keep exact implementation strings only when accuracy matters, but explain the customer behavior as a Job using versioned work-step instructions, knowledge, Connected Data, and capabilities.