A customer email arrives.
Operational Inbox
Work does not get lost.
The operational inbox for work that cannot get lost. Shared inboxes, tasks, and knowledge for small teams who keep work moving.
One thread. One owner. One place to finish the work.
- Email enters one inbox
- One owner per thread
- Public replies stay public
- Internal work stays internal
- Tasks stay attached
- Knowledge stays reusable
Built from the same operational surface: shared inboxes, ownership, tasks, context, and knowledge.
- Inbox
- Unassigned
- Mine
- Thread
- Public
- Internal
- Task
- Context Index
- Knowledge Base
The failure mode
Shared inboxes receive work. They do not finish it.
Most support work starts in email. Then it leaks into notes, chats, calls, spreadsheets, memory, and the ritual of assuming someone else handled it.
Context moves into chat.
A task appears somewhere else.
No one knows if it is closed.
Operating rhythm
Conversation to ownership to closure.
Conversation
Shared addresses flow into one operational inbox.
Ownership
Every thread gets one accountable owner.
Internal work
Notes, tasks, and decisions stay attached to the thread.
Closure
Close the thread when the linked work is resolved.
Product surface
Built around the way small teams actually work.
Shared inboxes
Handle multiple support addresses in one place without shared confusion.
One owner
New conversations start in Unassigned. A team member takes ownership.
Public / Internal
Two tabs keep customer replies and internal collaboration visibly separate.
Linked tasks
Create tasks where the work starts and keep them attached to context.
Standalone tasks
Detach work when it becomes standalone instead of burying it in a thread.
Knowledge
Search support history, internal docs, public articles, entities, and tasks.
Search
Find operational work without asking people where something was discussed.
Entity context
Link a thread to a customer, product, application, server, invoice, or subscription.
Settings
Manage inboxes, routes, signatures, and knowledge setup without enterprise clutter.
Explore
Find the workflow that matches your team.
Compare Opkivo
Compare Opkivo with helpdesk and shared inbox software.
Shared inbox for small teams
Give every shared support thread one clear owner.
Email helpdesk with tasks
Keep follow-up work attached to customer conversations.
Support thread ownership
Make accountability visible before work drifts.
Knowledge Base
Turn repeated answers into private docs and public articles.
Pricing
Review public EUR plans and limits.
Inside the work
Public replies stay public. Internal work stays internal.
Opkivo keeps the operational surface close to the thread: communication, internal decisions, task follow-up, and searchable context.
Unassigned Mine Closed
Email delivery issue on production domain
Can you confirm why invoices are bouncing?
Billing contact update
Need the finance address changed.
Public KB article request
Repeated setup answer needs publishing.
Thread 1428
Owner: Ana Email delivery issue on production domain
Public Internal
Customer communication
Public is for replies the customer should see: direct, clean, and attached to the thread.
We found the DNS issue and will send the exact records to update.
Team decisions and tasks
Internal is for notes, system activity, and task work that should never leak into a customer reply.
- Check SPF record
- Update delivery article
Close the thread only when the work is closed.
Opkivo keeps thread-linked tasks connected to the conversation. If open tasks remain, the closing flow makes the decision explicit: review the tasks or close them with the thread.
- Open thread
- Linked tasks
- Review or close tasks
- Closed thread
Plans
Start with the inbox count you actually need.
Plan limits and EUR pricing are public. Request access when you are ready to set up the first inbox.
Starter
For small teams starting with one operational inbox.
€9.99 EUR
- 3 users
- 1 inbound inbox
- Forwarding and IMAP inbound
- Customer SMTP route
- 500 MB storage
- Public KB domain disabled
- 10 articles
- Self-service checkout eligible
Team
BalancedFor teams running support across multiple inboxes.
€49.99 EUR
- 5 users
- 3 inbound inboxes
- Forwarding and IMAP inbound
- Customer SMTP and Platform SES routes
- 1000 MB storage
- Public KB domain enabled
- 50 articles
- Self-service checkout eligible
Business
For teams managing more inboxes, people, and knowledge.
€199.99 EUR
- 30 users
- 10 inbound inboxes
- Forwarding and IMAP inbound
- Customer SMTP and Platform SES routes
- 5000 MB storage
- Public KB domain enabled
- 500 articles
- Self-service checkout eligible
Trust model
Designed around the mistake teams cannot afford.
Opkivo is designed around a simple risk: internal work must never leak into customer communication. The product favors clear ownership, explicit tabs, and confirmed context over hidden automation.
- Public and Internal areas separate customer replies from team work.
- Clear composer states reduce the chance of sending internal notes to customers.
- Manual entity linking avoids risky automatic context in the current product.
FAQ
Direct answers before a demo.
Is Opkivo a helpdesk?
Opkivo includes helpdesk flow, but it is better described as an operational inbox. It starts with shared email support and adds ownership, internal communication, tasks, context, and knowledge.
Does Opkivo replace Gmail?
For support work, yes. Gmail can still exist as the underlying mail system, but the daily support workflow should happen inside Opkivo.
Is Opkivo a CRM?
No. Opkivo can link context from external systems, but it does not try to become your CRM.
Does Opkivo use automatic email tagging?
No. Email based automatic tagging is intentionally avoided in the first version because wrong context is worse than missing context.
How does Opkivo separate public and internal communication?
Each thread has two tabs. Public is for customer replies. Internal is for notes, tasks, and team activity. The two areas use different backgrounds and composer modes.
What happens when a thread closes?
If the thread has open tasks, Opkivo asks the user to review them or close the tasks with the thread. Work cannot disappear quietly.
Is pricing public?
Yes. Starter is €9.99 EUR, Team is €49.99 EUR, and Business is €199.99 EUR. Plan limits are public and self-service starts in the app.
Own the thread. Finish the work.
Stop using email as a memory system.
Use Opkivo to own the thread, finish the task, and keep the answer searchable.