Key takeaways
- Change three things before you send any script: the customer’s name, one detail from their message, and a real time. If you can’t change all three, pick a different script.
- Lead with the action. “Here’s what I can do” beats “Unfortunately, I can’t.” Never quote a policy without an option in the same message.
- Replace “Is there anything else?” with “Did I get all of that for you?” The second closer tells you whether the issue is actually solved.
- Keep your scripts and your help center in sync. Scripts tied to prices and policies go stale first, so review the library every quarter.
Every customer wants three things from support: a fast reply, a clear answer, and the sense that someone read their message. Live chat scripts let your team deliver all three on every shift, without burning agents out or making the conversation feel canned.
Below are 88 live chat scripts for 12 situations, plus three full sample conversations from hello to goodbye: greetings, proactive messages, refunds, delayed orders, password resets, after-hours replies, handoffs and angry customers. Copy one, swap what’s in the brackets, send.
Use live chat to support your customers in real time
What is a live chat script?
A live chat script is a pre-written reply that a support agent adapts during a conversation: a greeting, an answer to a common question, a refund confirmation, a handoff. It is a draft the agent edits for the customer in front of them, not an auto-reply that fires with nobody reading.
Scripts speed up replies, keep your brand voice the same across agents, and give new hires something to start from on day one. They are one of the most practical benefits of live chat for a growing support team. Customers expect quick answers, too: 82% now expect immediate resolution of a problem from support agents.[1] For response time benchmarks, see our live chat statistics.
Three things every good script does:
- Names the customer and the specific issue in the first line.
- States the action the agent is taking right now.
- Offers a next step with a real time the customer can hold you to.

How to use these scripts
Every script uses square brackets for anything you must change. Keep the same placeholders across your whole library so agents learn them once.
| Placeholder | What to swap in |
|---|---|
| [customer name] | First name only, spelled the way they spell it |
| [your name] | The name customers see, not your internal handle |
| [company] | Your store or brand name |
| [order number] | The full reference, including any prefix |
| [date] / [timeframe] | A real date or deadline: “by 5pm Friday”, never “soon” |
| [amount] | The figure and the currency |
| [link] | The exact page, not your homepage |
| [option A / option B] | Pick one, delete the rest |
Two rules on when not to use a script. If you can’t tell what the customer is asking, don’t send anything pre-written: a quick reply to the wrong question costs you more than a slow, correct one. And if the customer has already told you the answer, never paste a script that asks for it again.
Jump to a situation
- Greeting and opening scripts
- Proactive and promotional scripts
- Refunds, returns and cancellations
- Order status and tracking
- Technical troubleshooting
- Waiting and putting customers on hold
- Apologizing
- Transferring chats
- Angry customers
- Out-of-stock and alternatives
- After-hours and out-of-office
- Closing the chat and surveys
- Three sample live chat conversations
- Scripts for WhatsApp, Instagram and email
- What to say and avoid
- Scripts by industry
Live chat greeting and opening scripts
The first message tells the customer how much effort this chat will take. Say who you are, sound like a person, and ask one question they can answer in a line. Never open with a menu. For more on the different types, see our guide to welcome messages.

