Product Naming Guide
TROPIKAL distinguishes Components from Jobs. A Component owns an interactive experience and its UI. A Job is reusable, headless work that accepts input, performs steps, and returns an outcome. A Component may start an explicitly approved Job, but a Component is never represented as a Job.
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 interactive feature with its own setup, sessions, and lifecycle, such as Website Chat or Calendar Booking. |
| Job | Reusable work that accepts input, performs steps, and returns an outcome. |
| 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. |
| Start | The event or action that invokes a Job, such as email, Telegram, a schedule, a manual run, or an approved Component action. |
| Channel | A configured message source or delivery destination, such as email or Telegram. |
| 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 |
|---|---|
| Error-analysis Job started by email | Email assistant, frontline Job, or operator Job |
| 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 |
Never classify a Job as frontline, operator, front desk, website operator, or another UI archetype. Describe the work it performs and, separately, how it starts.
What belongs where
The Job version owns its input contract, work-step instructions, Conditions, workload package, outputs, and handoffs. Knowledge and capabilities define what the Job may safely use. Start settings connect an event source to the Job; they do not define a different kind of Job.
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 how a Job starts and where its result goes from the Job setup. 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.