# AZTCO Omni tenant guide

Documentation for AZTCO Omni workspace owners and tenant administrators. Learn channels, campaigns, contacts, AI, integrations and workspace settings.
Availability depends on deployment, subscription, channel capabilities and permissions.

## Tenant Admin Navigation And Setup Order
Source: https://oc.aztco.io/docs/tenant-admin-navigation-setup-order.html

Where to go first in the GUI and the recommended setup sequence.

Before You Configure


  Login with OWNER or ADMIN role.

  Confirm you can see tabs: Channels, Agents, Contacts, Billing, Tenant Settings, Tickets.



Recommended Setup Sequence


  Configure at least one channel in Channels.

  Create users and access rules in Agents.

  Create/import contacts in Contacts.

  Test live flow from Inbox.

  Verify plan and limits in Billing.



Daily Operations


  Use Notifications for alerts.

  Use Tickets to contact platform support.

  Use Documentation for staff runbooks.

## Create And Edit Channel (General Flow)
Source: https://oc.aztco.io/docs/create-edit-channel-general-flow.html

Standard steps that apply to all channel types in the tenant GUI.

Create Channel


  Go to Channels.

  Click Add channel.

  Select channel type.

  Enter channel name and required credentials.

  Click Create.



Edit Channel


  Open channel row actions.

  Click Edit.

  Change only required fields first.

  Save and run channel test/check action.



Delete Channel


  Open row actions.

  Click Delete.

  Confirm after verifying no active dependency.

## Channel Actions, Disconnection and Deletion
Source: https://oc.aztco.io/docs/channel-action-menu-every-action.html

Channel row actions and their operational effects.

Channel actions
Review connection health and agent status; edit the settings offered for that channel.
For official Meta connections, complete the available authorization/asset selection and review missing permissions before reconnecting.
For Telegram, use Set webhook/Webhook status; for Email, use the offered inbound test or polling actions.
For local WhatsApp Business App agents, use the installer, login-token, takeover or recovery actions only when relevant to that installation.
Open Business tools for supported official Meta automations, catalog/orders, native Flows and attribution.

Removing a channel
Review the deletion dialog carefully. When related content exists, the application can offer delete-all or set-inactive. Delete-all removes related workspace content; set-inactive retains the channel record but stops it being an active connection. Neither action is proof that all external provider copies were erased. Channel-name contact tags can remain and are not live channel assignments.

## WhatsApp Cloud Channel Configuration
Source: https://oc.aztco.io/docs/whatsapp-cloud-channel-configuration.html

Channels → connect an official WhatsApp Cloud account.

Where to find it
Channels → connect an official WhatsApp Cloud account.
How to use it
Use the platform’s Meta authorization flow with the business account you are authorized to manage.
Select the intended WhatsApp business asset/number and complete the offered registration steps.
Review connection health and template availability.
Verify inbound/outbound messages and receipts with an authorized test contact before campaigns.

Permissions and important details
Cloud API is distinct from official Coexistence and the separate Business App agent. Available setup depends on app permissions, account eligibility and provider approval; do not share tokens in support messages.

## Official WhatsApp Coexistence Configuration
Source: https://oc.aztco.io/docs/whatsapp-coexistence-channel-configuration.html

Channels → official WhatsApp Coexistence onboarding.

Where to find it
Channels → official WhatsApp Coexistence onboarding.
How to use it
Authorize an eligible WhatsApp Business account through the platform’s Meta app.
Select the correct business asset and complete the provider onboarding prompts.
Choose supported contact/history synchronization options and monitor progress.
Verify native-app messages, inbox messages and supported delivery events.

Permissions and important details
Official Coexistence connects eligible native Business App use with Cloud capabilities. It is not the separately installed local Business App agent. History/contact synchronization is limited to provider-supported data and authorization choices; complete historical parity is not guaranteed.

## WhatsApp Business App Channel Configuration
Source: https://oc.aztco.io/docs/whatsapp-business-app-channel-configuration.html

Detailed channel form configuration for WABA local agent mode.

Core Fields


  Session name

  Agent token

  Webhook secret

  Heartbeat timeout and delays

  Agent ID, require ID, takeover policy

  Retention settings



Configuration Steps


  Create/edit channel type WHATSAPP_BUSINESS_APP.

  Set token and secrets first.

  Tune delay/heartbeat values.

  Save and verify agent online status.



Security Notes


  Rotate tokens after leak suspicion.

  Do not share webhook secret in chat/email.

