Email a policy question.Get a cited answer back.
No app to open, nothing to install. Send the question from the address on your account and the answer lands in your inbox — pulled from your lender policy library and cited to the source document. Reply, and the follow-up stays in the same conversation.
ask@reply.creditpolicy.aiask@reply.creditpolicy.ai0
Things to set up
0
Credit per question
0
Policy libraries routed
0 days
A thread stays repliable
Why it matters
The fastest channel is the one you never left.
A broker with a question mid-application doesn't want a new tab. Email is already open, already on the phone, and already where the client's question arrived in the first place.
No app, no tab, no login
The channel you already have open.
You're in your inbox all day anyway. Forward the client's question, or type one line on the train, and the answer comes back the same way — nothing to install and nothing to sign into.
The same strict-RAG engine
An emailed answer is the app's answer.
Your question is routed to the right policy library and answered from the source documents, cited by name. It is the same routing, the same libraries and the same prompt the web chat uses — because it is literally the same code.
Replies land in the same thread
“What about at 90%?” just works.
Hit reply and the follow-up joins the conversation it came from, with the earlier turns already in context. No re-explaining, no quoting the whole chain back at yourself.
One history, three channels
It shows up in Saved chats, badged Email.
An email thread is a conversation like any other. Open it later in the app, keep going in the browser, or hand it to your assistant over MCP — same thread, same sources, same credits.
Under the hood
What happens in the minuteafter you hit send.
Seven steps, in this order, every time. Most of them exist to make sure the question really came from you, that it's answered from your documents, and that it's answered exactly once.
Receive
AWS SES takes delivery
Mail to the reply subdomain is accepted by SES, scanned for spam and viruses, and written to private storage. The app picks it up on the next pass — it checks every minute.
Record
The message is claimed before anything else
Its Message-ID is written down first. That single row is what makes a redelivered email harmless: the duplicate loses the race and stops, so nothing is ever answered — or billed — twice.
Verify
The sender has to prove they're the sender
A From header is trivially forged, so it counts for nothing on its own. SES's DKIM, DMARC and SPF verdicts have to pass before the message is treated as coming from a broker at all.
Identify
The address is matched to an account
The sender has to be on a CreditPolicy account with an active subscription or trial. One question costs one credit, and it's spent from the same balance the app uses.
Read
The question is separated from the email
Quoted history and signature blocks are stripped across Gmail, Outlook and Apple Mail, so only what you actually wrote reaches the model — you're not paying to re-read the thread on every reply.
Answer
Routed, retrieved and cited
The question goes to the right library — residential, commercial, asset, private, personal or compliance — and is answered from the source documents. If the library has nothing, the reply says so rather than guessing.
Reply
Written for an inbox, threaded for a reply
The answer comes back as a short reply with its sources listed beneath and your credit position at the foot, carrying a reply address that belongs to this conversation.
And how a reply finds its thread.
Not by who sent it. Every answer carries a reply address that names the conversation and is signed, so the thread is identified by something that can't be faked or guessed.
Reply-To: ask+c.<conversation>.<signature>@reply.creditpolicy.aiFirst
The signed reply address
Every answer carries a Reply-To that names the conversation and is signed with an HMAC. It can't be forged or enumerated, and it survives edited subjects, forwards and clients that strip threading headers.
Then
The threading headers
If the client rewrote the To line, the In-Reply-To and References headers are matched against the Message-ID of an answer we sent. Same thread, found a different way.
Otherwise
A new conversation
Neither matched, so it starts fresh. It never guesses from the sender's address — a broker with two questions open would be ambiguous, and the wrong guess puts someone else's thread in your inbox.
The guardrails
Anyone can send us an email.Not everyone gets an answer.
Anyone can put your address in a From header. Every rule below exists because of what would happen if it weren't there.
Nobody can ask as you
Sender authentication has to pass, so knowing your address isn't enough to spend your credits. Mail that fails is dropped silently.
No reply loops
Out-of-office notices, bounces and other auto-replies are recognised and never answered — otherwise our reply triggers theirs, and you'd be billed on every lap.
One answer per email
Delivery systems retry. The Message-ID is a primary key, so a message that arrives twice is answered once and charged once.
Strangers get one polite no
Mail from an address that isn't on an account gets a single explanation, at most once a day — enough to help someone who mistyped, useless to anyone abusing it.
Threads don't stay open forever
A conversation stays repliable for 30 days. After that a reply still gets answered, just as a new thread rather than reopening an old one.
Attachments aren't read yet
Files are counted and ignored, and the reply tells you so. Accepting broker uploads over unauthenticated email is a decision we haven't made yet.
This is the product, not a support desk. Nobody reads these emails — the answer is generated from your policy library and sent straight back. For help with your account, use the support tickets in the app.
Setup
There isn't any.
No key, no connector, no config file. If you have a CreditPolicy account, the channel is already on — it just needs an email.
Send your question to
ask@reply.creditpolicy.aiSend from the address you signed up with. Mail from anywhere else is declined — that's what stops someone else asking questions on your account.
What comes back
- A short answer, cited to the lender documents it came from
- A reply address that continues this exact conversation
- The thread, saved to your chats and badged Email
Then just ask.
Tap any of these to copy, and paste it into a draft.
Prefer it inside Claude or ChatGPT instead? Connect over MCP — same library, same citations, same credits.
Your next policy question
is one email away.
Answered from your own lender library, cited to the document, back in your inbox before you've finished the next call.