Framer and fintech app
Publishing a financial promotion with a single button
The app is not on this platform. A financial product builds its marketing site here and runs the product itself somewhere else entirely, which removes the problem that dominates every other install in this family: there is no signed in surface for the launcher to wander onto. What is left is a narrower and more awkward question. The site is a designed canvas, and the assistant answers by retrieving passages from it, and a canvas is very good at putting a compelling number a long way from the sentence that makes it lawful.
Why this pairing is its own job
The Framer install guide covers the tag, and the fintech app guide covers what the assistant has to know. What follows is the part that belongs to neither.
- A designed page separates the claim from its qualification by construction. The rate is in a hero, the conditions are in a section further down, the risk wording is in a footer component reused across the site. All three are on the page. Retrieval works on passages, and a passage carrying the number does not necessarily carry the sentence that constrains it.
- Publishing is one action available to anybody with edit access on the project, and it ships everything pending, not only the thing they touched. A copy change that has not been through whatever approval your firm runs can reach the public site inside somebody else's design publish, and the assistant will read whatever version was live when the crawl ran.
- The project answers on the platform's own address as well as on your domain, so a promotion is published at two public addresses. Whether the assistant renders on the second one is a choice you make in the allowlist. That the second one exists, and is a copy of regulated material nobody reviews, is not.
- Because the product lives elsewhere, this assistant will never stand beside a balance or a transaction. That is the one piece of good news on this pairing and it is worth stating rather than assuming, because it means the whole risk sits in the wording rather than in the placement.
What changes about the install here
<script src="https://cdn.askably.xyz/w.js" data-key="pk_live_YOUR_KEY" defer></script>The tag is the same one on the Framer guide. Everything below is about where it goes on a fintech app site specifically.
Treat the publish button as a control, because it is one
Two things ship through the same action here: the tag and the copy. That means the moment you paste the tag into the end of body field, you are also publishing whatever text edits were sitting unpublished in the project, made by whoever else has access to it.
Look at the project before you publish rather than after. If a colleague has been drafting a new rate page or reworking the charges section, your install ships it. On an ordinary marketing site that is untidy. On a regulated one it is a promotion going live without the review it was waiting for.
Then agree who may publish at all. The list of people with edit access on a design tool is usually longer than the list of people permitted to put a financial promotion in front of the public, and on this platform those are the same list.
Decide about the second address on purpose
A published project is reachable at the platform's address and at your domain. If you allowlist only the domain, the assistant is absent from the other copy and every check somebody runs there comes back empty with the refused address named in the console. If you allowlist both, you have an assistant answering questions about a regulated product on an address you do not use in any material.
Neither is wrong and one of them has to be chosen. What is worth avoiding is the third state, where nobody looked, the address is shared internally because it is convenient, and half the people testing the site are testing the copy without the assistant on it.
Put the condition in the same text element as the number
This is the concrete work on this pairing and it is a writing task rather than a configuration one. Wherever a figure appears, a rate, a fee, a limit, a timescale, the sentence that qualifies it has to be in the same block of text rather than in a component two sections away or in a footer shared across the site.
The reason is mechanical. An answer is built from passages, so a passage is the unit that has to be safe on its own. A hero that reads as a headline number with the qualification designed to sit elsewhere is a page that will produce an unqualified answer, and the answer will carry a citation to your own site.
Where the design genuinely needs the number to stand alone, publish a plain page carrying the same figures with their conditions attached and make sure it is crawled. The designed page keeps doing its job for readers, and the assistant has something it can quote without stripping anything out.
Where the answerable material lives
| Charges written so each figure carries its own condition | Every fee with the circumstance it applies in, in the same sentence: the amount, when it is charged, what it does not cover, and any threshold. Not a grid with the exceptions collected underneath it, because the exceptions will be retrieved separately from the numbers or not at all. |
|---|---|
| Eligibility and coverage as a page rather than as a signup step | Who can open an account, which countries and currencies, minimum age, residency conditions, and what identity documents are accepted. High volume, entirely publishable, and on most products it currently exists only as a series of screens somebody has to start signing up to see. |
| The complaints procedure with its published timescales | How a complaint is raised, what happens next, how long each stage takes and what route exists if it is not resolved. A message containing that word needs the procedure and a person, and the procedure has to be quotable rather than summarised, because the timescales in it are commitments. |
| The protection and regulatory wording, exactly as approved | Whatever statement your compliance function wrote about how money is held or protected, indexed as written. This is the material where a paraphrase is a misstatement rather than a style choice, so it goes in as the approved document rather than as a page somebody rewrote to fit a layout. |
The first thing to get right
Take the three numbers you would least like quoted alone, and rewrite each so the qualifying sentence is in the same text element.
It is the only change on this list that fixes the failure at the source rather than compensating for it afterwards. Thresholds, refusal wording and crawl scope all reduce how often an unqualified number comes back. Putting the condition in the same passage means the unqualified version does not exist for anything to retrieve, which is a different kind of fix and the only one that holds when somebody asks the question in a way you did not anticipate.
The failure that belongs to this combination
The headline figure arrives without the sentence that made it lawful
Somebody asks what they would earn, or what a transfer costs, or how long money is held. The answer comes back with the number from the hero of a page built to sell, phrased confidently, cited to your own site. The qualification that sat two sections below it, or in the footer that appears on every page, did not come with it.
Nothing invented anything. The page said that number, the number is correct, and the assistant did what it does, which is find the passage that best matches a question and answer from it. A designed marketing page is optimised for the opposite property: it separates the persuasive thing from the careful thing so the persuasive thing lands first.
The second half of the problem is that this is invisible from the inside. Reading the page, everything is present and balanced. The only way to see it is to read the assistant's answers rather than the site, so put a handful of your most sensitive questions into it after every crawl and read what comes back on its own terms, with no page around it.
Before you go live
- The origin the page is served from has to be on the allowlist for that assistant, or nothing renders and the browser console says which origin was refused. An apex domain and its www are two different origins to a browser, so list both, along with any staging or preview host you want it to work on.
- Open the site as a visitor would, on the pages a fintech app visitor actually lands on, and ask it something only your own material could answer. A widget that renders is not the same as a widget that has read anything.
Questions
- Our compliance team wants to know what it can say. What is the honest answer?
- It answers from the material you index and cites what it used, so the ceiling is whatever your pages say. That is reassuring and insufficient at the same time, because it will summarise, and a summary of carefully worded material is where the care goes missing. Index the approved wording, tell it to quote rather than restate, and set the threshold so a weak match refuses.
- Can it tell somebody whether the product is right for them?
- No, and it must not appear to. Describing what a product does is information. Relating that to somebody's circumstances is advice, and it stays advice when software produces it. The refusal wording should say plainly that it cannot advise, and it should not soften that into a suggestion.
- Somebody types that money has gone missing from their account. What happens?
- The fastest route you have, in the first reply, with a telephone number in it. That belongs in the refusal message rather than in the material, because it has to appear when somebody is frightened and typing badly, which is exactly when matching against a page is least reliable.
Keep reading
- Installing on FramerFramer keeps custom code in site settings. Paste the tag in the end of body field, publish again, and allowlist the staging address too.
- Everything for a fintech appFees, limits and identity checks are safe ground. Balances, transactions and anything reading as a personal recommendation are not.
- The work page is the one prospects want and the one you cannot indexAgencies run their own project and a dozen client projects from the same code field. One key across all of them mixes clients' material.
- Publishing an article and publishing an answer are the same act hereA published article is a communication in the firm's name. Guide lets any agent publish one, and the corpus keeps it until the next crawl.
- Getting a third party script past the policy a regulated product ships withThe policy decides whether the tag runs at all. Script and frame directives both matter, and a report only header proves nothing.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.