AI iOS Chat Agent that lives inside your app

What the AI iOS Chat Agent is

The AI iOS Chat Agent puts a MyChatBot sales and support assistant into the chat screen of your own iOS app. Users write where they already are, and the assistant answers from your Knowledge Base, suggests products, qualifies the request and brings in your team when a person is needed.

It connects through the Webhooks API channel, which MyChatBot documents for exactly this use: in-app chat for a mobile app. Your app sends each user message to MyChatBot over HTTP, and the assistant’s reply is delivered to an endpoint you control. You design the chat interface; MyChatBot provides the agent, the inbox and the CRM behind it.

It is a good fit if you:

• run a shopping, booking or service app and want questions answered inside the app, not in an outside messenger;
• already use MyChatBot on Instagram, WhatsApp or your website and want the app to follow the same instructions;
• want in-app conversations to become leads, bookings or orders without copying data by hand.

How it works in MyChatBot, step by step

1. A user writes in your app. Your app posts the message as JSON to the inbound webhook URL shown on the Channels page. Four fields are required: client_id, page_id, platform and text. Optional fields add client_name, client_avatar, an audio URL and attachments.
2. MyChatBot checks the request. The API token authenticates it, the page_id must match the Unique page_id you set, and the channel must be switched on.
3. The message joins the history. It is added to that user’s conversation, matched by client_id. Voice messages are transcribed to text first.
4. The assistant replies. It reads the conversation, applies its instructions, knowledge and tools, and answers after the Reply Delay you configured.
5. The reply reaches your app. MyChatBot posts it to your Reply webhook URL with text, images, file and audio fields. A long reply can arrive in several parts, so your app appends them in order.

Keep client_id stable for each user. That is what lets a conversation continue from one session to the next instead of starting over.

Key capabilities

Answers grounded in your Knowledge Base

The assistant reads the knowledge base linked to it: FAQ, Business Documents, Business Files and Business Links as reference, plus a Product Feed, Product Spreadsheet or Products catalog as searchable inventory. Product search matches by meaning, keywords and category, so users can describe what they need in their own words.

Qualification that sticks

With Contact Details on, the assistant saves the name, phone and email a user shares. Client Context collects the extra data points you define, such as budget or deadline, and keeps them on the client card across conversations.

Next steps inside the chat

Lead Management lets the assistant set pipeline statuses and labels as the conversation moves. With the right integrations it books appointments and creates orders during the chat.

Voice, photos and files

Users can send voice messages and attachments. With Voice reply settings on, each reply also includes an audio version in the voice you choose, and replies can carry images and files back to the app.

Tone and language

Communication style sets the tone, from short and concise to a warm support voice. In Reply & Tools you can fix a primary reply language or let the assistant follow the user’s language.

Channels and integrations involved

Your iOS app becomes one more channel of the same assistant. It can also answer on the website widget, WhatsApp, Instagram, Telegram, Viber, Facebook, TikTok, Gmail, SMS and phone calls. Every conversation lands in Active chats, the shared team inbox, with full history and a client card for statuses, labels, notes and tasks.

For CRM work, connect one CRM per assistant on the Integrations page: KeyCRM, SalesDrive, Bitrix24, Kommo, Zoho, Salesforce, GoHighLevel or HubSpot. Or keep everything in the built-in Leads and Pipelines. Leads and deals the assistant creates in a connected CRM get a source that marks them as coming from the AI, and in CRMs such as KeyCRM, SalesDrive, Zoho or HubSpot a chat link is also added so your team can open the exact conversation.

Bookings run through Google Calendar, Altegio or MyChatBot’s native Calendar. Orders can go to the native Orders page, KeyCRM, SalesDrive or Spreadsheet Orders.

When a human takes over, and limits to know

The assistant decides when a person is needed based on your instructions. It can send an operator notification, which flags the chat in the Attention tab and, if Flight Control is linked, posts the alert to your team’s Telegram group with the client’s contact details and a chat link. Or it can hand the chat off to operator mode.

Handoff Control sets the rules (more on the human hand-off page):

• Stop word or Implicit operator handoff: an operator takes over with a keyword or with any message. You choose one of the two.
• Silent handoff: the user is not notified and sees one continuous conversation.
• Auto return: if the operator does not turn the agent back on, it resumes after 24 hours or after a custom interval from 1 minute to one week.

Plan for these limits:

• Outside Work Hours the assistant is paused. Users get no away message, and the assistant does not go back to messages sent off-hours, though operators can reply to them.
• If the account balance runs out, assistants switch off automatically.
• On the Standard and Pro plans only one sales assistant is active at a time. See pricing.

How to set it up

1. Configure the assistant. On the Agents page set the Role, Communication style and knowledge base, then check answers in the Test Dialog. Test replies count toward your AI messages.
2. Connect the channel. Open Channels, select the assistant, choose Webhooks API and fill in API token, Unique page_id and Reply webhook URL. Turn on Connect agent to this channel, set Reply Delay and click Connect Webhooks API.
3. Wire up your app. Send user messages to the inbound webhook URL, and build a handler at your Reply webhook URL that passes text, images, files and audio to the chat screen.
4. Add tools. Connect a CRM or calendar under Integrations, set Lead Management and Handoff Control, and link a Telegram group in Flight Control.
5. Test end to end. Send a real message from a test build and confirm the reply arrives and the chat appears in Active chats. A 400 response means a required field is missing, a 401 means the token does not match. If replies do not come back, check the page_id and the Connect agent to this channel switch first.