## Telegram Channel Configuration
Source: https://oc.aztco.io/docs/telegram-channel-configuration.html

How to configure Telegram channel and set webhook from GUI.

Setup Steps


  Create Telegram channel in Channels.

  Enter bot token and required identifiers.

  Save channel.

  Use action Set webhook.

  Check Webhook status action.



Common Issues


  Webhook URL mismatch.

  Bot token revoked or incorrect bot permissions.

## Email Channel Configuration
Source: https://oc.aztco.io/docs/email-channel-configuration.html

How to configure inbound/outbound email channel behavior in GUI.

Required Sections


  Inbound protocol settings (IMAP/POP)

  SMTP/outbound settings

  Auto-reply/signature templates

  Trigger rules and status definitions



Setup Steps


  Create channel type EMAIL.

  Set inbound server/auth values.

  Set outbound SMTP values.

  Save channel and run Test inbound.

  Run Poll now for manual fetch check.



Agent Permissions

Configure email reply/reply-all/forward/delete permissions per channel access policy.

## Facebook Messenger Channel Configuration
Source: https://oc.aztco.io/docs/facebook-channel-configuration.html

Channels → connect Facebook Messenger.

Where to find it
Channels → connect Facebook Messenger.
How to use it
Authorize the business assets you manage through the platform connection flow.
Select the intended Page or professional account; finish the asset-selection step.
Review connection health and any missing permissions.
Verify supported inbound/outbound text and media before using automation.

Permissions and important details
Clients authorize their own assets through the platform app. Personal accounts and unsupported assets are not interchangeable with eligible business assets. Messaging windows, account permissions and supported attachment formats still apply.

## Instagram Channel Configuration
Source: https://oc.aztco.io/docs/instagram-channel-configuration.html

Channels → connect Instagram.

Where to find it
Channels → connect Instagram.
How to use it
Authorize the business assets you manage through the platform connection flow.
Select the intended Page or professional account; finish the asset-selection step.
Review connection health and any missing permissions.
Verify supported inbound/outbound text and media before using automation.

Permissions and important details
Clients authorize their own assets through the platform app. Personal accounts and unsupported assets are not interchangeable with eligible business assets. Messaging windows, account permissions and supported attachment formats still apply.

## Internal Conversations and Archive Access
Source: https://oc.aztco.io/docs/internal-channel-usage.html

Team collaboration and internal AI conversations.

Use internal conversations
Open the permitted internal conversation from Inbox and verify its participants.
Use it for team collaboration, not customer-facing outbound messaging.
Use internal AI chat only when your role and the channel AI permission allow it; review generated answers.
Use archive/history controls only when the separate internal archive permission is granted.

Visibility
Internal conversations follow their own participant and permission rules. Owner/admin status does not mean every separate archive or AI permission can be ignored. MCP connections exclude internal chats.

## Download Install And Connect WABA Agent
Source: https://oc.aztco.io/docs/download-install-connect-waba-agent.html

End-to-end flow for downloading installer and connecting channel to agent runtime.

Download


  Go to channel actions for WABA channel.

  Click Download agent.



Install


  Run installer on Windows machine.

  Set service/port values.

  Start service.



Connect


  Use channel token/ID values.

  Verify Agent status shows online.

## WABA Runtime Recovery Actions
Source: https://oc.aztco.io/docs/waba-runtime-recovery-actions.html

When and how to use disconnect, reset session, and clear agent DB actions.

Disconnect Session

Use when session is stale or QR/login must be re-established.

Reset Session

Use when session state is corrupted and normal reconnect is not enough.

Clear Agent DB

Use only for cache/history corruption recovery. This is destructive.

Recovery Sequence


  Try status check.

  Disconnect and reconnect.

  If still broken, reset session.

  Use clear DB as last resort.

## Agent Login Token Management
Source: https://oc.aztco.io/docs/agent-login-token-management.html

How to fetch and rotate tenant agent login token safely.

Fetch Token


  Open channel edit form for WABA.

  Click Fetch agent login token.

  Copy and store securely.



Rotate Token


  Click Rotate agent login token.

  Immediately update the running agent config.

  Verify agent reconnect.



Rule

Never rotate token without a controlled update window.

## Create Agent User And Assign Access
Source: https://oc.aztco.io/docs/create-agent-user-assign-access.html

Create users, roles, and per-channel access rules from tenant GUI.

