Messaging Agents

Messaging Agents help your team serve customers across social, chat, and website channels from one consistent setup. They can answer questions, capture leads, book meetings, follow up after silence, support product enquiries, take delivery-bearing orders, and hand conversations to people when needed.

Navigation: Open Email & Messaging in the left sidebar, then select Messaging Agents.

Create a Messaging Agent

Create one when you want a repeatable chat experience across one or more customer channels—for example, a website sales assistant that also answers Instagram messages.

1. Select Create Messaging Agent.
2. Enter a clear name and save the General tab.
3. Open Channels and connect at least one customer channel.
4. Review AI Reply — a new agent already has replies, AI-powered tools, Capture Customer Info, Smart Skip, and Human Handover switched on.
5. Assign knowledge and rehearse the conversation in Test before activating.
6. Add CRM, delivery, or follow-up behavior only when required.

A new agent is created in Draft, so nothing at all reaches customers until you select Activate — a draft agent stays silent even on channels with an Offline message configured. That, together with the Test chat, is how you check an agent safely.

Use the Messaging Agents list

Use the list to see where each chat experience is available, whether it is replying live, and which connection needs attention. Search by agent name or connected account name. Each card shows channel count, channel connection status, selected role, CRM or delivery indicators, and one line on what customers currently get: replies are live, AI Reply is off, or — for a draft or disabled agent — on how many channels an Offline message is still answering. A card whose agent is disabled or in draft also carries a colored edge, and a channel row is marked when its own AI replies switch is off.

Select a connected account name to open it on the channel when a link is available. Use Test, Conversations, or Settings for the agent’s main workflows.

General settings

Use General to define the job and personality customers experience consistently across connected channels. Change the agent name, status, language or role options shown in your workspace, and core instructions. Keep the agent in Draft while configuring it and use Disabled when it should stop responding.

The line under the status selector spells out what customers experience in the status you picked, so you can see the consequence before saving. Whenever the agent falls silent — you choose Disabled, or AI Reply is switched off — a highlighted note also says how many connected channels still answer with their Offline message, with a shortcut to the Channels tab to change that. The two counts differ on purpose: a disabled agent lets every channel with an offline message answer, while a live agent with AI Reply off answers only where the channel’s own AI replies switch is off.

See Agent roles and instructions before applying a role preset to a customized agent.

Connect channels

Channels determine where customers can reach the agent. Connecting several suitable channels lets you reuse the same approved behavior and knowledge while meeting customers where they already communicate.

Open Channels to see connected channels and available connection methods. Supported options can include Instagram, Facebook Messenger, Telegram, WhatsApp, TikTok, Web Chat, and Demo Widget.

If your organization has Announce AI assistance on, the first AI reply in Instagram, Facebook Messenger, Telegram, or WhatsApp identifies the assistant as AI. After a conversation has been inactive for 24 hours, the next AI reply does so again. Where your messenger account has a public profile or description, add a note that AI assists with replies. Web Chat instead displays a persistent AI assistant label in the chat header; it does not add a separate opening message.

To customize that introduction, open General, expand AI announcement wording overwrites, and edit Overwrite Messenger Agent Opening Message for the appropriate language. Select Save beside the edited field. This wording is shared across messaging agents in your organization; a blank field uses the default.

Follow the connection dialog for each channel. Some channels open an external authorization window; others ask you to connect a bot, number, page, or website. After connecting, confirm that the account name is correct and run a test message.

Removing a channel stops new messages through that connection. Review current conversations and any website embed before removal.

If WhatsApp messages work but the app cannot load approved templates, select Reconnect beside that WhatsApp channel in Channels. Grant access to the same WhatsApp Business Account and select the same phone number. Reconnecting keeps the channel’s existing conversation history and settings. Then return to Send WhatsApp and select Refresh templates; contact support if access is still denied.

Pause AI on one channel

Use the per-channel AI replies switch when you want people on a specific channel handled by your team rather than the agent — for example, keep AI answering Web Chat while your operators personally handle Instagram — without disconnecting the channel or losing its conversation history.

On the Channels tab, each connected channel row has an AI replies switch. Turn it off and its label changes to AI replies off. While it is off:

• Messages keep arriving and appear in the Conversations inbox as usual.
• The AI does not reply and scheduled follow-ups on that channel stop.
• Your team can still answer — from the Conversations inbox, your CRM, or the platform’s own app. Replying yourself keeps working exactly as before.
• Other channels of the same agent are unaffected.

