Flatpay Retention Playbook

Interactive guide for retention agents. Start with the decision tree below — pick how the call started and what the merchant is saying. Each card gives you the first line, discovery questions, response ladder, real call examples, and a CRM note template.
Step 1 — How did this call start?
Universal — apply on every call
Stay firm — don’t volunteer easy exits

Capitulation phrases hand merchants permission to walk away. Default stance: assume Flatpay is the right answer for their business. Make them earn the cancellation by walking through the pushback first.

  • Avoid: “I’ll respect your decision” · “If you change your mind, just let us know” · “No problem if you’d rather leave” · “We can cancel free of charge” (preemptively).
  • Use instead: “Before you commit, have you actually seen the full comparison?” · “Give it a fair shot for a couple of weeks — most merchants find…” · “Hold off on any decision until you’ve seen what I send.”
  • “I understand” + pushback is firm. “I understand” + concession is weak.
  • Free cancellation, free trial extensions, and rate matches are last-resort levers — not opening moves. Use them only after the merchant has held firm through multiple rounds.
Free trial considerations
  • Lowering the rate (competitor matching, churn request, missing feature, etc.) → outline that the free trial would have to end. We’re offering a very competitive rate, so we have to lock it in.
  • Merchant unhappy for any reason → fight harder to keep them. Extend the trial period, lower the rate, etc.
Remind about the £1,100 monthly minimum (if not a winback)
  • Every merchant has a minimum £1,100 monthly transaction volume commitment with Flatpay.
  • If the call isn’t turning into a winback (e.g. terminal isn’t being used, merchant is splitting volume, seasonal but light) — regardless of whether it’s a direct request or a content list follow-up — gently remind them of this minimum.
  • Frame it firmly but constructively: “Just so you’re aware — there’s a minimum monthly transaction volume of £1,100. We want to help you hit that, so let’s talk about what’s stopping you from running more through us.”
Contract & cancellation fee
  • Not on a free trial + refuses to use the terminal / wants to cancel → gently remind them they’re in a contract with us. Cancellation fee is £39+VAT per remaining month left in the contract.
  • Frame it: “we don’t want you to pay this, so we’d like to find a solution that works for you.”
Content list calls only — these merchants are inactive or low-activity
The stated reason is rarely the real one

Low usage almost always hides a different driver. Always diagnose before assuming. Common hidden reasons:

  • A surcharge concern the merchant didn’t proactively flag
  • A tech issue — terminal not charging, no connection, declined transactions
  • Bank verification holding payouts
  • A competitor terminal taking the volume
  • Genuine seasonal / temporary closure

Use the orange pivot chips inside each scenario card to jump as soon as the real driver emerges.

Never leave without a commitment date
  • Every content list call must close with a specific date the merchant will start (or resume) transacting. Vague answers (“soon”, “next week sometime”, “when we’re back open”) are not acceptable.
  • Push for a concrete day: “So we’re saying Monday the 14th — you’ll start running payments through then?”
  • Set the follow-up date in your notes to one or two days after that — so you can verify and re-engage if they haven’t.
  • If they genuinely can’t commit to a date (e.g. waiting on bank, tech, or building work), capture the blocker and the date the blocker resolves instead.

Scenario cards

Universal reactive cancellation triage

cancellationopeningreactive
192 tagged calls | saved 41 | pending 79 | churn/lost 24
When to use it
  • Merchant says they want to cancel, return the terminal, stop the agreement, or not proceed after installation.
First line

“I can help with that. Before I process anything, can I quickly understand what has driven the decision, so I can check whether there is a clean fix for you?”

Discovery questions
  • “Can I ask what’s driving the cancellation?”
  • “When did this become a problem for you?”
  • “Have you already moved to another provider, or are you still deciding?”
  • “What would need to change for this to make sense for your business?”
Response ladder
  1. Do not offer a discount before the root cause is clear.
  2. Repeat the real issue back in one sentence, then move into the relevant scenario card.
  3. Close with one concrete next step: update rate, remove/reduce surcharge, send comparison, book tech support, pause account, or confirm cancellation route.
