Policy red-pen sheet
Every line below is a DRAFT the copilot may show a rep word for word. Nothing reaches a rep until you approve it.
How to approve
- Open
policy/src/playbook-onboarding.jsonorpolicy/src/playbook-customer-success.jsonand find the line by itstext_id. - To approve it, set
"status": "approved","approved_by": "<email>"(one ofstevan@currencytransfer.com, frompolicy/approvers.json) and"approved_at": "<YYYY-MM-DD>". - A line marked VERIFY contains a
[VERIFY …]marker: confirm the fact or rewrite it, then remove the marker. The loader refuses any approved line that still contains[VERIFY. - A line marked CONCRETE FACT names a time, date, decimal rate or "yesterday"-style detail from one call. The loader refuses it in an approved line: generalise it or delete it.
- To drop a line, delete its object. Do not renumber the other
text_ids. A line with"status": "retired"is out of use and never shown; it is listed under "retired lines" with the rule it breaks. Delete it once you agree, or set it back todraftto reconsider it. - Move headlines, concern headlines, caution notes, call-purpose labels and client fact labels and templates are approved the same way (same three fields), each in its own object:
- a move headline is the
headlineof the move inpolicy/src/playbook-<scenario>.json(headline.<move id>): the situation in the client's words, 8 words or fewer; - a concern headline is
concerns.<topic>.headlinein the same file (concern.<topic>.headline), one per objection topic plus the bucketsmoneyandprocess; - a caution note is the
live_noteof the risk rule inpolicy/src/rules-<scenario>.json(caution.<risk id>): one line, never starting with "Careful", "Say", "Worth saying" or "Ask first", because the view already shows that tag. The build refuses one that does. - a call-purpose label is the
labelof the purpose inpolicy/src/plan-<scenario>.json(plan.purpose.<purpose id>): what the live view's purpose line shows, one per option of the purpose Choice. - a client fact label is one of the
labelsof a fact slot inpolicy/src/plan-<scenario>.jsonfact_slots(plan.fact.<slot>.<value>, a country id forresidency): the chip the live view shows for that value. The amount, currency-pair and bank-country slots have atemplate(plan.fact.<slot>.template) instead, whose{amount},{currency},{sell},{buy}and{country}code fills with digits, ISO 4217 codes and a country's name from the gazetteer only; keep those placeholders. - a plan template item's
title,hintandnot_needed_reasonsit intemplates.<purpose>ofpolicy/src/plan-<scenario>.json(plan.template.<purpose>.<item>.title,.hint,.not_needed); the rate-pressure item's title israte_pressure.title(plan.rate_pressure.title). An item that does not always apply needs a not-needed reason; the build refuses an item naming a move, line, checklist id, fact, slot, stage or situation that does not exist.
- a move headline is the
- Situations (
docs/policy/rate-objections.md,docs/policy/like-for-like.md) sit under their move insituations: a point is shown only when the client's turn matches its situation. Approve a point like a line (theverbatimones are the approved playbook wording and are never rewritten), and theheadline(situation.<id>.headline, the client's words, 8 words or fewer) andhint(situation.<id>.hint) like a move headline.whatandnot_forare what Jev reads to decide whether the situation fits: red-pen them as literal conditions. The client examples are turns the situation was said in (harvest: a real, pseudonymised turn; drafted; or the rate PDF). The build refuses acore_text_idthat is not one of the situation's points, a do-not flag that is not a risk rule, a headline over 8 words, fewer than 2 client examples or one that is not redacted, and anappliesnaming an unknown fact or slot. - Checklist rows: with
"checklist": "derived"a row is a must-say item of a plan template, so change itsappliesinpolicy/src/plan-<scenario>.json; a hand list is edited inpolicy/src/rules-<scenario>.json. The wording that ticks an item is the noul of the same id in the scenario bank. - Re-run
node scripts/redpen.mjsand commit the JSON together with this file.
Onboarding
Source: policy/src/playbook-onboarding.json, policy/src/rules-onboarding.json. 14 moves, 29 lines: 0 approved, 29 to review; 0 carry [VERIFY, 0 a concrete fact. 10 retired.
Onboarding lines
| text_id | move | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
open_with_agenda.1 |
Set the agenda | draft | Thanks for making time. In about ten minutes I'd like to understand the transfer you're planning, get you activated, and show you how booking works. Does that suit? | ||
open_with_agenda.2 |
Set the agenda | draft | This is the activation call: I'll check a couple of things on your registration, and then we can talk through your first transfer. | ||
open_with_agenda.3 |
Set the agenda | draft | Before I explain anything, can I just check what you're looking to do, so I don't waste your time? | ||
check_serviceability_first.1 |
Check we can serve them | draft | Before we go further, can I confirm where you're resident and which country your bank account is in? Some of our partners have country restrictions. | ||
check_serviceability_first.2 |
Check we can serve them | draft | For a company account, which country is the business registered in, and are all the directors and owners resident there? | ||
check_serviceability_first.3 |
Check we can serve them | draft | I want to be straight with you: if we can't open an account for your country I'd rather tell you now than after you've sent documents. | ||
ask_about_the_transfer.1 |
Ask an open question about the transfer | draft | Tell me about the transfer you're planning: what it's for, which currencies, and roughly when. | ||
ask_about_the_transfer.2 |
Ask an open question about the transfer | draft | How have you been sending money abroad so far, and what's changed? | ||
ask_about_the_transfer.3 |
Ask an open question about the transfer | draft | What's the money for, and is there a date it needs to be there by? | ||
pin_down_timing_and_amount.1 |
Pin down amount and date | draft | Roughly how much are we talking about for the first transfer, and is that a one-off or something that repeats? | ||
pin_down_timing_and_amount.2 |
Pin down amount and date | draft | Is there a hard date, like a completion or a payroll run, that the money has to be in the account by? | ||
pin_down_timing_and_amount.3 |
Pin down amount and date | draft | Are we looking at one payment or a series over the coming months? | ||
confirm_funding_account.1 |
Confirm the funding account | draft | Which account will the money come from? It needs to be an account in your own name, or the company's name, sent by bank transfer. | ||
confirm_funding_account.3 |
Confirm the funding account | draft | After you book, the partner's bank details appear on screen and you pay them directly from your account. Does that work for you? | ||
close_the_document_gap.1 |
Name the missing document | draft | The only thing we're missing is a proof of address dated within the last three months: a utility bill, bank statement or council tax bill, in colour. Can you upload that today? | ||
close_the_document_gap.3 |
Name the missing document | draft | I know it feels like a lot; it's a regulated industry and the partner has to verify you once. Most completed applications are activated the same day. | ||
explain_who_holds_the_money.1 |
Explain who holds the money | draft | We're the platform; your transfer is contracted with a named FCA-authorised payment partner, and CurrencyTransfer never holds your money at any point. | ||
explain_who_holds_the_money.3 |
Explain who holds the money | draft | You'll see the partner's name on every booking, so you always know exactly who is holding the funds. | ||
explain_settlement_and_cutoff.2 |
Explain when the money arrives | draft | Given your completion date, I'd book and fund a few days ahead so the cut-off doesn't matter. | ||
explain_settlement_and_cutoff.3 |
Explain when the money arrives | draft | Once funded, you can track the payment on the dashboard rather than wondering where it is. | ||
explain_booking_is_binding.1 |
Explain that a booking is binding | draft | One important thing before you book: the moment you confirm, the partner buys that currency for you, so it's a contract. If the funds don't arrive, any loss on unwinding it is yours. | ||
explain_booking_is_binding.2 |
Explain that a booking is binding | draft | If anything changes after you book, call me straight away; the earlier we know, the smaller the problem. | ||
explain_booking_is_binding.3 |
Explain that a booking is binding | draft | That's why I'd only book once you know the funds are ready to send. | ||
handle_alternative_provider.2 |
Address the bank, Wise or Revolut comparison | draft | What's been good and what's been frustrating about using them so far? | ||
handle_alternative_provider.3 |
Address the bank, Wise or Revolut comparison | draft | You don't have to move everything; try one transfer with us alongside them and compare the settled amounts. | ||
offer_alert_instead_of_waiting.2 |
Offer a bookable rate alert | draft | What rate would make you say yes? Let's set that as your alert. | ||
agree_next_step.1 |
Agree the next step | draft | So: you'll upload the proof of address this afternoon, I'll get you activated, and we'll book the transfer tomorrow morning. Shall I call you at ten? | ||
agree_next_step.2 |
Agree the next step | draft | Would you like to book it now while we're on the call, or set the alert and I'll message you on the dashboard when it hits? | ||
agree_next_step.3 |
Agree the next step | draft | I'll send you a summary on your dashboard with the partner's name and what happens next. Anything I've missed? |
Onboarding retired lines
| text_id | move | text | rule broken |
|---|---|---|---|
confirm_funding_account.2 |
Confirm the funding account | One thing that trips people up: the funds have to come from you, not a family member or a friend, or the partner can't accept them. Is that ok for this transfer? | v0 draft with an unverified fact; not approved in the red-pen of 2026-09-25 |
close_the_document_gap.2 |
Name the missing document | For the company we need the registration document, ID for the directors, and ID plus address for anyone owning over 25 percent. Which of those can you send now? | v0 draft with an unverified fact; not approved in the red-pen of 2026-09-25 |
explain_who_holds_the_money.2 |
Explain who holds the money | Your funds sit with the partner in safeguarded, segregated accounts until they're paid out to your beneficiary, and that protection applies even if the partner or we were to fail. | v0 draft with an unverified fact; not approved in the red-pen of 2026-09-25 |
show_the_rate_against_mid_market.1 |
Compare the rate against mid-market | On the dashboard you'll see the mid-market rate next to your rate, so you can see the margin rather than take my word for it. | Breaks 'compare what lands, not mid-market' (mid_market_comparison): it makes the mid-market rate the benchmark and puts our margin on the table ('so you can see the margin'). |
show_the_rate_against_mid_market.2 |
Compare the rate against mid-market | What rate did your bank quote you? Let's compare it against the live mid-market rate right now. | Breaks 'move to a comparison that can actually be made': it compares a bank quote with mid-market, a number nobody trades at, instead of what lands from each, same day, same amount (mid_market_comparison.2). |
show_the_rate_against_mid_market.3 |
Compare the rate against mid-market | There's no transfer fee; the only cost is the difference between the mid-market rate and your rate, and that's shown on screen before you book. | Breaks 'Do not explain the pricing' / 'Explain how the spread is built' (do-not): it tells the client our cost is the gap between mid-market and their rate. |
handle_rate_objection.1 |
Handle a rate objection | Was that quote against the mid-market rate at the time? Let's put both side by side now, because a headline rate on a different day isn't comparable. | Breaks 'do not defend the number, change what is being compared': it lines the two quotes up against mid-market. Its point about stale and headline rates is now qualify_the_quote.1 and .2. |
handle_rate_objection.2 |
Handle a rate objection | Fair challenge. What I can do is show you the live quote with the margin visible; if we're not competitive on your amount, I'll tell you. | Breaks 'Do not explain the pricing' ('the margin visible') and invites a discount: 'if we're not competitive on your amount, I'll tell you' concedes a better price exists for somebody. |
handle_rate_objection.3 |
Handle a rate objection | Banks typically build a margin of up to a few percent into the rate plus a flat fee; ours is shown transparently, so compare the total cost, not the fee. | Breaks 'Do not explain the pricing': it explains how bank margins and ours are built. 'Compare the total cost' is now qualify_the_quote.3 and .4. |
handle_alternative_provider.1 |
Address the bank, Wise or Revolut comparison | Those are fine for small amounts. At your size the questions are the rate on that amount, whether you get a person handling it, and settlement timing; shall we compare on those? | Breaks 'Do not suggest they are wrong ... do not rubbish the competitor': 'fine for small amounts' tells the client their provider is wrong for them, and it keeps the rate on one amount as the comparison (competitor_named compares what landed over three trades). |
Onboarding situations
Set the agenda (open_with_agenda)
Situation call_just_answered
- Headline
situation.call_just_answered.headline(approved): Hello? Who's speaking? - Hint
situation.call_just_answered.hint(approved): Name yourself and the reason for the call, then stop and let them answer. - What (when it applies, read by the
fits::call_just_answeredquestion): The call has just connected. The client has only answered or asked who is calling ('Hello?', 'Yes, speaking', 'Who's this?'), and the rep has not yet said who they are, that they are calling from Currency Transfer, or what the call is about. - Not for: Any point after the rep has introduced themselves and said why they are calling; a call the client placed to us or is returning; a client who opens with their own question about a transfer, a document or a problem.
- Applies: always
- Client example (harvest): Yes. Who's speaking?
- Client example (harvest): Yeah. Speaking. Who is this?
- Client example (harvest): Hello? Yes.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):open_with_agenda.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
open_with_agenda.h1 |
approved | My name is [your name]. I'm calling from Currency Transfer. It's just regarding an application you made with us to transfer {currency pair}. | harvest 30 calls/2 reps | rep fills [your name], {currency pair} |
Check we can serve them (check_serviceability_first)
Situation works_abroad
- Headline
situation.works_abroad.headline(approved): I'm working abroad at the moment. - Hint
situation.works_abroad.hint(approved): Only once they have said which country they work in; use that country. - What (when it applies, read by the
fits::works_abroadquestion): The client has said they live or work in a country other than the UK ('I work in Saudi', 'I'm based out of Qatar'), and nobody in the call has yet asked how long they have been there. - Not for: A client who lives in the UK; a client who has only said where the money is going or which currency they sell, since a destination or a currency is not where they live; a client whose UK address is the open question; a question about the rate, safety or documents.
- Applies: unless the
residencyfact isGB(applies while unknown) - Client example (harvest): Currently, I'm working in Saudi Arabia, and I do have asset in Australia that I need to transfer from time to time
- Client example (harvest): So I I work in I I'm British as in but I work in Saudi,
- Client example (harvest): I'm working in Lithuania at the moment.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):check_serviceability_first.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
check_serviceability_first.h1 |
approved | Have you been working in {country} for a while? | harvest 11 calls/3 reps | {country} from residency, shown once known |
Situation uk_address_unclear
- Headline
situation.uk_address_unclear.headline(approved): I don't live in the UK anymore. - Hint
situation.uk_address_unclear.hint(approved): Ask it straight; don't guess from the application address. - What (when it applies, read by the
fits::uk_address_unclearquestion): The client has said they moved abroad, no longer live at a UK address, or that the address they gave us is not their real or current one, and nobody has yet asked whether they still have a UK address. - Not for: A client who has said they live at a UK address; a client who works abroad but has said nothing about their address; a question about which document proves their address.
- Applies: always
- Client example (harvest): I It's not a It's not the correct address. I just put in a made up address to get through.
- Client example (harvest): So I was like, that's crazy. I don't live there anymore, and I've got I've been here for so long.
- Client example (harvest): So I've recently moved out to Saudi Arabia. I'll be spending at least sort of eight months a year out here.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):check_serviceability_first.h2 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
check_serviceability_first.h2 |
approved | Do you have a UK address? | harvest 6 calls/3 reps; stutter removed |
Ask an open question about the transfer (ask_about_the_transfer)
Situation amount_not_said
- Headline
situation.amount_not_said.headline(approved): I'd like to send some money over. - Hint
situation.amount_not_said.hint(approved): A rough figure is enough; don't press for an exact amount. - What (when it applies, read by the
fits::amount_not_saidquestion): The client has said they want to make a transfer, or has described it (what it is for, the currencies or the country), but nobody in the call has said an amount, and the client's latest turn is not a question or a problem of their own. - Not for: A client who has already given an amount or a range; a client whose latest turn asks a question (how it works, whether it is safe, how long it takes) or raises a problem, which needs answering first; a call where the transfer has not come up yet.
- Applies: always
- Client example (harvest): Okay. I I would like to understand how it works because I need to buy euro.
- Client example (harvest): It's from US to pounds.
- Client example (harvest): Yes. Because I'm living in Australia.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):ask_about_the_transfer.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
ask_about_the_transfer.h1 |
approved | And how much are you looking to transfer? | harvest 37 calls/4 reps |
Situation first_transfer_date_not_said
- Headline
situation.first_transfer_date_not_said.headline(approved): I know what I'm sending, not when. - Hint
situation.first_transfer_date_not_said.hint(approved): Ask about the first transfer only; the rest can follow. - What (when it applies, read by the
fits::first_transfer_date_not_saidquestion): The client has described what they want to send (the amount, how often, or what it is for), but nobody has said when the first transfer will be, and the client's latest turn is not a question or a problem of their own. - Not for: A client who has already said when they will send it (a date, 'this week', 'after completion'); a client whose latest turn asks a question or raises a problem; a client who has not yet said what they want to send.
- Applies: always
- Client example (harvest): No. Every month. My you know, every month, I'm sending probably half of my salary back to The UK.
- Client example (harvest): Probably once every three months, I'll I'll send or
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):ask_about_the_transfer.h2 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
ask_about_the_transfer.h2 |
approved | When are you looking to make your first transfer? | harvest 17 calls/5 reps |
Pin down amount and date (pin_down_timing_and_amount)
Situation plans_described_no_amount
- Headline
situation.plans_described_no_amount.headline(approved): I'll be sending money over the coming months. - Hint
situation.plans_described_no_amount.hint(approved): Anchor on the next transfer: roughly how much, and when. - What (when it applies, read by the
fits::plans_described_no_amountquestion): The client has explained what the money is for, or described transfers over the coming weeks or months (a property, salary, family support, a bigger transfer this time), but has not said how much the next transfer will be. - Not for: A client who has already given the amount of the next transfer; a client who has not yet said what the transfer is for; a client whose latest turn asks a question or raises a concern.
- Applies: always
- Client example (harvest): So this is why this is the why because I live there, so she needs to transfer the money from here to there.
- Client example (harvest): And so over the next two years, but it could be, like, in the next six months or it could be all the way up to two years. Just trying to find the right place.
- Client example (harvest): the transfer I'm gonna make or wanting to make is probably gonna be more significant this time. Otherwise, it's just to cover things back home that go out of our UK accounts still.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):pin_down_timing_and_amount.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
pin_down_timing_and_amount.h1 |
approved | What is the amount that you plan to transfer? | harvest 21 calls/4 reps; stutter removed | ||||
pin_down_timing_and_amount.h2 |
approved | What's the immediate amount you plan to send, and when? | harvest 9 calls/4 reps; stutter removed |
Confirm the funding account (confirm_funding_account)
Situation funding_owner_unclear
- Headline
situation.funding_owner_unclear.headline(approved): It might come from my husband's account. - Hint
situation.funding_owner_unclear.hint(approved): Ask it openly, before explaining any rule about someone else's money. - What (when it applies, read by the
fits::funding_owner_unclearquestion): The first transfer is being discussed and nobody has established whose account the money will leave from; or the client has mentioned a spouse, relative, partner or company in connection with paying, without saying whose account it will come from. - Not for: A client who has already said the money comes from an account in their own or their company's name; a client who has already said another named person will send it, which needs the third-party rule explained rather than a question; a question only about which bank or country the money comes from.
- Applies: always
- Client example (harvest): It'll well, I've got a few options. I can put it in my daughter's account and send it over.
- Client example (harvest): Like, maybe it's just coming all from my husband's account or all from
- Client example (harvest): The question, can I fund this transaction from my American personal account, or can I fund it from my American company account?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):confirm_funding_account.h2 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
confirm_funding_account.h2 |
approved | Whose account will the money come from, yours or someone else's? | Stevan 2026-09-25, open-ended variant, when applicable |
Situation bank_abroad_not_named
- Headline
situation.bank_abroad_not_named.headline(approved): I'll be sending it from my account abroad. - Hint
situation.bank_abroad_not_named.hint(approved): Only once they have said which country they bank in; use that country. - What (when it applies, read by the
fits::bank_abroad_not_namedquestion): The client will send money from a bank account outside the UK (they have said the country, or that they sell that country's currency from an account there), and has not named the bank. - Not for: A client funding from a UK bank account; a client who has already named their bank; a question about whose name the account is in.
- Applies: unless the
residencyfact isGB(applies while unknown) - Client example (harvest): Well, it's so so this will be transfers that I I will be doing in the future. But yeah. So from Saudi Real into Sterling. Yeah.
- Client example (harvest): It's SAR, GBP, and GBP SAR.
- Client example (harvest): To Sweden from Saudi.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):confirm_funding_account.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
confirm_funding_account.h1 |
approved | And who is it that you bank with in {country}? | harvest 51 calls/6 reps (+20 calls UAE variant); country from client facts | {country} from residency, shown once known |
Name the missing document (close_the_document_gap)
Situation documents_outstanding_next_step
- Headline
situation.documents_outstanding_next_step.headline(approved): So what's the next step with the documents? - Hint
situation.documents_outstanding_next_step.hint(approved): Tell them what happens next, then close on the email. - What (when it applies, read by the
fits::documents_outstanding_next_stepquestion): Verification documents are still missing, and the client asks what happens next or what they need to send, or says they will send the documents later. - Not for: A client whose documents are complete; a question about one specific document, such as the proof-of-life selfie; a client asking why a document is needed for a payment after activation.
- Applies: always
- Client example (harvest): okay, so what's the next step? There's there's some documents that need to be uploaded, I I gather.
- Client example (harvest): It won't be till this evening. But if you send me an email requesting the information, I'll look at it this evening and send it over.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):close_the_document_gap.h2 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
close_the_document_gap.h2 |
approved | I'll send you an email asking for the documents. | harvest 16 calls/4 reps | ||||
close_the_document_gap.h4 |
approved | Your documents go to us and to the regulated partner that holds your account, and nobody else. | decision 12, approved in the proposals of 2026-09-27: the line to say instead of "we don't share it with anyone else" |
Situation selfie_missing_or_rejected
- Headline
situation.selfie_missing_or_rejected.headline(approved): I already sent you the selfie. - Hint
situation.selfie_missing_or_rejected.hint(approved): Explain what the selfie must show, not why the last one failed. - What (when it applies, read by the
fits::selfie_missing_or_rejectedquestion): The proof-of-life selfie is missing or was not accepted (the ID was not held next to the face, or a different ID was used); the rep has said so, or the client disputes it by saying the selfie or ID already went through, or offers to send the ID separately. - Not for: Other documents such as proof of address or a bank statement; a client whose documents are all accepted; a client who says everything they uploaded went through when no document has been named as missing or rejected; a general question about what happens next.
- Applies: always
- Client example (harvest): Everything an everything attachment. came through. Yeah. So everything everything else came through. The, I believe, the other the ID and the selfie.
- Client example (harvest): I chunk can send of you the that as well as that as a separate document, the actual passport if you want.
- Client example (harvest): a passport was better in terms of ID, but that's fine.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):close_the_document_gap.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
close_the_document_gap.h1 |
approved | With the proof of life selfie, hold your passport next to your face; it's just to verify you're a real person. | harvest 34 calls/4 reps; tidied |
Situation address_ties_me_to_tax_residency
- Headline
situation.address_ties_me_to_tax_residency.headline(approved): Will this address tie me to that country? - Hint
situation.address_ties_me_to_tax_residency.hint(approved): One address is enough; don't push a second one. - What (when it applies, read by the
fits::address_ties_me_to_tax_residencyquestion): The client worries that giving us an address in a country, as their proof of address, ties them to tax residency there or exposes them to that country's tax office. - Not for: A genuine question about where the client lives, works or banks, or whether we can serve their country, which is serviceability; a question about what to send next or where to send the money.
- Applies: always
- Client example (harvest): a little bit worried about that just in terms of being a tax resident.
- Client example (harvest): both. I'm just more hesitant just because
- Client example (harvest): yeah, it's just putting that New Zealand or Canadian address, and it's, like, somewhere along the line that that you're a resident there is you know, there's a reason we work in Saudi and not in New Zealand.
- Client example (drafted): I'd rather not give you my address over there; I don't want anything saying I'm resident there for tax.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):situation.address_ties_me_to_tax_residency.point - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
situation.address_ties_me_to_tax_residency.point |
approved | We only need one proof of address, and a bank statement, utility bill or government letter for your {country} address is fine. | decision 13, approved in the proposals of 2026-09-27: employer or HR letters are not proof of address | {country} from residency, shown once known |
Explain who holds the money (explain_who_holds_the_money)
Situation is_my_money_safe
- Headline
situation.is_my_money_safe.headline(approved): Is my money protected with you? - Hint
situation.is_my_money_safe.hint(approved): Answer the safety question directly; add no guarantees. - What (when it applies, read by the
fits::is_my_money_safequestion): The client asks whether their money is safe or protected, who holds it, whether the service is regulated (FCA), or what happens to their funds if something goes wrong. - Not for: A question about where to send the money or which account it goes into; a question about the rate, the fees or how long the transfer takes.
- Applies: always
- Client example (harvest): you know, ready for a pretrade, is that FCA FCA protected?
- Client example (harvest): FCA broker? What what is your com what do your com what does your company do?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):explain_who_holds_the_money.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
explain_who_holds_the_money.h1 |
approved | The funds are held in a segregated account, so they cannot be used for business operations; they're held entirely separate. | harvest 2 calls/2 reps; tidied; safeguarding claim, locked tier |
Situation where_do_i_send_funds
- Headline
situation.where_do_i_send_funds.headline(approved): Where do I actually send the money? - Hint
situation.where_do_i_send_funds.hint(approved): Only when the activating partner is known; use that partner's bank and city. - What (when it applies, read by the
fits::where_do_i_send_fundsquestion): The client asks, or checks their understanding of, how or where they send their money after booking: the payment instructions, which account it goes into, or whose name that account is in. - Not for: A question about whether the money is safe or regulated; a question about how long the money takes to arrive.
- Applies: once
settlement_partner_knownis persisted (nothing sets it yet, so never in M1) - Client example (harvest): So, I book it online, and it should come out with the proper rate and also send me the instructions on how, how to actually transfer the funds. Is that correct?
- Client example (harvest): how does yours work? Is it an instant change and or, like, does it go into a different account
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):explain_who_holds_the_money.h2 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
explain_who_holds_the_money.h2 |
approved | verbatim | This is going to be an account in your name, but it will be with {settlement_bank} in {settlement_city}. | harvest 4 calls/2 reps. Stevan 2026-09-25: VARIES BY ACTIVATING PARTNER; not all accounts are in the client's name or with Barclays; show only when the partner is known and use that partner's structure | {settlement_bank} from settlement_partner, shown once known; {settlement_city} from settlement_partner, shown once known |
Compare the rate against mid-market (show_the_rate_against_mid_market)
Situation mid_market_comparison
- Headline
situation.mid_market_comparison.headline(approved): Why am I getting less than Google says? - Hint
situation.mid_market_comparison.hint(approved): Correct it once, briefly, and move to a comparison that can actually be made. If you argue the gap you are defending your margin on a call that was never about your margin. - What (when it applies, read by the
fits::mid_market_comparisonquestion): The client compares our rate with the mid-market or interbank rate they saw on Google, XE or a similar site, and asks why ours is lower or different. - Not for: A rate quoted by a bank or another provider.
- Applies: always
- Client example (ct-rate-objection.pdf): Google says 1.2740. Why am I getting 1.2690?
- Client example (harvest): the currency conversion is the same as the one that Google depicts, but normally it should be half the one that Google depicts.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):mid_market_comparison.2 - Do-not flags:
rep_explained_spread - Do not: Explain how the spread is built. The moment you break down your own pricing, the call is about what you make rather than what they get.
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
mid_market_comparison.1 |
approved | verbatim | That's the mid-market rate. It's the midpoint between buying and selling, so it's a reference number rather than a price. Nobody trades at it, banks included. | ||||
mid_market_comparison.2 |
approved | verbatim | The number worth comparing is what actually lands from us against what actually lands from your bank, same day, same amount. |
Explain when the money arrives (explain_settlement_and_cutoff)
Situation when_will_it_arrive
- Headline
situation.when_will_it_arrive.headline(approved): How long does it take to arrive? - Hint
situation.when_will_it_arrive.hint(approved): Give the rule for their currency, not a promise of a date. - What (when it applies, read by the
fits::when_will_it_arrivequestion): The client asks how long a transfer takes, when the money will arrive or whether it can land the same day, or names a date the money must arrive by. - Not for: A question about when their account will be activated or their documents checked; a question about whether their money is safe or who holds it.
- Applies: always
- Client example (drafted): If I book it on a Monday morning, will it get there the same day?
- Client example (drafted): The money has to be in the solicitor's account by the end of next week. How long does it take?
- Client example (harvest): Okay. And then once I initiate the the transfer, how long does it take to get to the other party?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):explain_settlement_and_cutoff.1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
explain_settlement_and_cutoff.1 |
approved | For major currencies, if your funds reach the partner before their cut-off, usually 2pm UK time, it settles the same day. Other currencies can take up to five working days. |
Explain that a booking is binding (explain_booking_is_binding)
Situation learning_to_quote_and_book
- Headline
situation.learning_to_quote_and_book.headline(approved): So I get a quote, then book? - Hint
situation.learning_to_quote_and_book.hint(approved): As they reach the booking step, before they confirm anything. - What (when it applies, read by the
fits::learning_to_quote_and_bookquestion): The client is being shown, or asks, how quoting and booking work ('so I get a quote, then book?'), says they will get a quote or book, or asks whether a booking can be cancelled or changed. - Not for: A client who has already been told that a booking is binding; a question about how long the transfer takes after booking; a client who only asks for today's rate.
- Applies: always
- Client example (harvest): And then you'll get a quote.
- Client example (harvest): doing doing this, this, like, like, 15 fifteen times a times day a or day whatever.
- Client example (drafted): If the rate drops after I book, can I just cancel it?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):explain_booking_is_binding.h2 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
explain_booking_is_binding.h1 |
approved | You can quote and see the amount you'd get, but don't book unless you're happy to make the transfer and happy with the amount. | harvest 5 calls/2 reps; tidied | ||||
explain_booking_is_binding.h2 |
approved | Cancelling a trade can result in losses, because it's a live trade. | harvest 3 calls/1 rep; tidied |
Handle a rate objection (handle_rate_objection)
Situation qualify_the_quote
- Headline
situation.qualify_the_quote.headline(approved): Qualify the quote before you respond - Hint
situation.qualify_the_quote.hint(approved): Ask calmly, in order. You are not challenging them, you are finding out what they are actually holding. - What (when it applies, read by the
fits::qualify_the_quotequestion): The client cites a rate or quote from another provider or their bank (a number, or 'they give me a better rate'), and the rep has not yet asked when they got it, whether it was a live quote on their amount, what the fees on top were, or what actually landed. - Not for: A request for a better rate with no competing number ('Can you do better than that?'); a comparison with the mid-market rate on Google or a similar site; the four questions already asked.
- Applies: always
- Client example (ct-rate-objection.pdf): Company X gives me a better rate.
- Client example (drafted): Another broker quoted me a better rate on the same amount last week.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):qualify_the_quote.4 - Do-not flags:
rep_rubbished_competitor
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
qualify_the_quote.1 |
approved | verbatim | When did you get that rate? | ||||
qualify_the_quote.2 |
approved | verbatim | Was that a live quote on your amount, or a headline off a website? | ||||
qualify_the_quote.3 |
approved | verbatim | What were the fees on top, including the receiving bank's cut? | ||||
qualify_the_quote.4 |
approved | verbatim | What actually landed in the beneficiary account last time, against what you were quoted? |
Situation no_quote_in_hand
- Headline
situation.no_quote_in_hand.headline(approved): Can you do better than that? - Hint
situation.no_quote_in_hand.hint(approved): Three beats, in order. Keep each one short: length reads as negotiation. - What (when it applies, read by the
fits::no_quote_in_handquestion): The client asks for a better rate or price ('Can you do better than that?', 'Is that the best you can do?') without naming another provider's rate, a bank quote, or the rate on Google. - Not for: A client who names a competitor's rate, cites the mid-market rate, or says their bank matched: if a real comparator comes back, you are no longer in this objection.
- Applies: always
- Client example (ct-rate-objection.pdf): Can you do better than that?
- Client example (drafted): Is that really the best rate you can give me?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):no_quote_in_hand.2 - Do-not flags:
rep_improved_rate_unasked,rep_explained_spread,rep_said_standard_for_volume - Do not: Improve the rate to close a question that was not about the rate.
- Do not: Do not explain the pricing, and do not say it is standard for their volume: that concedes a better price exists for somebody, which is the door you were trying to shut.
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
no_quote_in_hand.1 |
approved | verbatim | Better than what? | ||||
no_quote_in_hand.2 |
approved | verbatim | No. That's the price. | ||||
no_quote_in_hand.3 |
approved | verbatim | And it's live, so it's moving while we talk. Do you want it, or shall I requote in ten? |
Situation competitor_named
- Headline
situation.competitor_named.headline(approved): Company X gives me a better rate. - Hint
situation.competitor_named.hint(approved): Run the four qualifying questions before you say anything else. Move the comparison from one quote to the last three trades. - What (when it applies, read by the
fits::competitor_namedquestion): The client says another provider (a named company, a broker, their other platform) gives or offered them a better rate, usually with a number. - Not for: The client's own bank matching us after hearing from us; a number off Google or a similar site; a request for a better rate with no comparator.
- Applies: always
- Client example (ct-rate-objection.pdf): Company X gives me a better rate.
- Client example (drafted): My other broker gave me a better rate than this on my last transfer.
- Ask the qualifying questions first (
qualify_first): yes - Core line (
core_text_id, said = handled):competitor_named.2 - Do-not flags:
rep_rubbished_competitor - Do not: Suggest they are wrong or lying, and do not rubbish the competitor by name. Both make you sound like the expensive option defending itself.
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
competitor_named.1 |
approved | verbatim | They probably do on the first one. What matters is what you're getting on trade twenty, when nobody's watching. | ||||
competitor_named.2 |
approved | verbatim | Pull your last three confirmations from them and let's compare what landed, not what was quoted. |
Situation concession_terms
- Headline
situation.concession_terms.headline(approved): If you do move on price - Hint
situation.concession_terms.hint(approved): Get something on the call, not vaguely later. - What (when it applies, read by the
fits::concession_termsquestion): The rep is about to move on price or has just offered a better rate, or the client asks what it would take to get a better rate (more volume, moving other payments, a forward, an introduction). - Not for: Any of the five rate objections answered without moving on price.
- Applies: always
- Client example (drafted): What would it take for you to sharpen that rate?
- Client example (drafted): If I moved all my payments over to you, could you do better?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):concession_terms.5 - Do-not flags:
rep_improved_rate_unasked
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
concession_terms.1 |
approved | verbatim | Volume. A monthly or quarterly commitment that puts them in the band you are pricing them at. | ||||
concession_terms.2 |
approved | verbatim | Consolidation. The corridors they currently run elsewhere come to you. | ||||
concession_terms.3 |
approved | verbatim | Forward cover. The next tranche booked forward rather than left to shop. | ||||
concession_terms.4 |
approved | verbatim | Introduction. The finance contact at the group company, the supplier, the sister office. | ||||
concession_terms.5 |
approved | verbatim | The rate is one number on one day. What you're paying for is knowing what it'll be worth when it lands and when it'll get there. If you press send and then spend two days chasing, the half pip you saved cost you more than it was worth. |
Address the bank, Wise or Revolut comparison (handle_alternative_provider)
Situation serial_shopper
- Headline
situation.serial_shopper.headline(approved): I'll just check what the others are doing. - Hint
situation.serial_shopper.hint(approved): Price them for the time they cost, or let them go. Winning them at the floor is worse than losing them. - What (when it applies, read by the
fits::serial_shopperquestion): The client says they will check other brokers or providers before booking, or that they compare several providers on every trade ('I'll just check what the others are doing'). - Not for: A client with one competing quote already in hand; a client checking a provider for the first time who has not said they shop around.
- Applies: always
- Client example (ct-rate-objection.pdf): I'll just check what the others are doing.
- Client example (harvest): I've been just jumping between the two systems to just see which is giving me the best rates.
- Client example (harvest): I'll log in periodically just to test you out and see if you're any better
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):serial_shopper.1 - Do-not flags:
rep_improved_rate_unasked - Do not: Chase them down on each trade. Every match sets the new ceiling and the next call starts below it.
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
serial_shopper.1 |
approved | verbatim | Happy to quote you every time. If you want a better number without the ring-around, give me the flow for the quarter and I'll price it properly. |
Situation bank_matched
- Headline
situation.bank_matched.headline(approved): I spoke to my bank; they matched you. - Hint
situation.bank_matched.hint(approved): Do not argue the number. Test whether it survives. - What (when it applies, read by the
fits::bank_matchedquestion): The client says their bank has matched or beaten our rate since they started talking to us. - Not for: A bank quote the client had before talking to us, or another provider's rate.
- Applies: always
- Client example (ct-rate-objection.pdf): I spoke to my bank; they matched you.
- Client example (drafted): My bank came back and said they'll do the same rate as you.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):bank_matched.1 - Do-not flags:
rep_went_under_bank - Do not: Go under them. A bank defending one account is not pricing to make money on it, and you cannot win that on price. Win it on the six months after they stop paying attention.
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
bank_matched.1 |
approved | verbatim | Good. That's the first time they've sharpened up for you. Ask them to hold it in writing for the next twelve months and see what comes back. | ||||
bank_matched.2 |
approved | verbatim | Worth looking at what they were giving you before we started quoting. That's their real price, the one that applies when nobody's pushing. |
Offer a bookable rate alert (offer_alert_instead_of_waiting)
Situation waiting_for_a_better_rate
- Headline
situation.waiting_for_a_better_rate.headline(approved): I'll hold off until the rate improves. - Hint
situation.waiting_for_a_better_rate.hint(approved): Don't forecast the rate; offer the alert instead. - What (when it applies, read by the
fits::waiting_for_a_better_ratequestion): The client says they want to wait for the exchange rate to improve before sending, asks whether the rate will go up or down, or names a rate they are hoping for, and has not said the money must arrive by a particular date. - Not for: A client who says our rate is too high or that someone else offers better (a rate objection: never offer an alert then); a client with a date the money must arrive by; a client ready to book now.
- Applies: always
- Client example (harvest): After looking at the what the exchange rates are at the moment, I looked at it last night. I thought I'm just gonna hold off for a little bit
- Client example (harvest): It's not looking promising, but I'm just waiting to check, see if it goes up a bit.
- Client example (harvest): I will exchange some, a big amount, when it is close to point four, I reckon, if it gets there.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):offer_alert_instead_of_waiting.1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
offer_alert_instead_of_waiting.1 |
approved | Nobody can predict the rate, but you can set a bookable alert at the level you'd be happy with, and it'll book or notify you the moment it's hit. | |||||
offer_alert_instead_of_waiting.h2 |
approved | Have you thought of setting a rate alert or a market order? If your target rate triggers, even briefly, you'd achieve it. | harvest 2 calls/2 reps; tidied | ||||
offer_alert_instead_of_waiting.h1 |
approved | It's worth knowing that on our platform you can set rate alerts, and even bookable ones. | harvest 3 calls/2 reps; tidied |
Situation waiting_but_has_a_date
- Headline
situation.waiting_but_has_a_date.headline(approved): I'd wait, but I have a deadline. - Hint
situation.waiting_but_has_a_date.hint(approved): Only when they have a date the money must arrive by. - What (when it applies, read by the
fits::waiting_but_has_a_datequestion): The client wants to wait for a better rate, and has also said the money has to arrive by a particular date or event (a completion, a deposit, a fee deadline). - Not for: A client waiting for a better rate with no date; a client with a deadline who wants to book now; a rate objection.
- Applies: always
- Client example (drafted): I'd rather wait for the rate to pick up, but the deposit has to be paid by the end of the month.
- Client example (drafted): Can I hang on and see if it improves? It just has to land before completion.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):offer_alert_instead_of_waiting.3 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
offer_alert_instead_of_waiting.3 |
approved | If there's a date the money has to be there by, an alert with a fallback date protects you both ways. |
Agree the next step (agree_next_step)
Situation activation_next_steps
- Headline
situation.activation_next_steps.headline(approved): So what happens now? - Hint
situation.activation_next_steps.hint(approved): Close on who does what next; keep it short. - What (when it applies, read by the
fits::activation_next_stepsquestion): The call is ending while the client's account is not yet activated: the rep has taken the details or asked for the remaining documents, and the client asks what happens next or when they will be able to make their first transfer, or says they have no more questions. - Not for: An account that is already activated, so the client can book now; a client whose question or concern is still being answered; a client who has just asked a new question about the transfer itself (how long it takes, the rate, the fees) that the rep has not answered yet; a call where the client's details have not been taken yet.
- Applies: always
- Client example (harvest): So when the papers are ready, can I transfer?
- Client example (harvest): Is it possible to get the instruction by email?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):agree_next_step.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
agree_next_step.h1 |
approved | I'll take the next steps to get you activated; if you have any questions get in touch, and you'll hear from us once activated. | harvest 7 calls/3 reps; tidied |
Onboarding move headlines
| text_id | move | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
headline.open_with_agenda |
Set the agenda | approved | Client doesn't know what the call is for | ||
headline.check_serviceability_first |
Check we can serve them | approved | Client lives or is registered abroad | ||
headline.ask_about_the_transfer |
Ask an open question about the transfer | approved | Client hasn't said what the transfer is for | ||
headline.pin_down_timing_and_amount |
Pin down amount and date | approved | Amount and date of the transfer are unclear | ||
headline.confirm_funding_account |
Confirm the funding account | approved | Client hasn't said where the money comes from | ||
headline.close_the_document_gap |
Name the missing document | approved | Client still owes us a document | ||
headline.explain_who_holds_the_money |
Explain who holds the money | approved | Client asks if their money is safe | ||
headline.show_the_rate_against_mid_market |
Compare the rate against mid-market | approved | Client asks how good our rate is | ||
headline.explain_settlement_and_cutoff |
Explain when the money arrives | approved | Client needs the money there by a date | ||
headline.explain_booking_is_binding |
Explain that a booking is binding | approved | Client is about to book | ||
headline.handle_rate_objection |
Handle a rate objection | approved | Client says the rate is too high | ||
headline.handle_alternative_provider |
Address the bank, Wise or Revolut comparison | approved | Client already uses a bank or Wise | ||
headline.offer_alert_instead_of_waiting |
Offer a bookable rate alert | approved | Client wants to wait for a better rate | ||
headline.agree_next_step |
Agree the next step | approved | Client is ready for the next step |
Onboarding concern headlines
| text_id | concern | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
concern.rate.headline |
rate |
approved | Client thinks our rate is too high | ||
concern.safety.headline |
safety |
approved | Client is worried their money isn't safe | ||
concern.timing.headline |
timing |
approved | Client needs the money to land by a date | ||
concern.fees.headline |
fees |
approved | Client is comparing our fees with their bank | ||
concern.trust_in_ct.headline |
trust_in_ct |
approved | Client isn't sure who we are | ||
concern.alternative_provider.headline |
alternative_provider |
approved | Client would rather use their bank or Wise | ||
concern.process_friction.headline |
process_friction |
approved | Client finds signing up a hassle | ||
concern.jurisdiction.headline |
jurisdiction |
approved | Client may be somewhere we can't serve | ||
concern.money.headline |
money |
approved | Client has a worry about cost | ||
concern.process.headline |
process |
approved | Client has a worry about the process |
Onboarding caution notes
| text_id | risk rule | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
caution.rep_made_guarantee |
Rep made a guarantee | approved | That sounded like a guarantee. | ||
caution.rep_made_rate_prediction |
Rep predicted the rate | approved | That sounded like a rate prediction. | ||
caution.funding_from_third_party |
Funds from a third party | approved | The money may come from someone else's account. | ||
caution.jurisdiction_concern |
Country may block the account | approved | Their country may stop us opening the account. | ||
caution.rep_improved_rate_unasked |
Rep moved on price for nothing | approved | That moved the price for nothing. Get something on the call for it. | ||
caution.rep_explained_spread |
Rep explained the spread | approved | That explained our margin. Compare what lands instead. | ||
caution.rep_said_standard_for_volume |
Rep said the rate is standard for their volume | approved | 'Standard for your volume' says somebody gets a better price. | ||
caution.rep_rubbished_competitor |
Rep ran down a competitor or the client's quote | approved | Running them down makes us sound like the expensive option. | ||
caution.rep_went_under_bank |
Rep offered to go under the bank | approved | Don't go under the bank. Test whether their price survives. | ||
caution.rep_said_documents_not_shared |
Rep said the documents are not shared | approved | The partner sees their KYC documents. Say who does. | ||
caution.booking_without_binding |
Booking agreed before "booking is binding" was said | approved | They agreed to book before hearing it is binding. |
Onboarding call purposes
| text_id | purpose | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
plan.purpose.first_call_after_signup |
first_call_after_signup |
approved | First call after sign-up | ||
plan.purpose.document_chase |
document_chase |
approved | Documents to chase | ||
plan.purpose.first_transfer_walkthrough |
first_transfer_walkthrough |
approved | First transfer walkthrough | ||
plan.purpose.other |
other |
approved | Other |
Onboarding client fact labels
| text_id | slot: value | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
plan.fact.client_type.personal |
client_type: personal |
approved | Personal client | ||
plan.fact.client_type.corporate |
client_type: corporate |
approved | Corporate client | ||
plan.fact.amount.template |
amount: template |
approved | About {amount} {currency} | ||
plan.fact.frequency.one_off |
frequency: one_off |
approved | One-off transfer | ||
plan.fact.frequency.weekly |
frequency: weekly |
approved | Weekly transfers | ||
plan.fact.frequency.monthly |
frequency: monthly |
approved | Monthly transfers | ||
plan.fact.frequency.quarterly |
frequency: quarterly |
approved | Quarterly transfers | ||
plan.fact.frequency.irregular |
frequency: irregular |
approved | Transfers now and then | ||
plan.fact.currency_pair.template |
currency_pair: template |
approved | {sell} to {buy} | ||
plan.fact.transfer_purpose.property |
transfer_purpose: property |
approved | For a property | ||
plan.fact.transfer_purpose.family_support |
transfer_purpose: family_support |
approved | Supporting family | ||
plan.fact.transfer_purpose.salary_or_pension |
transfer_purpose: salary_or_pension |
approved | Salary or pension | ||
plan.fact.transfer_purpose.supplier_payment |
transfer_purpose: supplier_payment |
approved | Paying suppliers | ||
plan.fact.transfer_purpose.school_fees |
transfer_purpose: school_fees |
approved | School fees | ||
plan.fact.transfer_purpose.investment |
transfer_purpose: investment |
approved | Investment | ||
plan.fact.transfer_purpose.other |
transfer_purpose: other |
approved | Another purpose | ||
plan.fact.residency.GB |
residency: GB |
approved | Lives in the UK | ||
plan.fact.residency.IE |
residency: IE |
approved | Lives in Ireland | ||
plan.fact.residency.FR |
residency: FR |
approved | Lives in France | ||
plan.fact.residency.ES |
residency: ES |
approved | Lives in Spain | ||
plan.fact.residency.PT |
residency: PT |
approved | Lives in Portugal | ||
plan.fact.residency.DE |
residency: DE |
approved | Lives in Germany | ||
plan.fact.residency.IT |
residency: IT |
approved | Lives in Italy | ||
plan.fact.residency.NL |
residency: NL |
approved | Lives in the Netherlands | ||
plan.fact.residency.BE |
residency: BE |
approved | Lives in Belgium | ||
plan.fact.residency.CH |
residency: CH |
approved | Lives in Switzerland | ||
plan.fact.residency.AT |
residency: AT |
approved | Lives in Austria | ||
plan.fact.residency.SE |
residency: SE |
approved | Lives in Sweden | ||
plan.fact.residency.NO |
residency: NO |
approved | Lives in Norway | ||
plan.fact.residency.DK |
residency: DK |
approved | Lives in Denmark | ||
plan.fact.residency.PL |
residency: PL |
approved | Lives in Poland | ||
plan.fact.residency.GR |
residency: GR |
approved | Lives in Greece | ||
plan.fact.residency.CY |
residency: CY |
approved | Lives in Cyprus | ||
plan.fact.residency.MT |
residency: MT |
approved | Lives in Malta | ||
plan.fact.residency.US |
residency: US |
approved | Lives in the US | ||
plan.fact.residency.CA |
residency: CA |
approved | Lives in Canada | ||
plan.fact.residency.MX |
residency: MX |
approved | Lives in Mexico | ||
plan.fact.residency.AU |
residency: AU |
approved | Lives in Australia | ||
plan.fact.residency.NZ |
residency: NZ |
approved | Lives in New Zealand | ||
plan.fact.residency.SA |
residency: SA |
approved | Lives in Saudi Arabia | ||
plan.fact.residency.AE |
residency: AE |
approved | Lives in the UAE | ||
plan.fact.residency.QA |
residency: QA |
approved | Lives in Qatar | ||
plan.fact.residency.ZA |
residency: ZA |
approved | Lives in South Africa | ||
plan.fact.residency.IN |
residency: IN |
approved | Lives in India | ||
plan.fact.residency.CN |
residency: CN |
approved | Lives in China | ||
plan.fact.residency.HK |
residency: HK |
approved | Lives in Hong Kong | ||
plan.fact.residency.SG |
residency: SG |
approved | Lives in Singapore | ||
plan.fact.residency.JP |
residency: JP |
approved | Lives in Japan | ||
plan.fact.residency.TH |
residency: TH |
approved | Lives in Thailand | ||
plan.fact.residency.IL |
residency: IL |
approved | Lives in Israel | ||
plan.fact.residency.TR |
residency: TR |
approved | Lives in Turkey | ||
plan.fact.bank_country.template |
bank_country: template |
approved | Banks in {country} | ||
plan.fact.timing.this_week |
timing: this_week |
approved | Needed this week | ||
plan.fact.timing.this_month |
timing: this_month |
approved | Needed this month | ||
plan.fact.timing.within_three_months |
timing: within_three_months |
approved | Within three months | ||
plan.fact.timing.later |
timing: later |
approved | Not for three months or more | ||
plan.fact.timing.no_date |
timing: no_date |
approved | No fixed date | ||
plan.fact.decision_maker.caller |
decision_maker: caller |
approved | Caller decides | ||
plan.fact.decision_maker.colleague |
decision_maker: colleague |
approved | A colleague books or decides | ||
plan.fact.decision_maker.partner_or_family |
decision_maker: partner_or_family |
approved | Decides with family | ||
plan.fact.decision_maker.director_or_owner |
decision_maker: director_or_owner |
approved | Director or owner decides | ||
plan.fact.decision_maker.accountant |
decision_maker: accountant |
approved | Accountant involved | ||
plan.fact.funding_account.own_account |
funding_account: own_account |
approved | Pays from own account | ||
plan.fact.funding_account.company_account |
funding_account: company_account |
approved | Pays from company account | ||
plan.fact.funding_account.third_party |
funding_account: third_party |
approved | Someone else pays | ||
plan.fact.documents_status.complete |
documents_status: complete |
approved | Documents complete | ||
plan.fact.documents_status.proof_of_address_outstanding |
documents_status: proof_of_address_outstanding |
approved | Proof of address to come | ||
plan.fact.documents_status.id_outstanding |
documents_status: id_outstanding |
approved | ID to come | ||
plan.fact.documents_status.company_documents_outstanding |
documents_status: company_documents_outstanding |
approved | Company documents to come | ||
plan.fact.documents_status.source_of_funds_requested |
documents_status: source_of_funds_requested |
approved | Source of funds asked for | ||
plan.fact.current_provider.bank |
current_provider: bank |
approved | Uses their bank now | ||
plan.fact.current_provider.wise |
current_provider: wise |
approved | Uses Wise now | ||
plan.fact.current_provider.revolut |
current_provider: revolut |
approved | Uses Revolut now | ||
plan.fact.current_provider.other_broker |
current_provider: other_broker |
approved | Uses another broker | ||
plan.fact.rate_expectation.has_target_rate |
rate_expectation: has_target_rate |
approved | Has a target rate | ||
plan.fact.rate_expectation.wants_best_rate_now |
rate_expectation: wants_best_rate_now |
approved | Wants the best rate now | ||
plan.fact.rate_expectation.waiting_for_better_rate |
rate_expectation: waiting_for_better_rate |
approved | Waiting for a better rate | ||
plan.fact.rate_expectation.no_view |
rate_expectation: no_view |
approved | No view on the rate |
Onboarding plan templates
Item texts (title, hint, not-needed reason) are approved like a headline; their text_id is plan.template.<purpose>.<item>.title|hint|not_needed.
first_call_after_signup
| item | kind | title | hint | applies | not needed because | points from | done when |
|---|---|---|---|---|---|---|---|
open_with_agenda |
judgement | Why we're calling (approved) | One line on what the call is for; skip it if they're already telling you. | always | open_with_agenda |
its points delivered | |
understand_the_transfer |
fact | What they're sending, and why (approved) | Sign-up gave us a first answer; confirm it and ask only what's missing. | always | ask_about_the_transfer |
the transfer_purpose fact known and the amount fact known and the frequency fact known |
|
check_serviceability_first |
fact | Where they live and bank (approved) | Only needs a question if sign-up left it open or it's somewhere we can't serve. | always | check_serviceability_first |
the residency fact known |
|
confirm_funding_account |
must_say | Whose account pays (approved) | Worth a word if anyone else might pay; partners take money only from an account in the client's own name. | while the funding_account fact is third_party, company_account, or while it is unknown, unless the transfer_purpose fact is salary_or_pension |
Paying from their own account | confirm_funding_account |
said_fund_from_own_account said |
explain_who_holds_the_money |
must_say | Who holds their money (approved) | When they ask whether it's safe, or before they first send money. | once client_asked_about_safety was heard on a client turn |
Kept for the first transfer | explain_who_holds_the_money |
said_who_holds_funds said |
explain_settlement_and_cutoff |
judgement | When the money lands (approved) | Worth it when they have a date to hit. | always | explain_settlement_and_cutoff |
a judgement call: not ticked | |
explain_booking_is_binding |
must_say | A booking is a live trade (approved) | Before they can book on their own, so a practice booking doesn't cost them. | always | They can't book yet | explain_booking_is_binding |
said_booking_is_binding said |
close_the_document_gap |
must_say | Documents in, and when (approved) | Name what's missing and agree a day; the account can't trade until it's in. | unless the documents_status fact is complete (applies while unknown) |
The documents are complete | close_the_document_gap |
said_docs_needed said |
minimum_transfer |
must_say | Amounts under the minimum (approved) | One of their transfers may be under the minimum; better they hear it now. | unless an amount of at least £5,000 equivalent was mentioned | Every amount is above the minimum | none | said_minimum said |
agree_next_step |
fact | A next step with a day (approved) | One action and a time, agreed in their words. | always | agree_next_step |
next_step_agreed persisted |
document_chase
| item | kind | title | hint | applies | not needed because | points from | done when |
|---|---|---|---|---|---|---|---|
open_with_agenda |
judgement | Set the agenda (approved) | The client knows what this call is for and how long it takes. | always | open_with_agenda |
its points delivered | |
close_the_document_gap |
must_say | Documents still needed (approved) | The account cannot trade until the documents are in; agree when they will be uploaded. | always | close_the_document_gap |
said_docs_needed said |
|
understand_the_transfer |
fact | Understand the transfer (approved) | What the transfers are for, the amount and how often, before any explaining. | always | ask_about_the_transfer |
the transfer_purpose fact known and the amount fact known and the frequency fact known |
|
agree_next_step |
fact | Agree the next step (approved) | Leave with one concrete action and a time. | always | agree_next_step |
next_step_agreed persisted |
first_transfer_walkthrough
| item | kind | title | hint | applies | not needed because | points from | done when |
|---|---|---|---|---|---|---|---|
open_with_agenda |
judgement | Set the agenda (approved) | The client knows what this call is for and how long it takes. | always | open_with_agenda |
its points delivered | |
confirm_funding_account |
must_say | Fund from your own account (approved) | The money has to come from an account in the client's own name. | while the funding_account fact is third_party, company_account, or while it is unknown, unless the transfer_purpose fact is salary_or_pension |
Paying from their own account | confirm_funding_account |
said_fund_from_own_account said |
explain_who_holds_the_money |
must_say | Who holds their money (approved) | When they ask whether it's safe, or before they first send money. | always | Kept for the first transfer | explain_who_holds_the_money |
said_who_holds_funds said |
explain_settlement_and_cutoff |
judgement | When the money arrives (approved) | Cut-off and settlement timing for their currencies. | always | explain_settlement_and_cutoff |
a judgement call: not ticked | |
explain_booking_is_binding |
must_say | Booking is binding (approved) | Before the first booking: confirming a trade is a contract. | always | explain_booking_is_binding |
said_booking_is_binding said |
|
minimum_transfer |
must_say | Minimum transfer (approved) | Their amount may be below the minimum transfer. | unless an amount of at least £5,000 equivalent was mentioned | The amount is well above the minimum | none | said_minimum said |
agree_next_step |
fact | First transfer and next step (approved) | Leave with one concrete action and a time. | always | agree_next_step |
next_step_agreed persisted |
other
| item | kind | title | hint | applies | not needed because | points from | done when |
|---|---|---|---|---|---|---|---|
open_with_agenda |
judgement | Set the agenda (approved) | The client knows what this call is for and how long it takes. | always | open_with_agenda |
its points delivered | |
understand_the_transfer |
fact | Understand the transfer (approved) | What the transfers are for, the amount and how often, before any explaining. | always | ask_about_the_transfer |
the transfer_purpose fact known and the amount fact known and the frequency fact known |
|
agree_next_step |
fact | Agree the next step (approved) | Leave with one concrete action and a time. | always | agree_next_step |
next_step_agreed persisted |
Client asks (a client-persisted fact inserts its move as a later item): none.
- Rate pressure title
plan.rate_pressure.title(approved): Rate pressure - Ask first from
qualify_the_quote; concession points fromconcession_terms; headline, hint, points and do-not flags from the situation chosen for the call.
Onboarding checklist
Derived from the plan templates ("checklist": "derived"): each must-say item of a template is one row, with its title and applies; rate pressure closes every list. Change an item in policy/src/plan-<scenario>.json to change its row.
first_call_after_signup
| id | item | applies | ticked by (rep turns only) |
|---|---|---|---|
said_fund_from_own_account |
Whose account pays | while the funding_account fact is third_party, company_account, or while it is unknown, unless the transfer_purpose fact is salary_or_pension |
In recent_transcript, has the rep explained that the client must send the funds by bank transfer from an account in their own name (or the company's name) to the partner's account details shown after booking? |
said_who_holds_funds |
Who holds their money | once client_asked_about_safety was heard on a client turn |
In recent_transcript, has the rep explained that the client's money is held and safeguarded by a regulated payment partner and not by CurrencyTransfer? |
said_booking_is_binding |
A booking is a live trade | always | In recent_transcript, has the rep said that the currency is bought when the trade is booked, that the trade cannot simply be cancelled, or that a loss on reversing it is the client's? |
said_docs_needed |
Documents in, and when | unless the documents_status fact is complete (applies while unknown) |
In recent_transcript, has the rep named a document that is still outstanding, such as ID or proof of address, even one the client mentioned first? |
said_minimum |
Amounts under the minimum | unless an amount of at least £5,000 equivalent was mentioned | In recent_transcript, has the rep mentioned the minimum transfer size? |
rate_pressure_handled |
Rate pushback handled | once rate_pressure_raised is persisted |
In recent_transcript, has the rep answered the client's pushback on the rate without defending or moving the price, either by asking about the competing quote or by holding the price and changing what is being compared? |
document_chase
| id | item | applies | ticked by (rep turns only) |
|---|---|---|---|
said_docs_needed |
Documents still needed | always | In recent_transcript, has the rep named a document that is still outstanding, such as ID or proof of address, even one the client mentioned first? |
rate_pressure_handled |
Rate pushback handled | once rate_pressure_raised is persisted |
In recent_transcript, has the rep answered the client's pushback on the rate without defending or moving the price, either by asking about the competing quote or by holding the price and changing what is being compared? |
first_transfer_walkthrough
| id | item | applies | ticked by (rep turns only) |
|---|---|---|---|
said_fund_from_own_account |
Fund from your own account | while the funding_account fact is third_party, company_account, or while it is unknown, unless the transfer_purpose fact is salary_or_pension |
In recent_transcript, has the rep explained that the client must send the funds by bank transfer from an account in their own name (or the company's name) to the partner's account details shown after booking? |
said_who_holds_funds |
Who holds their money | always | In recent_transcript, has the rep explained that the client's money is held and safeguarded by a regulated payment partner and not by CurrencyTransfer? |
said_booking_is_binding |
Booking is binding | always | In recent_transcript, has the rep said that the currency is bought when the trade is booked, that the trade cannot simply be cancelled, or that a loss on reversing it is the client's? |
said_minimum |
Minimum transfer | unless an amount of at least £5,000 equivalent was mentioned | In recent_transcript, has the rep mentioned the minimum transfer size? |
rate_pressure_handled |
Rate pushback handled | once rate_pressure_raised is persisted |
In recent_transcript, has the rep answered the client's pushback on the rate without defending or moving the price, either by asking about the competing quote or by holding the price and changing what is being compared? |
other
| id | item | applies | ticked by (rep turns only) |
|---|---|---|---|
rate_pressure_handled |
Rate pushback handled | once rate_pressure_raised is persisted |
In recent_transcript, has the rep answered the client's pushback on the rate without defending or moving the price, either by asking about the competing quote or by holding the price and changing what is being compared? |
Customer success
Source: policy/src/playbook-customer-success.json, policy/src/rules-customer-success.json. 13 moves, 21 lines: 0 approved, 21 to review; 0 carry [VERIFY, 0 a concrete fact. 4 retired.
Customer success lines
| text_id | move | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
resolve_the_issue_first.1 |
Deal with the live issue before anything else | draft | Let me look at that right now; give me the amount or the date and I'll pull up the trade. | ||
resolve_the_issue_first.2 |
Deal with the live issue before anything else | draft | I can see exactly where it is: I'll tell you the status and what happens next before we talk about anything else. | ||
resolve_the_issue_first.3 |
Deal with the live issue before anything else | draft | I'll chase the partner as soon as we hang up and message you on the dashboard by three o'clock with an answer. | ||
give_status_with_specifics.3 |
State the status with specifics | draft | The payment is on hold for the supporting document the partner requested; as soon as that's uploaded it goes out. | ||
explain_document_request.1 |
Explain why a document was requested | draft | The partner is regulated and has to evidence the reason for larger or unusual payments; a copy of the invoice is normally all they need. | ||
explain_document_request.2 |
Explain why a document was requested | draft | I'll ask them to tell us up front what they need for this payee, so you're not chased twice. | ||
explain_document_request.3 |
Explain why a document was requested | draft | If you send it to me now I'll pass it straight to the partner and confirm when the payment is released. | ||
review_upcoming_exposure.2 |
Ask about upcoming payments | draft | Are the supplier payments still roughly the same amounts and dates as before? | ||
review_upcoming_exposure.3 |
Ask about upcoming payments | draft | Is there anything on the horizon, a purchase or a larger payment, where the rate really matters? | ||
offer_forward_for_known_future_payment.2 |
Offer a forward for a known future payment | draft | You can draw it down in parts as invoices fall due, so you're not tied to one payment date. | ||
offer_forward_for_known_future_payment.3 |
Offer a forward for a known future payment | draft | It removes the rate risk but it is a commitment; if the rate moves a lot the partner may ask for additional margin. Shall I get you a forward quote to compare? | ||
offer_alert_or_market_order.2 |
Offer a rate alert or market order | draft | What level would you be happy at? I'll set it now and you can change it any time. | ||
add_user_access.3 |
Add a colleague or approval step | draft | Send me their name and email and I'll set it up today. | ||
handle_service_complaint.1 |
Acknowledge a service failure and fix the process | draft | You're right, that shouldn't have happened, and I'm sorry. Here's what I'll change so it doesn't happen again. | ||
handle_service_complaint.2 |
Acknowledge a service failure and fix the process | draft | Tell me exactly what happened and when, and I'll raise it with the partner today. | ||
handle_service_complaint.3 |
Acknowledge a service failure and fix the process | draft | Going forward, I'll be your single point of contact for this; message me on the dashboard and I'll respond the same day. | ||
reengage_dormant_with_a_reason.2 |
Re-engage with a specific reason | draft | The rate has moved quite a bit since your last trade; is that relevant to anything you have coming up? | ||
accept_no_need_gracefully.2 |
Accept there is no current need | draft | Would a rate alert on your usual pair be useful, just so you hear if it moves in your favour? | ||
agree_next_step.1 |
Agree the next step | draft | So: I'll send you a forward quote for the May payment today, and you'll upload the invoice for the pending one. I'll confirm both on the dashboard. | ||
agree_next_step.2 |
Agree the next step | draft | Shall I set the alert at your level now, and call you the day it triggers? | ||
agree_next_step.3 |
Agree the next step | draft | I'll message a summary of what we agreed; anything you want me to add? |
Customer success retired lines
| text_id | move | text | rule broken |
|---|---|---|---|
give_status_with_specifics.1 |
State the status with specifics | Your trade settled with the partner at 11:40 today; the beneficiary's bank usually credits it within the day for euros. | v0 draft with an unverified fact; not approved in the red-pen of 2026-09-25 |
handle_rate_complaint.1 |
Handle a rate complaint | Let's look at the mid-market rate at the moment you booked and the margin you actually paid; then we can compare like for like. | Breaks 'Explain how the spread is built' (do-not): it walks the client through mid-market and the margin they paid. Compare what landed instead (competitor_named.2, qualify_the_quote.4). |
handle_rate_complaint.2 |
Handle a rate complaint | If a competitor quote is genuinely better on the same amount and date, tell me the rate and I'll see what the partners can do. | Invites a discount and a chase: 'tell me the rate and I'll see what the partners can do' breaks 'a concession given for nothing is a permanent price cut' and 'every match sets the new ceiling'. |
handle_rate_complaint.3 |
Handle a rate complaint | Margins vary by pair and amount; for the sizes you're doing I can check whether a different partner on the platform prices tighter. | Breaks 'do not say it is standard for their volume': 'margins vary by pair and amount; for the sizes you're doing' concedes a better price exists for somebody, and it offers to find one. Also a v0 draft with an unverified fact; not approved in the red-pen of 2026-09-25. |
Customer success situations
Deal with the live issue before anything else (resolve_the_issue_first)
Situation cancel_payment_at_own_bank
- Headline
situation.cancel_payment_at_own_bank.headline(approved): My bank won't let me change it. - Hint
situation.cancel_payment_at_own_bank.hint(approved): Only for a payment still with their own bank, not one we hold. - What (when it applies, read by the
fits::cancel_payment_at_own_bankquestion): The client wants to stop, cancel or change a payment they sent from their own bank (a wrong amount, wrong details or a duplicate), and the payment is still with their bank. - Not for: A payment the partner already holds, or a booked trade the client wants to cancel with us; a question about where a payment is; a document request on a payment.
- Applies: always
- Client example (harvest): just it doesn't give an option to change it.
- Client example (harvest): I've made a payment to Denmark and I want to stop it. Is there any chance that can happen?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):resolve_the_issue_first.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
resolve_the_issue_first.h1 |
approved | Give them a call and ask if there's any way you can cancel that transaction. | harvest 4 calls/4 reps; for problems on the client's own bank side |
State the status with specifics (give_status_with_specifics)
Situation where_is_my_money
- Headline
situation.where_is_my_money.headline(approved): Will they have the money today? - Hint
situation.where_is_my_money.hint(approved): Check the trade status first; read only the line that matches it. - What (when it applies, read by the
fits::where_is_my_moneyquestion): The client asks where their payment is, when the recipient will get the money, or whether it will arrive today, about a transfer that is already booked or paid for. - Not for: Choosing a delivery date on the booking screen for a new transfer; a document request holding the payment; the rate; a problem with a payment still at the client's own bank.
- Applies: once
trade_status_knownis persisted (nothing sets it yet, so never in M1) - Client example (harvest): So are they gonna have the money today?
- Client example (harvest): I have just made the transfer few minutes ago, then I got a message from email to contact you to make a location for the transfer.
- Client example (harvest): And then, well, like, how will I know when it lands there?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):give_status_with_specifics.h2 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
give_status_with_specifics.2 |
approved | It's showing as waiting for funds: the partner hasn't received your transfer yet. Can you check the reference you used? | |||||
give_status_with_specifics.h2 |
approved | We've already received your {sell_currency}; the {buy_currency} should be released today as soon as the partner opens. | harvest 4 calls/4 reps; tidied, partner name removed | {sell_currency} from currency_pair (sell leg), shown once known; {buy_currency} from currency_pair (buy leg), shown once known |
|||
give_status_with_specifics.h1 |
approved | The funds have already gone, so the {buy_currency} should be with you very shortly. | harvest 6 calls/2 reps; tidied | {buy_currency} from currency_pair (buy leg), shown once known |
Explain why a document was requested (explain_document_request)
Situation which_statement_needed
- Headline
situation.which_statement_needed.headline(approved): What exactly do you need, a bank statement? - Hint
situation.which_statement_needed.hint(approved): Name exactly what the document must show. - What (when it applies, read by the
fits::which_statement_neededquestion): A bank statement or other proof of where the funds came from has been requested, and the client asks what exactly they need to send (which account, a screenshot, a full statement). - Not for: A request for invoices or a contract for a payment; identity documents for opening the account; a complaint about being asked at all, where the reason needs explaining first.
- Applies: always
- Client example (harvest): Yeah. Okay. And so what do you want? Bank statement.
- Client example (harvest): What what would it have to be? Like, a screenshot of the bank account statement or the the kind of the just a screenshot of the account or or what
- Client example (harvest): you do you want do you want me to ask that from my bank, or you just need an email? Like, what what are you what are you asking for specifically?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):explain_document_request.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
explain_document_request.h1 |
approved | A bank statement for the account the funds are sent from. | harvest 4 calls/3 reps; tidied |
Situation invoice_needed_for_payment
- Headline
situation.invoice_needed_for_payment.headline(approved): What's the problem with my payment? - Hint
situation.invoice_needed_for_payment.hint(approved): Name the payee from the trade on your screen. - What (when it applies, read by the
fits::invoice_needed_for_paymentquestion): The rep is calling, or the client has heard, about a payment held until an invoice or contract for the payee is provided, and the client asks what the problem is or what is needed, or says what they have done so far to get it. - Not for: A request for a bank statement or proof of funds; a payment delayed for another reason.
- Applies: always
- Client example (harvest): Oh, you're calling from currency yes. What is the problem?
- Client example (harvest): I after you emailed me, I messaged the electrician and said, that you were asking for this extra information and could he provide it.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):explain_document_request.h2 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
explain_document_request.h2 |
approved | We just require the invoices for the payments going to {payee}. | harvest 4 calls/1 rep; tidied | rep fills {payee} |
Ask about upcoming payments (review_upcoming_exposure)
Situation upcoming_payments_unknown
- Headline
situation.upcoming_payments_unknown.headline(approved): That's all sorted now, thanks. - Hint
situation.upcoming_payments_unknown.hint(approved): Ask once the live issue is dealt with. - What (when it applies, read by the
fits::upcoming_payments_unknownquestion): The client's issue, if there was one, is dealt with and the client is wrapping up or thanking the rep, and the call has not yet covered what payments abroad they have coming up (amounts or dates). - Not for: A problem that is still open; a client who has already described their upcoming payments; a client who has said they have nothing planned.
- Applies: always
- Client example (drafted): Great, that's sorted then. Thanks for looking into it.
- Client example (drafted): No, that was the only thing I was calling about.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):review_upcoming_exposure.1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
review_upcoming_exposure.1 |
approved | What do you have coming up over the next few months in terms of payments abroad? |
Situation payment_mentioned_no_amount
- Headline
situation.payment_mentioned_no_amount.headline(approved): I'll be doing more of these soon. - Hint
situation.payment_mentioned_no_amount.hint(approved): A rough figure is enough. - What (when it applies, read by the
fits::payment_mentioned_no_amountquestion): The client mentions a payment or transfers they will make, soon or over the coming weeks or months (including making them more often), but has not said roughly how much. - Not for: A client who has already given the amount; a problem with a payment already in flight.
- Applies: always
- Client example (harvest): I just didn't wanna screw things up the fur I'm gonna be doing it probably a little more frequently over the next few months.
- Client example (harvest): So I I need to set up another payment transaction, don't I, from my
- Client example (harvest): Yeah. So maybe if you could is it could you just email those details and the right the correct reference across to me?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):review_upcoming_exposure.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
review_upcoming_exposure.h1 |
approved | How much, roughly, do you need to do? | harvest 2 calls/1 rep; tidied |
Offer a forward for a known future payment (offer_forward_for_known_future_payment)
Also shows concession_terms (listed under Handle a rate complaint).
Situation future_payment_rate_worry
- Headline
situation.future_payment_rate_worry.headline(approved): What if the rate moves before I pay? - Hint
situation.future_payment_rate_worry.hint(approved): Only for a payment weeks or months away, not days. - What (when it applies, read by the
fits::future_payment_rate_worryquestion): The client has a specific payment due weeks or months ahead, with a rough amount and date, and says they are worried the rate will move before then or asks whether they can fix today's rate. - Not for: A payment due within days; a client with no specific future payment; a client who has already been told how a forward works and declined.
- Applies: always
- Client example (drafted): The final payment to the builder is due in about four months. What if the rate drops before then?
- Client example (drafted): Is there any way to fix today's rate for the payment I have to make in the autumn?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):offer_forward_for_known_future_payment.1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
offer_forward_for_known_future_payment.1 |
approved | For a payment that far out you can fix today's rate with a forward: a deposit at booking, typically ten percent, and the balance at the agreed date. |
Situation putting_off_booking
- Headline
situation.putting_off_booking.headline(approved): I'll check it again tomorrow. - Hint
situation.putting_off_booking.hint(approved): Ask once; if they want to wait, leave it with them. - What (when it applies, read by the
fits::putting_off_bookingquestion): The client had been about to book or fix a rate today, and says they will leave it until later (tomorrow, after the weekend) or spread it over the coming days. - Not for: A client waiting for a better rate, who needs an alert instead; a client who has decided not to transfer at all; a client who has just booked.
- Applies: always
- Client example (harvest): I'm not really bothered about that tonight because it's it's getting a bit late here. So I'll check it tomorrow.
- Client example (harvest): I've got to ring, like, for the next four nights, it be Tuesday, Wednesday, Thursday, Friday, I'll do a £100,000 a night, but then Monday over there is a bank holiday, ain't it?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):offer_forward_for_known_future_payment.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
offer_forward_for_known_future_payment.h1 |
approved | Do you still want to lock the rate in today? | harvest 1 call/1 rep; tidied |
Offer a rate alert or market order (offer_alert_or_market_order)
Situation waiting_for_target_rate
- Headline
situation.waiting_for_target_rate.headline(approved): I'm waiting for the rate to go up. - Hint
situation.waiting_for_target_rate.hint(approved): Never while they are pushing back on our rate. - What (when it applies, read by the
fits::waiting_for_target_ratequestion): The client says they are waiting for the exchange rate to reach a level before booking, that the rate has been bad so they are holding off, or asks about rate alerts or market orders. - Not for: A rate complaint or a request for a better price (a rate concern is open: never offer an alert then); a client with a payment due within days; a client who already has an alert at the level they want.
- Applies: always
- Client example (harvest): I don't wanna draw it down until, really, until that exchange rate goes up.
- Client example (harvest): It's just, obviously, exchange rate's pretty been pretty bad. So I've been trying
- Client example (harvest): Okay. Okay. So the target rate is the rate that I want to get that
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):offer_alert_or_market_order.1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
offer_alert_or_market_order.h1 |
approved | Are you looking at setting a rate alert? | harvest 6 calls/4 reps; tidied | ||||
offer_alert_or_market_order.1 |
approved | Rather than watching the screen, set a bookable alert at your target and it books or notifies you the moment it's hit. | |||||
offer_alert_or_market_order.3 |
approved | If you want it hands-off, a market order executes automatically when the rate is reached. |
Set up recurring or batch payments (set_up_recurring_or_batch)
Situation same_payments_every_month
- Headline
situation.same_payments_every_month.headline(approved): It's the same payment every month. - Hint
situation.same_payments_every_month.hint(approved): Only for payments that repeat to the same people. - What (when it applies, read by the
fits::same_payments_every_monthquestion): The client pays the same person or account on a regular schedule (monthly rent, salaries, family support) and books each payment separately. - Not for: A one-off transfer; several different payments made at the same time; a client who already uses saved beneficiaries or recurring alerts.
- Applies: always
- Client example (drafted): I pay my mum and the landlord every month and type the details in each time.
- Client example (drafted): Salaries go out on the same date every month, and I do each one by hand.
- Client example (harvest): Yeah. It'll be a monthly sort of thing or, you know, as I build up some cash.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):set_up_recurring_or_batch.1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
set_up_recurring_or_batch.1 |
approved | Your regular beneficiaries are saved, so each month it's a quote and two clicks; you don't re-enter anything. | |||||
set_up_recurring_or_batch.3 |
approved | Would it help to set a recurring alert so you're prompted before each payroll date? |
Situation several_payments_at_once
- Headline
situation.several_payments_at_once.headline(approved): I pay several suppliers at once. - Hint
situation.several_payments_at_once.hint(approved): Only when they pay several people at the same time. - What (when it applies, read by the
fits::several_payments_at_oncequestion): The client pays several different people or suppliers at the same time and books each payment one by one. - Not for: One regular payment to the same person; a one-off transfer; a client who already uploads batches.
- Applies: always
- Client example (drafted): I've got eight supplier invoices to pay this week. Do I have to book them one by one?
- Client example (drafted): Every Friday we send payments to all our suppliers, each one separately.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):set_up_recurring_or_batch.2 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
set_up_recurring_or_batch.2 |
approved | For the supplier run you can upload all the payments as one batch against a single trade. |
Add a colleague or approval step (add_user_access)
Situation someone_else_books_payments
- Headline
situation.someone_else_books_payments.headline(approved): My bookkeeper usually does the payments. - Hint
situation.someone_else_books_payments.hint(approved): Offer it; don't push extra users. - What (when it applies, read by the
fits::someone_else_books_paymentsquestion): The client mentions a colleague, bookkeeper, accountant or partner who books, prepares or needs to see their payments, or says they share their login. - Not for: A client who wants a second person to approve payments before they go out; a sole user with no one else involved.
- Applies: always
- Client example (drafted): My bookkeeper normally does the payments. Can she just use my login?
- Client example (drafted): My business partner needs to be able to book them too.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):add_user_access.1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
add_user_access.h1 |
approved | I can add other people on there, if that would help. | harvest 1 call/1 rep; tidied | ||||
add_user_access.1 |
approved | You can add your bookkeeper with their own login and set exactly what they can do: quote, book, or add beneficiaries. |
Situation wants_a_second_approver
- Headline
situation.wants_a_second_approver.headline(approved): Can someone else check payments before they go? - Hint
situation.wants_a_second_approver.hint(approved): Only when they want a check before payments go out. - What (when it applies, read by the
fits::wants_a_second_approverquestion): The client wants someone else to check or approve payments or new beneficiaries before they go out. - Not for: A colleague who only needs their own login to book or view payments.
- Applies: always
- Client example (drafted): I'd like someone to check the payments before they actually go out.
- Client example (drafted): Can we set it so two of us have to approve a new payee?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):add_user_access.2 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
add_user_access.2 |
approved | If you'd like a second pair of eyes, payments and new beneficiaries can require approval from a second user before they go out. |
Handle a rate complaint (handle_rate_complaint)
Situation qualify_the_quote
- Headline
situation.qualify_the_quote.headline(approved): Qualify the quote before you respond - Hint
situation.qualify_the_quote.hint(approved): Ask calmly, in order. You are not challenging them, you are finding out what they are actually holding. - What (when it applies, read by the
fits::qualify_the_quotequestion): The client cites a rate or quote from another provider or their bank (a number, or 'they give me a better rate'), and the rep has not yet asked when they got it, whether it was a live quote on their amount, what the fees on top were, or what actually landed. - Not for: A request for a better rate with no competing number ('Can you do better than that?'); a comparison with the mid-market rate on Google or a similar site; the four questions already asked.
- Applies: always
- Client example (ct-rate-objection.pdf): Company X gives me a better rate.
- Client example (drafted): Another broker quoted me a better rate on the same amount last week.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):qualify_the_quote.4 - Do-not flags:
rep_rubbished_competitor
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
qualify_the_quote.1 |
approved | verbatim | When did you get that rate? | ||||
qualify_the_quote.2 |
approved | verbatim | Was that a live quote on your amount, or a headline off a website? | ||||
qualify_the_quote.3 |
approved | verbatim | What were the fees on top, including the receiving bank's cut? | ||||
qualify_the_quote.4 |
approved | verbatim | What actually landed in the beneficiary account last time, against what you were quoted? |
Situation no_quote_in_hand
- Headline
situation.no_quote_in_hand.headline(approved): Can you do better than that? - Hint
situation.no_quote_in_hand.hint(approved): Three beats, in order. Keep each one short: length reads as negotiation. - What (when it applies, read by the
fits::no_quote_in_handquestion): The client asks for a better rate or price ('Can you do better than that?', 'Is that the best you can do?') without naming another provider's rate, a bank quote, or the rate on Google. - Not for: A client who names a competitor's rate, cites the mid-market rate, or says their bank matched: if a real comparator comes back, you are no longer in this objection.
- Applies: always
- Client example (ct-rate-objection.pdf): Can you do better than that?
- Client example (drafted): Is that really the best rate you can give me?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):no_quote_in_hand.2 - Do-not flags:
rep_improved_rate_unasked,rep_explained_spread,rep_said_standard_for_volume - Do not: Improve the rate to close a question that was not about the rate.
- Do not: Do not explain the pricing, and do not say it is standard for their volume: that concedes a better price exists for somebody, which is the door you were trying to shut.
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
no_quote_in_hand.1 |
approved | verbatim | Better than what? | ||||
no_quote_in_hand.2 |
approved | verbatim | No. That's the price. | ||||
no_quote_in_hand.3 |
approved | verbatim | And it's live, so it's moving while we talk. Do you want it, or shall I requote in ten? |
Situation competitor_named
- Headline
situation.competitor_named.headline(approved): Company X gives me a better rate. - Hint
situation.competitor_named.hint(approved): Run the four qualifying questions before you say anything else. Move the comparison from one quote to the last three trades. - What (when it applies, read by the
fits::competitor_namedquestion): The client says another provider (a named company, a broker, their other platform) gives or offered them a better rate, usually with a number. - Not for: The client's own bank matching us after hearing from us; a number off Google or a similar site; a request for a better rate with no comparator.
- Applies: always
- Client example (ct-rate-objection.pdf): Company X gives me a better rate.
- Client example (drafted): My other broker gave me a better rate than this on my last transfer.
- Ask the qualifying questions first (
qualify_first): yes - Core line (
core_text_id, said = handled):competitor_named.2 - Do-not flags:
rep_rubbished_competitor - Do not: Suggest they are wrong or lying, and do not rubbish the competitor by name. Both make you sound like the expensive option defending itself.
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
competitor_named.1 |
approved | verbatim | They probably do on the first one. What matters is what you're getting on trade twenty, when nobody's watching. | ||||
competitor_named.2 |
approved | verbatim | Pull your last three confirmations from them and let's compare what landed, not what was quoted. |
Situation serial_shopper
- Headline
situation.serial_shopper.headline(approved): I'll just check what the others are doing. - Hint
situation.serial_shopper.hint(approved): Price them for the time they cost, or let them go. Winning them at the floor is worse than losing them. - What (when it applies, read by the
fits::serial_shopperquestion): The client says they will check other brokers or providers before booking, or that they compare several providers on every trade ('I'll just check what the others are doing'). - Not for: A client with one competing quote already in hand; a client checking a provider for the first time who has not said they shop around.
- Applies: always
- Client example (ct-rate-objection.pdf): I'll just check what the others are doing.
- Client example (harvest): I've been just jumping between the two systems to just see which is giving me the best rates.
- Client example (harvest): I'll log in periodically just to test you out and see if you're any better
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):serial_shopper.1 - Do-not flags:
rep_improved_rate_unasked - Do not: Chase them down on each trade. Every match sets the new ceiling and the next call starts below it.
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
serial_shopper.1 |
approved | verbatim | Happy to quote you every time. If you want a better number without the ring-around, give me the flow for the quarter and I'll price it properly. |
Situation mid_market_comparison
- Headline
situation.mid_market_comparison.headline(approved): Why am I getting less than Google says? - Hint
situation.mid_market_comparison.hint(approved): Correct it once, briefly, and move to a comparison that can actually be made. If you argue the gap you are defending your margin on a call that was never about your margin. - What (when it applies, read by the
fits::mid_market_comparisonquestion): The client compares our rate with the mid-market or interbank rate they saw on Google, XE or a similar site, and asks why ours is lower or different. - Not for: A rate quoted by a bank or another provider.
- Applies: always
- Client example (ct-rate-objection.pdf): Google says 1.2740. Why am I getting 1.2690?
- Client example (harvest): the currency conversion is the same as the one that Google depicts, but normally it should be half the one that Google depicts.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):mid_market_comparison.2 - Do-not flags:
rep_explained_spread - Do not: Explain how the spread is built. The moment you break down your own pricing, the call is about what you make rather than what they get.
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
mid_market_comparison.1 |
approved | verbatim | That's the mid-market rate. It's the midpoint between buying and selling, so it's a reference number rather than a price. Nobody trades at it, banks included. | ||||
mid_market_comparison.2 |
approved | verbatim | The number worth comparing is what actually lands from us against what actually lands from your bank, same day, same amount. |
Situation bank_matched
- Headline
situation.bank_matched.headline(approved): I spoke to my bank; they matched you. - Hint
situation.bank_matched.hint(approved): Do not argue the number. Test whether it survives. - What (when it applies, read by the
fits::bank_matchedquestion): The client says their bank has matched or beaten our rate since they started talking to us. - Not for: A bank quote the client had before talking to us, or another provider's rate.
- Applies: always
- Client example (ct-rate-objection.pdf): I spoke to my bank; they matched you.
- Client example (drafted): My bank came back and said they'll do the same rate as you.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):bank_matched.1 - Do-not flags:
rep_went_under_bank - Do not: Go under them. A bank defending one account is not pricing to make money on it, and you cannot win that on price. Win it on the six months after they stop paying attention.
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
bank_matched.1 |
approved | verbatim | Good. That's the first time they've sharpened up for you. Ask them to hold it in writing for the next twelve months and see what comes back. | ||||
bank_matched.2 |
approved | verbatim | Worth looking at what they were giving you before we started quoting. That's their real price, the one that applies when nobody's pushing. |
Situation concession_terms
- Headline
situation.concession_terms.headline(approved): If you do move on price - Hint
situation.concession_terms.hint(approved): Get something on the call, not vaguely later. - What (when it applies, read by the
fits::concession_termsquestion): The rep is about to move on price or has just offered a better rate, or the client asks what it would take to get a better rate (more volume, moving other payments, a forward, an introduction). - Not for: Any of the five rate objections answered without moving on price.
- Applies: always
- Client example (drafted): What would it take for you to sharpen that rate?
- Client example (drafted): If I moved all my payments over to you, could you do better?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):concession_terms.5 - Do-not flags:
rep_improved_rate_unasked
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
concession_terms.1 |
approved | verbatim | Volume. A monthly or quarterly commitment that puts them in the band you are pricing them at. | ||||
concession_terms.2 |
approved | verbatim | Consolidation. The corridors they currently run elsewhere come to you. | ||||
concession_terms.3 |
approved | verbatim | Forward cover. The next tranche booked forward rather than left to shop. | ||||
concession_terms.4 |
approved | verbatim | Introduction. The finance contact at the group company, the supplier, the sister office. | ||||
concession_terms.5 |
approved | verbatim | The rate is one number on one day. What you're paying for is knowing what it'll be worth when it lands and when it'll get there. If you press send and then spend two days chasing, the half pip you saved cost you more than it was worth. |
Acknowledge a service failure and fix the process (handle_service_complaint)
Situation calling_back_about_a_complaint
- Headline
situation.calling_back_about_a_complaint.headline(approved): Is this about my email? - Hint
situation.calling_back_about_a_complaint.hint(approved): Open with it, then let them tell you what went wrong. - What (when it applies, read by the
fits::calling_back_about_a_complaintquestion): The rep is calling the client back about a complaint the client sent by email (usually about how long a payment took), and the call is at the greeting or the client has just asked what the call is about. - Not for: A complaint the rep has already acknowledged; a client raising a new complaint for the first time on this call; a routine call with no complaint behind it.
- Applies: always
- Client example (harvest): Good and you.
- Client example (drafted): Hi, yes. Is this about the email I sent yesterday?
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):handle_service_complaint.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
handle_service_complaint.h1 |
approved | I just got your email and wanted to give you a quick call to cover any concerns; I understand you're not pleased with how long it took. | harvest 1 call/1 rep; tidied |
Re-engage with a specific reason (reengage_dormant_with_a_reason)
Situation not_traded_for_a_while
- Headline
situation.not_traded_for_a_while.headline(approved): I haven't used it in a while. - Hint
situation.not_traded_for_a_while.hint(approved): Ask why they stopped; don't pitch yet. - What (when it applies, read by the
fits::not_traded_for_a_whilequestion): The client has not traded for a long time, has no problem to report, and has not said why they stopped. - Not for: An active client; a client who has said they have nothing planned; a client reporting a problem.
- Applies: always
- Client example (drafted): To be honest, I haven't used the account since last year.
- Client example (drafted): We just stopped using it after the last transfer, really.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):reengage_dormant_with_a_reason.3 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
reengage_dormant_with_a_reason.1 |
approved | You last transferred in {month}; has the need gone away, or is something waiting on the rate? | {month} from last_transfer_month, shown once known |
||||
reengage_dormant_with_a_reason.3 |
approved | Is there anything about the platform or the process that put you off using it again? |
Accept there is no current need (accept_no_need_gracefully)
Situation no_transfers_planned
- Headline
situation.no_transfers_planned.headline(approved): Nothing planned at the moment. - Hint
situation.no_transfers_planned.hint(approved): Accept it and end warmly; no pitch. - What (when it applies, read by the
fits::no_transfers_plannedquestion): The client says clearly that they have no transfers planned, or no need for the service, at the moment. - Not for: A client who mentions any future payment, even vaguely; a client who has not yet been asked about upcoming payments.
- Applies: always
- Client example (drafted): We don't have anything planned at the moment.
- Client example (drafted): Honestly, I don't need to send anything for now.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):accept_no_need_gracefully.1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
accept_no_need_gracefully.1 |
approved | Understood. Your account stays open at no cost, and if anything comes up you can book online or call me. | |||||
accept_no_need_gracefully.3 |
approved | Thanks for your time; I'll leave you alone until you need us. |
Agree the next step (agree_next_step)
Situation ready_to_book_after_a_fix
- Headline
situation.ready_to_book_after_a_fix.headline(approved): I'll log on and do the trade now. - Hint
situation.ready_to_book_after_a_fix.hint(approved): Only once the thing that blocked the booking is fixed. - What (when it applies, read by the
fits::ready_to_book_after_a_fixquestion): Something that stopped the client booking (their login, two-factor authentication, account activation, or funds arriving) has just been fixed on this call, and the client says they will log in or book now. - Not for: A client asking which delivery date to choose on the booking screen; a problem that is not fixed yet; a client asking where a payment they already booked is.
- Applies: always
- Client example (harvest): But what I'm gonna do now is just log on and then try to reset up the two factor authentication and do the trade that I wanted to do.
- Client example (harvest): Well, I'll try it first of all, but I'll have to call you back if I fail miserably.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):agree_next_step.h1 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
agree_next_step.h1 |
approved | You should be able to book the trade now. | harvest 3 calls/3 reps |
Situation choosing_a_delivery_date
- Headline
situation.choosing_a_delivery_date.headline(approved): Which delivery date do I pick? - Hint
situation.choosing_a_delivery_date.hint(approved): Only when they are on the booking screen asking about the date. - What (when it applies, read by the
fits::choosing_a_delivery_datequestion): The client asks about the delivery date of a transfer they are booking or about to book: which date to choose, whether the date makes a difference, why a date is not available, or whether it can go today. - Not for: Anything that is not about the date field while booking: a login or two-factor problem, where a booked payment is, a document request, the rate, or wrapping up once an issue is fixed. A client whose issue has nothing to do with delivery dates never gets this line.
- Applies: always
- Client example (harvest): Oh, okay. Okay. So I have to request for Monday. Right?
- Client example (harvest): Delivery date. Does it make a difference?
- Client example (harvest): to be quick. Please remind me how does it start? That's in the website.
- Ask the qualifying questions first (
qualify_first): no - Core line (
core_text_id, said = handled):agree_next_step.h2 - Do-not flags: none
| text_id | status | locked | text | VERIFY | CONCRETE FACT | note | placeholders |
|---|---|---|---|---|---|---|---|
agree_next_step.h2 |
approved | You should have the delivery date; just choose the next day that's available. | harvest 3 calls/2 reps; tidied |
Customer success move headlines
| text_id | move | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
headline.resolve_the_issue_first |
Deal with the live issue before anything else | approved | Client has a problem with a payment | ||
headline.give_status_with_specifics |
State the status with specifics | approved | Client asks where their money is | ||
headline.explain_document_request |
Explain why a document was requested | approved | Client is annoyed by a document request | ||
headline.review_upcoming_exposure |
Ask about upcoming payments | approved | Upcoming payments are not known yet | ||
headline.offer_forward_for_known_future_payment |
Offer a forward for a known future payment | approved | Client has a big payment coming up | ||
headline.offer_alert_or_market_order |
Offer a rate alert or market order | approved | Client wants to wait for a better rate | ||
headline.set_up_recurring_or_batch |
Set up recurring or batch payments | approved | Client sends the same payments one by one | ||
headline.add_user_access |
Add a colleague or approval step | approved | A colleague also needs to book payments | ||
headline.handle_rate_complaint |
Handle a rate complaint | approved | Client says the rate has got worse | ||
headline.handle_service_complaint |
Acknowledge a service failure and fix the process | approved | Client is unhappy with how we handled it | ||
headline.reengage_dormant_with_a_reason |
Re-engage with a specific reason | approved | Client hasn't traded in a while | ||
headline.accept_no_need_gracefully |
Accept there is no current need | approved | Client has no transfers planned | ||
headline.agree_next_step |
Agree the next step | approved | Client is ready for the next step |
Customer success concern headlines
| text_id | concern | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
concern.rate.headline |
rate |
approved | Client thinks our rate is too high | ||
concern.service_issue.headline |
service_issue |
approved | Client has a problem with a payment | ||
concern.settlement_delay.headline |
settlement_delay |
approved | Client's payment hasn't arrived | ||
concern.fees.headline |
fees |
approved | Client is comparing our fees with their bank | ||
concern.alternative_provider.headline |
alternative_provider |
approved | Client is looking at another provider | ||
concern.no_need_now.headline |
no_need_now |
approved | Client has nothing to send right now | ||
concern.trust.headline |
trust |
approved | Client has doubts about us | ||
concern.money.headline |
money |
approved | Client has a worry about cost | ||
concern.process.headline |
process |
approved | Client has a worry about the process |
Customer success caution notes
| text_id | risk rule | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
caution.rep_made_guarantee |
Rep made a guarantee | approved | That sounded like a guarantee. | ||
caution.rep_made_rate_prediction |
Rep predicted the rate | approved | That sounded like a rate prediction. | ||
caution.rep_improved_rate_unasked |
Rep moved on price for nothing | approved | That moved the price for nothing. Get something on the call for it. | ||
caution.rep_explained_spread |
Rep explained the spread | approved | That explained our margin. Compare what lands instead. | ||
caution.rep_said_standard_for_volume |
Rep said the rate is standard for their volume | approved | 'Standard for your volume' says somebody gets a better price. | ||
caution.rep_rubbished_competitor |
Rep ran down a competitor or the client's quote | approved | Running them down makes us sound like the expensive option. | ||
caution.rep_went_under_bank |
Rep offered to go under the bank | approved | Don't go under the bank. Test whether their price survives. | ||
caution.rep_said_documents_not_shared |
Rep said the documents are not shared | approved | The partner sees their KYC documents. Say who does. |
Customer success call purposes
| text_id | purpose | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
plan.purpose.transfer_issue |
transfer_issue |
approved | Transfer issue | ||
plan.purpose.status_update |
status_update |
approved | Status update | ||
plan.purpose.rate_or_hedging |
rate_or_hedging |
approved | Rate or hedging | ||
plan.purpose.recurring_or_batch_setup |
recurring_or_batch_setup |
approved | Recurring or batch payments | ||
plan.purpose.dormant_reengagement |
dormant_reengagement |
approved | Checking in after a quiet spell | ||
plan.purpose.other |
other |
approved | Other |
Customer success client fact labels
| text_id | slot: value | status | text | VERIFY | CONCRETE FACT |
|---|---|---|---|---|---|
plan.fact.client_type.personal |
client_type: personal |
approved | Personal client | ||
plan.fact.client_type.corporate |
client_type: corporate |
approved | Corporate client | ||
plan.fact.amount.template |
amount: template |
approved | About {amount} {currency} | ||
plan.fact.frequency.one_off |
frequency: one_off |
approved | One-off transfer | ||
plan.fact.frequency.weekly |
frequency: weekly |
approved | Weekly transfers | ||
plan.fact.frequency.monthly |
frequency: monthly |
approved | Monthly transfers | ||
plan.fact.frequency.quarterly |
frequency: quarterly |
approved | Quarterly transfers | ||
plan.fact.frequency.irregular |
frequency: irregular |
approved | Transfers now and then | ||
plan.fact.currency_pair.template |
currency_pair: template |
approved | {sell} to {buy} | ||
plan.fact.transfer_purpose.property |
transfer_purpose: property |
approved | For a property | ||
plan.fact.transfer_purpose.family_support |
transfer_purpose: family_support |
approved | Supporting family | ||
plan.fact.transfer_purpose.salary_or_pension |
transfer_purpose: salary_or_pension |
approved | Salary or pension | ||
plan.fact.transfer_purpose.supplier_payment |
transfer_purpose: supplier_payment |
approved | Paying suppliers | ||
plan.fact.transfer_purpose.school_fees |
transfer_purpose: school_fees |
approved | School fees | ||
plan.fact.transfer_purpose.investment |
transfer_purpose: investment |
approved | Investment | ||
plan.fact.transfer_purpose.other |
transfer_purpose: other |
approved | Another purpose | ||
plan.fact.residency.GB |
residency: GB |
approved | Lives in the UK | ||
plan.fact.residency.IE |
residency: IE |
approved | Lives in Ireland | ||
plan.fact.residency.FR |
residency: FR |
approved | Lives in France | ||
plan.fact.residency.ES |
residency: ES |
approved | Lives in Spain | ||
plan.fact.residency.PT |
residency: PT |
approved | Lives in Portugal | ||
plan.fact.residency.DE |
residency: DE |
approved | Lives in Germany | ||
plan.fact.residency.IT |
residency: IT |
approved | Lives in Italy | ||
plan.fact.residency.NL |
residency: NL |
approved | Lives in the Netherlands | ||
plan.fact.residency.BE |
residency: BE |
approved | Lives in Belgium | ||
plan.fact.residency.CH |
residency: CH |
approved | Lives in Switzerland | ||
plan.fact.residency.AT |
residency: AT |
approved | Lives in Austria | ||
plan.fact.residency.SE |
residency: SE |
approved | Lives in Sweden | ||
plan.fact.residency.NO |
residency: NO |
approved | Lives in Norway | ||
plan.fact.residency.DK |
residency: DK |
approved | Lives in Denmark | ||
plan.fact.residency.PL |
residency: PL |
approved | Lives in Poland | ||
plan.fact.residency.GR |
residency: GR |
approved | Lives in Greece | ||
plan.fact.residency.CY |
residency: CY |
approved | Lives in Cyprus | ||
plan.fact.residency.MT |
residency: MT |
approved | Lives in Malta | ||
plan.fact.residency.US |
residency: US |
approved | Lives in the US | ||
plan.fact.residency.CA |
residency: CA |
approved | Lives in Canada | ||
plan.fact.residency.MX |
residency: MX |
approved | Lives in Mexico | ||
plan.fact.residency.AU |
residency: AU |
approved | Lives in Australia | ||
plan.fact.residency.NZ |
residency: NZ |
approved | Lives in New Zealand | ||
plan.fact.residency.SA |
residency: SA |
approved | Lives in Saudi Arabia | ||
plan.fact.residency.AE |
residency: AE |
approved | Lives in the UAE | ||
plan.fact.residency.QA |
residency: QA |
approved | Lives in Qatar | ||
plan.fact.residency.ZA |
residency: ZA |
approved | Lives in South Africa | ||
plan.fact.residency.IN |
residency: IN |
approved | Lives in India | ||
plan.fact.residency.CN |
residency: CN |
approved | Lives in China | ||
plan.fact.residency.HK |
residency: HK |
approved | Lives in Hong Kong | ||
plan.fact.residency.SG |
residency: SG |
approved | Lives in Singapore | ||
plan.fact.residency.JP |
residency: JP |
approved | Lives in Japan | ||
plan.fact.residency.TH |
residency: TH |
approved | Lives in Thailand | ||
plan.fact.residency.IL |
residency: IL |
approved | Lives in Israel | ||
plan.fact.residency.TR |
residency: TR |
approved | Lives in Turkey | ||
plan.fact.timing.this_week |
timing: this_week |
approved | Needed this week | ||
plan.fact.timing.this_month |
timing: this_month |
approved | Needed this month | ||
plan.fact.timing.within_three_months |
timing: within_three_months |
approved | Within three months | ||
plan.fact.timing.later |
timing: later |
approved | Not for three months or more | ||
plan.fact.timing.no_date |
timing: no_date |
approved | No fixed date | ||
plan.fact.decision_maker.caller |
decision_maker: caller |
approved | Caller decides | ||
plan.fact.decision_maker.colleague |
decision_maker: colleague |
approved | A colleague books or decides | ||
plan.fact.decision_maker.partner_or_family |
decision_maker: partner_or_family |
approved | Decides with family | ||
plan.fact.decision_maker.director_or_owner |
decision_maker: director_or_owner |
approved | Director or owner decides | ||
plan.fact.decision_maker.accountant |
decision_maker: accountant |
approved | Accountant involved | ||
plan.fact.funding_account.own_account |
funding_account: own_account |
approved | Pays from own account | ||
plan.fact.funding_account.company_account |
funding_account: company_account |
approved | Pays from company account | ||
plan.fact.funding_account.third_party |
funding_account: third_party |
approved | Someone else pays | ||
plan.fact.documents_status.complete |
documents_status: complete |
approved | Documents complete | ||
plan.fact.documents_status.proof_of_address_outstanding |
documents_status: proof_of_address_outstanding |
approved | Proof of address to come | ||
plan.fact.documents_status.id_outstanding |
documents_status: id_outstanding |
approved | ID to come | ||
plan.fact.documents_status.company_documents_outstanding |
documents_status: company_documents_outstanding |
approved | Company documents to come | ||
plan.fact.documents_status.source_of_funds_requested |
documents_status: source_of_funds_requested |
approved | Source of funds asked for | ||
plan.fact.current_provider.bank |
current_provider: bank |
approved | Uses their bank now | ||
plan.fact.current_provider.wise |
current_provider: wise |
approved | Uses Wise now | ||
plan.fact.current_provider.revolut |
current_provider: revolut |
approved | Uses Revolut now | ||
plan.fact.current_provider.other_broker |
current_provider: other_broker |
approved | Uses another broker | ||
plan.fact.rate_expectation.has_target_rate |
rate_expectation: has_target_rate |
approved | Has a target rate | ||
plan.fact.rate_expectation.wants_best_rate_now |
rate_expectation: wants_best_rate_now |
approved | Wants the best rate now | ||
plan.fact.rate_expectation.waiting_for_better_rate |
rate_expectation: waiting_for_better_rate |
approved | Waiting for a better rate | ||
plan.fact.rate_expectation.no_view |
rate_expectation: no_view |
approved | No view on the rate |
Customer success plan templates
Item texts (title, hint, not-needed reason) are approved like a headline; their text_id is plan.template.<purpose>.<item>.title|hint|not_needed.
transfer_issue
| item | kind | title | hint | applies | not needed because | points from | done when |
|---|---|---|---|---|---|---|---|
confirm_caller |
fact | Confirm the caller is on the account (approved) | Know who is calling and whether they can act on the account. | always | none | the decision_maker fact known |
|
resolve_the_issue_first |
must_say | Resolve the issue (approved) | Find the cause and own it before anything else. | always | resolve_the_issue_first |
issue_resolved_or_owned said |
|
give_status_with_specifics |
must_say | Status with specifics (approved) | Amounts, references and what happens next, in the client's words. | always | give_status_with_specifics |
rep_checked_status_with_specifics said |
|
review_upcoming_exposure |
fact | Upcoming payments (approved) | Learn what else is coming so the right tool can be offered. | always | review_upcoming_exposure |
upcoming_payment_known persisted |
|
tools_that_fit |
judgement | Tools that fit (approved) | An alert, a forward or a recurring payment, whichever fits what is coming up. | always | offer_alert_or_market_order |
its points delivered | |
explain_document_request |
judgement | Explain the document request (approved) | Why the partner asked for a document, and what it needs. | unless the documents_status fact is complete (applies while unknown) |
No document was asked for | explain_document_request |
its points delivered |
agree_next_step |
fact | Agree the next step (approved) | One concrete action, confirmed on the dashboard. | always | agree_next_step |
next_step_agreed persisted |
status_update
| item | kind | title | hint | applies | not needed because | points from | done when |
|---|---|---|---|---|---|---|---|
confirm_caller |
fact | Confirm the caller is on the account (approved) | Know who is calling and whether they can act on the account. | always | none | the decision_maker fact known |
|
give_status_with_specifics |
must_say | Status with specifics (approved) | Amounts, references and what happens next, in the client's words. | always | give_status_with_specifics |
rep_checked_status_with_specifics said |
|
review_upcoming_exposure |
fact | Upcoming payments (approved) | Learn what else is coming so the right tool can be offered. | always | review_upcoming_exposure |
upcoming_payment_known persisted |
|
agree_next_step |
fact | Agree the next step (approved) | One concrete action, confirmed on the dashboard. | always | agree_next_step |
next_step_agreed persisted |
rate_or_hedging
| item | kind | title | hint | applies | not needed because | points from | done when |
|---|---|---|---|---|---|---|---|
review_upcoming_exposure |
fact | Upcoming payments (approved) | Learn what else is coming so the right tool can be offered. | always | review_upcoming_exposure |
upcoming_payment_known persisted |
|
offer_forward |
must_say | Fix the rate for a known payment (approved) | A forward removes the rate risk on a payment with a date; say what it commits them to. | always | offer_forward_for_known_future_payment |
said_forward_deposit_and_liability said |
|
offer_alert_or_market_order |
judgement | Offer a rate alert (approved) | A target rate that books or notifies, instead of watching the screen. | always | offer_alert_or_market_order |
its points delivered | |
agree_next_step |
fact | Agree the next step (approved) | One concrete action, confirmed on the dashboard. | always | agree_next_step |
next_step_agreed persisted |
recurring_or_batch_setup
| item | kind | title | hint | applies | not needed because | points from | done when |
|---|---|---|---|---|---|---|---|
review_upcoming_exposure |
fact | Upcoming payments (approved) | Learn what else is coming so the right tool can be offered. | always | review_upcoming_exposure |
upcoming_payment_known persisted |
|
set_up_recurring_or_batch |
judgement | Recurring payments (approved) | Regular payments set up once instead of booked one by one. | always | set_up_recurring_or_batch |
its points delivered | |
add_user_access |
judgement | Who else books payments (approved) | A colleague or bookkeeper with their own login and limits. | while the decision_maker fact is colleague, accountant, director_or_owner (applies while unknown) |
The caller books the payments themselves | add_user_access |
its points delivered |
agree_next_step |
fact | Agree the next step (approved) | One concrete action, confirmed on the dashboard. | always | agree_next_step |
next_step_agreed persisted |
dormant_reengagement
| item | kind | title | hint | applies | not needed because | points from | done when |
|---|---|---|---|---|---|---|---|
reengage_dormant_with_a_reason |
judgement | Reconnect with a reason (approved) | Find out whether the need went away or something put them off. | always | reengage_dormant_with_a_reason |
its points delivered | |
review_upcoming_exposure |
fact | Upcoming payments (approved) | Learn what else is coming so the right tool can be offered. | always | review_upcoming_exposure |
upcoming_payment_known persisted |
|
offer_alert_or_market_order |
judgement | Offer a rate alert (approved) | A target rate that books or notifies, instead of watching the screen. | always | offer_alert_or_market_order |
its points delivered | |
agree_next_step |
fact | Agree the next step (approved) | One concrete action, confirmed on the dashboard. | always | agree_next_step |
next_step_agreed persisted |
other
| item | kind | title | hint | applies | not needed because | points from | done when |
|---|---|---|---|---|---|---|---|
confirm_caller |
fact | Confirm the caller is on the account (approved) | Know who is calling and whether they can act on the account. | always | none | the decision_maker fact known |
|
review_upcoming_exposure |
fact | Upcoming payments (approved) | Learn what else is coming so the right tool can be offered. | always | review_upcoming_exposure |
upcoming_payment_known persisted |
|
agree_next_step |
fact | Agree the next step (approved) | One concrete action, confirmed on the dashboard. | always | agree_next_step |
next_step_agreed persisted |
Client asks (a client-persisted fact inserts its move as a later item): client_asked_about_access → add_user_access, client_asked_about_recurring → set_up_recurring_or_batch, client_asked_about_alerts_or_orders → offer_alert_or_market_order, client_asked_about_forwards → offer_forward_for_known_future_payment.
- Rate pressure title
plan.rate_pressure.title(approved): Rate pressure - Ask first from
qualify_the_quote; concession points fromconcession_terms; headline, hint, points and do-not flags from the situation chosen for the call.
Customer success checklist
Derived from the plan templates ("checklist": "derived"): each must-say item of a template is one row, with its title and applies; rate pressure closes every list. Change an item in policy/src/plan-<scenario>.json to change its row.
transfer_issue
| id | item | applies | ticked by (rep turns only) |
|---|---|---|---|
issue_resolved_or_owned |
Resolve the issue | always | In recent_transcript, has the rep resolved the client's reported problem, found its cause and told the client the exact change that fixes it, or stated exactly what they will do about it and by when? |
rep_checked_status_with_specifics |
Status with specifics | always | Does latest_utterance.text, spoken by the rep (latest_utterance.speaker is rep), state the current status of the specific trade, payment, beneficiary or account the client's problem is about, with a concrete detail such as a time, a status word, a reference, a setting on the record, or the partner's name? |
rate_pressure_handled |
Rate pushback handled | once rate_pressure_raised is persisted |
In recent_transcript, has the rep answered the client's pushback on the rate without defending or moving the price, either by asking about the competing quote or by holding the price and changing what is being compared? |
status_update
| id | item | applies | ticked by (rep turns only) |
|---|---|---|---|
rep_checked_status_with_specifics |
Status with specifics | always | Does latest_utterance.text, spoken by the rep (latest_utterance.speaker is rep), state the current status of the specific trade, payment, beneficiary or account the client's problem is about, with a concrete detail such as a time, a status word, a reference, a setting on the record, or the partner's name? |
rate_pressure_handled |
Rate pushback handled | once rate_pressure_raised is persisted |
In recent_transcript, has the rep answered the client's pushback on the rate without defending or moving the price, either by asking about the competing quote or by holding the price and changing what is being compared? |
rate_or_hedging
| id | item | applies | ticked by (rep turns only) |
|---|---|---|---|
said_forward_deposit_and_liability |
Fix the rate for a known payment | always | In recent_transcript, if a forward contract was discussed, has the rep explained that a deposit is required at booking, that the balance is paid at the agreed date, and that the client is committed to the contract? |
rate_pressure_handled |
Rate pushback handled | once rate_pressure_raised is persisted |
In recent_transcript, has the rep answered the client's pushback on the rate without defending or moving the price, either by asking about the competing quote or by holding the price and changing what is being compared? |
recurring_or_batch_setup
| id | item | applies | ticked by (rep turns only) |
|---|---|---|---|
rate_pressure_handled |
Rate pushback handled | once rate_pressure_raised is persisted |
In recent_transcript, has the rep answered the client's pushback on the rate without defending or moving the price, either by asking about the competing quote or by holding the price and changing what is being compared? |
dormant_reengagement
| id | item | applies | ticked by (rep turns only) |
|---|---|---|---|
rate_pressure_handled |
Rate pushback handled | once rate_pressure_raised is persisted |
In recent_transcript, has the rep answered the client's pushback on the rate without defending or moving the price, either by asking about the competing quote or by holding the price and changing what is being compared? |
other
| id | item | applies | ticked by (rep turns only) |
|---|---|---|---|
rate_pressure_handled |
Rate pushback handled | once rate_pressure_raised is persisted |
In recent_transcript, has the rep answered the client's pushback on the rate without defending or moving the price, either by asking about the competing quote or by holding the price and changing what is being compared? |