Every connected channel row has an Offline: on/off button. Open it to tell customers you are away whenever nobody is answering on that channel — its AI replies switch is off, or the whole agent is disabled. On messenger channels the text is sent as a reply, once per conversation and again only after the conversation has been quiet long enough to start a new session; on Web Chat it is shown as a notice in the widget. Edit the wording there, or leave the field empty to use the standard text.

Turn the switch back on to resume AI replies on that channel. Conversations a human replied to stay paused if Pause AI on human intervention is enabled — the agent will not barge back into them.

If you want the team notified when a customer writes on a channel with AI off, enable Alert me when a customer writes on a channel with AI replies off under AI Reply → Human takeover and pick the notification channels. The alert arrives once per conversation session and links straight to the waiting conversation.

Configure Web Chat

Web Chat places the agent directly on your website so visitors can ask questions, qualify themselves, or begin an order without leaving the page. Select Configure branding on the Web Chat row to set placement, button style and size, entrance behavior, spacing, website address, and branding, or pick the chat color from the swatch next to it. Preview changes before saving. Links in the welcome message are clickable in both the preview and the published chat. For example, https://docs.versafy.ai displays as docs.versafy.ai and opens the full address in a new tab.

The Install code on your site block on the same row holds everything needed to publish the widget: pick your platform (HTML, Shopify, WordPress, or Wix) for the exact placement step, then copy the one-line snippet with the copy button and paste it into your site. On WordPress, keep the snippet as copied: its data-no-minify="1" part stops WP Rocket from moving the chat script onto your own site, where the chat cannot connect. If WP Rocket also combines JavaScript files, add widget-loader.js under File Optimization → Excluded JavaScript Files in WP Rocket and clear its cache. If you regenerate the widget token, update the embed code on your website; the previous code will no longer connect. Appearance changes may take a short time to reach the live site.

If you pause AI on the Web Chat channel (see Pause AI on one channel), the widget keeps working: visitors can still write, and their messages arrive in your Conversations inbox. Instead of silence, the visitor sees an offline notice telling them their message was received and someone will reply later — answer them from the inbox and your reply appears in their chat. The notice is controlled by the Offline: on/off button on the channel row on the Channels tab: turn it off entirely, or edit the wording there; leave the field empty to use the standard text shown as the placeholder. It also covers a disabled agent — while it is on, the widget stays on your site and shows the notice instead of disappearing.

Offer visitors other contact channels

Give visitors a choice of where to contact you while keeping Web Chat on your website. For example, show your connected Telegram account alongside a custom Viber number or TikTok profile. Each destination opens a separate conversation in that service; your Web Chat conversation is not transferred.

1. Open Channels on your messaging agent, select Configure branding on the Web Chat row, then open Channels in that settings window.
2. Edit Channel heading to change the text above the app choices, or leave it blank to use the default in the visitor’s language. Use Connected channels to choose which connected accounts to show, edit their Button label, and change their order. Accounts need a healthy connection and usable public contact details. Use Reconnect when those details are unavailable. Instagram and Facebook connections that were not completed appear as Not connected; use Connect to finish connecting them.
3. Under Custom links, select Add link, choose a Channel, and enter its destination. Choose a preset under Icon library, or select Upload your own image followed by Choose image. Review the Button preview before adding the link. For LinkedIn, X, Threads, Snapchat, Pinterest, WeChat, LINE or KakaoTalk, choose Other link, enter an HTTPS destination, and select the matching preset icon. Uploads accept PNG, JPEG or WebP up to 2 MB; animated images are not supported. Select Add link to add it to your draft.
4. Review the preview and select Save changes to publish. Select Preview channels after a message to see the compact channel buttons visitors see immediately after sending their first message. The launcher bubble opens a sample chat preview. Adding, editing or deleting a link only changes the draft until you save. If you close Web Chat Settings with unsaved changes in either tab, choose Keep editing to save them first or Discard changes to leave. Save appearance edits with Publish Appearance and channel edits with Save changes. You can add up to six custom links, with button labels up to 12 characters.

Custom links provide a destination; they do not connect that service to your agent. You can show multiple destinations for the same service, including custom links alongside connected accounts. Repeated destination URLs are allowed; use distinct button labels to explain their purposes. Switching Show channel buttons in the chat off hides these choices while leaving Web Chat available. Existing Web Chats keep these choices hidden until you turn Show channel buttons in the chat on and save. Newly created Web Chats enable the choices by default.

