Phone outreach still earns meetings. Senior buyers continue to take business calls when the message is relevant and the rep gets to the point. The opportunity has never been the problem. Execution is.

I’ve seen the same failure pattern across sales teams, service businesses, and centralized call ops. Reps call with a vague opener, rush into a pitch, miss the qualification step, and end the conversation without a clear commitment. A weak outbound script creates inconsistency. No script creates even more of it. Results swing by rep, by shift, and by lead source, which makes coaching harder and forecasting worse.

A useful script for outbound calls works as an operating system, not a paragraph to memorize.

It needs five parts. A reason for the call that sounds specific. A permission-based opener. Qualification questions that surface fit without turning the call into an interview. Objection paths that keep the rep in control. A close tied to one next step, whether that is an appointment, a transfer, a callback, or a disqualification.

That structure matters more when teams run mixed coverage models. Some conversations should stay with experienced reps from start to finish. Some are better handled with AI support for prompting, note capture, and QA. Some should begin with AI qualification and route to a human only after intent, urgency, or complexity is clear. Teams that ignore deployment usually blame the script, when the underlying problem is poor routing, weak handoff rules, or no measurement discipline.

That is the full-stack approach this guide takes.

The eight scripts below are built for real operating conditions across home services, healthcare, legal, insurance, real estate, franchise recruiting, events, and service recovery. Each one includes the language, the context where it works, and the trade-offs that affect performance. The goal is not to hand reps generic templates. The goal is to give you a system you can adapt by industry, track with conversion metrics, and deploy through AI-human workflows, including platforms such as Recepta.ai, without losing call quality or compliance.

1. Lead Qualification and Appointment Setting Script

Qualification calls decide whether your pipeline fills with real opportunities or calendar clutter. Teams that run this script well book more meetings, disqualify faster, and waste fewer rep hours on people who were never going to buy.

This script works best when the goal is simple. Confirm fit, confirm urgency, and earn the next step.

The script

“Hi [First Name], this is [Rep] with [Company]. I’m calling because [specific reason tied to source, area, service history, or inquiry]. Did I catch you at an okay time for a quick question?”

If yes:

“Great. We usually reach out when someone is trying to fix [specific problem]. Is that something you need help with now, or is the timing off?”

Then qualify with two or three questions, not a full intake:

“What have you tried so far?”
“How soon would you want this handled if the option looks right?”
“Who else, if anyone, is involved in the decision?”

If there’s a fit:

“Based on that, the next step is a short appointment so we can look at your situation properly. I have [time option 1] or [time option 2]. Which works better?”

If they hesitate:

“Fair enough. What would you need to know before you’d feel comfortable booking?”

Where it works best

Use this structure any time the call has a clear trigger and a clear next step. Home services teams use it after quote requests, seasonal service windows, and inactive estimates. Healthcare groups use it for preventive visits or lapsed follow-up care, with tighter compliance rules on language and privacy. Legal, insurance, and real estate teams use the same skeleton, but the qualification questions need to reflect risk, timing, and decision authority.

The structure stays consistent. The opening line and the diagnostic question do the heavy lifting.

A practical rule from the floor. Personalize the first sentence from the CRM, then keep the rest of the call clean and controlled. Reps lose calls when they over-customize and start rambling. One relevant detail is enough to show the prospect is not just another name on a list.

List quality and call timing still matter. As noted earlier, weak contact rates usually point to targeting, routing, or dialing strategy problems before they point to script problems. Fix those first.

What works and what doesn’t

• Works: Ask permission early and keep the opener short.
• Works: Qualify for problem, timing, and decision path before offering the appointment.
• Works: Offer two specific appointment slots instead of asking open-ended availability.
• Works: Leave room after a question. Prospects often explain the underlying issue in the pause.
• Doesn’t work: Giving a company pitch before the prospect understands why you called.
• Doesn’t work: Running through five qualifying questions with no explanation of what the appointment gets them.
• Doesn’t work: Using the same wording for a cold list, an inbound hand-raiser, and a reactivation lead.

In an AI-human workflow, this script gets stronger when each stage has a job. AI can handle first-pass outreach, capture the qualification fields, and offer calendar times. A human rep should take over when the buyer asks situational questions, raises objections tied to price or risk, or needs trust built in real time. That handoff model is what turns a script into an operating system, and platforms like Recepta.ai are built for that kind of deployment.

