How to design external automations to coexist well with Kronos AI
If you run ManyChat, Instagram's native auto-replies, or WhatsApp greeting messages alongside Kronos, design those flows so your AI agent can pick the conversation up cleanly. One core rule does most of the work.
Before you read: does this apply to you?
This guide is only for you if your goal with the automation is to accomplish something through a conversation on the inbox or social network — qualify a lead, book a call, sell a product, give support, run an upsell, recover a cart. Any goal that depends on the lead replying and the conversation moving forward.
If your only goal is to send something automated and end there (deliver a PDF when someone comments a keyword, send a discount code on the first DM and nothing else, post fixed business hours to after-hours messages), you don't need any of what follows. That said — if your real goal IS conversational but you're using fire-and-forget automations, you're leaving money on the table. The data below shows why.
The core rule
Every external automation on Instagram, Messenger, or WhatsApp with a conversational goal must end with an open-ended question that invites the lead to reply. The moment the lead replies, your Kronos agent picks up control and continues.
"Thanks for contacting us, we'll get back to you shortly."
No reply. Agent never receives anything. Lead cools off.
"Tell me briefly what you're looking for and I'll help you right now."
Lead replies. Kronos picks up. Conversation continues.
Why it matters: the data
- Broadcast messages without a CTA inviting a reply get very low response rates. The interaction ends on delivery.
- Messages with clear CTAs ("reply YES", "reply BOOK") measurably raise response rates.
- Reference: conversational SMS with explicit CTAs reaches ~45% reply rate, vs ~3–4% for cold email (SalesCaptain, 2026).
- ManyChat's own recommended pattern: use the Open Conversation action, tag the lead, pause the bot during handover, end on an open question.
Translation: if you're investing time or money in a conversational automation, ending it without an invitation to reply wastes the entire flow.
How Kronos behaves when an inbound message arrives
- 1Meta's webhook delivers the message to Kronos's backend.
- 2Kronos finds the existing conversation for that contact on that account. If none exists, it creates one.
- 3If the conversation has an agent assigned (default when you set an agent as the assignee on that inbox), the agent reads the message and replies. No keyword, no trigger — any customer message fires the agent.
- 4If the message arrived during an external flow (ManyChat or Meta auto-reply), what happens next depends on that flow's configuration. If it released control, the next reply lands clean in Kronos. If it's still running, both systems can answer the same customer — which looks bad. You have to coordinate.
Kronos does not distinguish whether a conversation was started by an external automation or a human. To Kronos, any inbound message on a conversation with an assigned agent fires a response. Designing the external flow is your responsibility.
Recommended pattern: warm handoff
The industry term is warm handoff: when an automation finishes its part and passes the conversation to another entity (human or AI) with enough context for them to continue without the customer feeling the switch.
In the Kronos + ManyChat context:
- Design your ManyChat flow to capture minimum lead info (name, what they want, budget if applicable) in short steps.
- End the flow with an open-ended line, e.g. "All set. So I don't waste your time, tell me in one sentence what you'd like to achieve and I'll take it from here."
- Trigger ManyChat's Open Conversation action. Pause the bot. Tag the lead.
- The customer replies. Kronos receives the inbound. Your agent picks up the history and continues.
Real limits of Meta's native auto-responders
| Tool | Limitations |
|---|---|
| Instagram Instant Reply (Meta Business Suite) | Single static message, same for everyone, only on the first DM. No branches, no keywords, no comment-to-DM. |
| Quick Replies (IG & Messenger) | Typing shortcuts for humans. Not real automation. |
| WhatsApp Business app greeting message | Static, generic, no conditional logic, no scheduling. Customer still waits for a real person. |
These tools aren't bad — they're limited. If your native automation ends with "we'll get back to you shortly," replace it with one that invites the customer to keep talking. That one-line change is the difference between a dead conversation and one your agent can convert.
Patterns: what to do, what to avoid
Do this
- - Close every flow with an open-ended question. Always.
- - Pause the external bot and tag the conversation on handoff.
- - Keep the external flow short. Hand off early to Kronos.
- - Use external automation only for first-touch, resource delivery, or quick segmentation.
- - Document which automations are live and where they hand off.
Don't do this
- - Mass broadcasts without a CTA.
- - ManyChat flows that end on a link and close.
- - Leave the ManyChat bot running after handoff (both systems answer at once).
- - Use closing keywords ("exit", "menu") without a bridge to the inbox.
- - Rigid form-style steps with no escape hatch when the customer gets stuck.
Strong recommendation: prefer conversational goals
If your instinct is "I just want to send the PDF and call it a day," reconsider. Conversational SMS with a CTA sits near 45% reply rate. Cold email sits at 3–4%. That's not marginal — it's an order of magnitude.
Even if your stated goal is "deliver the PDF," adding "did you read it? want me to walk you through how to apply it to your case?" multiplies conversion. The send becomes the entry door to a conversation, and the conversation is where your Kronos agent closes. Cost of adding the line: zero. Cost of skipping it: most of the leads who opened your message.
Final checklist
- The last message of the flow ends with an open-ended question or explicit CTA to reply.
- If using ManyChat, the "Open Conversation to inbox" action is configured and the bot pauses at the end.
- The inbox has a Kronos agent set as the default assignee.
- You tested the flow with a real test account — the customer's reply lands in Kronos and the agent responds.
- You don't have two automations listening to the same event. If both exist, one is disabled.