Odly
← All guides

Setup Guide

Set up Odly

Getting a workspace live takes minutes. Sign up, walk the guided onboarding wizard, and you're answering messages the same day. This guide covers the whole journey — signing up, the wizard, picking a plan, your first steps after signup, and the Enterprise Cloudextras (SSO & SCIM).
Part 1 · Get started

1 · Sign up

Every new organization starts on Free in a trial. Choosing a plan just tells the wizard which plan to offer a card for.

  1. Go to app.odly.ai/signup and create your organization.
  2. Landing links can deep-link a plan with ?plan=free|starter|pro|enterprise-cloud — every cloud plan is self-serve; only self-hosted is sales-assisted.
  3. Self-hosted is the one sales-assisted plan — contact us rather than signing up.
https://app.odly.ai/signup                       → Free trial (default)
https://app.odly.ai/signup?plan=starter          → offers a Starter card in the wizard
https://app.odly.ai/signup?plan=pro              → offers a Pro card in the wizard
https://app.odly.ai/signup?plan=enterprise-cloud → offers an Enterprise Cloud card
The ?plan value never charges you — it only decides which plan the wizard proposes at the end. Your org still begins on Free.

2 · The onboarding wizard

A short, guided setup you can pause and resume. It walks you through everything you need to go live.

In one sitting the wizard collects your:

  1. AI setup — managed AI or Bring your own keys (see below).
  2. Database — keep the managed database (on every plan, Free included, within its limits), or connect your own Postgres. It comes before channels so mail lands in the database you'll keep.
  3. Storage — Odly-managed, or your own S3-compatible bucket.
  4. Channels — connect an inbox so messages start flowing.
  5. Team — invite the people who'll work the inbox.
  6. Knowledge — add the docs Odly drafts from.
  7. Payment — only if you picked a paid plan: an embedded Stripe checkout at the very end. It's optional — skip it and your trial carries on.
Resumable. Hit Finish later any time and pick up where you left off. When you complete the wizard, Odly restamps a fresh 14-day trial — so the clock starts when you're actually ready.

3 · AI choice: Managed vs Bring your own keys

How Odly gets a model to draft answers depends on your plan.

Managed AI (paid plans)

Included on paid plans — Odly runs the model, no key needed. It activates on wizard completion only if your org has a verified admin email (anti-abuse). If unverified, it turns on the moment you verify.

Bring-your-own-key (Free)

On Free, managed AI is never available — switch the AI provider mode to Bring your own keys in Settings → Integrations → AI Providers and paste the key on a provider card; Free runs on the managed database within its limits, or on your own Postgres. Paid plans can also bring their own key if they prefer.

On Free you must bring your own key for AI features to work. There's no managed model on the Free plan.

4 · The 14-day trial & no card

Paid plans start free. You're never charged during the trial.

  1. The trial unlocks the full managed experience — all plan features, managed AI, ~10 seats and up to ~1,000 messages.
  2. Adding a card is optional. If you add one, the embedded checkout charges nothing during the trial; skip it and the trial carries on — set billing up later from Subscription.
  3. With a card saved, the Stripe subscription starts in trialing and converts automatically at day 14.
  4. On Free you can start with no card at all.
  5. If the trial ends without a card, the workspace moves to Free: your data stays, Free's limits apply and AI runs on your own key.
Want to explore before committing a card? Start on Free with your own AI key, and upgrade from Settings when you're ready.
Part 2 · Pick your plan

Plans at a glance

Every cloud plan is self-serve. Only self-hosted is sales-assisted.

Free

€0
Self-serve

2 agents · 500 msg/mo · 1 channel · 1 department · 2 GB

Your own AI key required — managed AI is never available on Free. Runs on the managed database within Free's limits; your own Postgres is optional.

Start on Free →

Starter

€150
Self-serve · 14-day trial

5 agents · 4,000 msg · 3 channels · 2 departments · 10 GB

