Skip to Content
Contact Us

Adomo Help Center

Search our knowledge base or browse articles below

Getting Started

Who is this for? Everyone new to Adomo. A short tour of what's in the app and where to go first.

Adomo is a single place where your AI workflows live, run, and ask for help. This article gives you the shortest path from signing in to your first useful run.

Sign in

Open app.adomo.ai and sign in with your work email. If your company has set up single sign-on, click the SSO option and you'll be redirected to your identity provider.

First time here? You'll land on the workspace your admin invited you to. If you don't see anything, ask your admin to check that they've added you.

The sidebar, in plain English

  • Home - a summary of what's running, what's waiting on you, and what ran recently.
  • Workflows - the automations you can run or manage. Think of each workflow as a standard operating procedure that Adomo executes on your behalf.
  • Runs - every execution of a workflow, past and present, with full step-by-step detail.
  • Approvals - anything waiting for your decision, in one list.
  • Meetings - the agent's history in your Zoom calls (see Meeting Agent).
  • Settings - your profile, notifications, and personal integrations.
  • Admin (admins only) - workspace-wide settings: users, channels, integrations, models, workflows, billing.

Do three things in your first 10 minutes

  1. Set your notification preferences. Open Settings > Notifications and add at least one contact method (email is fine). This is how Adomo reaches you when a workflow needs your decision. Full details in the Notifications article.
  2. Run a workflow end-to-end. Open Workflows, pick one that's been shared with you, and click Run. Watch it execute step by step in Runs and approve any prompts it sends you.

Are you a workspace admin?

Workspace setup (enabling channels, connecting business systems, inviting users, turning on the meeting agent) lives in the Admin Guide tab at the top of this page. Switch tabs to see those articles.

Tips

  • Everything is searchable. The search bar in the top nav searches workflows, runs, approvals, and articles in this help center.
  • Approvals come to you. You don't need to stay in the Adomo app to respond - approvals land in Email, SMS, Slack, Teams, or WhatsApp depending on your preferences.
  • Nothing runs silently. Every workflow execution is visible in Runs with inputs, outputs, approvals, and timing. If you ever wonder "what did the AI do here?", that's where you look.
  • Ask the agent. If the Adomo meeting agent is enabled in your Zoom meetings, you can ask it for a report, a customer lookup, or to start a workflow without leaving the call.

What to read next

  • Notifications - control how Adomo reaches you.
  • Meeting Agent (Zoom) - put an AI teammate in your meetings.
  • Account - sign-in, profile, two-factor authentication, personal integrations.

Platform

Platform Guide

Getting Started

Log in to your Adomo dashboard at app.adomo.ai to access all platform features. Your dashboard provides an overview of key metrics, recent activity, and quick actions.

Dashboard Overview

The main dashboard displays real-time data about your business operations, including sales performance, customer interactions, and team productivity.

Roles and Permissions

Adomo supports role-based access control. Administrators can assign roles to team members to control access to different modules and data. Contact your account administrator to request permission changes.

Integrations

Integrations

Available Integrations

Adomo connects with popular business tools including email providers, calendar apps, payment processors, and communication platforms.

Setup

Navigate to Settings > Integrations to view available connectors. Each integration includes step-by-step setup instructions and configuration options.

Troubleshooting

If an integration is not syncing properly, verify your API credentials, check that the third-party service is operational, and review the sync logs under Settings > Technical > Integration Logs.

Account

Account Management

Creating an Account

Visit app.adomo.ai/signup to create a new account. You will need a valid email address and will be asked to verify it before accessing the platform.

Password Reset

Click "Forgot Password" on the login page to receive a reset link via email. The link expires after 24 hours. If you do not receive the email, check your spam folder or contact support.

Profile Updates

Update your name, email, phone number, and notification preferences under My Profile in the top-right menu.

Billing

Billing and Subscriptions

Plans and Pricing

Adomo offers flexible plans to match your business needs. Visit adomo.ai/pricing for current plan details and feature comparisons.

Managing Subscriptions

View and manage your subscription under Settings > Billing. You can upgrade, downgrade, or cancel your plan at any time. Changes take effect at the start of your next billing cycle.

Invoices

Download invoices from Settings > Billing > Invoice History. Invoices are generated on the first of each month and sent to your billing email address.

Notifications (for Users)

Who is this for? Everyone who uses Adomo. This article covers how you personally get notified about approvals and updates, and how to change it. If you're a workspace admin turning on Slack, Teams, SMS, email, or WhatsApp for your whole team, see Channels Setup instead.