Create User


  Go to Agents.

  Click Add user.

  Set name, email, password.

  Select role set (AGENT/ADMIN/etc).

  Set channel access and save.



Channel Access Modes


  ALL: agent sees all conversations in channel.

  ASSIGNED: agent sees only assigned conversations.

## Edit User Roles Password And Status
Source: https://oc.aztco.io/docs/edit-user-roles-password-status.html

Update tenant user roles, suspend/activate users, and reset passwords.

Edit User


  Open user row action Edit.

  Update roles/status/channel access.

  Save and request relogin if permission changed.



Password Reset


  Use user password action.

  Set strong temporary password.

  Require user to change after login.

## Agent Groups Management
Source: https://oc.aztco.io/docs/agent-groups-management.html

Create, edit, delete groups and maintain group members for assignment workflows.

Create Group


  Open agent group form.

  Set group name and optional description.

  Select member users.

  Save group.



Edit Or Delete Group

Use group actions to update members or remove group when no longer needed.

## Contact CRUD Workflow
Source: https://oc.aztco.io/docs/contact-crud-workflow.html

Create, edit, delete contacts and keep contact profile data clean.

Create Contact


  Go to Contacts and click Add contact.

  Enter name and at least one reachable identifier (phone/email).

  Save.



Edit Contact


  Open contact row action Edit.

  Update tags/company/identity fields.

  Save changes.



Delete Contact

Only delete when record is invalid/duplicate and no operational dependency remains.

## Assign Contacts To Agents And Groups
Source: https://oc.aztco.io/docs/assign-contacts-to-agents-and-groups.html

Detailed assignment workflow for contact routing and ownership.

Assignment Steps


  Edit target contact.

  Use Assign agents and/or group selection.

  Save assignment.



Operational Rule

Keep ownership clear. Avoid assigning too many agents to the same contact unless team-handoff is intended.

## Billing Plan Change And Checkout
Source: https://oc.aztco.io/docs/billing-plan-change-and-checkout.html

How to change plan and complete payment flow from tenant GUI.

Change Plan


  Open Billing.

  Select target plan.

  Choose payment method (card or transfer).

  Submit and track status in billing history.



Validation

After approval/payment, confirm new limits (agents/channels) are active.

## Fund Transfer Submission
Source: https://oc.aztco.io/docs/fund-transfer-submission.html

How to submit transfer reference/date and proof correctly.

Submit Transfer


  Select payment method Fund transfer.

  Enter reference and transfer date.

  Upload proof file when requested.

  Submit request and wait for admin review.



Best Practice

Use bank reference exactly as it appears in transfer statement.

## Invoice View Print And PDF Download
Source: https://oc.aztco.io/docs/invoice-view-print-pdf-download.html

How to open invoices and export printable PDF from GUI.

Invoice Actions


  Open invoice from billing history.

  Use print preview for quick review.

  Use download PDF for accounting archive.

## Support Ticket Lifecycle
Source: https://oc.aztco.io/docs/support-ticket-lifecycle.html

Create, reply, attach evidence, and close/reopen support tickets.

Create Ticket


  Go to Tickets.

  Create ticket with subject and full issue context.

  Add image/video evidence if useful.



Manage Ticket


  Reply from ticket detail page.

  Update status when issue is solved or reopened.

## Feature Request Workflow
Source: https://oc.aztco.io/docs/feature-request-workflow.html

Submit feature requests and follow discussion/reply flow.

Create Feature Request


  Go to Request new feature.

  Provide clear title and business impact.

  Submit and monitor replies.



Reply Flow

Use follow-up replies for additional context, examples, and priority impact.

## Tenant Settings General Configuration
Source: https://oc.aztco.io/docs/tenant-settings-general-configuration.html

Configure timezone and KPI run schedule from tenant settings.

Update General Settings


  Open Tenant Settings.

  Set timezone correctly.

  Set KPI daily run time.

  Save and verify next KPI run timing.

## Notifications And Push Alerts
Source: https://oc.aztco.io/docs/notifications-and-push-alerts.html

How to use notifications tab and enable browser push subscriptions.

Notifications


  Open Notifications.

  Open each alert to navigate to related item.

  Mark as read once handled.



Push Setup


  Enable push from profile/device browser prompt.

  Select channels for notification scope.

## Using Workspace Documentation
Source: https://oc.aztco.io/docs/tenant-documentation-management.html

Documentation.

