Question 1

What pricing tiers does InboxOps offer?

Accepted Answer

InboxOps ships three tiers: Starter ($99/mo, 500 auto-resolutions, 1 seat, email + chat), Growth ($299/mo, 2,500 auto-resolutions, 3 seats, all channels including the web widget and Intercom), and Scale ($599/mo, 10,000 auto-resolutions, unlimited seats, +Zendesk integration, named onboarding contact during early access). There are never seat fees. Overage resolutions are billed per-resolved at the rate listed on the pricing page.

Question 2

Which channels are supported on each plan?

Accepted Answer

Starter supports Email and Chat. Growth adds the Web widget so visitors can submit questions from your site, plus the Intercom integration. Scale keeps the same channel set as Growth and layers the Zendesk integration on top. Channels surface here reflect what is wired today, not what we plan to launch.

Question 3

Does setup require a developer?

Accepted Answer

No — but it does require a working session with us. Onboarding is a guided flow: you connect the integrations you already use (Intercom and Zendesk today), your historical tickets and help center content import, and we tune tone and escalation rules together with you over the first sessions. The full flow lives at /onboarding.

Question 4

How does the widget look in the wild?

Accepted Answer

The InboxOps widget renders as a small IO tile anchored to your site footer. Visitors tap to expand it, fill in a name and message, and submit. After submission they see a confirmation panel; matched questions show the prior answer, unmatched ones tell the visitor the team will reply by email.

Question 5

Where is submission data stored?

Accepted Answer

Every widget, webform, and email submission is persisted to a Postgres database managed for your InboxOps workspace. The authenticated /api/outcomes surface and the public /outcomes dashboard expose the resulting ticket, decision, confidence, and reply — only signed-in admins can read raw rows, and no data is used to train shared models.

Question 6

How does widget-to-email handoff work?

Accepted Answer

The widget posts to /api/widget/submit (typed contract WidgetSubmitResponse). The route persists an Outcome row, runs the resolver, and replies with the matching outcome id plus any prior similar answer. Unmatched submissions queue on /outcomes for human review and the visitor receives a confirmation panel; matched submissions can be auto-replied or escalated depending on the resolver confidence threshold.

Frequently asked questions

Ready to put InboxOps on it?