2. Customer Follow-up and Reconnection Script

Revenue from existing customers is usually cheaper to recover than revenue from cold outreach, but reconnection calls still fail when reps call without a concrete reason. A customer who hears “just checking in” has no reason to stay on the line.

Give them timing, context, and a next step.

The script

“Hi [First Name], this is [Rep] from [Company]. We worked with you on [service] before. I’m calling because [renewal date, maintenance window, usage milestone, policy review timing, or follow-up item] is coming up. Do you have a minute?”

If yes:

“The last time we spoke, you were dealing with [brief reminder]. I’m reaching out now because [specific reason tied to value or timing]. Has anything changed since then?”

Then move to a simple decision prompt:

“Would it help to schedule a quick review or service check so you can handle this before it turns into a bigger issue?”

For a soft no:

“Understood. I can send a short summary by text or email, or I can reach out again around [season, renewal month, or date]. Which do you prefer?”

For voicemail:

“Hi [First Name], this is [Rep] from [Company]. I’m calling because [specific service or review reason] is coming up. You can reach me at [number], and I’m also happy to follow up by text or email if that’s easier.”

Why this script works in the field

A reconnection call needs to sound like account management, not a cold prospecting attempt. The customer should immediately understand why now, why you, and what they get by responding.

Specificity does the work. A pest control team can reference the last treatment window. An HVAC company can tie the call to seasonal maintenance. An insurance agency can anchor the conversation to renewal timing or a coverage review. A legal or financial team can reference a prior matter that may need an update. A dental office can reference recall timing, with the right privacy and compliance controls.

The trade-off is simple. Scripts with too little context feel lazy. Scripts with too much context feel invasive or scripted. One relevant reference from the CRM is usually enough.

Reconnection calls should feel like the next logical touchpoint in an existing relationship.

How to run it as a system

This section gets stronger when the script is tied to workflow, not treated as standalone wording. The list should be segmented before the first dial. Recent customers, lapsed customers, declined renewals, and quote-no-close accounts should not get the same opener because the reason to call is different in each case.

Use AI to prepare the call, not to fake familiarity. A platform such as Recepta.ai can pull the last service date, summarize prior notes, suggest the reason for outreach, and trigger a follow-up SMS or email after the call. A human rep should step in when the customer asks account-specific questions, raises trust concerns, or needs a judgment call on timing, pricing, or service scope.

That AI-human split is what makes reconnection campaigns scale without sounding generic.

Practical adjustments by industry

• Home services: “Your last service was [timeframe], and this is usually the point when smaller issues start showing up again.”
• Healthcare and wellness: “You’re due for a follow-up, and we wanted to help you schedule before your calendar fills up.”
• Insurance: “Your policy review window is coming up, and this is a good time to check whether your coverage still matches what you need.”
• Legal or financial advisory: “I’m calling because the work we handled previously may be due for an update, and I wanted to see whether anything has changed.”

What hurts these calls is fake familiarity or vague outreach. If the CRM does not show a real prior touchpoint, keep the reference broad and honest. If it does, use one detail that earns the next 30 seconds of attention.

3. Healthcare and Medical Practice Appointment Reminder and Rescheduling Script

No-shows hit twice. They cut revenue for the hour you held, and they leave staff too little time to refill the slot.

Healthcare reminder calls need tighter control than a standard service follow-up. Front-desk teams have to verify identity, avoid disclosing protected details, and move the patient to a clear yes, no, or reschedule outcome in under a minute. That is why the script matters. It is not just a courtesy touchpoint. It is part of schedule management.

The script

“Hi, this is [Name] calling from [Practice Name]. May I please confirm I’m speaking with [Patient First Name]?”

Once identity is confirmed:

“I’m calling about an upcoming appointment at our office. I wanted to confirm whether you’re still able to attend.”

If yes:

“Great. Please arrive [time guidance if appropriate]. If anything changes, call us as soon as you can and we’ll help you reschedule.”

If no:

“No problem. We can help with that now. Would [option 1] or [option 2] work better, or would you prefer a callback from our scheduling team?”

If voicemail is appropriate under your practice’s rules and consent framework, keep it minimal:

“This is [Name] from [Practice Name] calling for [First Name]. Please call us back at [number] regarding your upcoming appointment.”