Visitors initially see the channel labels. Once they send a message, the choices become compact icons; More opens additional destinations. The settings show clicks for each destination over the last 30 days. These counts measure link clicks, rather than completed conversations or sales.

Saved channel changes appear when a visitor reloads the widget. Connection-health changes are checked periodically while it is open. If an account is missing, check its connection and public contact details, or add a custom link with a valid destination.

Add Web Chat to your Shopify store

If your store is connected through the Versafy AI app on Shopify, you can put Web Chat on your storefront without editing theme code. This keeps your theme untouched, so a theme update never wipes the chat, and uninstalling the app removes it cleanly.

1. Open the Install code on your site block of the Web Chat row. It opens on Shopify when a store is connected through the Versafy AI app.
2. If you have several stores, pick the store.
3. Select Add to Shopify store, then Add chat in the message that names your store. If the chat is already switched on in your theme, it appears on your store right away. Cancel leaves your store unchanged.
4. When the message says Chat added, select Open theme editor. Shopify opens your theme editor with Chat widget switched on under App embeds.
5. Select Save at the top right of the Shopify theme editor. The chat now appears on your storefront.

If you close the message with Done, the row keeps an Open theme editor button for the same step.

To show a different agent’s chat, open that agent’s Web Chat row and select Add to Shopify store for the same store; it replaces the chat that was there, and no second visit to the theme editor is needed. After you regenerate the widget token, select Add to Shopify store again so the store uses the new code. To take the chat off your storefront, select Remove from store and confirm with Remove chat. Pages Shopify has cached can show the chat for a few more minutes.

Keep in mind:

• The chat is switched on per theme. After you publish a different theme, select Open theme editor again and save.
• If you pasted the Versafy code into theme.liquid earlier, remove it from your theme so the store keeps a single setup.
• Store unavailable means Versafy could not reach the store. Reconnect it under General → Integrations → Shopify, then try again.
• Changing a store requires permission to manage both agents and Shopify. Without it you see the store’s status only.
• While your workspace has a store connected through the Versafy AI app, the chat footer shows a small Versafy icon instead of the Powered by Versafy.ai text, on every site where the chat runs.
• Stores connected with your organization’s own Shopify app show the one-line code instead. Paste it before the closing </body> tag of theme.liquid.

Style the chat button with your site’s CSS

When the chat button should match your site’s design, you can style it from your own site’s CSS. For example, #versafy-chat-launcher { box-shadow: none; } removes the button’s shadow.

Use these names in your CSS:

• #versafy-chat-launcher — the chat button;
• #versafy-chat-window — the frame of the chat window;
• .versafy-chat-open — added to both while the chat is open.

Rules written with these names take priority over the widget’s own styles. To move the button, for example so it clears a cookie banner, use Offset from Side and Offset from Bottom in Configure branding instead. They move the button and the chat window together; moving only the button with CSS leaves the window where it was, so the button can cover the open chat. Other class names on these elements may change without notice, so do not rely on them. The inside of the chat window (messages, header, and message box) cannot be styled from your site; use Configure branding for colors, fonts, and the button. Check your changes on a test page before publishing them.

Give Web Chat useful page context

Optional context helps your agent answer with awareness of what the visitor is currently viewing. For example, your website can tell the agent which product, help article, account reference, language, or order page is open, so the visitor does not have to repeat that information in their first message.

Your application may provide its own field names and structure as a JSON object; there is no required Versafy customer or account format. Add static context to the Web Chat embed with data-context:

<script
  src="https://app.versafy.ai/widget-loader.js"
  data-token="ww_your_token"
  data-context='{"currentPage":"/products/blue-chair","locale":"en","product":{"sku":"CHAIR-01"}}'
  async
></script>

If the visitor moves between pages without a full reload, your website developer can update the context by dispatching the versafy-widget-context browser event with a detail.context JSON object. Keep the context concise. It supports nested objects, arrays, text, numbers, true/false values, and null; unsupported or oversized context is ignored.

Website-provided context helps with conversation relevance but does not prove who the visitor is and cannot grant permission to perform protected actions. Never include passwords, API keys, access tokens, payment details, or other secrets. If your use case requires verified signed-in account details, contact Versafy support to plan a secure server-side connection.