When Adomo (or a teammate) needs your attention, it reaches you through the channels your admin has enabled and the preferences you've set. You can approve, reject, or reply right from the message, or click through to see more context in the app.

Where to set your preferences

Open Settings > Notifications in the top-right menu. You'll see three things to configure.

1. Your contact methods

These are the addresses Adomo uses to reach you. Add the ones you want to be reachable on:

  • Email - the address you want notifications sent to.
  • Phone (SMS) - an E.164 number like +14155551234. When you add a phone number, you'll see a consent checkbox with the workspace's SMS disclosure and a link to the SMS Messaging and Opt-In article. You must tick the box for Adomo to send you SMS; until you do, SMS is skipped and outbound notifications fall through to your next channel. You can untick it at any time to stop SMS.
  • Slack - your work email or Slack handle. Your admin's Slack app has to be installed in your workspace first.
  • Microsoft Teams - your work email / UPN (for example, [email protected]).
  • WhatsApp - an E.164 number like +14155551234.

You only need to enter addresses for the channels you actually want to use.

2. Your preference order

This is the order Adomo tries your channels in. For example:

  1. Slack
  2. SMS
  3. Email

If you don't respond on the first channel within the workflow's time window, Adomo moves to the next one, and so on.

3. In-app and mobile push

Two extra channels are available automatically:

  • In-app - approval requests always show up in your Adomo inbox when you're signed in. You don't enter an address.
  • Mobile push - if you've installed the Adomo mobile app and signed in, push notifications are delivered to your device automatically.

You can include these in your preference order the same way as the other channels.

What a notification looks like

Every approval notification includes:

  • A short summary of what's being asked.
  • Approve and Reject buttons (or a deep link that takes you to the approvals page, depending on the channel).
  • A link to the full context in the Adomo app: the workflow, the run, and any relevant history.

All decisions are attributable to you personally and are logged with a timestamp.

FAQ

Can I approve from my phone without the app?

Yes. Email, SMS, Slack, Teams, and WhatsApp all include a link or button that records your decision. The mobile app is a convenience, not a requirement.

I keep getting pinged. How do I quiet things down?

Shorten your preference order to one or two channels, and remove the ones you don't want. Everything still lands in your in-app inbox, so you won't miss it.

I'm not getting any messages. What should I check?

  1. Open Settings > Notifications and confirm you've entered a contact method for the channel you expect.
  2. Confirm the channel is enabled for your workspace. If, for example, Slack shows no options at all, ask your admin whether Slack has been set up under Admin > Channels.
  3. Check the workflow's run history in the app - you'll see whether a notification was attempted for you and what the outcome was.
  4. If you're still stuck, contact support.

What if I'm on vacation?

Ask your workspace admin to add a fallback approver on the workflows that route to you, or delegate approvals to a colleague for the period you're away. (The specific delegation UI depends on your workspace configuration.)

Where do I see everything that's been sent to me?

Your Adomo inbox in the app shows every notification you've received, along with the decision you made and when.

Channels Setup (for Admins)

Who is this for? Workspace admins enabling Email, SMS, Slack, Microsoft Teams, or WhatsApp for the whole workspace. If you're an individual user looking to change how you personally get notified, see the Notifications article instead.

Adomo reaches your team where they already work. Once you enable a channel here, each user picks their own preferred order (for example, Slack first, SMS as a fallback) under Settings > Notifications, and Adomo tries their channels in that order until someone responds.

How to set up a channel (at a glance)

  1. Sign in to Adomo as an admin.
  2. Go to Admin > Channels and pick the tab for the channel you want to enable (Email, SMS, Slack, Teams, WhatsApp).
  3. Paste the credentials from the provider (see the guide below for each).
  4. Click Test Connection. Adomo verifies with the provider without sending a real message, so you can set things up safely.
  5. Click Save. The channel is now available for approvals and notifications across your workspace.

Each user then picks how they want to be reached under Settings > Notifications.

Email

Adomo can send email two ways: through a standard SMTP relay (simplest when you already have one), or through Gmail / Microsoft 365 with OAuth2 (recommended for personal Gmail accounts, since Google no longer allows basic-auth SMTP from most accounts).

Option A: SMTP relay (basic)

Works with services like SendGrid, Postmark, Amazon SES, Mailgun, or your own corporate mail server.

  1. Create (or log in to) your relay account and create an API key or SMTP credentials.
  2. In Adomo under Admin > Channels > Email, fill in:
    • SMTP host and SMTP port (usually 587 with STARTTLS, or 465 with SSL).
    • From address - must be a verified sender on your relay.
    • SMTP username and SMTP password (the API key or credentials from step 1).
  3. Leave Auth type on basic.
  4. Click Test Connection, then Save.

