IVR vs One-Way Calls: Which Fits Your Campaign?

1. What “IVR vs one-way calls” really means (in plain terms)

“IVR vs one-way calls” sounds like a tooling choice, but it’s really a choice about how much the person on the other end needs to do during the call.

If your customer just needs to hear a short message and move on, one-way calls usually win. If they need to choose, confirm, or enter info, IVR usually wins.

Interactive voice response (IVR): IVR is a two-way phone flow where the caller presses keypad numbers (DTMF) and/or speaks to navigate a menu, confirm details, or complete a task. It’s often used to route calls, collect an order/account ID, or handle simple self-service without an agent.

One-way automated voice calls: One-way calls are outbound voice messages delivered to recipients without structured interaction. The person can answer and listen, but the system isn’t guiding them through a menu or collecting inputs as the main goal.

A delivery company is the classic IVR example: “Press 1 for tracking, press 2 to reschedule, press 3 to talk to an agent.” The whole point is choices, and the call adapts based on what the caller does.

A webshop is the classic one-way call example: “Hi Sara, this is Northline Shop. Your order #18421 ships today and your tracking link is in your email.” No menu, no branching, just a clear message.

One limitation that trips teams up: the same platform can sometimes support both IVR and one-way calls. So the real “IVR vs one-way calls” decision is about interaction design (do we need inputs?) and compliance (do we have consent and logs?), not just which vendor has which checkbox.

If you treat it like a pure feature war, you’ll miss the part that actually affects results: how the call feels to the customer in the first 5 seconds. Research from FCC guidance on robocalls and automated calling rules supports this.

2. Quick decision guide: when IVR beats one-way calls (and vice versa)

Here’s a rule of thumb that’s boring but reliable: if your message can be delivered in Research from What is IVR (interactive voice response)? supports this.30–45 seconds and needs zero input, one-way calls are usually enough.

If the call needs choices, verification, routing, or data capture (even just “enter your order ID”), IVR fits better.

A simple decision tree you can actually use

• Need routing? (Sales vs Support vs Billing) → IVR
• Need to broadcast to 5,000 customers? (storm closure, delivery delay, deadline reminder) → One-way calls
• Need to capture info? (order ID, postcode, “confirm yes/no”) → IVR or a hybrid
• Need both? (notify + let them act) → Hybrid (one-way message with “press 1 to connect” or “press 9 for a text link”)

In “IVR vs one-way calls” conversations, teams often forget customer mood. Some recipients genuinely hate menus, especially if they’re calling because they’re already annoyed.

For high-value customers, a live agent or a callback option can outperform IVR even if it costs more. If you have 200 VIP customers generating 40% of revenue, shaving 60 seconds off their support experience might matter more than automating anything.

This approach won’t work if your phone numbers are messy. If 8–12% of your list is wrong, one-way calls waste money fast and IVR won’t fix it either.

3. Interactive voice response (IVR): how it works and where it shines

IVR works by moving callers through a call flow: prompts, choices, validation, retries, and then either completion (self-service) or a transfer to a human.

In an “IVR vs one-way calls” decision, IVR is the “guided task completion” option.

DTMF IVR vs speech IVR

DTMF IVR uses keypad input (“press 1 for billing”). It’s predictable and usually more reliable than speech in noisy environments.

Speech IVR lets callers say what they want (“billing”, “cancel”, “track my order”). It can feel faster, but recognition quality varies by accent, mic quality, and background noise.

Call flows: retries, timeouts, and transfers

• Retries: If the caller enters an invalid option, the IVR repeats the prompt (usually 1–2 retries before offering an agent).
• Timeouts: If there’s silence for, say, 5–8 seconds, the IVR reprompts or routes to help. Timeouts that are too short feel pushy; too long feels broken.
• Transfers: The IVR can pass the caller to a queue, a specific team, or a priority line based on input, time of day, or caller ID.

Metrics that tell you if your IVR is helping or hurting

• Containment rate: % of callers who complete their task without an agent. Many teams aim for 20–40% on day one, then improve from there.
• Average handle time (AHT): Total time per interaction. A good IVR can reduce AHT by collecting info upfront.
• Transfer rate: % of calls sent to agents. High transfer isn’t always bad, but high transfer after long menus is a red flag.

