YundaDeskA welcome message is not just “Hi, how can we help?” For cross-border e-commerce teams, it is the first second of a customer conversation. It should show that support is online, understands the customer’s language, and can move the question toward an answer without sounding like a campaign blast.
A good welcome message script is short, variable-driven, and easy for an AI agent to use. Use the templates below as a base, then feed the approved version into your knowledge base so AI can answer first and humans can back it up.
Start with Rules: Warmer Is Not Always Better
A welcome message should answer three things: who is speaking, what it can help with, and what the customer should send next. Do not pack discounts, delivery rules, return policies, and brand storytelling into the first line.
| Variable | Use | Example |
|---|---|---|
{first_name} |
Customer name | Mia |
{language} |
Customer language | English |
{market} |
Country or region | United States |
{local_time} |
Customer local time | evening |
{order_status} |
Order status | shipped |
{topic} |
Entry topic | size / delivery |
Variables are not there to look smart. They remove unnecessary back-and-forth. If a customer enters from the tracking page, say you can help check delivery status for this order.
Welcome Message Scripts for Cross-Border Ecommerce, Website Widget: turn timing into a measurable signal
Website Widget Templates: Catch Customers While They Are Deciding
The website widget should feel light and page-aware. On a product page, do not ask for an email too early. At checkout, be direct about shipping, discount codes, and delivery questions.
| Scenario | Welcome message script |
|---|---|
| Homepage | Hi, this is the YundaDesk AI agent. I can help with products, delivery, returns, and handoff to a human when needed. |
| Product page | Not sure about size, material, or compatibility? Ask here and I will help you check. |
| Checkout page | Trouble with a discount code, shipping fee, or delivery time? Send the question and I will take a look first. |
| Order page | Need to check order progress? Send your order number or checkout email. |
WhatsApp Templates: Sound Human, Do Not Pretend to Be Human
WhatsApp customers expect speed and directness. The tone can be conversational, but do not pretend the AI is a human agent. AI answers first, humans back up.
| Scenario | Welcome message script |
|---|---|
| New customer | Hi {first_name}, this is {brand} support. I can help with delivery, sizing, returns, and order questions. If a human needs to review it, I will hand it off. |
| Existing order | Hi {first_name}, your order is currently {order_status}. If you want to check tracking or update details, tell me what you need. |
| Outside business hours | It is {local_time} in your time zone. AI will handle common questions first. Refunds, compensation, or price changes go to human approval. |
| Multilingual customer | I can reply in {language}. Please describe the issue in the language you prefer. |
Keep the risk line firm. For refunds, compensation, and price changes, do not say “I will process this now.” Say: “I will collect the details and send this for human approval.”
Instagram Templates: Turn Comments and DMs into Clear Questions
Instagram welcome messages often start from comments moving into DM, or from a customer messaging after a post or ad. The job is not to explain everything. It is to turn interest into a clear next step.
| Entry point | Welcome message script |
|---|---|
| Price question | Thanks for asking. Which item are you looking at? Send the product code or a screenshot, and I can check price, size, and delivery. |
| Inventory DM | Send your country or region and the product link. I can confirm delivery availability and estimated shipping time. |
| Ad message | You came in from {campaign}. I can check whether the offer applies, plus shipping fee and estimated delivery time. |
| After-sales DM | If this is about an order, send the order number or checkout email. I will organize the details first and hand off complex cases. |
Do not turn the Instagram welcome message into a full FAQ. On mobile, the customer only needs to know what to send next.
Omnichannel Variables: One Base Script, Channel-Specific Variants
Do not write a separate system for every channel. Keep one base script, then create variants by channel, language, and time zone.
Hi {first_name}, this is {brand}. I can help with {topic_list}. Please send {required_info}. If this involves {risk_topic}, I will route it to human approval.
| Channel | Tone |
|---|---|
| Website widget | Clear, restrained, tool-like |
| Shorter, closer to live chat | |
| Lighter, tied to product interest | |
| Slightly fuller, with the next reply path explained |
This is where an Omnichannel inbox matters. Entry points can differ, while customer profile, knowledge base, and support boundaries stay consistent.
Feed the Knowledge Base: Let AI Answer First
After writing welcome messages, do not leave them as copy-paste snippets. Break them into knowledge base entries so the AI agent can use them consistently.
- Trigger condition: channel, page, customer state, language, time zone
- Message body: the welcome message that can be sent
- Variable rules: how to fall back when data is missing
- Boundary rules: which cases must hand off to a human
For example, a “WhatsApp outside business hours” entry can trigger when the customer is in a quiet-hour window and no human agent is online. AI handles low-risk questions such as logistics, sizing, and delivery. Refunds, compensation, and price changes go to human approval.
YundaDesk getting smarter over time does not mean AI edits scripts on its own. When AI misses an answer, an agent replies, or an agent corrects AI, the system creates learning suggestions you confirm. They only take effect after owner review, and every item is traceable, testable, and revertible.
Use CRM Variants: Speak by Language, Time Zone, and Customer State
The same welcome message should not sound identical for a new visitor, an existing buyer, and an after-sales customer. Cross-border CRM fields can be used from day one: country, language, time zone, social IDs, order status, and segment.
| Customer state | Variant direction |
|---|---|
| New visitor | Explain what support can help with and lower the barrier to ask |
| Existing buyer | Prioritize order lookup, tracking, and address changes |
| After-sales customer | Collect order details first, then decide whether to hand off |
| High-risk customer | Use steadier language and avoid promising refunds or compensation |
Multilingual support should not depend on agents translating in the moment. The AI agent can follow the customer’s language automatically, while the same boundary stays in place: what AI can answer, what humans must back up. See AI answers first, humans back up.
Pre-Launch Check: Keep Templates from Becoming Interruptions
Before the messages go live, run this checklist:
- Each channel has only one default welcome message
- Missing variables have natural fallback copy
- Outside business hours explain that AI answers first and humans back up
- Refunds, compensation, and price changes go to human approval
- Multilingual variants sound native, not translated word by word
- Proactive messages do not interrupt an active customer conversation
If you use proactive outreach, do not treat welcome messages like pop-up ads. YundaDesk supports three modes: observe only, confirm every message, and auto-send. Six guardrails stay in place: cooldown, frequency caps, quiet hours, no interruption when the customer is already chatting, do-not-disturb lists, and human approval for sensitive actions.
A welcome message is not a small decoration for the support team. It is the entry point that decides whether an AI agent can catch the first question. Connect templates, variables, knowledge base, CRM, and human boundaries, and the first reply can feel solid whether the customer comes from a website widget, WhatsApp, or Instagram.