What makes this work in practice

The script only works if the workflow behind it is clean. Calling too early leads to forgotten confirmations. Calling too late leaves no time to refill the schedule. Most clinics get better results by setting call windows based on appointment type, patient history, and how hard the slot is to replace.

Specialty practices usually need more than one version. A dermatology follow-up, a dental hygiene visit, and a high-value specialist consult do not carry the same rescheduling risk. Build the script family around those differences. Keep the language simple, but set different rules for timing, escalation, and who gets a live call versus an automated reminder.

AI can handle the first layer well if you set clear boundaries. Recepta.ai can trigger reminders, capture confirmation status, offer approved rescheduling windows, and hand the conversation to staff when the patient asks a clinical question or sounds confused. That hybrid setup is the full-stack model that holds up in production. Automation covers repeatable steps. Staff handle judgment, exceptions, and anything sensitive.

What to keep tight

• Identity verification: Confirm the patient before discussing any appointment details.
• Message discipline: Leave out diagnosis, procedure names, and any detail the wrong listener should not hear.
• Rescheduling path: Offer specific next steps immediately so the patient does not delay.
• Escalation rules: Route medical questions, distress, or uncertainty to trained staff.
• Tracking: Measure confirmation rate, reschedule rate, voicemail callback rate, and recovered slots by appointment type.

Friendly tone helps. Loose wording does not. In healthcare, a short, controlled call usually performs better and creates less risk than a longer call that tries to sound personal.

4. Legal and Professional Services Case and Matter Follow-up Script

Law firms, accountants, and advisory teams need a script that qualifies the matter without drifting into free consulting. That’s a common mistake. The caller starts showing expertise, the prospect keeps talking, and thirty minutes later the firm has given away value without booking a consultation.

The script

“Hi [Name], this is [Rep] from [Firm]. I’m following up regarding your inquiry about [broad issue only]. I’d like to understand what’s going on and whether our team is the right fit. Is now a good time for a brief conversation?”

Then use open-ended intake questions:

“Can you tell me what prompted you to reach out?”
“How urgent is this?”
“Have you spoken with any other firm or advisor yet?”
“What outcome are you hoping for?”

Once you hear enough to identify likely fit:

“Based on what you’ve shared, this sounds like something we should review more closely in a formal consultation. I can help schedule that with the right attorney or advisor.”

If the person starts pushing for advice:

“I want to be careful not to give incomplete guidance before the team reviews the details. The best next step is to get you in front of the right person.”

Why this script works

Professional service buyers want to feel heard before they’re sold. If the intake caller cuts them off too early, trust drops. If the caller over-explains, the firm loses control of the process.

The strongest version of this script feels calm and procedural. That’s good. It signals competence.

“You don’t need to sound persuasive on legal intake. You need to sound organized.”

Where AI fits and where it shouldn’t

AI can handle initial qualification, conflict-check intake fields, and scheduling prompts well. It can also summarize what the caller said so the attorney or advisor starts the consultation with context. But once the issue gets fact-specific or emotional, a trained human should take over.

That’s especially important in sectors where compliance and communication quality are barriers to automation. There’s a documented content gap around service-based SMBs needing industry-specific personalization and regulatory compliance in outbound scripts, including healthcare, finance, and similar regulated fields, as discussed in this analysis of gaps in outbound call scripting resources.

Practical notes for firms

• Family law: Slow the pace. People are often overwhelmed.
• Personal injury: Confirm urgency and stage quickly.
• Estate planning: Ask who else is involved in the decision.
• Accounting and advisory: Clarify whether the need is transactional or ongoing.

A legal or professional services script for outbound calls should move the person toward a proper engagement, not toward a free answer.

5. Insurance and Real Estate Sales Script

About half of the bad calls in insurance and real estate fail before the rep ever gets to the offer. The rep starts quoting too early, talks through inventory or policy features, and never learns what is driving the decision.

Strong teams script these calls around timing, risk, money, and decision process. That is the full-stack version of an outbound script. The opener, the questions, the objection path, the handoff, and the follow-up all need to work together.

The script

“Hi [First Name], this is [Rep] with [Company]. I’m calling because we help people review their [coverage, purchase plans, sale timeline, financing options], and I wanted to ask one quick question so I don’t waste your time. Is now a bad time?”

If they stay on the line:

