Built for
Retail branch teams
Scripts and prompts tailored to teller workflows and handoffs
AI Writing Assistant • Accounting & Finance
Ready-to-use teller scripts, compliant phrasing, and operational notes
A curated set of editable prompts and script patterns designed for frontline tellers, branch managers, and operations teams — standardize customer messages, reduce drafting time, and create audit-friendly handoffs without rewriting every interaction.
Content types
Scripts, emails, checklists, reconciliation notes
Short customer-facing lines and longer operational templates
Localization
Region-ready patterns
Prompts designed to swap local terminology and disclosure blocks
Problem solved
Why a teller prompt library matters
In-branch consistency is essential for customer trust and regulatory compliance. This library provides role-aware, editable prompt patterns so tellers spend less time drafting wording and more time serving customers. Each prompt is written to be short, clear, and suitable for rapid review by compliance or training teams.
- Reduce inconsistent messaging across tellers with standardized scripts.
- Cut drafting time for emails, incident notes, and reconciliation logs.
- Provide compliance-aware phrasing and safe default language for disclosures.
Core templates
Ready prompt clusters — copy, paste, and adapt
Use these concrete prompt examples to generate teller-ready outputs. Each prompt includes intent, expected length, and suggested fields for localization or required disclosure insertion.
Customer greeting and ID verification (short script)
Prompt: Write a friendly 1–2 line greeting for a teller to start a transaction, include a brief ID request and one-sentence expected wait time.
- Use: lobby interactions, line management
- Example output: "Good morning—welcome to [Bank Name]. May I see a photo ID and your account number? I’ll be with you shortly; this should take about two minutes."
Cash deposit flow (step-by-step)
Prompt: Create a clear teller script for accepting a cash deposit, include confirmation of amount, account type, and next steps for receipts.
- Use: teller workstation scripting
- Example output: "I’ll deposit $X into your [checking/savings] account. Can you confirm the amount and account ending in [####]? You’ll receive a receipt and a confirmation message if you’re enrolled in alerts."
Cash withdrawal (large-amount guidance)
Prompt: Compose a concise teller script to handle a large cash withdrawal, include polite verification questions and instructions about teller limits or manager approval.
- Use: risk-aware frontline guidance
- Example output: "For a withdrawal of $X, I’ll need to verify your ID and account. Because this is over our standard teller limit, a manager will briefly review; this should only add a few minutes."
Check cashing checklist
Prompt: Generate a checklist-style script that reminds tellers to verify endorsement, compare ID, and record check number; include a short customer-facing explanation of any holds.
- Use: control and customer transparency
- Example output: "Checklist: verify endorsement ✓ compare ID ✓ record check number ✓. Customer line: 'I’ll need to endorse and verify your ID. A short hold may apply depending on the check type.'"
Disputed transaction acknowledgement email
Prompt: Draft a professional, compliant acknowledgement email a teller or operations clerk can send after a customer reports a transaction dispute; include expected timeline and next steps.
- Use: email templates for follow-up
- Example output excerpt: 'We’ve received your dispute regarding transaction on [date]. We will review and contact you within our standard investigation timeframe. Please do not share account numbers over email.'
End-of-day reconciliation note template
Prompt: Produce a structured template for daily cash reconciliation notes with fields for opening balance, cash counted, variances, and manager sign-off.
- Use: operations logs and audits
- Example fields: Opening balance, Cash counted, Deposits, Withdrawals, Variance (explain), Manager initials.
Deployment
How to use these prompts in-branch
Prompts are designed to be copied into branch CRM notes, internal tickets, teller pads, and training decks. Follow a simple pilot-and-approve workflow to integrate them safely.
- Start with a pilot in a few branches to collect feedback on local terminology and timing.
- Create a short compliance review for each prompt type before broad rollout.
- Provide quick-reference cards at teller stations and include prompts in new-hire training.
Evidence and alignment
Source ecosystem & review inputs
Prompts are organized around common branch sources so outputs fit existing controls and audit needs.
- Branch operations manuals and teller procedure checklists inform control points.
- Retail banking product documentation provides accurate timing and disclosure language.
- Training decks and CRM note patterns shape wording appropriate for front-line use.
Adaptation guidance
Localization and compliance notes
Each prompt includes fields for local disclosure language and terminology. Keep a version-controlled list of approved disclosure blocks that compliance can swap into prompt outputs.
- Replace placeholder [disclosure] blocks with region-approved text before customer use.
- Avoid PII in prompts; use placeholders (e.g., [account ending in ####]) for generation.
- Maintain an approval log for prompt changes and localizations.
FAQ
How do I adapt teller prompts to local disclosure and regulatory language?
Use the prompt placeholders for disclosure blocks and maintain a centrally approved library of region-specific disclosure text. During pilot rollouts, collect compliance feedback and store localized versions in the branch playbook so tellers copy approved wording rather than freeform text.
What are best practices for training tellers on AI-generated scripts?
Train tellers on when to use short scripts versus longer explanations, run role-play sessions with sample prompts, and include a quick-reference sheet at workstations. Require a compliance sign-off for commonly used templates and include examples of when to deviate for customer-specific situations.
What customer data should I avoid feeding into prompt tools?
Never include full account numbers, social security numbers, passwords, or other direct PII in prompts. Use masked placeholders (e.g., [account ending in 1234]) and restrict any generation tools that retain or log raw customer identifiers.
When should an interaction be escalated rather than fully scripted?
Escalate when you encounter potential fraud indicators, verbal threats, requests to bypass controls, complex disputes requiring investigation, or when a manager’s authorization is needed. Include escalation cues in scripts (e.g., unusual endorsement, conflicting ID) and provide a ready handoff note template.
How do I customize templates for multi-branch rollouts and languages?
Create language-specific prompt variants and a central glossary of terms (e.g., 'savings' vs 'deposit account') so local teams swap approved terminology. Roll out in phases, translate and legal-review each prompt set, then publish localized packs to branch staff.
What review process should generated text follow before public use?
Establish a lightweight compliance and training review for any template used with customers. Use spot audits of branch outputs, require manager sign-off for modified templates, and store approved versions in a shared repository with version history.
How can prompts help create audit-friendly logs and reconciliation notes?
Use structured templates that capture required fields (opening balance, counted cash, variances, initials). Prompts can produce consistently formatted notes that make variance explanations and manager sign-offs easy to find in audits.
What are the limitations — when is human judgment required?
Use prompts for routine, low-risk communications. Human judgment is required for suspected fraud, complex disputes, legal requests, or any situation that could materially affect a customer. Scripts should include escalation triggers and remind tellers to pause and consult.
Related pages
- IndustriesExplore other industry prompt libraries and templates.
- Product comparisonSee how Texta's approach to visibility and prompt libraries compares.
- PricingPlans and licensing for teams and branch rollouts.
- BlogRead product updates and best-practice guides for frontline teams.
- About TextaCompany overview and mission.