Keep the conversation together. Give your team the context.
A shared conversation timeline and AI-assisted routing workflow for supported channels. Channel count, provider support, reply actions and commercial availability are confirmed during onboarding.
Run it fully automated, or with a human in the loop — your call.
A shared conversation timeline and routing workflow can be scoped for supported channels.
Channel count, reply actions, provider support and commercial availability are confirmed before purchase.
See the complete product-status matrixWhat does Inbox do?
A shared conversation timeline and AI-assisted routing workflow for supported channels. Channel count, provider support, reply actions and commercial availability are confirmed during onboarding.
Key workflow
- Confirm supported channels: List the providers and message events available for the deployment before promising one cross-channel view.
- Test routing labels: Evaluate proposed categories such as Interested, Question, OOO and Not now against representative messages.
- Build the shared timeline: Store supported conversation events against the same lead record, with identity and retention rules agreed first.
From start to outcome.
Confirm supported channels
List the providers and message events available for the deployment before promising one cross-channel view.
Channel scopeTest routing labels
Evaluate proposed categories such as Interested, Question, OOO and Not now against representative messages.
Routing evaluationBuild the shared timeline
Store supported conversation events against the same lead record, with identity and retention rules agreed first.
One Record™Approve reply actions
Choose which replies may be drafted, sent, held for approval or handed to a person.
Auto · Ask · PingHow to validate this workflow.
Treat the page as a workflow description, not a promised outcome. Confirm commercial availability, providers, permissions and human-review points before implementation.
Evidence to collect
- Record the current baseline and the business outcome that matters.
- Test representative inputs, exceptions, interruptions and escalation paths.
- Review accuracy, latency, failure handling and operator workload.
- Approve rollout only against written acceptance criteria.
Why Inbox is different
Supported channels, one contact
Merge only the channels and identities confirmed for the deployment onto a shared record.
Evaluated AI triage
Test labels and routing thresholds before automating message handling.
Conversation workspace
Inbox handles messages and replies; Lead Management handles fields, scoring, ownership and stages.
Auto or human reply
Where a provider and reply action are enabled, Nate can draft, send, hold or hand off a routine reply under the configured approval rule.
Scoped history per contact
Keep the supported conversation events in one ordered timeline with configured retention.
Configurable safeguards
Apply quiet hours, consent requirements and suppression checks across supported channels.
Inbox is designed as the conversation layer for supported, enabled channel events on One Record™; it does not imply that every product or provider is connected by default.
Inbox questions, answered
A scoped conversation workspace that can place supported channel events and routing decisions on the shared lead record. Exact channel and action support is confirmed during onboarding.
It is designed to connect supported conversations to the same lead record used by Voice and Nate; it does not promise every channel or provider by default.
Only when the channel provider and reply action are included, connected and approved. The workflow can then draft, send, hold or hand off according to its Auto / Ask / Ping rule.
Support depends on the selected provider, permissions, message events and deployment. Culvion confirms the exact list before purchase.
Inbox is where teams read, triage and reply across channels. Lead Management owns qualification data, scoring, routing, stages and next steps.
Put Inbox to work today.
Choose the NATE capacity that fits your workflow — automated or with you in the loop.
Let’s make this
work for your team.
Bring your use case. We’ll discuss the workflow, what needs to connect and the scope of a practical pilot.
Or email sales@culvion.ai ↗Book a demo
Name and work email are required. We’ll contact you to arrange the demo.