First-time visitors
Simple hello
Hi [customer name], thanks for stopping by. I’m [your name]. Let me know if you need help with anything.
Welcome with a question
Hello and welcome to [company]. Got a question about [product or service]? I’m here.
Low-pressure
Hi there, I’m [your name] at [company]. Have a look around, and if anything is unclear, type it here and I’ll answer right away.
Morning, afternoon or evening
Good [morning/afternoon/evening], [customer name]. This is [your name] from [company]. What can I help you find today?
Returning visitors and previous conversations
Welcome back
Welcome back, [customer name]. Good to see you again. What can I help with today?
Picking up where you left off
Hey [customer name], been a minute. Want to pick up where we left off, or is this something new?
Following up on an old issue
Hi [customer name], last time we were sorting out [previous issue]. Did that get resolved on your end, or do you want to keep going?
Continuing with a colleague’s thread
Welcome back. I see you and [previous agent name] were working on [issue]. I have the full thread, so there’s no need to repeat anything.
Opening a chat the customer started
Acknowledging the first message
Thanks for writing in, [customer name]. I’ve read your message about [issue] and I’m looking into it now.
Asking for the one detail you need
Happy to help with that. Could you send me your order number? It starts with [prefix] and is in your confirmation email.
Confirming you understood
Just so I get this right: you [restate the problem in their words], and you’d like [what they want]. Is that correct?
After a chatbot handoff
Hi [customer name], I’m [your name]. I can see you were chatting with our assistant about [issue], so I have everything you’ve told it. Let’s pick it up from there.
When the queue is long
Thanks for waiting, [customer name]. We’re busier than usual this morning. I have you now. What’s the issue?
When a customer writes in all caps
I can see how important this is, [customer name], and I want to get it right. Tell me what happened and I’ll start on it now.
Proactive and promotional live chat scripts
Proactive scripts trigger when a visitor lingers on a page, hovers near a checkout button or looks ready to leave. The goal is to offer help at the moment they need it without interrupting a calm browsing session. Our guide to proactive live chat covers the trigger rules, and live chat triggers explains which events to use.

On the pricing page
Offering a walk-through
Hi, looks like you’re checking out our pricing. Want a 60-second walk-through of which plan fits your team size?
On the checkout page
Checkout trouble
Hi, looks like checkout is giving you trouble. Want me to walk you through it, or is there a discount code I can help you apply?
Open cart
Hey, I noticed your cart has been open for a few minutes. Anything I can sort out before you finish?
On product and category pages
Choosing between two options
Hi, need help picking between [option A] and [option B]? I can give you the short version.
Can’t find the item
Hey, if you’re trying to find something specific and it isn’t showing up, tell me what you’re after and I’ll point you to it.
On the help center
Not finding the answer
Looks like you’ve been reading about [topic]. Did you find what you needed, or would you like me to answer it directly?
Promotions and discounts
Promotional scripts work when they feel like a tip, not a pitch. A short message that gives the customer something useful (a code, a deadline, a heads-up) earns goodwill. A long one that reads like a banner ad earns a closed chat window.