“What changed recently that made this worth looking at now?”
“What are you trying to protect, solve, or accomplish?”
“Are you early in the process, or are you trying to make a decision soon?”
“Who else needs to weigh in before anything moves?”

Then move to a specific next step:

“Got it. Based on that, the next step is a short review so I can bring options that fit your situation instead of guessing on this call. Would later today or tomorrow work better?”

Why this structure works

Insurance and real estate buyers rarely make decisions for one reason. A homeowner asking about coverage may really be worried about a renovation, a rate increase, or a bad claim experience. A buyer asking about listings may be blocked by financing uncertainty or the need to sell first.

The script has to surface that context fast.

That is also where AI and human reps should split the work carefully. AI can handle first-pass outreach, capture intent signals, tag urgency, and route the lead based on product type or transaction stage. A licensed agent or experienced rep should take over when the conversation turns into advice, pricing nuance, local market judgment, or regulated disclosures. Platforms such as Recepta.ai are useful here because they let teams run that hybrid model without losing call notes, qualification data, or scheduling context between steps.

Use this structure by scenario

• Home insurance review: “Have there been any property, household, or replacement cost changes since your last policy review?”
• Auto policy conversation: “Are you focused more on premium, deductible structure, coverage limits, or bundling everything under one carrier?”
• Buyer lead: “What has to happen before you would feel ready to tour homes seriously?”
• Seller lead: “Is your main concern price, speed, timing, or what happens after the sale?”

Objections and redirects

These prospects often give soft brush-offs, not hard no’s. Reps need a response path.

If they say, “I’m just looking,” use:
“That makes sense. A lot of people start there. What are you trying to get clear on first, monthly cost, timing, or available options?”

If they say, “Just send me information,” use:
“Happy to. I can send something generic, but it will be more useful if I know whether you’re comparing now or planning ahead.”

If they say, “I already have an agent,” use:
“Understood. Are you fully set, or are you checking whether your current setup still fits where things stand now?”

Common failure points

Reading the script like a checklist hurts performance. So does asking four discovery questions in a row without acknowledging what the prospect just said.

Good reps mirror one useful detail before advancing the call. “You mentioned the renewal jumped and you’re not sure the current limits still make sense.” That kind of reflection earns the next question.

Track the script the same way you would track a campaign. Measure contact-to-conversation rate, conversation-to-appointment rate, quote or tour set rate, and close rate by lead source and scenario. That is how teams improve the script itself, not just rep delivery.

6. Franchise Development and Partner Recruitment Script

Franchise candidate quality decides whether your development team spends the quarter advancing deals or babysitting curiosity. A weak script creates a full top of funnel and a thin close pipeline because it attracts interest without testing readiness.

These calls work best when the rep screens for operator fit, financial fit, territory fit, and decision timing in the first conversation. Franchise sales has real compliance constraints, so the script also needs clear boundaries on earnings talk, claims, and next-step promises.

The script

“Hi [First Name], this is [Rep] with [Brand]. You asked for information about business ownership, and I wanted to understand what you’re evaluating before I send material that may not fit. Do you have a minute?”

If yes:

“Tell me what attracted you to franchise ownership right now.”

“What kind of management, hiring, or multi-site responsibility have you handled before?”

“Are you looking to run the business day to day, hire an operator, or build toward a larger portfolio?”

“What locations are you open to, and are there any markets you would rule out?”

“How far along are you. Early research, active evaluation, or ready to review a specific model?”

Then set the next step with precision:

“Based on what you’ve shared, the next step would be a short qualification call to review the business model, territory approach, investment range, and process. If the fit is there, we’ll schedule that.”

What strong franchise teams do differently

They do not rush into a glossy brand story. They establish whether the candidate can progress.

I want reps to listen for three things. Can this person follow a process? Can they explain why this category fits them? Can they make a decision on a business timeline, not a consumer impulse? A candidate who cannot answer those points clearly may still convert later, but they should not consume senior development time yet.

Good franchise scripts also explain the path ahead in plain language. Intro call. Candidate review. Brand education. Validation or discovery process. Decision. That structure reduces drop-off because people know what commitment is being asked for now, not six steps from now.

Objections and qualification redirects

Franchise prospects often sound enthusiastic before they are qualified. Reps need redirect language that protects time without sounding dismissive.