Where to find it
Documentation.
How to use it
Search by feature or problem and browse the article groups.
Follow the guide for your actual channel/provider and permissions.
If the documented control is unavailable, check entitlement and ask your workspace owner or platform support.
Report outdated instructions through a support ticket with the page title and the affected workflow.

Permissions and important details
This guide is for workspace owners and tenant administrators. Maintaining platform-wide published help content is a separate privileged operation, not a tenant setup requirement.

Public documentation and AI access
Open the public tenant guide without signing in. Each article has a shareable HTML address and is readable without JavaScript. AI tools can use the article index or the complete plain-text guide. This public guide is updated with frontend releases; it contains product instructions, not your workspace records.

## Campaigns AI Providers And API Keys
Source: https://oc.aztco.io/docs/campaigns-ai-providers-and-api-keys.html

Operational setup for campaigns, AI provider configs, and API key lifecycle.

Campaigns


  Open Campaigns.

  Create campaign with audience/template.

  Validate content before send.



AI Providers


  Open AI.

  Add provider with API credentials.

  Save and test expected behavior.



API Keys


  Open API Keys.

  Create and copy key once.

  Rotate/delete keys no longer used.

## Workspace Owner and Tenant Administrator Permissions
Source: https://oc.aztco.io/docs/tenant-owner-permissions.html

Your own workspace; Agents and Tenant Settings.

Where to find it
Your own workspace; Agents and Tenant Settings.
How to use it
Confirm the workspace name before making changes. An owner/admin role here applies to this tenant, not other customers.
Use Agents to grant each team member only the roles, channels and conversation/email access needed for their work.
Check subscription entitlement, channel assignment and feature permissions if a page or action is missing.
Deactivate departing users and revoke their API/MCP connections. Review Audit Logs after access changes.

Permissions and important details
Menus depend on roles, plan, country and channel capabilities. Owner and administrator access are not identical: MCP administrators manage their own connections and must have full assigned-channel access; owners can manage tenant connections. Global platform settings, provider app approval, infrastructure and policy publication are outside this guide.

## Inbox: Conversations, Replies and Message Actions
Source: https://oc.aztco.io/docs/inbox-conversations-and-messages.html

Inbox.

Where to find it
Inbox.
How to use it
Select a permitted channel and conversation; use the visible search, status and unread filters to narrow the list.
Review the contact identity and conversation history before replying. Use the composer for text, supported attachments, voice messages or available saved replies.
Use the conversation controls to assign work, change its status, apply conversation tags or record the relevant lead case when available.
Use the message menu for supported reply, forward, copy, download or other channel-specific actions. Review the target before forwarding.
Check pending/sent/delivered/read/failed indicators; inspect failures before retrying. Review AI reply suggestions before sending.

Permissions and important details
Actions vary by channel and permission. Official Meta service windows and templates still apply. A preview, typing indicator or queued message is not proof of delivery. Internal conversation archives require their separate permission.
Delete from platform
Use the message action menu and choose Delete from platform. This is separate from editing or Delete for everyone: it does not delete anything on the recipient’s device. Messages still being sent must finish before deletion.
Deleted message permissions
In Agents, grant Delete platform messages and View deleted messages separately. With neither permission, deleted messages are hidden. Delete permission alone shows only a Deleted message placeholder. View permission reveals the retained original, marked as deleted, in conversations the user can access; it does not allow deletion. With both permissions, the user can delete and view originals. Workspace owners and tenant administrators have both automatically.
Deletion preserves the message identifier, so WhatsApp history sync acknowledges it without restoring it. Background transcription and status updates cannot restore its content. Authorized viewers can view retained attachments; search, exports and automation use the deletion marker. This is visibility control with retained originals, not permanent data erasure or recipient deletion.

## Search Across Workspace Records
Source: https://oc.aztco.io/docs/workspace-search.html

Search.

Where to find it
Search.
How to use it
Enter a search term and run Search.
Select the available result category and page through matches.
Open the matching record to inspect its channel and customer context.

Permissions and important details
Results follow your workspace access. A record hidden by permissions is not necessarily missing.

## KPI Dashboards and Team Performance
Source: https://oc.aztco.io/docs/workspace-kpi.html

KPI.

Where to find it
KPI.
How to use it
Choose the available date, channel and agent filters.
Review system totals and agent rankings alongside the displayed KPI scope.
Use metric explanations for seen speed, reply speed, open-to-resolve time, solve rate and reopen rate.
Review top contacts and compare equivalent date ranges before taking action.