A real-world example: a SaaS support line routes VIP customers by caller ID to a priority queue. Before connecting, the IVR asks for an account ID, so the agent answers already looking at the right workspace.

The drawback: speech recognition isn’t magic. If you serve customers in loud warehouses, on old phones, or across multiple accents, speech IVR can frustrate people fast.

Long menus also increase hang-ups and “zero-out” behavior (people pressing 0 repeatedly to escape). If your menu has 9 options, you’re basically betting against human patience.

4. One-way voice calls: how automated voice broadcasts work

One-way calls are outbound calls that deliver a message and stop. In “IVR vs one-way calls,” this is the “high reach, low friction” option.

You record (or generate) a short voice message, choose who gets it, and schedule when it goes out. The system dials numbers, plays the message if answered, and logs results.

Pre-recorded audio vs AI text-to-speech (TTS)

Pre-recorded audio sounds more human when you have a good voice and a quiet recording setup. It’s great for brand tone, but updates take effort.

AI TTS is faster to iterate. If you need to change “Tuesday” to “Wednesday” across 12 campaigns, TTS saves hours. The downside is that some voices still sound slightly synthetic, especially with names, street addresses, or mixed-language text.

Outbound dialer behavior: what actually happens

• Attempts: Many campaigns use 1–3 attempts per recipient, spaced out to avoid annoyance.
• Answer detection: Some systems try to detect voicemail vs human pickup. It’s not perfect, and false positives happen.
• Retries: If there’s no answer, you retry later (often during business hours or a preferred window).

Scheduling by timezone and event-triggered campaigns

Timezone scheduling matters more than teams expect. Calling at 8:30pm local time is a fast way to get complaints, even if your intent is “helpful reminder.”

Event-triggered one-way calls usually perform best because the timing makes sense. The call is tied to something the customer just did (or failed to do).

Example: a WooCommerce failed payment triggers a call 15 minutes after the failure. If it’s still unpaid, a second attempt goes out 24 hours later. The campaign stops the moment payment succeeds.

The biggest limitation is targeting. If your segments are sloppy, complaint rates rise and deliverability can drop. Carriers filter more aggressively when they see high complaint patterns, and number reputation can get worse over time.

This is why “IVR vs one-way calls” isn’t just UX—it’s also list hygiene and operational discipline.

5. IVR vs one-way calls: feature-by-feature voice system comparison

Most teams want a simple grid for “IVR vs one-way calls,” so here it is. Just remember: tables hide nuance, and hybrids can blur the line.

Feature/Aspect	IVR (Option A)	One-way voice calls (Option B)	Winner
User interaction	Two-way (DTMF keypad and/or speech input)	No structured interaction (broadcast delivery)	A
Primary goal	Self-service + routing + data capture	Notify, remind, announce, nudge	Tie
Typical direction	Mostly inbound (can be outbound)	Mostly outbound	Tie
Build complexity	Higher (menus, branches, retries, error handling)	Lower (message + schedule + targeting)	B
Time to launch	Days to weeks for a solid flow	Hours to days for most campaigns	B
Best for eCommerce triggers	Rescheduling, verification, “press 1 to confirm” flows	Order updates, payment reminders, abandoned cart nudges	Tie
Agent workload impact	Can reduce inbound load significantly	Reduces follow-up by proactive messaging	Tie
Failure modes	Menu loops, speech recognition errors, long menus	Annoyance, spam perception, compliance risk	Tie
Measurement	Task completion rate, containment rate, transfer rate	Answer rate, listen-through rate, callback rate	Tie
Summary	IVR is a guided conversation for completing tasks	One-way calls are best when the job is simply delivering a message fast at scale

Practical implication of the “winner” column: IVR wins on interaction, but it also means more QA. You’re testing branches, edge cases, and what happens when people do weird things (because they will).

One-way calls win on speed to launch, which is why marketing teams love them. You can ship a campaign in a day, then improve the script tomorrow.

Mini case study: webshop vs service business

A small webshop tests one-way calls for delivery exceptions: “Your package is delayed. Check your email for the new ETA.” They send to 312 customers over a week and see fewer “where is my order?” tickets.

A local service business uses IVR to reduce missed calls: “Press 1 to book, press 2 to reschedule, press 3 for billing.” They cut voicemail tag and route calls correctly without adding staff.