Real call examples
Call 887231 · Pending / competitor-feature objection
Merchant: “I got a better device from another company.”
Agent: “Just so I have a bit of understanding as feedback, could you let me know why you would like to cancel and then we’ll go from there?”
Call 886656 · Churn / overpromised-product path
Merchant: “I was looking to return the terminal.”
Agent: “Can I ask why you haven’t used it — is there any particular reason?”
Call 1042636 · Saved / new product
Merchant: “It’s two things: remote payment and the three-year contract.”
Agent: “I understand. I can actually help with both of those things.”
Do not say / watch-out
  • “Can I offer you a different rate?” as the first response. In the calls, several cancellation requests were not really about rate.

Proactive inactive terminal / silent churn

inactiveproactiveusageseasonal
81 tagged calls | saved 12 | pending 31 | churn/lost 5
When to use it
  • No usage, low usage, merchant says they are using another machine, bank transfer, cash, or only using Flatpay occasionally.
First line

“I’m just reaching out in regards to your card terminal. I can see there hasn’t been much usage recently, just wanted to check in and see how things are going.”

Discovery questions
  • “Is the terminal working as expected?”
  • “Are customers paying another way, such as bank transfer, cash, or another terminal?”
  • “When do you expect card payments to pick up again?”
  • “Do you use Flatpay as your main terminal or as backup?”
Response ladder
  1. If seasonal: record expected restart date and schedule follow-up.
  2. If another terminal: move to competitor/rate comparison or payout card.
  3. If technical: capture exact symptom and evidence, then raise support.
  4. If merchant forgot / unclear: remind them of agreement/minimum usage only after confirming context.
Real call examples
Call 873539 · Seasonal / large few transactions
Merchant: “There hasn’t been any payments lately… they’ve been transfers rather than card transactions.”
Agent: “I can look at potentially switching you over to our faster payouts, but I would have to ask a few questions.”
Call 886117 · Temporary/seasonal
Merchant: “It’s a quiet season for my business.”
Agent: “Just to confirm, when would you say it will begin to get better in terms of transactions, just so I can make a note?”
Call 987236 · Seasonal/low volume
Merchant: “My business operates on different days, different weeks.”
Agent: “I’ll pop that in the notes.”
Do not say / watch-out
  • Do not open with a warning about charges. First identify whether there is a valid operational reason for low usage.

Surcharge complaint: customers are being charged extra

surchargepricetrust
125 tagged calls | saved 54 | pending 47 | churn/lost 9
When to use it
  • Merchant says customers complain, business/international/corporate cards trigger extra charges, surcharge was not explained, or they fear losing customers.
First line

“I’ll just explain to you basically why the surcharge is a unique benefit that we offer, and then I’ll be happy to go through the options if you’re happy to proceed.”

Discovery questions
  • “Is it mainly business cards, international cards, Amex, or all of them?”
  • “Out of 10 customers, roughly how many pay with those card types?”
  • “Are customers refusing to pay, or are they asking for an explanation?”
  • “Would you prefer to keep the customer charge lower, or remove it completely even if your base rate needs to be recalculated?”
Response ladder
  1. Explain the value neutrally: with surcharge enabled, merchant keeps 100% of those business/international card payments and can receive a lower base rate.
  2. Land the loss framing if needed: “If the surcharge wasn’t in place, you’d essentially be losing money because you’d have to carry the cost out of your own pocket on those cards.”
  3. Show the amount on real baskets: £10, £100, £550, etc. The strongest calls translated percentage into pounds.
  4. Offer ladder: keep as-is if customer impact is low; reduce surcharge to 1.89/half if available; remove for selected card type if allowed; remove completely with base-rate recalculation.
  5. Give a trial option: “Let’s try the reduction; if complaints continue, we can revisit removal.”
  6. Confirm operational timeline: surcharge/rate updates were repeatedly quoted as taking two to three working days.