Permissions and important details
KPI values depend on observed events, configured timing and access scope. They are not the same report as campaign revenue or Meta advertising attribution.

## Lead Status and Case Types
Source: https://oc.aztco.io/docs/workspace-leads.html

Lead status; Tenant Settings → Lead case types.

Where to find it
Lead status; Tenant Settings → Lead case types.
How to use it
Filter lead records by status, channel or case type.
Open the linked conversation to inspect the customer interaction and available case/closure controls.
Use Lead case types to maintain the categories available to your team; deactivate obsolete types when appropriate.

Permissions and important details
Visibility follows channel/lead permissions. A lead status does not confirm a payment, shipment or external CRM update.

## Important Files: Find, Preview and Manage
Source: https://oc.aztco.io/docs/workspace-important-files.html

Important Files.

Where to find it
Important Files.
How to use it
Filter by channel and search for a file name.
Preview the attachment or download it if your role permits.
Use Rename to keep the file listing understandable; review the target before using Delete.
Refresh if a recently updated file has not appeared.

Permissions and important details
File-management and download permissions are separate. Deletion can remove access to an attachment; it is not a general customer-data deletion workflow.

## WhatsApp Status Scheduling
Source: https://oc.aztco.io/docs/workspace-whatsapp-status.html

WhatsApp Status.

Where to find it
WhatsApp Status.
How to use it
Create a status schedule and select an eligible channel.
Enter the supported content and media, then set the available schedule fields.
Save the schedule; use Edit, Publish now or Delete as needed.
Inspect errors and channel connection state when publication fails.

Permissions and important details
Only channels supported by the status integration are eligible. This feature does not establish official Cloud API or Coexistence status-publishing capability for every WhatsApp connection.

## Urgent Call Requests
Source: https://oc.aztco.io/docs/workspace-urgent-calls.html

Urgent Calls.

Where to find it
Urgent Calls.
How to use it
Filter requests by pending, approved, rejected, expired or consumed status.
Review the requester and conversation context.
Use the available approval/rejection controls on an eligible pending request.
Refresh to follow its final status.

Permissions and important details
This is the platform urgent-call approval workflow, not a claim that native calling is supported by every Meta channel.

## Audit Logs and Data Activity
Source: https://oc.aztco.io/docs/workspace-audit-and-data-activity.html

Audit Logs; Data Activity.

Where to find it
Audit Logs; Data Activity.
How to use it
Use Audit Logs to investigate recorded administrative actions in your tenant.
Use Data Activity categories to find the relevant operation, then load further records when available.
Open an event to inspect its recorded time, actor and details.
When reporting a problem, share the event time and record identifier rather than credentials or full customer content.

Permissions and important details
Logs describe recorded platform events; absence of an entry is not proof that an external action never happened. MCP tool audit records intentionally exclude raw customer text and tokens.

## vCards, QR Sharing and Statistics
Source: https://oc.aztco.io/docs/workspace-vcards.html

My vCard QR; vCard Statistics; Tenant Settings → Contact information.

Where to find it
My vCard QR; vCard Statistics; Tenant Settings → Contact information.
How to use it
Check the contact information shown on the public card.
Open My vCard QR and share the intended card or QR through the available controls.
Review views, visits and unique-visitor figures in vCard Statistics.
Use the available contact-information synchronization control when your integration requires it.

Permissions and important details
These functions appear only when the tenant vCard integration is enabled. Public cards can reveal the contact information you publish; visitor statistics are not sales conversions.

## Account Access, Notifications and Installed App
Source: https://oc.aztco.io/docs/workspace-account-and-notifications.html

Account menu; Notifications; browser installation controls.

Where to find it
Account menu; Notifications; browser installation controls.
How to use it
Use the available profile/account controls to maintain your details and secure sign-in.
Review notifications and open the related workspace record.
Enable browser push permission and select the available channel notification scope.
Use the install prompt where supported, and refresh when an application update is offered.
Sign out on shared devices; ask your workspace owner to revoke access if a device or credential is compromised.

Permissions and important details
Browser/device permissions and operating-system notification settings also affect delivery. Installing the app does not grant additional workspace permissions.

## Saved Replies, Conversation Tags and Workspace Preferences
Source: https://oc.aztco.io/docs/tenant-shorts-and-conversation-tags.html

Tenant Settings → General settings, Conversation tags, Shorts and Contact information.