One caveat: hybrids change the game. A one-way call that says “press 1 to connect” starts to behave like interactive voice response, and that can change compliance requirements depending on region and purpose.

Feature/Aspect	IVR (Option A)	One-way voice calls (Option B)	Winner
Pros	Handles repeat questions; routes callers; collects data before agents	Fast to deploy; great for reminders; strong reach vs email/SMS in some markets	Tie
Cons	Can frustrate users; needs careful design; higher setup cost	Can feel intrusive; limited interactivity; higher compliance scrutiny for marketing	Tie
User experience risk	High if menus are long or unclear	High if frequency is too high or targeting is sloppy	Tie
Operational risk	Maintenance of flows, prompts, and routing logic	List quality, consent tracking, and deliverability issues	Tie
Summary	IVR fails when it wastes time	One-way calls fail when they hit the wrong people too often

6. Pricing: what you actually pay for (and what surprises teams)

Pricing is where “IVR vs one-way calls” gets real, because the cheaper-looking option can become expensive through hidden work.

Most voice systems charge based on a mix of usage and infrastructure.

Typical pricing drivers

• Per-minute rates: You pay for connected time (and sometimes for voicemail time too).
• Per-number costs: Local numbers, toll-free numbers, or dedicated caller IDs can have monthly fees.
• Concurrent calls: Higher throughput can cost more, especially for big outbound bursts.
• Setup/build hours: IVR design, prompt writing, recordings, testing, and integrations often cost more than the minutes.

Illustrative budget ranges (these are not quotes):

• 10,000-call one-way campaign: If the average listen time is 25 seconds, you’re buying roughly 4,167 minutes of talk time. Depending on destination rates and tooling, teams often land somewhere in the $150–$900 range for usage, plus whatever time it takes to prep the list and script.
• Small IVR for one department: A basic flow (language select → reason → collect ID → transfer) can take 8–25 hours to design and test well. At typical internal or agency rates, that’s often $800–$5,000 before you even think about minutes.

Outbound one-way campaign costs are usually predictable with volume. IVR costs spike when you add languages, branches, and integrations (CRM lookups, ticket creation, payment links).

Honest limitation: exact rates vary by country, carrier, and platform. Ask for destination-based rate cards and run a test of 100–200 calls before you scale. That small test catches 80% of the “we didn’t expect that” issues.

Feature/Aspect	IVR (Option A)	One-way voice calls (Option B)	Winner
Main cost driver	Minutes + IVR platform fees + setup/build time	Outbound minutes + campaign tooling	B
Upfront effort	Often higher (flow design, prompts, testing)	Often lower (message + segments + schedule)	B
Ongoing costs	Flow updates, new branches, number management	List hygiene, compliance, creative refresh	Tie
Hidden costs	Bad containment increases agent time; poor UX increases hang-ups	Complaints/blocks reduce deliverability; legal risk if consent isn’t tracked	Tie
Summary	IVR costs are usually dominated by design and maintenance	One-way call costs are dominated by outbound volume plus list quality and compliance

7. Compliance and consent: the part most comparison posts gloss over

Compliance is the unsexy part of “IVR vs one-way calls,” but it’s the part that can shut a campaign down.

One-way calls usually get more scrutiny when they’re used for marketing, because they’re outbound and can feel intrusive if the recipient didn’t ask for them.

Transactional vs promotional: same tech, different risk

A payment reminder and an upsell call can use the exact same automated calling types. Legally and operationally, they’re not treated the same in many regions.

Transactional/informational calls (order updates, appointment reminders, security alerts) are often easier to justify, but still may require consent depending on where you operate.

Promotional/marketing calls (discounts, upgrades, cross-sells) tend to require clearer opt-in and stronger opt-out handling.

Suggested audit checklist (simple, but it saves teams)

• Consent source: Where did the phone number come from (checkout, lead form, offline list)?
• Consent language: What exactly did the user agree to (transactional updates only, or marketing too)?
• Timestamps: Store when consent was captured and what version of the form/policy was shown.
• Purpose tag: Log why you called (failed payment reminder vs promo).
• Opt-out handling: How can the recipient stop future calls (process + timeline)?
• Suppression lists: Do-not-call and complaint-driven suppression that updates fast.

My opinion: teams obsess over call scripts and forget record-keeping. If you can’t prove consent, you’re relying on luck.