Real call examples
Call 876276 · Saved / surcharge deactivated with base-rate increase
Merchant: “I don’t want to lose my customer, I don’t want to lose my business.”
Agent: “Now you’ve explained your circumstances, I understand why you want to have it removed… I can offer 0.69% with no surcharge.”
Call 877344 · Saved / surcharge deactivated with base-rate increase
Merchant: “A lot of our customers are corporate or international customers.”
Agent: “I’m happy to reduce the surcharge to 1.89%… if you want it removed completely, I’ll recalculate the base rate.”
Call 872772 · Lost / Takepayments
Merchant: “It was more the charges of customers… business credit cards and international cards.”
Agent: “I can look to take off the surcharge and give you a cheaper rate.”
Call 887381 · Retained / surcharge kept
Merchant: “One customer tried to pay £1000 and the surcharge came on.”
Agent: “Surcharge being enabled allows us to give you a much better base rate. It really maximises your savings because you get the 0% fees on those cards.”
Recent · Saved / reduced to 1.89%
Merchant: “I find it a bit unfair on our customers — a customer tapped their card for £40 and it came up to £41.55.”
Agent: “I can reduce that rate to 1.89% — the customer pays roughly 18 pence for every 10 pounds, a lot smaller. And you still keep 100% of those payments.”
Do not say / watch-out
  • Do not treat this as only a rate objection. In several calls the first stated reason was “better rate”, but the true driver was customer surcharge reaction.

Competitor offer / lower rate

competitorpricerate
108 tagged calls | saved 34 | pending 49 | churn/lost 15
When to use it
  • Merchant says another provider is cheaper, current provider matched, they received 0.3/0.4/0.65/0.8 style rates, or they are staying with Takepayments/SumUp/Dojo/Square/Teya/Worldpay.
First line

“That’s completely fair — most businesses will check the best offer. Before you decide, let me compare it like-for-like so you can see the full cost, not just the headline rate.”

Discovery questions
  • “Can you send the quote or latest statement?”
  • “Does that rate include terminal rental, authorisation fees, transaction fees, minimum monthly fees, PCI/CPI, business cards and international cards?”
  • “How many transactions do you take roughly per month, and what is your debit/credit split?”
  • “Is the competitor rate for all cards or only consumer debit?”
Response ladder
  1. Ask for proof or a statement before promising a match.
  2. Calculate true blended rate with rental + per-transaction + authorisation + minimum monthly fees.
  3. Only then offer match/beat, lower rate, or rate lock within authority.
  4. Reposition Flatpay: flat rate, no terminal rental, no authorisation/transaction/rental fees where applicable, transparent cost, human support.
  5. Close with: “If I can beat the true full cost, are you happy to continue with us?”
Real call examples
Call 901013 · Saved / lowered rate
Merchant: “Takepayment only charges debit cards 0.3.”
Agent: Calculated rental and transaction fees, got a true blended rate around 0.49, then offered 0.47 flat with no rental/authorisation fees.
Call 887231 · Pending / competitor quote
Merchant: “They don’t have a contract.”
Agent: Explained that terminal/rental/transaction fees can make a no-contract offer cost more, then requested the rate/quote by email.
Call 882200 · Surcharge deactivation path
Merchant: “The other provider is 0.65.”
Agent: Verified that 0.65 applied to business and international cards, then moved to discuss a cheaper Flatpay rate with surcharge removed.
Call 920600 · Pending / quote requested
Merchant: “They are charging me 0.3.”
Agent: “If you could send the formal offer, I’ll see if I can offer you a better rate.”
Do not say / watch-out
  • Avoid words like “scam” or “sneaky” about competitors. Say “headline rate” vs “full cost” instead.

Contract length / “I feel locked in”

contracttrustprice
93 tagged calls | saved 27 | pending 40 | churn/lost 17
When to use it
  • Merchant objects to 36 months, says they were promised 18/24 months, says competitor has no contract, or is worried about closing/selling the business.
First line

“I understand. The term matters because you don’t want to feel trapped. Let me check what flexibility we have and also clarify what happens if your business closes or you get a better offer.”

Discovery questions
  • “What term were you expecting?”
  • “Is the concern the length itself, or the risk of exit fees if the business changes?”
  • “Were you told a different term during the sale?”
  • “Would a reduced term plus a rate guarantee solve the concern?”
Response ladder
  1. Acknowledge before explaining the agreement.
  2. Offer approved term reduction where available: examples in calls included 24 months and 18 months.
  3. Reassure that Flatpay will review better offers for existing customers; do not imply cancellation is always free unless policy allows it.
  4. Put the revised term/rate in writing.