Unlocked discount
Hey, you’ve unlocked [10% off] on this visit. Use code [PROMO] at checkout and it will apply automatically.
Price drop
Hi, quick heads-up: [product name] just dropped to [discounted price]. The sale ends [date] if you want to grab it.
Sale reminder
Hi, our [season] sale starts [date]. Want me to email you the morning it goes live so you don’t miss it?
Code at checkout
One thing before you finish: here’s a code for [10% off]: [CODE]. Drop it in the discount field and your total updates.
Free shipping offer
Looks like you’re checking out. Want a code for [free shipping] before you go?
Customer service chat scripts by situation
These run from money questions to orders to technical problems, then the moments in between. Each one leads with the action and ends with a next step.
Refunds, returns and cancellations
Refund and return questions are the highest-stakes chats your team handles. The customer is already frustrated, the money has already left their account, and one bad reply turns a refund into a chargeback. These scripts give you time, set clear expectations and protect the relationship even when the answer is no.
Approving a refund
Hi [customer name], thanks for reaching out. I’ve reviewed order #[order number] and approved a full refund of [amount] to your original payment method. You’ll see it within 5 to 10 business days, depending on your bank. Anything else I can sort out for you today?
Refund in progress (customer is checking)
Good news: your refund for order #[order number] was processed on [date]. Most banks post refunds within 5 to 10 business days. If you don’t see it by [date plus 10 days], reply here with a screenshot of your statement and I’ll escalate it the same day.
Declining a refund (outside the policy window)
I hear you, and I’m sorry this didn’t work out. Your order was placed on [order date], which falls outside our [number]-day refund window, so I can’t issue a full refund. Here’s what I can do: [store credit / partial refund / exchange]. Which works best for you?
Starting a return
Happy to help with the return. I’ve created return label #[return ID] and emailed it to [customer email]. Drop the package at any [carrier] location within 14 days. Once it reaches our warehouse, your refund processes within 2 business days.
Offering an exchange
I can swap that for you. Which [size/color/model] would you like instead? I’ll reserve it now and send the return label with it, so you’re never without one.
Canceling an order that hasn’t shipped
Caught it just in time. Your order hasn’t shipped yet, so I’ve canceled it. Your card was authorized but not charged, and the hold drops off in 3 to 5 business days.
Canceling an order that has shipped
Your order shipped this morning, so I can’t cancel it directly. The simplest fix: refuse delivery when the carrier arrives, or accept it and start a free return. Either way, you won’t pay return shipping. Which works better?
Canceling a subscription
Confirmed: your [plan name] subscription is canceled. You’ll keep access until [end of billing period], and you won’t be charged again. If you canceled for a specific reason, I’d like to hear it. Sometimes there’s a fix we can offer that you didn’t know about.
Order status and tracking
“Where is my order?” is the most common e-commerce support question. The script has to give a real answer fast, set expectations when the news is bad and offer an action the customer can take. Vague reassurance like “it should arrive soon” makes things worse.
Order is on the way
Order #[order number] shipped on [ship date] via [carrier]. Tracking: [link]. Estimated delivery: [date]. Want me to set up a notification for when it’s out for delivery?
Order is delayed
I can see order #[order number] is running about [number] days behind schedule. Here’s what happened: [honest reason: warehouse delay, carrier disruption, weather]. New estimated delivery: [date]. If you’d rather not wait, I can cancel and refund right now.
Tracking says delivered, but nothing arrived
That’s frustrating, and I’ll help you sort it out. Tracking shows delivery on [date] at [time]. Three quick things to check first: (1) side doors, porches or neighbors, (2) anyone else in your household, (3) the building’s front desk, if you have one. If none of those turn it up, reply within 48 hours and I’ll file a lost-package claim and ship a replacement.
Item arrived damaged
I’m sorry it arrived like that. Could you send a photo of the item and the packaging? As soon as I have it, I’ll send a replacement or refund it, whichever you prefer. You don’t need to return the damaged one.
Changing the address (not shipped yet)
Let me check if it’s still in time. Good news: your order is still in our warehouse, so I’ve updated the address to [new address]. Can you confirm that’s correct before I save it?
Changing the address (already shipped)
It already shipped, so I can’t change the address on our end. Two options: (1) [carrier] sometimes lets you redirect the parcel on their site, or (2) refuse delivery and I’ll reship to the new address at no charge.
Technical troubleshooting
Technical issues like password resets, lockouts, login errors and payment failures need a script that diagnoses before it solves. Jumping straight to “have you tried clearing your cache?” makes the customer feel unheard. Start with the symptom, confirm the setup, then act.
Password reset
I’ve sent a reset link to [customer email]. Check your inbox and spam folder. The link expires in 60 minutes. Once you’ve set the new password, reply here and I’ll confirm you’re back in.
Account locked
You’re locked out after [number] failed login attempts, which is a standard security measure. I’ve unlocked the account. Try logging in again, and use the reset link if you’ve forgotten the password.
Login error: account not found
That usually means one of two things: the account is registered to a different email, or it was created through [Google/Apple/Facebook] sign-in. Which email have you used with us in the past? I’ll check both.
Payment failed at checkout
Sorry about that. A failed payment is almost always one of three things: an expired card, a billing-address mismatch, or your bank flagging the transaction. Which error message did you see? Paste it here and I’ll point you to the fix.
App or website loading slowly
Let’s narrow it down. Three quick checks: (1) is it slow on both Wi-Fi and mobile data, (2) is it slow in a different browser, (3) does it happen on more than one page? Reply with what you find and I’ll know whether it’s your network, your browser or something on our end.
Asking for a screenshot
Could you send a screenshot of what you’re seeing, including the address bar at the top? It will help me see exactly where it goes wrong.
Waiting and putting customers on hold
Waiting scripts have one job: acknowledge the delay without making it worse. 88% of customers now expect faster response times than they did a year ago.[2] “Thanks for your patience” is hollow on its own. Pair it with what you’re doing right now to help.
Thanking the customer for waiting
Sorry for the wait. I had to dig into your account to give you a real answer. Here’s what I found: [answer].
Busy period
Thanks for hanging on. We’re busier than usual this morning. I have you now. What’s the issue?
Time-sensitive request
I see your request is time-sensitive. I’m pulling in [colleague name] from the [team] right now so we can get this resolved without you having to repeat anything.
Checking your account
Give me 60 seconds to pull up your account.
Checking with a supervisor
I want to double-check this with my supervisor before I give you the wrong answer. Two minutes, tops. Can you stay on the chat?
Checking a specific thing
Let me check [specific thing]. About 90 seconds. Sit tight.
Holding a customer is a small breach of trust. The script repairs it by giving a reason and a time frame, never a vague “one moment.”
Boost customer satisfaction with a professional AI agent
Apologizing
Most unhappy customers don’t tell you they’re unhappy. 84% of customers say they struggle to find information or get help.[3] The customer who complains is doing you a favor: they’re the one who didn’t leave silently. Apologize specifically, fix the problem and say when it will be done.