Where to find it
Tenant Settings → General settings, Conversation tags, Shorts and Contact information.
How to use it
Set the workspace timezone and available operational preferences under General settings.
Maintain contact information used by your workspace-facing features.
Create/edit conversation tag definitions for consistent inbox categorization.
Create and maintain Shorts for reusable text, links or media; review the final recipient and content when inserting a saved reply.

Permissions and important details
Contact tags and conversation tags have different purposes. Tenant contact information is not the platform operator’s legal invoice identity. Do not change another company’s details to repair your own profile.

## AI Knowledge Base and Human-Reviewed Suggestions
Source: https://oc.aztco.io/docs/tenant-ai-knowledge-base.html

AI → Knowledge Base and tenant AI settings.

Where to find it
AI → Knowledge Base and tenant AI settings.
How to use it
Add the available knowledge sources using the supported text, document or website input.
Organize knowledge with the available tags and channel visibility controls.
Check indexing/status information after saving or changing a source.
Enable eligible tenant/channel AI features and select the provider for KB suggestions.
Review draft answers against the underlying source and customer context before sending.

Permissions and important details
Do not upload material you are not authorized to share. Indexing completion, provider configuration and channel permissions all affect results. Conversation-memory settings are separate from the maintained knowledge base.

## Voice Transcription, Groq and ElevenLabs Setup
Source: https://oc.aztco.io/docs/tenant-transcription-providers.html

AI provider configuration; tenant AI settings → Speech-to-text provider; channel AI controls.

Where to find it
AI provider configuration; tenant AI settings → Speech-to-text provider; channel AI controls.
How to use it
Add the chosen provider and its API key. For ElevenLabs choose ElevenLabs Scribe, use the Scribe template and save.
Choose the provider in Speech-to-text provider for this tenant.
Enable transcription on the intended channels and confirm your AI plan is active.
For ElevenLabs use scribe_v2 or scribe_v1. Leave language blank for automatic detection or enter an appropriate language code.
Inspect transcript status/errors in the audio/transcript views. Use the available old-record/backfill controls carefully when processing historical audio.

Permissions and important details
Supported routes: AZTCO LLM Agent, OpenAI, Azure OpenAI, Gemini, ElevenLabs and Groq. For Groq select the Groq transcription template and use whisper-large-v3-turbo or whisper-large-v3. Direct providers bill your own provider account. DeepSeek and Anthropic are chat options, not direct transcription routes. OpenAI audio models belong in the speech settings, not the chat-model field. Azure needs an audio-capable deployment; Gemini needs an accessible audio-capable model. External processing may incur provider charges. ElevenLabs logging/retention follows your account; disabling logging needs enterprise eligibility. Speaker/timestamp output is not displayed in the inbox. Report failures with the message ID and time; do not share API keys.
Managed transcription and allowances
Open the transcription management panel to select local, automatic or managed processing. Automatic routing uses audio length, channel urgency and queue wait. Cloud processing requires permission and available managed minutes. Saving a disabled policy pauses managed transcription; it does not remove limits.
Review local and managed balances, reservations and expiry dates before purchasing a package. Managed processing has a minimum of ten billable seconds per request, including silence. Direct providers bill your own account; you can set a separate direct usage cap. Fallback between local and cloud must be explicitly enabled.
Channels and older recordings
Choose a channel override or mark a channel urgent. Preview historical recordings by channel and date before applying the batch. The preview fixes the selected records and expires after thirty minutes. Pause or cancel stops future batch work; an already active recording may finish. Missing media cannot be reconstructed. Allowance holds are checked periodically; uncertain provider outcomes require review before retrying to avoid duplicate charges.
Billing
Packages and the billing portal are available when platform billing is configured. Free local and direct caps use calendar months; subscription credits use the paid subscription period. Top-ups expire after 365 days. No unlimited overage is enabled. Shared allowance accounts do not grant access to another workspace’s recordings.

## Connect an External AI Assistant with MCP
Source: https://oc.aztco.io/docs/tenant-mcp-connections.html

Tenant Settings → AI connections (MCP).

Where to find it
Tenant Settings → AI connections (MCP).
How to use it
Create a named connection and choose its expiry.
Select only the required permissions and explicit channels. Reply previews also require conversation access.
Copy the token once into your approved assistant’s secret storage.
Use the displayed server URL with Streamable HTTP and an Authorization: Bearer header in a compatible client.
Review last-used/expiry information. Revoke unwanted connections, or create a replacement and revoke the old one to rotate credentials.