The Demo Widget provides a controlled test page for demonstrations. Configure its allowed website context and use it only for testing; it is separate from the embed used on your production website.

Configure AI Reply

AI Reply controls when and how automation participates in a real conversation. It is on for a new agent, and no AI reply reaches a customer until the agent is active — use Test to see what the agent would say before you activate it. (A disabled agent still sends nothing of its own; the one thing that can reach a customer then is a channel’s configured Offline message.) Write concise system instructions and configure:

• how much recent conversation context to use;
• when inactivity begins a new session;
• whether an unanswered earlier outreach should be included when a customer returns;
• how long to wait for rapid consecutive messages before replying;
• how long replies should be on channels with message limits;
• whether a human reply pauses automation;
• whether paused conversations trigger a team notification;
• whether messages on channels with AI replies off trigger a team notification.

Switching AI Reply off stops AI replies on every channel at once, so every answer becomes your team’s to write. It does not touch the Offline message: a channel whose own AI replies switch is off keeps sending its configured text, and Web Chat keeps showing its notice. A channel whose switch is still on has neither — the customer’s message simply waits in the inbox, so switch it off as well if you want people told you are away. Because an agent-wide silence is easy to forget, an AI Reply off badge appears beside the agent’s status — on the agent card, in its settings header, on the Connected Channels card, and in the Conversations header — and the per-channel AI replies switches are dimmed, since they no longer decide anything about AI replies.

Enable live replies only after testing every connected channel.

Let the agent learn from its conversations

Your agent can get better from the questions it didn’t resolve: Conversation Quality drafts changes to its instructions and knowledge-base articles from how your team answered them. The Self-learning setting at the top of the System Prompt card decides how much of that the agent may do and how much waits for your OK — from Off to Full autopilot. The System Prompt card stays on the AI Reply tab when AI Reply is switched off, since the agent keeps learning from your team’s answers. See How your agent improves itself for what each mode does.

Reconnect a reply to an earlier outreach

A customer often answers days after you wrote to them. Your colleague pitched something on Friday, the customer replies “yes, let’s do it” on Monday — and by then the conversation has been quiet long enough to count as finished, so the agent would greet them as a stranger and ask how it can help. Bridge prior outreach prevents that: the agent sees the message you sent and answers as a continuation instead of starting over.

Open the agent’s AI Reply settings and switch on Bridge prior outreach. Two limits sit under it:

• Max age (days) — how far back an unanswered outreach still counts. The default is 7 days; a reply to something you sent last month usually needs a person, not an agent working from stale context.
• Max messages — how many of those earlier messages to carry over. The default is 10.

It only applies when the earlier conversation ended on a message you sent that nobody answered. A conversation that ended on the agent’s own reply starts fresh, because there is nothing left hanging. Customers who reply quickly need nothing from this setting — the exchange is still part of the same conversation and the agent already sees it.

Nothing changes in the thread you see; the earlier messages are shown to the agent as background so its first answer makes sense.

One thing worth knowing: if Pause AI on human intervention is on, writing to a customer yourself pauses automation for that conversation, and the agent stays silent when they reply — that is the setting doing its job. Resume the conversation when you want the agent to take over, and it will still pick up the earlier outreach as context.

Configure agent capabilities

Capabilities let the agent move a conversation toward an outcome rather than only answer questions. A sales assistant might capture contact details and book a meeting; an order assistant might check product information, collect an order, prepare Nova Post delivery, and create a CRM follow-up for the team.

The AI Behavior area can enable customer-information capture, smart skip, escalation to a human, sentiment review, calendar booking, commerce actions, CRM actions, and delivery tools. Availability depends on connected services and your plan.

Choosing an agent for Send Email

In Send Email tool settings, the dropdown lists unavailable Email Agents as disabled choices. The text beneath each name explains how to activate that agent, connect a sending mailbox, or change its email category reply modes before you select it.

Enable Schedule Call when a customer should be able to ask for a future call. Open the capability first, select the Voice Agent that will place the call and its outbound caller number, then switch it on. If the customer writes a different number—or your AI Instructions specify one for a particular situation—the agent uses that exact international number. A simple “call me” request can use the trusted number already captured from the customer or channel. Test Chat simulates this capability and does not create a real callback.

New agents start with AI Reply, customer-information capture, and Escalate to Human enabled. Escalation notifications initially use your workspace’s Versafy system email channel; you can change or add notification destinations at any time.