Apologizing for an error
[customer name], that’s our mistake, and I’m sorry about it. I’m looking into it now, and you’ll have an answer within [timeframe].
Apologizing for a specific incident
Thanks for flagging this, [customer name]. We had a [specific issue] this morning and your order was caught in it. I’m refunding [amount] now and reshipping at no charge.
Apologizing for an outage
We had a technical issue between [time] and [time] today. Our engineering team has a fix in place. Sorry it affected your account. Here’s [credit/refund/replacement] to make up for the trouble.
Declining a feature request
Thanks for the suggestion. Right now, [requested feature] isn’t on our roadmap because [honest reason]. I’ve logged your request so our product team sees it. If anything changes, I’ll email you personally.
Declining without losing the customer
I can’t do exactly what you’re asking, but here’s the closest thing I can offer: [alternative]. Would that solve the underlying problem?
Transferring chats
Handoffs are where most customer trust dies. The customer has to repeat the issue, the new agent has no context and the conversation feels like it’s starting over. Good transfer scripts prevent that. In Tidio, you can reassign a chat to another operator without losing the conversation history.
To a specialist
[colleague name] on our [team] is the right person for this. She handles [topic] all day. I’ve shared the full thread with her so you won’t have to repeat anything. Bringing her in now.
To billing
I want to bring in [colleague name] from billing. She can see your invoice history directly and will get you a faster answer. Two minutes.
Back to a familiar agent
[colleague name] has your file from last time. I’m passing you back to him so you keep continuity. One moment.
Angry customers
Angry customers are testing whether you’ll listen or get defensive. The script that defuses them acknowledges the specific thing they’re upset about, takes responsibility for what you can and offers a real next step in the same message. For the wider playbook, see how to deal with angry customers.

Acknowledging the feeling
I hear you, and I’d be annoyed too. Let me see what I can sort out right now.
Naming the problem
That’s a real problem, and I’m sorry it happened. Can you tell me exactly what went wrong with [issue] so I can fix the right thing?
Owning it and acting
You’re right to be upset. This shouldn’t have happened. Here’s what I’m doing about it: [action].
Asking for the story step by step
Can you walk me through what happened step by step? I want to make sure I’m fixing the actual issue, not guessing.
Clearing up what they mean
When you say [issue], do you mean [interpretation A] or [interpretation B]? I want to fix the right thing the first time.
Out-of-stock and alternatives
An out-of-stock message is a chance to keep the customer in the conversation. Pair every “it’s not available” with a back-in-stock alert or a comparable alternative, and a dead conversation becomes a saved sale.

Back in stock soon
That size is out of stock right now. We expect it back the week of [date]. Want me to email you the moment it’s available? One notification, no marketing.
Backorder
[Item] is on backorder, shipping [date]. You can pre-order today and your card won’t be charged until it ships.
Discontinued
[Item] was discontinued at the end of [year], so I can’t get you that exact one. The closest thing we sell is [alternative]: [link]. Most customers who liked [item] now use this one.
Suggesting an alternative
Sorry about that. Here’s an alternative that might work: [alternative]. The main differences from what you wanted: [one or two differences].
Softening the disappointment
I get it, that’s a disappointment. Let me show you [alternative]. It fits the same use case at a slightly different price point.