Caveat: this isn’t legal advice. Regulations differ by country and state, and carrier policies can be stricter than the law. If you’re calling across borders, get counsel for your markets and document your process.

8. Use cases by industry: eCommerce, SaaS, and local services

“IVR vs one-way calls” gets easier when you anchor it to real workflows instead of features.

Tools like VoxaTalk — Automated Voice Calls & Global VOIP can help streamline this process.

eCommerce (Shopify, WooCommerce, small webshops)

• Order confirmation: One-way call within 1–5 minutes of purchase for high-risk orders (COD, high value).
• Delivery exception alerts: One-way call when carrier status changes to “delayed” or “address issue.”
• COD verification: IVR or hybrid: “Press 1 to confirm you’ll be available tomorrow.”
• Payment reminders: One-way call at 15 minutes after failure, then 24 hours later if unpaid.
• Abandoned cart: One-way call at 30–60 minutes after abandonment, then a second attempt next day during business hours.

One limitation: voice won’t fix weak offers. If your shipping is slow and your return policy is confusing, calls just make the problem louder.

SaaS

• Trial onboarding nudges: One-way calls to prompt the next step (“Your workspace is ready. Check your email for the login link.”).
• Renewal reminders: One-way calls for deadline awareness, especially when email gets ignored.
• Incident updates: One-way calls to affected customers when uptime issues hit critical workflows.
• Support routing: IVR for “billing vs technical,” language selection, and account verification before an agent joins.

SaaS teams often underestimate how much trust voice can build when used sparingly. One clear incident update can prevent 200 angry tickets.

Local services (clinics, salons, repair, home services)

• Appointment reminders: One-way calls 24 hours before, plus 2 hours before for no-show heavy services.
• Rescheduling: IVR if you can connect to a booking system or at least route to the right staff member.
• Missed call handling: IVR to route or capture intent, then offer callback.

Limitation: if your team doesn’t answer or call back quickly, IVR and one-way calls both backfire. Customers don’t blame the system; they blame you.

9. Best for: IVR vs one-way calls (recommendations by team size and goal)

If you want a quick “best for” view of IVR vs one-way calls, think in terms of team constraints and what you’re trying to achieve this month.

Feature/Aspect	IVR (Option A)	One-way voice calls (Option B)	Winner
Customer support routing	Excellent (menus + skills-based routing)	Weak (not designed for routing)	A
Order confirmation / delivery updates	Overkill unless action is required	Excellent (short, clear message)	B
Payment reminders	Good if you need “press 1 to pay/confirm”	Excellent for simple reminders and deadlines	B
Appointment scheduling/rescheduling	Strong if integrated with booking system	Good for reminders; limited for changes	A
Lead qualification	Strong when you need inputs (budget, timeline)	Good for “call us back” prompts	A
Summary	If the recipient must choose, confirm, or enter info, IVR wins	If you just need them to know something, one-way calls win

Recommendations by team type

• Startups (speed-focused): One-way calls for reminders and updates. Build IVR later when inbound volume justifies it.
• Enterprises (routing + governance): IVR for controlled routing and consistent handling, plus one-way calls for critical notifications.
• Marketing teams: One-way calls (with strict consent, frequency caps, and suppression lists).
• Support teams: IVR for routing and data capture, especially if agents waste time asking for IDs.

Example: a 2-person webshop will usually get more value from a simple delivery update campaign than building a full IVR tree. They don’t need “Press 3 for returns” if they can answer returns by email.

Caveat: if you can’t maintain message quality and frequency caps, one-way calls can backfire even if they’re easy to launch.

10. My take: the “clear winner” depends on whether the user must act now

My take on IVR vs one-way calls is simple: the winner depends on whether the user must act during the call.

Choose one-way calls when the job is awareness: a short message, high reach, and the recipient doesn’t need to do anything right now.

Choose IVR when the job is completion: choices, verification, routing, or capturing data that unlocks the next step.

A practical hybrid approach (often the sweet spot)

A hybrid can give you the best of both: a one-way call delivers the message, then offers a path to act.

• One-way call → callback path: “If you need help, call us back at this number” or “press 1 to connect” (depending on what your setup supports and what’s compliant in your market).
• IVR → “press 9 to get a text link”: Great for payment/checkout links, where voice alone is clunky.

