Listing What a Request Requires
Work out exactly what a customer has to provide for a given request, and write the list in language they can act on.
About this use case
The documents a request needs depend on what is being asked, who is asking, and the circumstances — and the list lives in a procedure written for staff. Customers get a partial list, send part of it, and the request cycles.
This use case produces the complete list for the specific request, with what each document must show, and writes it plainly enough that a customer can gather everything in one go.
Adding a party to an account returns every document and form, what each must show and how to send it; a request involving a trust picks up the additional authority documents; anything already on file and still inside its validity window is left off the list and named as held.
Documents to consider
- Your documentation requirements by request type
- Identity and authority verification standards
- Forms and their completion instructions
- Acceptance criteria: what each document must show
- Approved customer-facing language
The prompt
Written to be pasted straight into your AI assistant, with the documents it asks for attached. Request access below and we’ll send it over.
Files
Nothing to download here. This prompt runs against your own institution’s material — the documents it lists above.
More in Retail & Branch Banking
Customer Support
Give a support agent a customer-ready answer drawn from the knowledge base, fee schedule and product terms, with the decision path documented.
Client Advisement
Draft a client-ready explanation from approved product material and compliance-cleared scripts, with the required disclosures already in place.
Cross-Sell and Upsell Opportunities
Match a customer's holdings and behavior against eligibility rules and current offers, then draft outreach that is relevant rather than generic.