After-hours and out-of-office
After-hours scripts have one job: give the customer a real next step. “We’ll get back to you soon” is the worst auto-reply because the customer can’t act on it. Good ones state when you’ll respond, offer self-service options and capture the right contact details so the morning shift can resolve the chat in one message.
Standard out-of-office
Thanks for reaching out. Our team is offline right now. We’re back at [open time] [time zone] on [next business day], and we reply to overnight messages in the order they come in. For order status, check [link] anytime.
Out-of-office with self-service
We’re offline until [open time] tomorrow. Most questions get answered faster in our help center, so try these links first: track an order [link], start a return [link], reset a password [link]. If you still need a human, leave your question here and we’ll reply by [time].
Weekend or holiday closure
Our support team is off for [holiday] and back on [date]. We’ll reply first thing that morning. For urgent shipping issues, [carrier] support is available 24/7 at [link].
Capturing contact details before handoff
Before you go: what’s the best email to reach you on if I need to follow up? And if I solve this overnight, do you want a reply tonight or first thing tomorrow?
Closing the chat and surveys
Closing scripts confirm the issue is actually resolved, not just that the conversation is over. The biggest mistake is the lazy “Is there anything else?” It invites a “no” that ends the chat before you’ve checked whether the real problem is solved. Better closers ask a specific question.