The drawback: hybrids add moving parts. Tracking, attribution, consent, and integrations all need tighter QA. If your team doesn’t have time to test edge cases, keep it simple.

11. How VoxaTalk fits: one-way automated calls + global VoIP (and when you still need IVR)

VoxaTalk fits best when your “IVR vs one-way calls” decision lands on one-way automated voice calls and straightforward outbound calling.

It’s built for short, clear messages: reminders, follow-ups, notifications, and time-based nudges. It’s not trying to be a full contact-center IVR builder.

Where VoxaTalk is strong (practical mapping)

• Browser-based outbound calling: Make global VoIP calls from your browser with no SIM cards, no hardware, and no installs.
• Scheduled campaigns: Run outbound one-way calls during business hours and by timezone.
• Event-triggered calls: Trigger calls from forms, carts, CRM updates, payments, or bookings.
• Audio options: Use AI text-to-speech or pre-recorded audio depending on what sounds best for your brand.
• Usage-based approach: Pay-as-you-go is often easier for seasonal shops and small teams that don’t want another subscription.

Example workflow: WooCommerce abandoned cart

Here’s a workflow that’s simple enough to run without a call ops team:

• Trigger: Cart abandoned.
• Call #1: One-way call after 30 minutes with a 25–30 second message.
• Stop condition: If purchase happens, the campaign stops immediately for that customer.
• Call #2: If not purchased, a second call goes out next day during business hours (local timezone).

This is where one-way calls shine: clear timing, clear purpose, and no confusing menus.

When you still need IVR (or an integration)

If you need complex inbound self-service menus, skills-based routing, or deep call center features, a dedicated IVR/contact-center tool may be a better fit.

That doesn’t mean VoxaTalk is useless in that world. Many teams pair a one-way calling tool for proactive notifications with an IVR system for inbound support.

Honest limitation: if your success criteria depends on the caller completing a multi-step task entirely by phone, VoxaTalk isn’t trying to be that product.

12. Implementation checklist (so you don’t annoy customers)

Most “IVR vs one-way calls” failures are self-inflicted. The tech works; the execution is sloppy.

Use this checklist to stay on the right side of customer patience.

1. Set a message length target: 20–35 seconds for one-way calls. If you can’t say it in 35 seconds, you’re trying to do too much.
2. Say identity + purpose in the first 5 seconds: Company name, why you’re calling, and what the recipient should do next.
3. Use a frequency cap: Max 1–2 calls per week per customer unless it’s critical (fraud, safety, same-day delivery issue).
4. Respect quiet hours by timezone: A common safe window is 9:00–18:00 local time. Tighter windows can perform better if your audience is predictable.
5. Validate phone numbers: Remove obvious bad formats, duplicates, and landlines if your message assumes mobile behavior.
6. Segment by intent: Don’t mix “failed payment” with “promo discount” in the same campaign logic.
7. Write for listening, not reading: Short sentences, no long order numbers, no URLs unless you also send them by text/email.
8. Log outcomes: Answered, voicemail, no answer, and callback events. Without this, you can’t improve.
9. Have an opt-out process: Even for transactional calls, recipients will ask to stop. Make it easy internally.
10. Pilot before scaling: Run 100–300 calls, monitor complaint signals, and adjust timing/script before you hit 10,000.

Example scripts (short and usable)

Delivery exception (one-way): “Hi, this is Northline Shop. Quick update: your delivery is delayed due to an address issue. Please check your email for the link to confirm your address. If you need help, reply to that email and we’ll sort it today.”

Payment reminder (one-way): “Hi, this is Northline Shop calling about your recent checkout. Your payment didn’t go through, so your order isn’t confirmed yet. You can retry using the link we sent by email. If you’ve already paid, you can ignore this message.”

Appointment reminder (one-way): “Hi, this is River Dental. Reminder of your appointment tomorrow at 2:30 PM. If you need to reschedule, please call us back during business hours. See you tomorrow.”

Caveat: deliverability and sentiment vary by country. In some markets, voice performs like magic; in others, people treat unknown numbers like spam by default. That’s why the small pilot matters.

13. People Also Ask: fast answers about automated calling types

These are the questions that keep showing up around “IVR vs one-way calls” and automated calling types. The answers are short on purpose.

Is IVR inbound or outbound?