Permissions and important details
Owners manage tenant connections; administrators manage their own and need full assigned-channel access. Support-ticket metadata permission is tenant-wide. Credentials expire and are rechecked against the issuing user. OAuth-only clients are not supported by this release. Tools can search/read records and prepare reply previews; they cannot send messages, launch campaigns, delete records or save drafts. Revocation does not recall information already received by an external assistant.

## API Keys: Scopes, Channels and Revocation
Source: https://oc.aztco.io/docs/tenant-api-key-permissions.html

API Keys.

Where to find it
API Keys.
How to use it
Create a named key for one integration and copy the secret when displayed.
Choose the required read/write baseline and module scopes instead of broad access where possible.
Restrict channel access, set expiry and enable signed requests if your integration supports the required signature headers.
Review usage and revoke unused keys. Update the consuming integration when rotating its credentials.

Permissions and important details
API keys and MCP tokens are separate credentials and are not interchangeable. Keep both out of messages, URLs and source control. Channel-restricted API operations may require an explicit channel ID.

## Create, Schedule and Monitor Campaigns
Source: https://oc.aztco.io/docs/tenant-campaign-delivery.html

Campaigns.

Where to find it
Campaigns.
How to use it
Choose a channel, audience and supported message/template.
Check consent evidence and personalization before creating the campaign. Template approval does not establish marketing permission.
Review preflight exclusions and available readiness information.
Schedule delivery or start through the available controls; use pause/resume/cancel as needed.
Inspect delivery failures and Analytics. Record expenses in the correct currency and use CSV export when needed.

Permissions and important details
Cancellation cannot recall messages already sent. Reports reflect observed events; local attribution can differ from Meta Ads Manager. Recorded expenses are not automatic billing reconciliation, and delivery does not prove a purchase.

## Instagram Comment Automation
Source: https://oc.aztco.io/docs/tenant-instagram-comment-rules.html

Channels → Business tools on an eligible Instagram connection.

Where to find it
Channels → Business tools on an eligible Instagram connection.
How to use it
Create a named rule with the available keyword and post/reel filters.
Set the initial private reply and optional independent public reply.
Enable the rule and review matched comments and failures.
Pause a rule when it is no longer needed; inspect the reason before retrying a failed action.

Permissions and important details
A public comment is not blanket marketing consent. The implementation applies the initial private-reply deadline and deduplication. Live comments are excluded. Account permissions and provider subscriptions must be available; contact platform support if setup is blocked.

## WhatsApp Catalogs and Order Workflows
Source: https://oc.aztco.io/docs/tenant-whatsapp-commerce.html

Channels → Business tools on an official WhatsApp connection.

Where to find it
Channels → Business tools on an official WhatsApp connection.
How to use it
Select the connected catalog and browse its products.
Choose an authorized conversation and prepare the supported catalog/product message.
Review inbound itemized order requests.
Use the available confirm, fulfill or cancel controls according to your real business operation.

Permissions and important details
Catalog availability is controlled by the provider account. A local order status does not collect payment, reserve stock, issue refunds or update an external fulfillment system. Messaging-window and commerce restrictions still apply.

## Native WhatsApp Flows
Source: https://oc.aztco.io/docs/tenant-native-whatsapp-flows.html

Channels → Business tools → WhatsApp Flows.

Where to find it
Channels → Business tools → WhatsApp Flows.
How to use it
Create a draft with the simple form generator or JSON editor.
Validate it and correct the reported provider errors before publication.
Use the available publication, cloning, refresh and deprecation controls.
Select an eligible conversation or approved campaign template; supply initial screen data when needed.
Review recorded completions and submitted values through the feature views.

Permissions and important details
Native WhatsApp Flows are separate from the standalone Aztco Flow builder. Dynamic forms depend on the platform endpoint configuration. External appointment, stock and payment systems need their own integration; a form alone does not provide them.

## Ad Referrals, Conversions and Campaign Analytics
Source: https://oc.aztco.io/docs/tenant-ads-attribution.html

Channels → Business tools; Campaigns → Analytics.

Where to find it
Channels → Business tools; Campaigns → Analytics.
How to use it
Review captured messaging referrals and linked campaign activity.
Connect or select the available dataset when exporting Business Messaging conversions.
Record a genuine conversion with its event time, value and currency where applicable.
Select Meta export only when you have the required notices and permission; inspect export status/errors.
Compare observed campaign replies, conversions, revenue and recorded costs using consistent date ranges and currencies.