Option B: Gmail with OAuth2

Best for personal Gmail or Google Workspace accounts.

  1. In Google Cloud Console > Credentials create a project and add an OAuth 2.0 Client ID (Web application).
  2. Enable the Gmail API.
  3. Use the OAuth Playground (or your own flow) to obtain a refresh token for the scope https://mail.google.com/. In the Playground, click the gear icon, tick Use your own OAuth credentials, and paste your Client ID and Secret.
  4. In Adomo under Admin > Channels > Email, set:
    • SMTP host: smtp.gmail.com
    • SMTP port: 465, Secure: on
    • Auth type: oauth2
    • Paste Client ID, Client Secret, Refresh Token, and Username (the Gmail address you're sending from).
  5. Click Test Connection, then Save.

Option C: Microsoft 365 / Outlook with OAuth2

  1. Register an app at Azure AD > App registrations.
  2. Add the delegated permission SMTP.Send on Microsoft Graph and grant admin consent.
  3. Obtain a refresh token via the authorization code flow.
  4. In Adomo under Admin > Channels > Email, set:
    • SMTP host: smtp.office365.com
    • SMTP port: 587
    • Auth type: oauth2
    • Paste the Client ID, Secret, Refresh Token, and your mailbox address.
  5. Click Test Connection, then Save.

How Test Connection works for email. Adomo logs in to your SMTP server to verify authentication. No email is sent, so there's no delivery or charge.

SMS (Twilio)

Adomo uses Twilio for SMS delivery. You'll need a Twilio account and either a provisioned number or a Messaging Service.

  1. Sign up at twilio.com/try-twilio. The free trial includes a provisioned number.
  2. In the Twilio Console home panel, copy the Account SID and Auth Token.
  3. Under Phone Numbers > Active numbers, copy a number in E.164 format (for example +14155551234).
  4. In Adomo under Admin > Channels > SMS, paste the Account SID, Auth Token, and the From Number.
  5. Click Test Connection, then Save.

SMS compliance: opt-in consent (required)

Adomo blocks SMS dispatch to any number until a recorded consent exists for that number. To make that work, you also need to fill in two compliance fields on the SMS admin page. Both are required before SMS will dispatch at all.

  • SMS Opt-In Proof URL (smsOptInProofUrl) - a public URL that describes how your end users opt in to SMS. This is the URL you submit to Twilio / the downstream carriers during brand and campaign registration. Adomo ships with a ready-to-use public article, SMS Messaging and Opt-In, in this help center; paste its public URL here (for example, https://<your-help-center-host>/helpdesk/.../sms-opt-in once the knowledge base is deployed). Users also see this link next to the consent checkbox in their Notifications settings.
  • SMS Opt-In Disclosure (smsOptInDisclosure) - the short consent text shown to users when they add an SMS contact method. A sensible default ships with the product; override it only if your legal or compliance team requires different wording. Example: > I consent to receive transactional SMS from this platform at > the number above. Reply STOP to opt out. Msg & data rates > may apply.

After you save these, users see the disclosure text + the proof URL + a consent checkbox when they add their phone number under Settings > Notifications. They must tick the checkbox for SMS to dispatch; otherwise outbound notifications fall through to the next channel in their preference order.

For external authorities (outside approvers who don't sign in to Adomo directly), admins attest consent on behalf of the external authority under Admin > DOAG > External Authorities.

SMS compliance: STOP / HELP handling

Adomo handles inbound carrier keywords automatically through the Twilio inbound webhook:

  • STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT - the number is added to the workspace's suppression list and no further SMS is sent to it, regardless of consent status.
  • START, UNSTOP, YES - the number is removed from suppression.
  • HELP, INFO - a TwiML help reply is returned automatically.

No admin action is required for these - wire up the Twilio inbound webhook URL shown on the SMS admin page during your Twilio number configuration and the behavior is automatic.

US registration (10DLC, toll-free, short code)

For US traffic you must register a brand and campaign in Twilio before messages deliver reliably. See Twilio's 10DLC guide for long codes, or the equivalent toll-free verification / short-code flow for those number types. For EU traffic, follow Twilio's regional equivalent.

During registration, paste the SMS Opt-In Proof URL you configured above into the "proof of consent" field that Twilio and the carriers require.

Reference

Contact methods for SMS are E.164 phone numbers (+14155551234).

How Test Connection works for SMS. Adomo verifies your credentials by calling a read-only Twilio endpoint. No SMS is sent, so you aren't charged.

Before you enable SMS for your workspace. Read the SMS Messaging and Opt-In article in this help center and confirm your workspace's usage is consistent with it (operational messages only, never marketing, recipients opt in via the app). If you need to send message types or volumes outside that scope, contact your account team first.

Slack

Adomo posts approval requests to Slack via a Slack app installed in your workspace. Users can reply right from the message.

  1. Go to api.slack.com/apps > Create New App > From scratch. Give it a name (for example "Adomo") and pick the target workspace.
  2. Open OAuth & Permissions > Scopes and add these Bot Token Scopes:
    • chat:write - post messages
    • chat:write.public - post to channels the bot isn't a member of
    • users:read and users:read.email - resolve users by email
    • im:write - open DMs for per-user approval routing
  3. Click Install to Workspace and approve.
  4. Copy the Bot User OAuth Token (starts with xoxb-).
  5. In Adomo under Admin > Channels > Slack, paste the token.
  6. Click Test Connection, then Save.
  7. (Optional) Invite the bot to any channel it should post to (/invite @adomo). With chat:write.public you can skip this.

Contact methods for Slack accept any of:

  • user email
  • @username
  • a Slack user ID like U01ABCDEFG
  • a channel like #channel or a channel ID C01ABCDEFG

How Test Connection works for Slack. Adomo calls Slack's auth.test endpoint to verify the token. No message is posted.

Microsoft Teams - Incoming Webhook (simple, one channel)

Use this option if you just want approval cards posted to a single Teams channel. Everyone in that channel can see the card. This is quick to set up but not suitable for sensitive approvals - there's no per-user identity, so anyone in the channel could click the button. For DMs, group chats, or per-user routing, use the Teams (Graph) option below instead.

  1. In Microsoft Teams, open the target channel and pick ... > Connectors (or Manage channel > Connectors in newer UI).
  2. Search for Incoming Webhook, click Configure, give it a name (for example "Adomo Approvals"), and optionally upload an icon.
  3. Click Create and copy the generated webhook URL.
  4. In Adomo under Admin > Channels > Teams, paste the URL into Teams Webhook URL.
  5. Click Test Connection, then Save.

Limitations. Webhooks post to exactly one channel, only support "Open URL" buttons (no in-chat Approve/Reject), and have no user identity. Don't use webhooks for sensitive approvals.

How Test Connection works for Teams webhook. Adomo posts a small "Connection test" card to the channel so you can confirm it lands.

Microsoft Teams - Graph (per-user DMs, group chats, channels)

This is the full Teams integration. It supports 1:1 direct messages, group chats, and channel posts, and it preserves per-user identity so only the right person can approve.

1. Register an app in Azure AD

  1. Open Azure Portal > App registrations and click New registration.
  2. Name it (for example "Adomo Teams Approvals") and choose Accounts in this organizational directory only.
  3. From the app's Overview page, copy the Application (client) ID and the Directory (tenant) ID.

2. Add API permissions

Under API permissions > Add a permission > Microsoft Graph > Application permissions, add:

  • Chat.ReadWrite.All - create and post 1:1 / group chats
  • User.Read.All - resolve users by email / UPN
  • Organization.Read.All - used by Test Connection
  • ChannelMessage.Send - only needed if you'll post to team channels

Click Grant admin consent for <your tenant>. Every row must show the green checkmark.

3. Create a client secret

Under Certificates & secrets > Client secrets > New client secret, create one and copy the Value (not the Secret ID). This is shown only once.

4. Save the credentials in Adomo

In Admin > Channels > Teams (Graph), paste the Client ID, Tenant ID, and Client Secret. Click Test Connection, then Save.

5. (Optional) Enable in-chat Approve / Reject buttons

By default, Teams messages include an Open Adomo button that takes the approver to the Adomo approvals page in a browser. If you want the Approve and Reject buttons to work directly inside the Teams chat:

  1. Create an Azure Bot resource. Choose Multi-tenant and reuse the App ID from step 1 (or create a new one).
  2. Set the bot's messaging endpoint to the URL shown in Adomo under Admin > Channels > Teams (Graph) > Bot mode (copy the URL displayed there; it's specific to your workspace).
  3. In the bot's Channels blade, add the Microsoft Teams channel.
  4. Author a Teams app manifest for the bot. The easiest path is Teams Developer Portal, which lets you edit the manifest visually; otherwise see the manifest schema docs. Export the .zip package.
  5. Upload the manifest to Teams Admin Center > Manage apps > Upload new app. Users in your tenant then install the app (or an admin pre-installs it). Proactive 1:1 DMs only deliver after install.
  6. In Adomo, enable Bot mode and paste the Bot App ID.

Contact methods for Teams (Graph)

Any of:

  • [email protected] - resolved by email or UPN (delivers a 1:1 DM)
  • user:<aad-object-id> - direct Azure AD user ID (1:1 DM)
  • group:<chat-id> - existing Teams group chat
  • team:<teamId>/channel:<channelId> - post in a team channel

WhatsApp (Meta WhatsApp Business Cloud API)

Adomo uses Meta's WhatsApp Business Cloud API. You'll need a Meta developer account, a WhatsApp Business Account (WABA), and a verified phone number. WhatsApp requires pre-approved message templates for any message sent outside a 24-hour active conversation - this is Meta's rule, not Adomo's.

  1. Create a Meta app at developers.facebook.com/apps. Choose Business as the app type.
  2. Add the WhatsApp product. Meta gives you a test phone number you can use immediately. For production, add and verify your own number.
  3. Copy the Phone number ID (numeric).
  4. In Meta Business Manager, create a System User and generate a permanent access token with the whatsapp_business_messaging and whatsapp_business_management permissions.
  5. Create a message template (category Utility or Authentication) named, for example, approval_request, with placeholders for the request details. Adomo uses your template for proactive messages.
  6. In Adomo under Admin > Channels > WhatsApp, paste the Phone number ID and the access token.
  7. Click Test Connection, then Save.

Contact methods for WhatsApp are E.164 phone numbers (+14155551234).

How Test Connection works for WhatsApp. Adomo fetches phone-number metadata from Meta's Graph API. No WhatsApp message is sent.

Admin FAQ

Can I enable more than one channel at once?

Yes. Enable any combination. Each user then picks their own preference order under Settings > Notifications.

Can I test channels without bothering real users?

Yes. Test Connection on each channel verifies credentials with the provider without sending a real message. The one exception is Teams Webhook, which has no silent test option on Microsoft's side, so Adomo posts a small "connection test" card to the channel only.

Where do I see delivery history?

Each approval's timeline in the Adomo app shows which channels were attempted, in what order, and what the response was. Admins can also view cross-workspace delivery activity under Admin > Channels > Activity.

What happens if a user hasn't set any contact methods?

The approval still records, and the user sees it in-app when they next sign in. No outbound message is sent. Remind users to set their contact methods under Settings > Notifications after you enable channels.

What happens if a channel fails for a given user?

Adomo tries the next channel in that user's preference order. If no channel responds within the workflow's configured time window, the approval escalates to the fallback approver defined on the workflow (if any), and the timeout is logged.

How do I rotate a credential?

Open the channel's tab in Admin > Channels, paste the new credential, click Test Connection, then Save. Previous credentials are overwritten.

Where do approvers actually change their own preferences?

They do it themselves under Settings > Notifications (see the Notifications article). Admins don't manage per-user contact methods.

Meeting Agent (Zoom)

Who is this for? This article has two parts. For Users covers how to use the meeting agent in your Zoom calls. For Admins covers how to set Adomo up in Zoom and control what the agent is allowed to do.

The Adomo meeting agent joins your Zoom meetings as a quiet participant, listens for a wake word, and responds when spoken to. It can pull a report, look up a customer, draft a follow-up, or kick off a workflow on the spot, on behalf of whoever asked. When the meeting ends, it leaves a summary behind.

The agent acts as a real teammate: it only does what the person asking is authorized to do, every action is logged, and anything sensitive pauses for explicit approval the same way it would outside the meeting.

For Users

What you can ask the agent to do

Anything Adomo can do for you outside the meeting, phrased in plain English. For example:

  • "Adomo, what was last quarter's pipeline coverage for the West region?"
  • "Adomo, pull up the renewal workflow for Acme and tell me where it stands."
  • "Adomo, draft a follow-up email to the customer summarizing what we just agreed."
  • "Adomo, kick off the vendor onboarding SOP for the company we just discussed."

The agent replies in the meeting (text shown in the in-meeting panel, and read back if your admin has enabled voice), and for anything that changes data or sends a message, you get an approval step back in Adomo before it runs.

When the agent is (and isn't) listening

The agent only acts when it hears the wake word your admin has configured (by default, "Adomo"). Until then, nothing is processed by the LLM. Speech is transcribed live by Zoom's own real-time media service, and the agent receives only the lines it needs to respond to.

You'll see a visible indicator in the Adomo in-meeting panel whenever the agent is listening for a wake word, and a second indicator when it's actively processing a request. Meeting summaries and the transcript are retained according to your workspace's data retention settings, which your admin controls.

Link your Zoom account (one-time)

So the agent can act "as you" during meetings, you link your Adomo account to your Zoom identity once:

  1. In Adomo, open Settings > Integrations > Zoom.
  2. Click Connect Zoom.
  3. Sign in to Zoom and approve the permissions.
  4. You'll be returned to Adomo with a "Connected" status.

The linked status also shows on your profile. Your admin can see which users are linked and can unlink anyone if needed.

If you don't link your Zoom account, the agent still listens in meetings you're in, but will treat you as an external participant: it will answer general questions but won't use tools or take actions on your behalf.

Join a meeting with the agent

If your workspace has installed the Adomo Zoom app, the agent is already available in your meetings. Depending on how your admin set it up, it either joins automatically when you start a meeting, or you invite it with a button in the Adomo app panel inside Zoom.

During the meeting you can open the Adomo panel in Zoom to see:

  • Whether the agent is connected
  • Recent transcripts with any wake-word hits highlighted
  • The agent's responses
  • Any approval requests the agent raised

What the agent will not do

  • Take actions beyond your own permissions. If you can't do it in the Adomo app, the agent can't do it for you in the meeting either.
  • Act on behalf of someone who hasn't linked their Zoom account. External participants get general answers only, no tool use.
  • Bypass approvals. Anything that requires a human sign-off outside the meeting still requires it here.
  • Auto-escalate. If a request needs admin or builder permissions you don't have, the agent tells you that in plain language rather than trying anyway.

User FAQ

Can I mute it? Yes. The agent only acts on wake-word hits, so simply not using the wake word is the easiest "mute". You can also disable the Adomo app for a specific meeting from the Zoom apps panel.

What if two people say the wake word at once? The agent processes the first clear request and ignores overlapping speech until it finishes. You'll see which participant it resolved the request to in the panel.

Can I review what it did? Yes. After the meeting, open the session in Adomo > Meetings to see every transcript segment that triggered the agent, every response it gave, and every tool or approval it ran.

For Admins

Setting up the meeting agent has four pieces:

  1. Create a Zoom Marketplace app and connect it to Adomo.
  2. Configure what the meeting agent is allowed to do.
  3. Have users link their Zoom identities.
  4. (Optional) Review meeting sessions in the admin panel.

1. Create a Zoom Marketplace app

  1. Go to marketplace.zoom.us and sign in with a Zoom account that can create apps for your organization.
  2. Click Develop > Build App and choose the General App type.
  3. Set the app's Redirect URL and Webhook Endpoint URL to the URLs shown in Adomo under Admin > Integrations > Zoom > Add App. Copy them exactly from the Adomo page - they're specific to your workspace.
  4. Under Scopes, add the scopes needed for the meeting agent:
    • user:read - identify the user who installs the app
    • meeting:read - read meeting metadata
    • Real-time media (RTMS) scopes, as listed on the Adomo setup page
    • Any additional scopes for tools you plan to expose (for example, cloud recording read if you want the agent to reference past meetings)
  5. Under Event Subscriptions, subscribe to the meeting and RTMS events listed on the Adomo setup page.
  6. In the Zoom app's App Credentials section, copy:
    • Client ID
    • Client Secret
    • Secret Token
    • Verification Token
  7. In Adomo, paste each value into the matching field under Admin > Integrations > Zoom > Add App, then click Validate & Save. Adomo performs a health check against the Zoom API and reports success or a specific error.
  8. Publish or distribute the app according to your org's Zoom policy. Most customers use an internal ("intra-account") app so only people in your Zoom account see it.

If credentials later expire or get revoked, the connection will show as Expired or Error in Admin > Integrations > Zoom with a link to re-authenticate.

2. Configure the meeting agent

Open Admin > Meeting Agent and set:

  • Enable meeting agent - on / off for the workspace. Off means users can't start agent-enabled meetings at all, even if the Zoom app is installed.
  • LLM model - which model the agent uses. Only models approved for your workspace appear here.
  • System prompt - the base instructions for the agent (tone, guardrails, what to decline). A sensible default is prefilled.
  • Wake words - one or more trigger phrases (for example, "Adomo", "Hey Adomo"). The agent ignores everything else.
  • Allowed tools - the set of Adomo tools the agent may use during meetings. Only tools with an active connection appear here. If a tool isn't in this list, the agent cannot call it during a meeting, even if a user has access to it in the app.

If you haven't configured the meeting agent, users can't start sessions. There is no implicit default set - this is intentional, so nothing runs in live meetings without admin consent.

Enabling or disabling the agent takes effect on the next meeting start. Meetings already in progress continue until they end.

3. User identity linking

For the agent to act on behalf of a specific participant, that participant must have linked their Adomo account to their Zoom identity.

  • Users do this themselves from Settings > Integrations > Zoom (see the user section above).
  • Admins can see every user's link status (Linked / Not linked / Expired) under Admin > Users.
  • Admins can manually unlink a user at any time, which revokes Adomo's stored OAuth token and clears the identity mapping.

What happens to participants who aren't linked. The agent treats them as unauthenticated external participants: they can ask general questions and get LLM-only answers, but the agent will not call tools or take actions on their behalf. This is the conservative default and cannot be loosened.

4. Review meeting sessions

Admin > Meetings shows every meeting the agent has joined, with:

  • Meeting title, start and end times, and Zoom meeting ID
  • Which workspace users participated and which were linked
  • Every wake-word hit, the transcript segment that triggered it, the agent's response, any tools invoked, and any approvals raised
  • Errors or reconnection events (for example, if the RTMS stream dropped mid-meeting)

Use this panel to audit the agent's behavior, debug failed sessions, and review the agent's behavior for debugging or auditing purposes.

Security model (what the agent can and can't do)

  • Per-user scoping. When the agent invokes a tool during a meeting, it uses the requesting participant's identity and credentials, not a shared service account. If the participant can't do something in the Adomo app, they can't do it via the agent either.
  • No privilege escalation. If a request requires admin or builder permissions the participant doesn't have, the agent declines in plain language and logs the denial in the audit trail.
  • No ambient authority for external participants. Anyone without a linked Adomo identity gets LLM-only answers.
  • Approvals still apply. Tool invocations that require sign-off outside the meeting still require sign-off here. The approval is routed through the participant's normal notification channels (see Notifications).
  • Everything is logged. Every transcript segment that triggered the agent, every tool call, every approval, and every denial is recorded on the meeting session and available in the admin panel.

Admin FAQ

Can I limit the agent to certain meetings? Yes. The Adomo Zoom app is installed per user / per meeting in the standard Zoom Marketplace way. Combine that with the Allowed tools list to control both where the agent runs and what it can do when it does.

Can I disable the agent for the whole workspace temporarily? Yes. Toggle Enable meeting agent off in Admin > Meeting Agent. Active meetings continue until they end; no new meetings will use the agent.

How do I rotate Zoom app credentials? Update them in the Zoom Marketplace, then paste the new values into Admin > Integrations > Zoom and click Validate & Save. The old values are overwritten.

What about data retention? Meeting transcripts and summaries follow your workspace's data retention policy. Ask your account team if you need a retention setting that's different from the default.

Does the agent join meetings without anyone inviting it? Only meetings where the Adomo Zoom app has been installed and permitted, according to your Zoom Marketplace app configuration. If the app isn't installed on a given meeting, the agent doesn't join.

Can I restrict which tools the agent uses for which users? Tool access is enforced by each user's existing Adomo permissions. To limit what a specific user's agent can do, adjust that user's role and tool-connection access the same way you would for the rest of the Adomo app.

SMS Messaging and Opt-In

Who is this for? End recipients of Adomo SMS messages, and the mobile carriers who require a publicly reachable description of how consumers consent to receive messages from our numbers. This article is the canonical URL Adomo submits for SMS registration (10DLC, toll-free, short code).

Adomo sends SMS messages on behalf of our customers (workspace admins) to reach their own team members and approved contacts with operational, transactional, and notification content. Adomo itself does not send marketing SMS, and does not use any third party's phone number without that third party's explicit opt-in.

Who we are

What messages we send

Adomo SMS messages are strictly operational. They fall into these categories:

  • Approval requests. A short summary of an item awaiting the recipient's decision, plus a secure link to review and respond.
  • Status updates. Confirmation that an approval was recorded, that a workflow completed, or that a scheduled job ran.
  • Account security. Sign-in codes, password reset codes, and two-factor authentication (2FA) codes when the recipient is signing in to their Adomo account.
  • Direct user-to-user notifications. When another authorized member of the recipient's workspace directs Adomo to notify the recipient about a specific piece of work.

We do not send marketing messages, promotional offers, or third-party advertising via SMS.

How consumers opt in

Adomo SMS is never sent to a phone number until the owner of that number has given explicit, affirmative consent to receive SMS through the Adomo app. There are two equivalent consent flows, both of which record the consent with a timestamp so that proof of opt-in is retained for the lifetime of the relationship:

  1. Self-service consent in the Adomo app. The recipient signs in to Adomo, opens Settings > Notifications, and enters their own mobile phone number as a contact method. Inline with that phone number, Adomo displays a consent checkbox labeled with the workspace's SMS disclosure text and a link to this article. The default disclosure text is: > I consent to receive transactional SMS from this platform at > the number above. Reply STOP to opt out. Msg & data rates > may apply. (Workspace admins may customize this text; the link to this article is always present.) The recipient must explicitly tick the checkbox to consent. Adomo records the consent boolean and timestamp on the contact method. Until the box is ticked, Adomo will not dispatch any SMS to the number; outbound notifications fall through to the next channel in the recipient's preferences.
  2. Admin attestation for external authorities. When a workspace admin provisions an SMS contact method for an external authority (for example, an outside approver who does not sign in to Adomo directly), the admin sees the same disclosure text and the same checkbox in the admin External Authorities tab and attests, on the record, that the external authority has consented out-of-band (typically via a signed agreement, a written authorization, or an equivalent record the workspace keeps on file). As with user self-consent, Adomo blocks SMS dispatch to the number until the attestation is recorded.

Adomo does not purchase, rent, or otherwise acquire phone numbers from third-party lists, and does not send SMS to any number whose record does not carry a recorded consent.

Message frequency

Message frequency varies with the recipient's workspace activity. Typical recipients receive approximately 1 to 10 messages per week. Busier workspaces or higher-volume approvers may receive more. A typical workspace sends no marketing SMS.

Message and data rates

Message and data rates may apply. Adomo does not charge the recipient for messages; however, standard messaging rates from the recipient's mobile carrier apply.

How to get help

Reply HELP to any Adomo SMS message to receive support contact information, or email [email protected], or call +1 (866) 995-4498.

How to opt out

At any time, the recipient may stop receiving Adomo SMS messages by any of these methods:

  • Reply STOP to any Adomo SMS. The following keywords are all recognized and handled automatically: STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT. The number is added to our suppression list immediately, one confirmation message is sent, and no further SMS will be dispatched to the number.
  • Reply HELP to any Adomo SMS to receive support contact information. HELP and INFO are both recognized.
  • Untick consent or remove the number in the app. Sign in, open Settings > Notifications, and either untick the SMS consent checkbox or remove the mobile phone number from the contact methods list. SMS dispatch stops immediately.
  • Contact support. Email [email protected] or call +1 (866) 995-4498. We will remove the number from all outbound SMS within one business day.

Opting out of SMS does not cancel the recipient's Adomo account or remove them from their workspace. The recipient may continue to receive approval requests and notifications through other channels (email, Slack, Microsoft Teams, WhatsApp, in-app, mobile push) if they have configured them.

After opting out, the recipient may opt back in at any time by re-ticking the consent checkbox in Settings > Notifications, or by replying START (or UNSTOP or YES) to an Adomo number.

Data handling

  • Phone numbers are stored encrypted and are used only for the purposes described above.
  • Adomo does not share, sell, rent, or trade phone numbers with third parties. Phone numbers may be shared with our downstream SMS delivery providers (for example, Twilio) strictly to deliver the messages the recipient has opted in to receive.
  • When a number is removed (by opt-out or by deleting it from Settings > Notifications), Adomo retains it only as required for regulatory record-keeping (typically proof of consent and opt-out history) and otherwise deletes it from active systems per our data retention policy.

Full details are in our Privacy Policy.

Sample message

A typical Adomo approval SMS looks like this:

Adomo: Jane Smith requested approval for "Q2 Marketing Spend Increase" ($42,000). Review: https://app.adomo.ai/a/ab12cd34. Reply STOP to opt out, HELP for help.

A typical Adomo sign-in code SMS looks like this:

Adomo sign-in code: 123456. Do not share this code. Expires in 10 minutes. Reply STOP to opt out.

Questions

If you are a mobile carrier, aggregator, or compliance reviewer evaluating Adomo for messaging registration, please reach out to [email protected] for additional documentation, consent-flow screenshots, and sample traffic.

Email: [email protected]
Phone: +1 (866) 995-4498
Submit a ticket: Contact Us

© 2026 CXO AGI, LLC. All rights reserved.

Privacy Terms adomo.ai