Six things to connect, in order, and how to run him once they're on. Written for Dona by Willis, Christa's agent.
Every blue box below is something you copy and paste to Seth in your chat with him. Tap Copy, paste it, send it. He does the work and tells you what he needs from you.
You do not have to understand the technical parts. Your job is to decide what gets connected and to say yes or no. His job is the how.
15 minutes. This is the only step on this page with a deadline.
This is a custom GPT I built in ChatGPT and I want to keep it. Save it as a skill I can call by name. Keep the instructions word for word unless something in them conflicts with how you already work — if it does, tell me instead of quietly changing it. When you're done, tell me the name to call it by and give me one example of how to use it. Here it is: [paste the Instructions box here]
Separate from the GPTs: ChatGPT → Settings → Data controls → Export data. It emails you a .zip. Save it somewhere on your computer, then:
My ChatGPT export zip is saved on this computer — find it, it's called something like chatgpt-export.zip. Read through it and write down what you learn about me: how I talk, what I ask for most, the projects I keep coming back to, and anything I've already decided so we don't re-decide it. Put that in your own memory files. Don't dump the whole thing back at me — just tell me the ten things you learned that matter most.
20 minutes, and it changes every answer he gives you after it.
An agent with no context about you writes like a press release. The single biggest jump in quality comes from three files he keeps about you — who you are, how you two work, and what he's learned. You don't write them. He interviews you and writes them himself.
Interview me for ten minutes so you actually know who you're working for, then write your own USER.md, AGENTS.md and SOUL.md from my answers and show them to me before you save them. Ask me one question at a time, not a list. Cover: what I do and who I do it for, how I want you to talk to me, what I want you to just do without asking, what you must always ask me first, what I hate, and how I like things delivered. If an answer of mine is vague, push back and ask again instead of guessing.
These are already public on your site, so there's nothing sensitive here — but having them exactly right means he never writes "serving Montana" or guesses an NMLS number in a client email.
Save these as my facts of record and never guess at any of them. If you're ever unsure, ask me — do not improvise a number or a link into anything a client will read. Name: Dona Jeka Title: Certified Mortgage Advisor, Branch Manager Company: Clear Home Loans, a division of Aspire Home Loans, LLC (NMLS 1955132) My NMLS: 13100 Licensed in: Idaho and Oregon only Office: 3023 E Copper Point Dr, Ste 109, Meridian, ID 83642 Hours: Mon-Fri 8-7, Sat 9-3 Phone: (208) 794-3371 Email: jeka.dona@clearhomeloans.com Website: donajeka.com Apply (Floify): https://donajeka.floify.com/ Experience: 31 years What I'm known for: first-time buyers, investors, seniors, and free reverse-mortgage assessments My teammate: Lorie Adams, Senior Loan Officer, NMLS 34663, (208) 794-2350, lorie.adams@clearhomeloans.com My voice: calm, clear, steady. Not folksy, not hype. Clarity and confidence, every step home. My leader: Christa Votaw, National Sales Director
Each one takes 10–30 minutes of back-and-forth with him. Do not skip to #4.
If you're already texting him, this is done. Keep it to one chat — one door in, one door out. Don't start a second bot for a second topic; you'll lose track of which one knows what.
Before we connect any of my accounts, set up an encrypted vault on this machine for secrets — API keys, app passwords, tokens. AES-256, the key stored locally only, never committed to any repository and never printed back to me in chat. Then show me the one command I'd use to add a secret, and tell me plainly where the key file lives and what happens if I lose it. From now on: no password, key or token of mine ever goes anywhere except that vault.
This needs an app registration in Clear's Microsoft tenant, and only IT can approve it. Christa's was approved — so there's a precedent you can point at. Two parts:
Part A — Seth builds it:
Connect my Clear Home Loans email and calendar (jeka.dona@clearhomeloans.com, Microsoft 365) using Microsoft Graph with a device-code login, so I sign in as myself and no password is ever stored. Delegated scopes only: User.Read, Mail.ReadWrite, Mail.Send, Calendars.ReadWrite, offline_access. Put the client ID and tenant ID in the vault. Then build me a small command-line tool for it with: whoami, inbox, search, read, draft, sent, drafts. Rules I want baked in: you may draft and revise, you never send without me saying send; every draft ends with my real signature; and you never write borrower names, phone numbers, emails or loan details into any code repository or any public page. Before we start, tell me exactly what to ask IT for.
Part B — you email IT. Send this and copy Christa so she can vouch that hers is already approved:
Hi — I'm setting up an AI assistant on my own machine to help me with my email and calendar, the same setup Christa Votaw has approved and running. Could you create (or point me to) an Azure app registration I can use with Microsoft Graph, with delegated permissions only: User.Read, Mail.ReadWrite, Mail.Send, Calendars.ReadWrite, offline_access? It signs in as me with a device code, so no password is stored anywhere. It needs no access to SharePoint, no access to anyone else's mailbox, and no application-level permissions. I just need the client ID and tenant ID. Thank you, Dona Jeka NMLS 13100
Connect my personal Google account — Gmail, Calendar, Drive and Contacts — using the gog command-line tool with OAuth, and keep the token in the vault, not in my home folder in the clear. Walk me through it one screen at a time: I'll be clicking through Google Cloud and I've never seen it before, so tell me what to click and what to ignore. When it's connected, prove it by showing me the subject lines of my last five emails — don't just tell me it worked.
donajeka.com is my site. Learn it: read every page, note my voice and my brand colors (royal blue #2F5FD0 and gold #C9A227), and tell me the three weakest things on it. Going forward you can draft anything for it — posts, pages, flyers, emails — but nothing publishes, posts or sends until I see it and say go. Show me a preview link, never a file path.
And when texting does come up: a mortgage text to a consumer has consent rules attached. That's a conversation with compliance before it's a conversation with your agent.
This is the part nobody tells you, and it's the difference between a toy and a second set of hands.
Give him one thing at a time. Jumping from a loan file to a flyer to your calendar inside one long chat is how he gets confused and starts mixing details between them. Finish, close, start fresh.
He has no memory of yesterday. That question makes him go read his own notes before he touches anything — and it catches the thing you asked for last week that never got finished.
Standing rule from now on. For every project we work on, keep a short STATUS file in that project with: what changed and when, every link I actually use, what's next and who it's waiting on, and a section called "Waiting on you" listing every question you've asked me that I haven't answered yet, in plain language. Update it as we work, not at the end. An unanswered question of mine held only in the chat is lost the moment the chat ends — so it goes in that file or it doesn't exist. And at the start of every session, tell me what's open there before we start anything new.
One word. It means: tell me what changed, write it all down, save everything, and confirm nothing was lost. Train him on it once and it's yours forever.
When I type "close" by itself, that's my whole instruction and it means: tell me in two or three plain sentences what changed this session, write every open question of mine into the STATUS file, save and back up everything you touched, then confirm out loud that nothing is unsaved. If something couldn't be saved, say so plainly instead of telling me it went fine.
Long sessions get compressed and he loses the middle of them. It looks like he got dumber. He didn't — the notes are the fix. If he starts repeating himself or asking something you already answered, say "re-read the status file" and carry on.
Set up a watchdog on this machine that checks every couple of minutes that you're actually running and actually receiving my messages, restarts you if you've died, and texts me if it can't. Important: it must also catch the case where you look like you're running but aren't getting my messages at all. Then prove the alarm works by making it fire on purpose while I watch.
When he gets something wrong — your voice, a number, how you want things delivered — tell him plainly and add "write that down so you don't do it again." That's how he actually gets better. Being polite about it just means you'll fix it again next week.
Pick three. Real work, not demos.
Short list. Tell him all six on day one.
My red lines. These never expire and you never need to ask me to confirm them again: 1. Nothing goes out to a real person — email, text, post, submission — without me reading it first and saying send. 2. Borrower information never goes into a code repository, a public page, a temp folder or a chat with anyone but me. It lives in the company's secure storage. 3. No credential, key or password of mine is ever stored anywhere but the encrypted vault, and never printed back to me. 4. Nothing is deleted. If something's in the way, move it or archive it, and tell me where it went. 5. Anything mortgage-facing that a consumer could read waits for compliance before it's live. Rates, "pre-approved", down-payment claims — you flag them, you don't publish them. 6. If you're not sure, ask me. If you got something wrong, say so immediately and fix it in the same breath.
That's the whole run sheet. Work top to bottom, and don't let the email step stall the rest — steps 1, 2 and the vault don't need anyone's approval but yours.
Built by Willis — Christa's agent — for Dona, 2026-10-19.
Stuck on a step? Send Christa the step number and what he said back. Most of what's on this page we learned by getting it wrong first.
build