The web workspace uses compact buttons and tabs, with page title and actions arranged horizontally where space permits. Narrow screens wrap controls rather than hiding the entire toolbar. Controls retain accessible interaction areas; native mobile uses its own touch design.
Watch the lesson
Primary and secondary actions
Important controls such as Save, Cancel, handover, the current resolution action and Help remain directly visible where applicable. Secondary actions can appear in a labelled ellipsis menu. There is no universal rule that every group of three buttons becomes a dropdown.
- Conversation headers retain handover/details controls; Customer actions holds permitted profile, identity, deal and follow-up shortcuts.
- Customer profiles retain core edit/tab actions; More actions contains permitted secondary customer operations.
- Helpdesk keeps conversation, handover and current lifecycle actions accessible, with secondary customer/ticket actions grouped where useful.
- Small toolbars and deal forms remain inline unless that surface explicitly groups secondary work.
Menus size to their content within the viewport and close after selection. A menu opens outside clipped conversation containers so it does not squeeze or cover the message area unnecessarily. Help stays outside optional action groups.
Slide-over previews
Customer-profile and Helpdesk conversation previews use the shared Large support-panel convention. The conversation uses available panel height and scrolls internally. Use the close control to return, or View full page to open the complete record. Information/analysis is loaded for the opened panel, including charts that initialize after the panel becomes visible.
Integrations
Integration cards share the Zoho card structure: recognizable medium logos, purpose-specific descriptions and the action appropriate to each provider. Brand assets have light/dark treatment without forcing a fixed white logo box. SMTP is placed toward the end; unavailable/upcoming integrations are distinct from configured connections. A provider's availability still depends on runtime configuration, plan and permission, not its card position.
See Integrations, Customer profile and View an interaction.