Managed AI included — Odly runs the model, no key needed.

Start on Starter →

Pro

€500
Self-serve · 14-day trial

20 agents · 16,000 msg · 10 channels · unlimited departments · 100 GB

Adds Automate (auto-reply, lead qualification, learned auto-actions), advanced analytics, and bidirectional Jira.

Start on Pro →

Enterprise Cloud

€1,000
Self-serve · 14-day trial

50 agents · 40,000 msg · 25 channels · 1 TB

Adds SSO, SCIM & audit logs, plus an onboarding session within 5 business days and support replies within 1 business day. Bought self-serve like the tiers below it.

Start on Enterprise Cloud →
Part 3 · First steps after signup

5 · Connect a channel

Bring messages in from wherever your customers write.

In Settings → Integrations → Message Sources each source has an Add button — Add Email, Add Gmail, Add Telegram, Add Slack, Add WhatsApp:

  1. Email — any mailbox over IMAP/SMTP
  2. Gmail — a Google mailbox via OAuth sign-in
  3. Telegram bot
  4. WhatsApp through your own Meta Cloud API account
  5. Slack workspace
  6. Chat widget for your site — created under Settings → Integrations → Chat Widgets
You pick the source's departments inside the connect flow (Assign departments), so its mail lands with the right team.

6 · Invite teammates

On the Users page → Invite User. The dialog asks for Email Address, Workspace (fixed to the workspace you're working in — switch first to invite into another), Role, Departments and, when several mailboxes are connected, Send invitation from. Roles map to system names:

  1. Admin org_admin — runs the organization. Only a Platform Admin can grant it (their dialog shows Workspace Admin - Full control; everyone else sees "Org admins cannot invite other org admins").
  2. Manager moderator — leads the team (the Moderator option).
  3. Agent support — works the inbox (the Support option).
  4. Read-only associate — views and requests changes (the Associate option).

Invitees set their own password from the emailed link — someone who already has an Odly account keeps it; the invite just adds a membership. Workspace selection is per browser tab, and an admin can enforce 2FA org-wide under Settings → Workspace → Authentication (Require two-factor authentication).

7 · Set up AI

In Settings → Integrations → AI Providers.

On paid plans, managed AI is already on (once your admin email is verified). For your own key, switch the AI provider mode to Bring your own keys, pick a provider card, paste the key, choose a model and enable it — the same card runs a health test, enable/disable and delete. Keys are stored encrypted per-organization.

8 · Add departments

Optional — route messages to the right team.

Signup seeds all six defaults — Support, Sales, Billing, Info, HR, Marketing — and your plan decides which start active: Free starts with just Info (the org-wide default and routing fallback), Starter adds Support, Pro adds Sales. There's no Departments screen inside a workspace's own Settings — turning more on goes through your Odly platform contact (the platform console) or the API, within your plan's active-department budget. See the department one-pagers for how each team is scoped.

Part 4 · Enterprise Cloud extras

9 · Single Sign-On (OIDC)

Enterprise  Per-org OpenID Connect in Settings → SSO.

  1. Uses the authorization-code + PKCE flow. Providers: Google, Microsoft Entra ID, Okta, Auth0, or any compliant OIDC.
  2. Supply your issuer URL plus client ID / secret.
  3. Copy the shown callback URL into your IdP.
JIT provisioning auto-creates first-time users from allowed email domains with the read-only associate role (never admin) — and requires a verified email.

10 · SCIM 2.0 provisioning

Enterprise  Sync users and groups from your IdP in Settings → SCIM.

  1. Copy the SCIM Base URL and click Generate token — the bearer token is shown exactly once, so copy it now.
  2. Paste both into your IdP's provisioning config, then enable SCIM on the card.
  3. Push a group from the IdP, then map it → an org role + optional department(s). Highest role wins; departments union.
Deprovision is a soft delete. Setting a user inactive frees the seat, revokes sessions and reassigns their tickets — but keeps rows for reactivation.