Workspace identity
How NovaraDesk appears to agents and customers.

Monitor AI performance, manage escalations and give your team the context they need—all from one secure workspace.
Continue with the approved Google account connected to your workspace.
Sample tickets and analytics. No sign-in or session timeout.
By continuing, you agree to the Terms of Service.
Monitor customer conversations and CX performance.
| Session | Date | Query | Intent | Rating | Sentiment | Status |
|---|---|---|---|---|---|---|
|
No conversations yet.
|
||||||
| Session | Date | Query | Intent | Rating | Sentiment | Status |
|---|---|---|---|---|---|---|
|
No human conversations yet.
|
||||||
Narrow the queue. Results update instantly.
| Ticket | Created | Customer / Query | Assigned To | Status | Age | Resolution |
|---|---|---|---|---|---|---|
|
No escalated tickets yet.
|
||||||
Add any saved chart, summary table or pivot report. There is no widget limit.
| Customer | Organisation & segment | Last interaction | Support | CSAT | Health | Lifetime value |
|---|
Configure the identity and operating defaults for this workspace.
How NovaraDesk appears to agents and customers.
Used for SLA calculations and channel availability.
Invite teammates and control their access.
Keep administration separate from daily ticket handling.
Standardise how new support cases are created and managed.
Default response and resolution expectations.
Control the customer entry points available to the workspace.
Connect customer, commerce and fulfilment data.
Choose which operational events should interrupt agents.
Protect administrative and customer information.
Prototype audit trail for critical changes.
Last 28 days
Current dashboard date range
| Group | Value | Share |
|---|
Reusable views stored in this browser.
See how customers experience your currently published configuration.
Tell the AI what to do in specific situations. If rules conflict, the first matching rule takes priority.
Choose the model used for customer conversations.
Only change these settings if you understand their impact on response quality, speed and cost.
Apply a preset, then fine-tune it if needed.
Deploy the same published intelligence while preserving channel-specific identity and replies.
Restore any earlier configuration as a new draft before publishing.
Draft content remains unavailable to customers until published.