If they say, “Just send me everything,” use:
“I can send an overview, but I want to make sure it matches what you’re trying to build. Are you evaluating owner-operator opportunities, semi-absentee models, or something more passive?”

If they say, “I’m looking at a few brands,” use:
“That’s normal. What criteria are you using to compare them. Category, investment level, support model, or territory potential?”

If they say, “I need something with strong returns,” use:
“I understand. We need to stay within the formal evaluation process on performance questions, so let’s start with your goals, investment comfort, and operating expectations.”

AI-human deployment for franchise recruiting

Franchise development benefits from a full-stack outbound system, not a standalone script file. The script should connect to disposition codes, qualification fields, objection tags, follow-up sequences, and handoff rules.

AI can handle the repeatable front end well. It can confirm interest, collect geography and timeline, answer basic process questions, and book the next conversation. Human recruiters should step in once the prospect moves into fit assessment, compliance-sensitive questions, or nuanced ownership discussions. That split keeps response times fast without letting serious candidates feel like they are stuck in automation.

Platforms such as Recepta.ai fit this model when teams need AI and human calling in the same operating flow. The gain is not just labor savings. It is cleaner data, tighter follow-up, and fewer dead-end meetings on the calendar.

What to avoid

• Avoid aspirational hype: serious candidates want operating reality, not motivational language.
• Avoid vague qualification: ask about role preference, timeline, geography, and relevant experience early.
• Avoid earnings improvisation: keep reps inside approved language and process.
• Avoid sending senior staff too early: protect discovery time for candidates who meet baseline criteria.
• Avoid one-shot outreach: good prospects often need a structured nurture track before they are ready for formal evaluation.

The best franchise development scripts create clarity on both sides. The prospect understands the process. The team understands whether to advance, nurture, or disqualify.

7. Event Attendance and Webinar Registration Script

No-show rates can wreck event ROI fast. A good call script does more than get a verbal yes. It qualifies interest, secures a calendar commitment, and sets up the reminder flow that drives actual attendance.

Event promotion calls work when the invite feels earned. If it sounds like a blast email read out loud, people tune out before you reach the topic.

The script

“Hi [First Name], this is [Rep] with [Company]. I’m calling because we’re hosting a [webinar, seminar, roundtable, discovery day] on [topic], and it lines up with the work you’re doing in [role, function, or business type]. Can I take 30 seconds and tell you why I thought of you?”

If yes:

“We’re covering [specific pain point, change, or decision area]. It’s built for people dealing with [specific scenario], especially those trying to [practical outcome].”

Then move to commitment:

“Would you like me to reserve a spot for you?”

If they say yes:

“Great. I’ll send the registration details now. What’s the best email, and do you want me to text the reminder link as well?”

If they hesitate on time:

“Understood. Would the recording, slides, or a short follow-up call be more useful?”

What makes this script work

The call has to answer three questions quickly. Why this event. Why now. Why this person.

That means the rep needs more than an event title. They need the audience segment, the problem the session addresses, the likely trigger behind interest, and the right fallback offer if live attendance is unrealistic. A CFO invite sounds different from a clinic manager invite. A local breakfast briefing should feel practical and specific. A webinar for IT leaders should sound tighter and more outcome-driven.

Timing also changes the script. For webinars, I usually call closer to the event date so attendance feels concrete. For in-person events, the rep should reach out earlier, then run a confirmation pass closer to the day. That two-step approach improves show rates and gives the team cleaner intent data.

AI is useful in the repeatable parts of this flow. It can confirm interest, collect contact details, send registration links, trigger reminders, and flag hot responses for a human follow-up. Platforms like Recepta.ai are useful here because the event script, reminder cadence, and handoff rules can sit in one operating flow instead of getting split across disconnected tools.

Simple ways to improve attendance quality

• Lead with relevance: Name the role, industry, or situation that makes the event worth their time.
• Sell the problem, not the title: “Q3 Compliance Update” is weaker than the issue the attendee is trying to solve.
• Ask for the calendar step: A verbal maybe is not a registration.
• Offer a fallback path: Recording, materials, or a short consult keeps interested prospects in motion.
• Track outcomes by source and segment: Registration volume matters less than attended meetings, qualified follow-ups, and pipeline created.

One rule I use with every event script. If the rep cannot explain the value in under a minute, the pitch is still too broad.