When the customer has gone quiet
Looks like you’ve stepped away. I’m going to close the chat for now, but everything we discussed is logged on your account. If you need me again, just open a new chat.
Last call before closing
Haven’t heard from you in a few minutes, so I’m closing this one out. If anything from this conversation is still open, reply here and it will come back to me.
Thanks and a note on the account
Thanks for reaching out. I’ve made a note on your account so the next agent who picks up knows what we covered.
Checking the answer landed
Glad we sorted that. Does anything from the last 10 minutes still feel unclear?
The better closer
All set on my end. Did I get all of that for you, or is something still open?
One-word survey
Quick favor: did this conversation actually solve your problem? A one-word answer is fine.
Survey link
If you have 30 seconds, I’d value your feedback on this chat: [link]. It goes straight to me and the support lead.
Three sample live chat conversations
Single replies are only half of a chat. These sample conversations show how the scripts above fit together from hello to goodbye. They work as mock chats for training new agents or testing your own flow.
Sample 1: A delayed order
Customer: Hi, where is my order? It was supposed to arrive Tuesday.
Agent: Hi Dana, thanks for writing in. I’m Alex. Give me 60 seconds to pull up your account.
Agent: Thanks for waiting. Order #4821 shipped on Friday via UPS and is running about 3 days behind schedule. A weather delay hit the regional hub. The new estimated delivery is Friday, with tracking here: [link]. If you’d rather not wait, I can cancel and refund right now.
Customer: Friday is too late, I need it for a gift.
Agent: That makes sense. I can cancel it and refund the full $89.50 to your card today, or I can send a replacement by express shipping at no charge, arriving Thursday. Which works better for you?
Customer: Express shipping, please.
Agent: Done. Your replacement ships this afternoon and you’ll get a new tracking email within the hour. Did I get all of that for you, or is something still open?
Customer: That’s everything, thanks.
Agent: You’re welcome, Dana. If it doesn’t arrive Thursday, reply to that email and it comes straight to me.
Sample 2: A login problem
Customer: I can’t log in. It says account not found.
Agent: Hi Sam, I’m Priya. That usually means the account is registered to a different email, or it was created through Google sign-in. Which email have you used with us in the past?
Customer: Maybe my work email? sam@northwind.example
Agent: Thanks. I can see an account under that address, and it was created with Google sign-in. Try the “Continue with Google” button on the login page instead of typing a password. Could you send a screenshot if it doesn’t work?
Customer: That worked, I’m in.
Agent: Glad we sorted that. Does anything from the last few minutes still feel unclear?
Customer: No, all good.
Agent: Great. If you’d rather use a password next time, I can send you a reset link. Just say so here.
Sample 3: A refund outside the policy window
Customer: I want a refund. This jacket doesn’t fit and you won’t answer my emails.
Agent: Hi Jordan, I’m Maya. You’re right to be annoyed that the emails went unanswered, and I’m sorry. Let me look at your order now.
Agent: Your order was placed on September 2, which falls outside our 30-day refund window, so I can’t issue a full refund. Here’s what I can do: an exchange for a different size at no charge, or store credit for the full amount. Which works best for you?
Customer: I’d rather get my money back.
Agent: I understand. I can’t change the refund window, but I can offer store credit with an extra 10% added, valid for a year. Would that work?
Customer: Fine, do that.
Agent: Done. The credit will show in your account within the hour, and I’ll email you the confirmation. Did I get all of that for you?
Customer: Yes. Thanks for actually answering.
Live chat scripts for WhatsApp, Instagram and email
Your customer doesn’t see four channels. They see one brand. If the WhatsApp reply is breezy and the email reads like a legal disclaimer, trust drops on both. Keep the substance the same and adjust length, tone and formatting for the platform.
What stays the same across channels:
- The customer’s name and the order number, always in the first line.
- The action you’re taking, stated plainly.
- The next step, with a time the customer can hold you to.
What changes by channel:
- WhatsApp and SMS: short, one idea per message, no formal sign-off. Emojis sparingly, and only if they’re already in your brand voice.
- Messenger and Instagram DM: slightly longer than WhatsApp. A casual tone fits. Use quick-reply buttons for yes/no and routing questions.
- Email: full context in the first paragraph. Sign off with a name and role, and use a reply-to address a human actually monitors.
- Live chat on your site: conversational, fast, and willing to ask follow-up questions in the same thread.
Here is the same refund approval written for each channel.
Hi Sarah, refund for order #4821 approved. $89.50 is going back to your card in 5 to 10 days. Anything else?
Instagram DM
Hi Sarah! Refund for order #4821 is approved. The $89.50 will hit your card in 5 to 10 business days. Let me know if I can help with anything else.
Subject: Your refund for order #4821
Hi Sarah,
Thanks for getting in touch about order #4821. I’ve approved a full refund of $89.50 to your original payment method. You’ll see it within 5 to 10 business days, depending on your bank.
Best, Alex, Customer Support
Live chat
Refund approved for order #4821. $89.50 is going back to your card in 5 to 10 business days. Want me to send a confirmation email too?
Tidio brings live chat, email, WhatsApp, Instagram and Messenger into one inbox, so the same agent can keep the voice consistent without copying and pasting between tools. For longer copy-paste libraries, see our canned responses and the help desk template for ticket replies.
What to say (and avoid) in a live chat reply
The fastest way to improve script quality is to cut the phrases that frustrate customers and replace them with the honest equivalent. Most bad replies aren’t dishonest. They’re defensive, vague or padded with corporate filler.
| Skip this phrase | Say this instead | Why the swap works |
|---|---|---|
| “Unfortunately, I can’t…” | “Here’s what I can do…” | Leads with the option, not the wall. |
| “Please be patient” | “I’m on it. Give me 60 seconds.” | Names a real time frame. |
| “As per our policy…” | “Our refund window is 30 days, and your order is on day 35. Two options I can offer…” | Cites the rule and the workaround together. |
| “I understand your frustration” | “That’s a real problem, and I’d be annoyed too.” | Validates without sounding scripted. |
| “Let me transfer you to the right team” | “Sarah on billing is the right person. Bringing her in now without restarting your case.” | Keeps continuity, not just a handoff. |
| “Is there anything else?” | “Did I get all of that for you?” | Easier to answer, and gives a clear signal. |
| “We apologize for the inconvenience” | “Sorry, this one’s on us. Here’s the fix…” | Owns the mistake and names the action. |
| “Your call is important to us” | (Delete it. Show it, don’t say it.) | Saying it proves the opposite. |
Three rules sit behind the table:
- Never apologize without naming what you’re apologizing for.
- Never quote a policy without also offering an action.
- Never close a chat without confirming the customer’s question is fully answered.
For a deeper look at the language choices that de-escalate and convert, read our guide to positive scripting, and the live chat etiquette rules for the agent’s side.
Live chat scripts by industry
Your script library should change shape depending on what you sell. An e-commerce script that opens with order tracking will fall flat for a SaaS user asking about an integration error. These four sets cover the most common differences from the general scripts above.
E-commerce
Lead with order status, refund eligibility and shipping times. Add sizing, restock and gift-receipt scripts. Pair every “out of stock” reply with a back-in-stock offer.
Sizing question
Happy to help you find the right fit. What size do you usually wear in [brand you know], and do you prefer a snug or relaxed fit? I’ll tell you which size most customers with that preference choose.
SaaS and software
Lead with login, billing and feature-specific troubleshooting. Most SaaS chats fall into four buckets: “I can’t log in,” “I was charged for something I didn’t expect,” “the integration broke” and “how do I do X.” Build a script for each.
Unexpected charge
Looks like your card was charged on [date] for the [plan name] annual plan. Your team plan switched from monthly to annual at renewal. Here’s the setting that controls that: [link]. Want me to switch it back to monthly and refund the difference?
Hospitality and travel
Lead with booking changes, cancellation policies and confirmation resends. The tone runs warmer than e-commerce, because the customer is often planning something they care about.
Booking change
Looking forward to having you with us on [date]. I’ve updated your reservation to a king room with a late check-in flag noted in your file. Confirmation resent to [customer email]. Anything else for the trip?
Financial services and fintech
Stricter. Every script needs to verify identity before anything sensitive happens, and every script should remind the customer what you will never ask for.
Identity check
For your security, I need to verify a couple of details before we look at the account: the last four digits of your card and the email on file. As a reminder, we’ll never ask for your full card number or your password in chat.
How to save these scripts as macros in Tidio
Tidio calls saved replies macros: a library of replies you can drop into a live chat, a ticket or an internal note in a couple of keystrokes. The steps below follow Tidio’s own Macros guide.
Macros are not on every plan. Macros come with the Growth plan and above, per the pricing page, and are not available on Free or Starter (checked in October 2026). Check that before you build a library your agents depend on.
- In the Tidio panel, open Settings → Macros.
- Click Create a new macro, name it the way an agent would search for it (“Refund approved”), and paste the script.
- Choose whether it’s private to you or visible to every agent, and add a label so it’s easy to find by situation.
- In any conversation, click the Macros icon at the lower left, or type / to open the list and keep typing to filter by name. Type # to filter by label. Pick one, edit the brackets, send.
Scripts with one correct answer, such as order status, opening hours and return windows, don’t have to be typed by a person at all. Lyro, Tidio’s AI agent, builds its knowledge base from your support content and hands the chat to a human when it can’t answer. So keep the facts in your scripts (refund windows, shipping times) in your help center too, and keep your agents’ time for the chats where someone is upset or spending money.
Put your scripts to work in one Tidio inbox
Frequently asked questions
A live chat script is a pre-written reply your support agents adapt to each customer, covering greetings, refunds, troubleshooting, handoffs and after-hours messages. The agent edits the script to fit the conversation. The goal is consistency and speed, with the chat still feeling human.
Say who you are, name the company and ask one open question, like “Hi [customer name], welcome to [company]. I’m [your name], and I’m happy to help. What brings you in today?” If you know why the visitor is on the page, be specific: “I see checkout is giving you trouble. Describe what happens and I’ll fix it from my end.”
Enough to cover the questions that repeat, and no more. For most small teams that’s 30 to 60 in active use, so the 88 here are a menu, not a target. A library nobody can search is slower than typing.
They do when sent blind: the wrong script, an unedited placeholder, a policy quote with nothing after it. They work when the agent has read the message, picked the right moment and changed the details. The script saves the typing. The agent still does the thinking.
Yes, in a different way. Scripts are for your human agents. Lyro answers from your support content, so write the facts your scripts rely on into your help center, and let Lyro handle the repetitive questions while your team handles the rest.
Review the library every quarter, and refresh any script tied to a policy that changes: refund windows, shipping carriers, return periods. Scripts that quote a price, a date or a product name go stale fastest. Put a recurring reminder in the calendar of whoever owns your help center.
Use live chat to support your customers in real-time

