Follow-up stays visible
Inbox work items remain the review queue for approvals and requests; notifications remain awareness alerts with deep links.
Communications
Messages, boards, notifications, and follow-up in one workspace.
Keep direct messages, board announcements, app notifications, and review-required inbox work distinct but connected.
Launch posture
Core launch surface
Workflow-aware internal messaging, acknowledgements, notifications, review-first AI recaps, and follow-up queues are launch-ready internal channels.
Asset slot
Admin Messages with Inbox and Board modes plus notification bell
Capture inbox, board, and notification center after final notification examples are seeded.
What is ready now
These points describe shipped product behavior or explicitly scoped setup readiness. Final screenshots and recordings will be captured from the product after demo data is frozen.
Direct messages create admin inbox follow-up when needed
Board channels support organization announcements, posts, threads, reactions, and acknowledgements
AI summaries are review-first and cite visible source messages
App notifications have read, dismiss, deep-link, routing, delivery-history, and preference state
External pipes are optional
Email digest, Slack webhook, SMS, Slack OAuth, and Microsoft Teams delivery are integration pipes, not the source of truth.
Included scope
- Direct messages
- Board announcements
- Threads and reactions
- Acknowledgements
- App notifications
- Notification routing rules and delivery history where configured
- Review-first AI recaps
Not included
- External messaging systems as source of truth
- Autonomous acknowledgement chasing
- Compliance communications guarantees
Asset source tracking
Product imagery is published only after the capture source, demo organization, viewport, data set, and refresh trigger are recorded.
- Route
- /communications
- Surface
- Admin Messages with Inbox and Board modes plus notification bell
- Organization
- Approved demo organization after final seed reset
- Viewport
- Desktop 1440x1024 and mobile 390x844
- Data set
- Synthetic approved demo data only
- Refresh date
- Pending final product capture
- Refresh trigger
- Refresh after material UI, legal copy, seed data, data model, or route changes
Buyer FAQ
These answers keep trial, support, export, provider, AI, mobile, and trust expectations consistent across the public site.
Can I start without a sales call?
The current path supports controlled trial activation. No-card demo tenants remain support-approved so capacity, provider setup, sensitive uploads, and data-retention expectations stay bounded.
What happens if we cancel?
Paid access normally ends at the end of the billing period, then the workspace enters a 30-day export/reactivation window unless a verified deletion request is completed earlier.
Does Yrka process payroll or file taxes?
No. Yrka supports timekeeping, payroll-prep exports, review, and provider handoff. Customers remain responsible for payroll processing, tax filing, legal, HR, and compliance decisions.
What mobile support is included?
Launch mobile support is responsive web/PWA-oriented. Employees get scoped offline read context and supported queued writes with visible sync states; native app-store apps and broad offline admin operation are not part of launch scope.