Real call examples
Call 872784 · Saved / surcharge + contract
Merchant: “I’m not comfortable with that longer term.”
Agent: Reduced agreement to 24 months, kept 0.70, positioned it as a relationship rather than the merchant feeling trapped; merchant agreed to start using that day.
Call 901013 · Saved / lowered rate with trust issue
Merchant: “They told us 18 months, and now you’re telling me 36 months.”
Agent: Apologised, agreed to honour the shorter term, and offered to put the rate/term in an email.
Call 1042636 · Saved / new product
Merchant: “The main thing is also the three-year contract because I want to end the business in about two years.”
Agent: Explained closure proof/free cancellation route and offered written confirmation.
Do not say / watch-out
  • Do not say “you signed it” as the main response when the merchant says they were told something different. That increases the trust issue.

Payout, settlement, bank verification, cash-flow issue

payoutbankcashflow
108 tagged calls | saved 37 | pending 43 | churn/lost 13
When to use it
  • Merchant says money is missing, payout is late, bank statement was rejected, Amex slowed payout, or weekend/bank-holiday payouts hurt cash flow.
First line

“I understand why that is serious — if money is not landing when expected, it affects cash flow. Let me separate whether this is a bank-verification issue, an Amex/weekend timing issue, or an actual missing payout.”

Discovery questions
  • “Which transaction date and amount are you missing?”
  • “Has the bank statement or bank account verification been accepted?”
  • “Are you using Amex, and was faster payout discussed?”
  • “Is the issue weekday payout, weekend payout, or bank-holiday delay?”
Response ladder
  1. Bank verification: reassure funds are not lost, identify exactly what document is needed, and send the correct email path.
  2. Weekend payout: be transparent if it cannot be changed; do not sell rate as a fix if payout is the true blocker.
  3. Amex/faster payout: explain the trade-off if applicable and confirm the setting.
  4. Goodwill lever seen in calls: rate reduction for inconvenience where approved.
  5. Rescue script when they’re ready to cancel: “I’m reducing your rate to 0.59 — flat for all UK credit and debit. That’s a meaningful saving and I want you to give it a fair shot. If after a couple of weeks payouts are still a genuine blocker for your business — not just an inconvenience — we’ll review then. Most merchants find the rate offset more than covers the cadence.” Do not volunteer free cancellation up front.
  6. Close with the exact document/action, owner, and next callback date.
Real call examples
Call 960277 · Saved / lowered rate
Merchant: “We aren’t receiving any payouts. Nothing. Not a penny.”
Agent: Explained the rejected bank-statement issue, reassured funds would be reimbursed, and reduced rate from 0.59 to 0.55 for inconvenience.
Call 901013 · Saved / lower rate
Merchant: “Peter said we will get payment next day, which we didn’t.”
Agent: Explained Amex/faster-payment conflict and repositioned the new flat rate while agreeing written follow-up.
Call 900318 · Pending / payout blocker
Merchant: “I want the weekend as well.”
Agent: “The quickest we can do is Friday, Saturday and Sunday on the Monday.”
Call 1024520 · Lost / payout frequency
Merchant: “The rate is not a problem. It’s the payouts.”
Agent: This is a warning example: when payout is the root cause, rate reduction alone may not save the call.
Do not say / watch-out
  • Do not promise a payout schedule that operations cannot deliver. This is one of the fastest ways to create a mis-sold/trust issue.

Technical issue: terminal, network, connection, declined payments

technicalsupportinactive
74 tagged calls | saved 29 | pending 34 | churn/lost 2
When to use it
  • Terminal does not connect, no network, payments fail, customer says machine is offline/declining, driver terminals not working, or support has not resolved it.
First line

“I’m sorry that has disrupted taking payments. Let me capture the exact symptom so support can troubleshoot the right thing rather than just call you back generally.”

Discovery questions
  • “How many terminals are affected?”
  • “What exactly appears on screen — no network, loading, declined, offline, or error code?”
  • “Does it happen on Wi-Fi, 4G/SIM, or both?”
  • “Can you send a short video or photo of the error?”
Response ladder
  1. Capture the technical symptom, not just “not working”.
  2. Ask for video/photo evidence if possible.
  3. Send to support/tech with call ID and customer impact.
  4. If repeated issue: offer replacement/field visit/escalation where available.
  5. Follow up after fix and ask for first successful transaction.
Real call examples
Call 886113 · Awaiting tech support
Merchant: “One is working only, two are not working… no network or just loading up.”
Agent: Asked for a video by email and committed to sending it to support for troubleshooting.
Call 884334 · Technical + trust issue
Merchant: “It is offline… declining… you let me down.”
Agent: Acknowledged the prior 4G issue and booked a callback at a time the merchant chose.
Call 883688 · Surcharge retained / bank issue overlap
Merchant: Payments declined because of business description/alcohol category.
Agent: Confirmed the bank had been chased and that the team would call back once they had an update.
Do not say / watch-out
  • Do not simply ask “is it working?” and close the call when they say no. Get evidence, error state, and terminal count.