For calendar booking, choose a connected calendar and set working hours and meeting defaults.

Decide what escalation does to the agent

Escalation exists so a person can take over a conversation the agent should not finish alone. The part worth deciding is what happens in the minutes between the alert and someone actually opening the chat. If the agent goes quiet the moment it escalates, a customer who is mid-conversation sees silence and often keeps writing—“hello?”, “are you there?”—which reads worse than a holding answer. If the agent keeps talking, the customer stays served, but a genuinely angry person may be further annoyed by another automated reply.

Open the agent’s Escalate to Human capability and choose under When the AI escalates:

• Always pause the AI — the agent stops replying and the conversation waits for a teammate. Best when your team answers quickly, or when an automated message after an escalation would look careless.
• Never pause the AI — the agent keeps answering while your team is alerted. Best for busy channels, out-of-hours traffic, or anything where a wait would be visible to the customer.
• Let the AI decide — the agent keeps answering by default and stops only when carrying on would make things worse, such as a customer who explicitly demanded a person.

Every option alerts your team and creates or moves the CRM record in exactly the same way; only the customer-facing behaviour differs. New agents start on Never pause the AI so they keep answering while your team is alerted. Existing agents with no saved choice retain Always pause the AI until you change it.

When the agent keeps replying, it raises only one escalation per conversation session: later escalation attempts in the same session send no second alert, so keeping the agent live does not multiply notifications. A new session starts the count over.

Use Notification channels in the same capability to choose which destinations receive the alert. A new agent already has Versafy (system email) selected, so escalations reach your workspace owner’s email without any setup — add or clear destinations whenever you want the alert to go somewhere else.

Set up follow-ups

Follow-ups help restart promising conversations after a customer goes quiet—for example, checking whether a shopper still needs help after asking about a product. Open Follow-ups to create a sequence for customers who have not replied. Choose eligible connected channels and add ordered steps.

For each step, set:

• how long to wait;
• minutes, hours, or days;
• AI (smart) for a context-aware follow-up or Fixed text for approved wording;
• fixed text when that mode is selected.

Order steps carefully and keep the sequence respectful. New customer activity or human control can stop pending follow-ups according to the visible conversation state.

Assign knowledge

Knowledge keeps answers grounded in your approved products, services, and policies across every connected channel. Open Knowledge and select the relevant Knowledge Base folders. Avoid assigning unrelated regions, brands, or policies. The facts the agent learned from your team’s answers need no assignment and are not listed there: it always uses its own. See Knowledge Base and Facts your agents learned.

Configure CRM and delivery

CRM makes qualified conversations visible to the people who must continue them. For example, a website lead can enter the correct sales pipeline with its contact details and conversation context. Open CRM to select a connection, choose routing by channel, control when conversation records are created, and decide how returning visitors are handled. If chat mirroring is available, confirm that your CRM supports the selected channel and account.

Contacts on the AI exclusion list should be routed consistently so your team knows automation is paused for them.

Delivery lets a chat agent act as an order-booking assistant without Shopify: it can collect items and recipient details, help choose a delivery location, confirm payment and price, prepare a waybill, and notify the fulfillment team through CRM. The Delivery tab requires both a CRM connection and a verified delivery integration. Enable it only for agents expected to discuss and confirm delivery-bearing orders.

Test a Messaging Agent

Testing protects every connected audience from an unreviewed change and reveals channel-specific differences before launch. Use Test Chat for quick behavior checks. Also send a real test through every connected channel because channel formatting and limits differ.

Test short messages, several messages sent quickly, media or unsupported attachments, human takeover, a returning conversation, and any enabled tools.

Disable or delete a Messaging Agent

Use Disabled to stop the agent while preserving its setup; channels whose Offline message is on keep telling customers you are away, so decide whether you want that before switching off. Before using the Danger tab to delete it, review connected channels, website embed code, open conversations, follow-ups, CRM behavior, and delivery settings. Remove or replace live website embeds as part of the same change.

When your agent stops answering

Customers keep writing whether or not your agent can reply, so it is worth knowing what they experience while something is blocking it — and how you find out.

Your customers receive nothing by default. When the agent cannot answer for a reason on your side, it stays silent rather than sending an automatic “I’m temporarily unavailable” reply. Such a reply told your customers about your account, repeated itself on every message they sent, and gave them nothing to act on. On Web Chat the visitor sees the same thing — the chat opens and simply gets no answer.