IVR is mostly inbound: a caller dials your number and the interactive voice response system routes them or helps them complete a task. IVR can also be used outbound (like a call that asks you to confirm an appointment), but the most common IVR use is inbound support and routing.

What’s the difference between IVR and a robocall?

IVR is interactive: it expects input (keypresses or speech) and changes the call flow based on what the person does. A robocall usually refers to an automated outbound call that plays a recorded message with little or no interaction. In practice, many one-way calls are considered robocalls under regional rules.

Can IVR be used for outbound calls?

Yes. Outbound IVR is used for confirmations, surveys, or verification flows, like “Press 1 to confirm your delivery window.” The catch is complexity and compliance: outbound interactive flows require tighter testing, clear consent, and careful handling of transfers, timeouts, and failed inputs.

Do one-way calls support DTMF?

Basic one-way calls don’t usually rely on DTMF because they’re designed to deliver a message, not collect inputs. Some systems offer a hybrid option where the call is mostly one-way but includes “press 1 to connect” or “press 9 for a link.” That starts to overlap with IVR behavior.

Mini glossary (quick definitions)

• DTMF: Keypad tones (pressing 1, 2, 3) used for phone menu input.
• TTS: Text-to-speech, where written text is converted into spoken audio.
• Call flow: The step-by-step logic of prompts, choices, retries, and outcomes.
• Transfer: Moving a call from automation to a live agent or another number/queue.
• Containment: When the system completes the task without needing an agent.

Limitation: People Also Ask varies by region and changes over time. Refresh these questions quarterly using Search Console and live SERP checks so your “IVR vs one-way calls” page stays aligned with what people are actually searching.

14. FAQ (schema-ready): IVR vs one-way calls

What is the difference between IVR and one-way calls?

IVR (interactive voice response) is a two-way phone flow where the caller presses keys or speaks to navigate menus, confirm details, or complete tasks. One-way calls are outbound voice messages delivered to recipients without expecting input (they can answer, but the system doesn’t guide them through a menu). IVR is best for self-service and routing; one-way calls are best for fast broadcasts, reminders, and time-based notifications.

What is interactive voice response (IVR) used for?

Interactive voice response is commonly used to route calls to the right team, capture information (like account number or order ID), and handle self-service tasks (hours, delivery status, appointment changes). IVR reduces agent workload by answering repeat questions and collecting data before an agent joins. It works best when the user’s goal can be completed in 1–3 minutes and the menu is short and predictable.

Are one-way voice calls considered robocalls?

Often, yes. One-way automated calls (pre-recorded or AI text-to-speech) typically fall under “robocall” rules in many regions, especially when used for marketing. Some informational or transactional messages can be allowed with different consent requirements, but the details vary by country and carrier. The practical takeaway: treat one-way calling as regulated, get consent where required, include opt-out when applicable, and keep clear logs of who you called and why.

How do I choose between IVR vs one-way calls for eCommerce?

Pick one-way calls when you need fast, high-reach notifications: order confirmation, delivery updates, payment reminders, or abandoned cart nudges. Pick IVR when customers need to complete an action during the call: reschedule delivery, confirm identity, choose a language, or route to support. Many shops use both: one-way calls for proactive updates, and IVR for inbound support or for outbound “press 1 to confirm” flows.

Can I run event-triggered one-way calls from WooCommerce or Shopify?

Yes—event-triggered one-way calls are commonly tied to store events like new orders, failed payments, abandoned carts, form submissions, bookings, or CRM stage changes. The call content can be AI text-to-speech or a recorded message, and campaigns can be scheduled by timezone and business hours. The key limitation is data hygiene: if phone numbers aren’t validated and consent isn’t tracked, deliverability and compliance risk go up quickly.

Can one-way calls connect to a live agent?

Yes, but only if your setup supports a hybrid flow (for example, “press 1 to connect”) or if you include a clear callback path. The condition is that you must handle routing, staffing, and compliance correctly, because adding interaction or transfers can change how the call is classified and what consent rules apply.

Brief conclusion

IVR vs one-way calls comes down to one question: does the customer need to do something during the call, or just know something?

If it’s awareness at scale, one-way calls are usually the cleanest move. If it’s task completion, routing, or verification, IVR is the better tool—assuming you keep menus short and test the edge cases.

When you’re unsure, start with a 100–300 call pilot, measure complaints and outcomes, and only then decide whether you need interaction or just a sharper message.