Product or feature gap: remote payment, pay-by-link, split payment, smaller terminal, POS

productfeatureroadmap
81 tagged calls | saved 25 | pending 35 | churn/lost 13
When to use it
  • Merchant needs pay-by-link, phone payments, deposits, split payments, smaller/mobile terminal, POS/till integration, or a feature they were told existed.
First line

“I understand why that would be a concern.”

Discovery questions
  • “Which feature do you need day-to-day, and how often?”
  • “Were you told this was already available?”
  • “Can the business continue temporarily with card-present payments, or is the feature essential before you can use Flatpay?”
  • “Would a test phase, account pause, or written guarantee solve the risk?”
Response ladder
  1. Be clear: live now vs roadmap vs not available.
  2. Offer workaround or product specialist/test phase where genuinely available.
  3. If we do not offer the feature they were promised, apologise. Clarify internally whether it’s on the roadmap, then let the merchant know if we will have it in the future.
  4. If it’s not on the roadmap, still push for usage where possible — don’t drop the relationship just because that specific feature isn’t coming.
Qualifying questions for Pay-by-Link / product testing phase
  • “Do you require any plug-in integrations?”
  • “Are you okay with experiencing bugs and initial technical limitations? It is in trial phase, so it may not be perfect.”
Real call examples
Call 921280 · Awaiting new product/feature
Merchant: “If I need to take a deposit on the phone, I cannot do that.”
Agent: Explained Pay By Link as the upcoming alternative, but clarified it had not been released yet.
Call 1042636 · Saved / new product
Merchant: “Remote payment and the three-year contract.”
Agent: Offered Pay By Link test phase, account pause, and free cancellation if the test did not work.
Call 1053768 · Pending / split payment
Merchant: “I was told the features are the same as Dojo.”
Agent: Apologised for the mismatch and arranged for someone to demonstrate the upcoming split/calculator feature within the customer’s timeline.
Do not say / watch-out
  • Do not say “very soon” without a safe expectation or next step. Roadmap promises can become the next churn reason.

Trust complaint — sales promise didn’t match reality

trustmis-soldescalation
73 tagged calls | saved 27 | pending 28 | churn/lost 15
When to use it
  • Merchant says sales rep lied, disappeared, promised old-provider cancellation, Amex, free trial, a shorter contract, no contract at all, or same features as another provider. For surcharge-specific promises, use the Surcharge scenario instead.
First line

“I’m sorry — that is not the experience we want you to have. I’m going to separate the issues, check what was promised, and give you clear next steps in writing so you are not left chasing.”

Discovery questions
  • “What exactly were you told before signing?”
  • “Which part has not happened: old-provider cancellation, payout timing, rate, contract length, Amex, or feature availability?”
  • “Do you have messages/screenshots from the rep that I can review?”
  • “What outcome would rebuild enough confidence for you to continue?”
Response ladder
  1. Apologise without blaming the merchant.
  2. Acknowledge the specific failure: “I understand you were told X and experienced Y.”
  3. Do not debate the agreement first; investigate and escalate to sales/manager if needed.
  4. Where possible, honour the promise or offer a practical equivalent: term reduction, rate adjustment, pause, product test, or cancellation route.
  5. Send an email summary of what was agreed.
Real call examples
Call 900180 · Pending / trust recovery
Merchant: “The sales rep got me signed… whatever he told me wasn’t true and he disappeared.”
Agent: Apologised for the miscommunication and started to separate the old-provider cancellation, payout, and contract issues.
Call 901013 · Saved / trust recovery
Merchant: “So far everything has been bad advice… we made a bad judgement.”
Agent: Took the complaint seriously, offered 0.47, agreed shorter term, and committed to email confirmation.
Do not say / watch-out
  • Avoid “everything is written in the agreement” as the first defence. It may be true, but it does not repair trust.

Seasonal, temporary closure, renovation, event business, low-volume business