One case is different. Channels with their own Offline message enabled keep telling customers you are away while the agent is disabled — once per conversation session, not on every message. Web Chat ships with that section on, so its visitors see the notice unless you turn it off; messenger channels are off until you enable them. This covers only an agent you switched off deliberately; a depleted balance, a spending limit, or a deactivated workspace stay silent.

If the answer itself fails. Everything above is about your account. When the agent is running normally and the reply simply fails to come out on our side, your customer gets one short apology asking them to try again, rather than silence. This is rare, and it says nothing about your account.

Your customers’ messages reach you either way. Whatever the cause, incoming messages stay in your inbox with the customer’s messages waiting: nothing is lost, and you can reply by hand at any time. If your balance or spending limit is the blocker, the agent resumes on its own once you clear the block. If the agent itself is switched off, its connected channels keep collecting messages, Web Chat included: while its Offline message is on, the widget stays on your site, shows the notice, and still delivers what visitors write to your inbox. Turn that section off and the widget disappears from the site while the agent is off, as before. If your workspace is deactivated, messages are still recorded, but Billing is the only page you can open until the workspace is active again.

You get an alert either way. It names the agent, the channel, what is blocking the reply, and what clears it. It arrives at most once a day per cause, so a busy channel cannot flood you, and it keeps arriving each day for as long as the block lasts. It goes to the destinations you chose under General → Notification Channels → Account alerts; if you chose none, Versafy emails your account owner. This alert cannot be turned off — it reports that your customers are already going unanswered.

Four things block replies:

If your plan expired or your workspace was deactivated, your agents were switched off with it — so reactivating the workspace is the step that matters, not the agent’s own toggle.

Troubleshoot a Messaging Agent

A channel does not receive messages

Confirm the channel shows as connected, the agent is active, and the correct account or page was selected. Reconnect if authorization has expired.

The agent generates but does not send a reply

Check whether the agent is activated, then channel status, human takeover state, contact exclusion, and whether the conversation is paused.

Customers write but get no reply at all

Check your balance, your spending limit, and whether the agent is active — see When your agent stops answering. Look for the alert email; it names the specific cause. If every channel is silent at once, look for the AI Reply off badge beside the agent’s status: replies are switched off agent-wide on the AI Reply tab. If only one channel is silent, check its AI replies switch on the Channels tab — a label reading AI replies off means the channel is set to human handling (see Pause AI on one channel).

Replies are duplicated or badly timed

Review the rapid-message wait setting and test using one channel at a time. Check the conversation for both native-platform and Versafy operator replies.

The agent keeps replying after handing over

Check When the AI escalates on the agent’s Escalate to Human capability. On Never pause the AI and Let the AI decide, continuing the conversation is the intended behaviour. Switch to Always pause the AI if you want the agent to stop, or pause the individual conversation from its thread header.

Web Chat does not appear

Confirm the website URL, live embed code, current widget token, and page placement. Allow time for saved appearance changes to propagate. If the agent is disabled, the widget only stays on the site while the channel’s Offline message is on; with it off, the widget is hidden until you activate the agent again.

On WordPress, a caching or optimization plugin can copy the chat script onto your own site. You can recognize it in your page’s source code: the Versafy script tag points to your own domain, for example /wp-content/cache/min/1/widget-loader.js, instead of app.versafy.ai. To fix it:

1. Select WordPress in Install code on your site, copy the embed code again, and replace the old code on your site. It includes data-no-minify="1", which stops WP Rocket from minifying the script. If WP Rocket also combines JavaScript files, add widget-loader.js under File Optimization → Excluded JavaScript Files. With another plugin, exclude widget-loader.js from JavaScript minification and combining in that plugin’s settings.
2. Clear the plugin’s cache, then reload your site.

Clear or enable scheduling tools

Unavailable destination agents include a Go to agent link after their setup instructions, opening that agent’s editor.

Scheduling tools clear their destination settings when disabled. Saving a complete configuration enables the tool automatically. Use Clear settings to remove the selections; for Send Email and Send WhatsApp, save afterward to apply the cleared configuration. Schedule Call changes are saved immediately.

Related guides

• Conversations
• Conversation Quality
• Agent roles and instructions
• Notification Channels
• CRM integrations
• Knowledge Base