Permissions and important details
Business Messaging events must represent the appropriate messaging interaction. Website/app conversion tracking is a separate integration. Counts and attribution are not a guarantee of incremental sales or payment completion.

## Contacts: Consent, Contact Cards and Channel Lists
Source: https://oc.aztco.io/docs/tenant-contacts-consent-and-cards.html

Contacts; contact messaging-permission dialog; Inbox contact cards.

Where to find it
Contacts; contact messaging-permission dialog; Inbox contact cards.
How to use it
Search/filter contacts and review their identities before editing or deleting through the available controls.
Use contact-card details to identify the intended person before saving information.
Open Messaging permission for a contact and choose the relevant channel and purpose.
Record consent already obtained, or record its withdrawal, with the actual source and evidence.
Refresh Contacts if channel options look stale. Distinguish channel filters from contact tags with channel-like names.

Permissions and important details
Saving permission does not ask the customer for consent. Deleted channel names may remain as contact tags; tags are categorization records, not live connections. Historical tag cleanup has not been automated. Channel-list refresh fixes do not certify the outstanding reported Tags-versus-channel-picker issue.

## Customer Privacy and Connected Provider Responsibilities
Source: https://oc.aztco.io/docs/tenant-privacy-responsibilities.html

Your customer communication procedures; public Privacy, Terms and Data deletion pages; Tickets for platform assistance.

Where to find it
Your customer communication procedures; public Privacy, Terms and Data deletion pages; Tickets for platform assistance.
How to use it
Provide your customers with the notices and permissions required for your business communications.
Keep real consent and opt-out evidence, and apply withdrawals to future messaging.
Choose approved AI/transcription providers and disclose applicable external processing.
For deletion/access requests, identify the contact, workspace and scope and coordinate with platform support where needed.
Revoke unused provider or MCP access and track copies held by external processors separately.

Permissions and important details
Workspace owners do not publish the platform-wide legal policy or change its invoice issuer identity. Disconnecting a channel or revoking MCP does not erase all existing data or external copies. Do not promise retention or deletion behavior that your operating procedure cannot deliver.

## AI Diagnostics, Usage and Transcript Queues
Source: https://oc.aztco.io/docs/tenant-ai-diagnostics-and-usage.html

AI diagnostic, usage and transcript views.

How to use it
Open the AI status views and refresh connectivity or end-to-end status.
Check the selected KB/transcription provider, configuration status, tenant eligibility and channel switches.
Review the AI Token Report for recorded usage; provider billing and platform metering may differ.
In Transcript Queue Status, switch between pending/ready/failed views, page through records and open the related conversation.
If eligible historical audio needs processing, review the available all/range and limit controls before queuing a backfill.

When to contact support
A successful health response does not prove a speech model is ready. Share the affected record ID, error and timestamp. Do not change shared service settings or expose credentials. Backfills can generate provider usage and do not guarantee recovery of missing media.

## Contacts: Bulk Editing, Tags and Deletion
Source: https://oc.aztco.io/docs/tenant-contact-bulk-actions.html

Contacts selection controls and Tags.

How to use it
Apply search/channel/company/tag filters and review the result list.
Select the intended contacts; check the selected count before using Bulk edit.
Enable only the fields or assignments you intend to change in the bulk editor and review the values.
Save and inspect the updated records. Clear selection before starting unrelated work.
Use Delete selected only for the intended records and review the confirmation. Maintain reusable contact tags through the Tags controls.

Permissions and scope
Bulk changes affect the selected records, not necessarily every matching record on other pages. Contact tags are not live channel assignments. Deleting contacts may affect related workspace data; it is not an automatic erasure of copies held by every external provider.

## Aztco Flow License and Builder Access
Source: https://oc.aztco.io/docs/tenant-flow-license-and-builder.html

Billing → Flow controls, when enabled for the workspace.

How to use it
Review the Flow plans and existing license status shown in Billing.
Refresh plan/license information before changing or activating access.
Use the available license-key and plan controls according to your entitlement.
Open the Flow builder using the provided launch control.

Feature boundary
The separately hosted Flow builder has its own availability and license integration. It is distinct from native WhatsApp Flows under Channels → Business tools. Ask support if the platform integration is unavailable; tenants do not configure its shared server credentials here.