8. Complaint Resolution and Service Recovery Script

This is the most emotional script in the stack, and it’s where automation should step back. You can use systems to flag the issue, queue the callback, and document the outcome. But the actual recovery call usually needs a person who can listen and use judgment.

The script

“Hi [First Name], this is [Manager or Rep] from [Company]. I’m calling because I understand we missed the mark on your recent experience, and I wanted to speak with you directly.”

Pause.

“I’m sorry. I’d like to understand what happened from your perspective.”

Let them talk. Don’t interrupt to defend the team.

Then respond:

“Thank you for telling me. I can hear why that was frustrating. Here’s what I can do to help fix it.”

If appropriate:

“We can [specific remedy], and I’ll personally make sure it’s handled.”

Close with accountability:

“I’ll send confirmation of what we agreed and stay with this until it’s resolved.”

Why speed and ownership matter

The best service recovery calls happen quickly, with a specific owner, and with enough authority to make things right. What fails is the half-apology. “I’m sorry you felt that way” is not a recovery script. It sounds evasive.

If you use AI in this flow, use it upstream and downstream. Let it capture the complaint, route urgency, summarize the customer’s issue, and log the resolution. Don’t let it run the actual emotional repair unless the issue is minor and the customer clearly prefers a routine interaction.

There’s also a growing scripting gap around AI-powered dynamic scripting and voicemail optimization for high-volume SMBs, especially in sectors like home services and insurance, including the need to account for post-2025 AI disclosure concerns and localized messaging, as noted in this discussion of outbound script blind spots.

A useful training aid for managers is below.

Practical recovery standards

• Own the issue: Say what went wrong plainly.
• Acknowledge impact: Time, inconvenience, trust, or cost.
• Offer a concrete remedy: Don’t make the customer design your fix.
• Document everything: Future teams need the context.

Customers usually don’t expect perfection. They expect seriousness when something goes wrong. Your script for outbound calls should reflect that.

8-Point Outbound Call Scripts Comparison

Deploy Your Scripts and Automate Success with Recepta.ai

Teams lose money in the handoff between a good script and daily execution.

A script in a shared doc does not control response times, route calls, log outcomes, or keep follow-up clean. Reps still skip steps when queues build. Leads still cool off after hours. Notes still end up split across the dialer, CRM, and inbox. That is why outbound performance depends on operating design, not copy alone.

The practical model is full-stack. Build the script, then connect it to routing rules, booking logic, CRM sync, summaries, escalation paths, and QA review. If one part breaks, the script underperforms even when the wording is solid. I have seen teams blame the opener when the actual problem was delayed callbacks or weak list segmentation.

Recepta.ai fits that operating model because it combines AI-led conversations with human handoff. That matters for the scripts in this guide. Low-complexity calls such as first-touch qualification, reminder calls, basic follow-up, and appointment booking can run through automation with a defined script path. Higher-stakes conversations such as complaint recovery, legal intake nuance, or complex insurance objections should move to a trained person with context already captured.

That hybrid setup improves consistency in ways managers can readily measure. You can review which script branch was used, which objections appeared, how often calls reached a booking outcome, where handoffs happened, and whether the next step was completed on time. If summaries and dispositions sync into the CRM, coaching gets easier because the team is working from the same record instead of three partial ones.

The trade-off is straightforward. More automation usually gives faster response times and better coverage. It also requires tighter script logic, clearer escalation thresholds, and regular QA. If those controls are loose, automation will scale mistakes. If those controls are tight, it will remove admin work and protect rep time for the calls that need judgment.

If you’re evaluating your broader stack, it also helps to review how your call centre software supports call routing, logging, and campaign visibility.

Recepta.ai’s platform materials cite gains in qualified leads, lower operating cost, and strong ROI. Treat those figures as vendor-reported performance, then validate them in your own process with a limited rollout. Start with one or two script types that have clear success criteria, usually high-volume and lower-complexity calls. Measure contact rate, booking rate, handoff quality, and no-show reduction before expanding into more nuanced workflows.

That is how scripts move from theory to production.

If you want to put these scripts into production instead of leaving them in a doc, Recepta.ai is a practical next step. You can use it to run outbound qualification, appointment setting, follow-ups, and human handoffs in one workflow, then review summaries and outcomes to keep improving the script.