Starter
For small teams starting with one operational inbox.
- 3 users
- 1 inbox
- 1 IMAP connection
- Customer SMTP route
- 500 storage units
- 10 assets
- No public knowledge base domain
Start small. Add inboxes, users, knowledge domains, and storage as the work grows.
For small teams starting with one operational inbox.
For teams running support across multiple inboxes.
For teams managing more inboxes, people, and knowledge.
Need a different setup? Contact us.
FAQ
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.
For support work, yes. Gmail can still exist as the underlying mail system, but the daily support workflow should happen inside Opkivo.
No. Opkivo can link context from external systems, but it does not try to become your CRM.
No. Email based automatic tagging is intentionally avoided in the first version because wrong context is worse than missing context.
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.
If the thread has open tasks, Opkivo asks the user to review them or close the tasks with the thread. Work cannot disappear quietly.
Plan limits are public. Commercial pricing can be shown if configured, otherwise visitors can request access.
Own the thread. Finish the work.
Request access and we will review the right setup for your shared inboxes, tasks, and knowledge base.