seasonaltemporaryusage
101 tagged calls | saved 17 | pending 19 | churn/lost 7
When to use it
  • Merchant is closed temporarily, quiet season, renovation, moving, holiday, sickness, event-only/large-few-transactions business, or irregular opening hours.
First line

“That makes sense. I’ll note that the low usage is seasonal/temporary rather than an issue with Flatpay. When do you expect payments to restart?”

Discovery questions
  • “Is the business closed temporarily or just quieter?”
  • “What date should we expect transactions to restart?”
  • “Will transactions be fewer but larger, or regular once you reopen?”
  • “Do you need the account paused or just noted for follow-up?”
Response ladder
  1. Record reason and restart date.
  2. If closure is temporary, note pause/follow-up options if available.
  3. If event-based, tag as large/few transactions and avoid repeated low-usage calls.
  4. If minimum usage applies, mention it carefully after context is captured.
Real call examples
Call 879212 · Seasonal / event
Merchant: “We had the London Marathon Expo and we’re going to have a few in-store events.”
Agent: Confirmed event-based usage and used the call to answer an international-card surcharge question.
Call 884568 · Temp closed / renovation
Merchant: “We’re moving into a different phase… renovation.”
Agent: Asked for approximate time frame and noted renovation.
Call 880515 · Seasonal / large few transactions
Merchant: “I rent holiday caravans… fewer transactions, but larger amounts.”
Agent: Classified the business correctly as larger payments/fewer transactions.
Call 885370 · Seasonal / event
Merchant: “I’ve been closed… hopefully this week.”
Agent: Made a note and set next-week follow-up rather than pushing.
Do not say / watch-out
  • Do not treat event/seasonal businesses like daily retail usage. It creates unnecessary friction.

Business closed, new owner, or takeover

closedtakeoverownership
20 tagged calls | saved 4 | pending 3 | churn/lost 2
When to use it
  • Merchant permanently closed, sold the business, new owner is using the premises/terminal, or wants to transfer the account.
First line

“I’m sorry to hear that. Just so I guide you correctly, is the business permanently closed, temporarily closed, or has someone taken over?”

Discovery questions
  • “Is there a new owner or new company?”
  • “Are transactions still going through the terminal?”
  • “Can the new owner take over the agreement, or do we need closure documentation?”
  • “Do you have DS01/CS01 or other proof of closure if required?”
Response ladder
  1. Temporary closure: move to seasonal/pause card.
  2. Permanent closure: explain documents and return process.
  3. Takeover: collect new-owner details and start takeover route.
  4. If new business opening soon: check if terminal can be linked to new business.
Real call examples
Call 878844 · Closed/new business possibility
Merchant: “It’s closed already.”
Agent: Asked for DS01/CS01 and checked whether a new company could use/link the terminal.
Call 981074 · Takeover info needed
Merchant: “I closed down permanently.”
Agent: Explained takeover as an option if someone is taking over the business or property.
Call 991419 · Takeover / new owner
Merchant: “Someone else took it over… transfer the account to him.”
Agent: Offered to arrange the takeover process and requested the new owner’s details.
Call 1066054 · Closed shop / churn
Merchant: Business closed / looking for another location.
Agent: Offered pause while they found another location before proceeding with cancellation.
Do not say / watch-out
  • Do not process as simple churn if there is a new owner who could take over the agreement.

General flow phrases

Acknowledge
  • “I understand why that would be a concern.”
  • “I’m sorry — that is not the experience we want you to have.”
  • “Now you’ve explained your circumstances, I understand why you want that changed.”
Discover
  • “Can I ask what is driving the cancellation?”
  • “When did this become a problem for you?”
  • “Out of 10 customers, roughly how many pay with business or international cards?”
Compare competitor offers
  • “Let me compare the full cost, not just the headline rate.”
  • “Does that include rental, authorisation, transaction, minimum monthly and business-card fees?”
  • “If I can beat the true blended cost, would you be open to staying?”
Surcharge value
  • “With surcharge enabled, you keep 100% of those business/international card payments.”
  • “We can reduce it first and review again if customers still object.”
  • “If we remove it completely, I’ll need to recalculate the base rate because those cards cost more to process.”
Close
  • “Are you happy for me to put that in place today?”
  • “I’ll send this in writing so you can confirm it with your partner.”
  • “Once this is updated, when will you be ready to start using the terminal again?”
  • “Is there anything else I can help you with in the meantime?”