Per-client profiles, typed variables, guardrails, 'don't forget' notes, and uploaded reference files load the moment you reply — so every draft uses real values, never guesses. See how teams feed the brain.
Everything below runs on real controls — nothing invented.
Client profiles
Domain-keyed profiles with status, point of contact, tier, tags, and open loops that auto-load on reply.
Typed variables
Global, per-client, and template variables resolve into drafts with real values — never a placeholder.
Guardrails
Must-follow rules per client ('never mention pricing without approval', 'always CC legal').
Don't-forget notes
Standing reminders the agent respects ('they prefer email over calls', 'CEO's name is Robert').
Context folders
Shared reference notes and materials attached to a mailbox to steer voice and facts.
Uploaded files
Attach PDF, DOCX, or Markdown; they convert to reference the agent reads while drafting.
02—Use cases
200 ways people put Context brain to work.
Each example shows which brain fields do the work — profile, variables, guardrails, don't-forget, files. Filter by your industry or role.
200 results
Real estate
First-time buyer profile
Without a profile flagging someone as a first-timer, every draft assumes they already know what escrow is — and the replies show it.
When
You start working a new buyer who's never purchased before.
Setup
A client profile flags them first-time with a don't-forget note and a no-legal-advice guardrail.
Result
Every draft to this client stays patient, jargon-light, and within your lane.
First-timers always get replies that meet them where they are — without extra effort from you.
Profile tier: first-time
Don't-forget: explain each step
Guardrail: no legal advice
Real estate
Closing-date variable
A client under contract asks about timing and you're juggling three deals — the wrong date in a reply erodes trust at the worst possible moment.
When
A client under contract asks about timing anywhere in a thread.
Setup
A per-client variable holds their closing date so the agent references it while drafting.
Result
Dates stay accurate in every reply without you looking them up.
Every timeline reply is accurate without you cross-checking another tab.
Variable: {closing_date}
Profile status: under contract
Per-client scope
Real estate
Preferred-lender variable
If every agent on your team refers a different lender to the same buyer, it looks disorganized — and buyers wonder who to trust.
When
Any buyer asks who you'd recommend for financing.
Setup
A global variable stores your go-to lender's name and intro so it drops into drafts consistently.
Result
Buyers always get the same trusted lender referral, worded the same way.
Your lender referral is always consistent, professional, and ready in one keystroke.
Variable: {preferred_lender}
Global scope
Guardrail: no rate quotes
Real estate
Neighborhood reference file
A relocating buyer asks about school ratings and commute times and you're guessing from memory — or stalling while you Google.
When
A relocating buyer asks about schools, commute, or local amenities.
Setup
You upload an area-guide PDF into a context folder the agent reads while drafting.
Result
Local answers stay grounded and consistent across every buyer you serve.
Relocating buyers get accurate, detailed local answers — not vague reassurances.
Reference file: area guide (PDF)
Context folder: Neighborhoods
Purpose: local answers
Real estate
Process playbook folder
"What happens after inspection?" gets asked a hundred times a year — and without a reference, the answer varies every time.
When
A first-timer asks what earnest money, contingencies, or escrow mean.
Setup
A context folder holds your markdown explainers for each buying step.
Result
Common process questions get accurate, on-brand answers every time.
Process answers are always consistent, accurate, and sound like you — not improvised.
Context folder: Buying 101
Items: markdown explainers
Purpose: FAQ answers
Real estate
VIP client open loops
A high-value client under contract emails about something you promised last week and your reply makes clear you forgot — that's the moment trust breaks.
When
A high-value client under contract emails with a status question.
Setup
Their VIP profile tracks open loops and dont-forget items the agent surfaces in replies.
Result
Nothing pending falls through the cracks for your most important deals.
VIP clients always feel like your only client — because the context keeps you sharp.
Profile tier: VIP
Open loops: tracked
Don't-forget: weekly check-in
Real estate
Disclosure guardrail
Fair-housing rules are easy to violate accidentally in a rushed reply — and the consequences far outweigh the time you saved.
When
A buyer asks a question that edges into legal or fair-housing territory.
Setup
A profile guardrail instructs the agent to defer instead of advising on legal matters.
Result
You stay compliant automatically, with risky topics handed back to you.
Compliance guardrails travel with every thread — you never have to remember to apply them.
Guardrail: no legal advice
Guardrail: fair-housing safe
Escalate to me
Real estate
Point-of-contact profile
Emailing the wrong person in a buying couple — or getting a name wrong — is the small thing that signals you're not really paying attention.
When
A buying couple emails and you need to address the right person by name.
Setup
The client profile stores each partner's name, point-of-contact, and preferred tone tags.
Result
Replies greet the right person warmly without you re-checking who's who.
Every reply feels personal — because it addresses exactly the right person, correctly.
Profile poc: primary contact
Tags: couple
Variable: {partner_name}
Mortgage
Active borrower profile
A reply that reflects the wrong loan status or misses an open condition tells the borrower you're not tracking their file as closely as they hoped.
When
You reply to anyone on a live purchase file.
Setup
A client profile holds status, tier, open loops, and a hard guardrail against quoting rates in writing.
Result
Every reply is accurate to the file's stage and never crosses a compliance line.
Every reply reflects the real state of the file — no stale details, no compliance slip.
Profile: status = In Underwriting
Guardrail: no rate quotes in writing
Open-loop: paystub outstanding
Mortgage
Rate-lock expiry variable
A rate lock that expires unannounced triggers a relock fee, a frustrated borrower, and a damaged referral relationship — all avoidable.
When
A borrower or agent asks how much time is left on the lock.
Setup
A per-client variable stores the lock-expiry date so drafts reference the real deadline.
Result
Lock timing is always stated correctly, and nobody drifts past expiry unaware.
Lock expiry is always front-of-mind — for you and the borrower.
Variable: {rate_lock_expiry}
Per-client scope
Don't-forget: warn 5 days out
Mortgage
Closing timeline guardrails
A closing date mentioned in a reply that turns out to be wrong creates a chain reaction — angry borrowers, panicked agents, and a file that misses its window.
When
A message touches the closing date on an active file.
Setup
The profile records the target closing date and a don't-forget on TRID timing, plus a guardrail that closing dates get human confirmation.
Result
Timeline replies respect TRID and never commit to a date the file can't hit.
Dates are only confirmed when the file can actually support them — TRID-safe, every time.
Variable: {closing_date}
Don't-forget: TRID timing
Guardrail: confirm dates with a human
Mortgage
Document-checklist folder
A borrower submitting the wrong documents for their loan type wastes a week of everyone's time — and usually means starting the collection process over.
When
A borrower asks what to submit for a given loan type.
Setup
A context folder holds your intake checklists (conventional, FHA, VA, self-employed) as Markdown items.
Result
Checklist answers are consistent and complete no matter who asks or when.
Borrowers always get the right checklist for their loan type — on the first ask.
Folder: Intake Checklists
Items: FHA.md, VA.md, self-employed.md
Purpose: answer doc questions
Mortgage
Compliance guardrail library
A written rate quote, approval hint, or closing guarantee in any email — however casual — is a compliance exposure that doesn't go away.
When
Any draft that could stray into rate, APR, or approval promises.
Setup
A global guardrail set forbids written rate quotes, approval guarantees, and legal/tax advice across every reply.
Result
The whole inbox inherits your compliance rules, so no draft ever puts a risky line in writing.
Compliance guardrails are baked into every draft — not relying on memory or habit.
Guardrail: no rate quotes in writing
Guardrail: no approval guarantees
Global scope
Mortgage
Referral-partner tier
A top-tier referral agent gets a reply that reads like you pulled a template — and quietly starts routing deals to the LO who sounds like they know them.
When
You correspond with a repeat agent or builder.
Setup
The partner's profile stores tier, preferred contact, and a note on their typical buyer, so replies match the relationship.
Result
Top partners feel known and prioritized in every exchange, protecting your referral pipeline.
Referral partners feel genuinely known — not like one of a hundred agents you work with.
Profile: tier = Platinum
POC: agent name
Variable: {typical_buyer_profile}
Mortgage
Loan-program cheat sheet
A borrower who doesn't understand the difference between FHA and conventional is going to shop the question online — and find a competitor who answered it first.
When
A borrower asks how FHA, VA, or conventional differ for them.
Setup
A context folder holds plain-language program overviews and current overlay notes as text items.
Result
Program questions get answered accurately without you re-explaining the basics daily.
Program questions get clear, accurate answers the first time — without you re-explaining daily.
Folder: Loan Programs
Items: overlays.md, program-basics.md
Purpose: explain options
Mortgage
Wire-fraud reminder standing text
Borrowers who don't have a wiring-caution reminder in writing before closing are the ones most vulnerable to spoofed emails asking them to redirect funds.
When
Any closing-related reply going to a borrower.
Setup
A don't-forget on the closing profile ensures the wiring-caution language is included whenever funds or closing are discussed.
Result
The fraud warning is attached to every closing message automatically, protecting borrowers and you.
The wire-fraud caution is in every closing email — automatically, without exception.
Don't-forget: include wire-fraud caution
Applies on: closing tag
Guardrail: never share wiring info by email
Insurance
Policyholder profiles
Drafting a reply to a client without knowing their renewal date, policy number, or status means sounding generic to someone who's been with you for years.
When
A known client emails and the agent needs their file at a glance.
Setup
A profile per household holds status (active/renewing/lapsed), primary point of contact, tier, and variables for {policy_number} and {renewal_date}. Guardrail: no coverage promises over email.
Result
Every reply is grounded in the right policy details, and the coverage-promise guardrail travels with the client.
Every client reply is grounded in their actual file — not approximated from memory.
Profile: status + renewal date
Variable: {policy_number}
Guardrail: no coverage promises
Insurance
Open loops per client
A client with an open claim or pending endorsement emails again and your reply makes clear you forgot what you promised them — that's the moment they start looking at other agents.
When
A client with a claim or endorsement in flight emails again.
Setup
The profile's openLoops track in-progress items (claim #, pending endorsement, missing signature) and dontForget notes surface commitments the office made.
Result
Nothing owed to a client falls through the cracks — the outstanding item is right there when they write.
Outstanding commitments surface automatically — clients never have to remind you.
Profile: openLoops (claim, endorsement)
dontForget: promised callback
Variable: {claim_number}
Insurance
Carrier appetite folder
Telling a prospect you can write their risk and then discovering the carrier won't touch it wastes their time and damages your credibility.
When
Deciding which carrier fits a risk while replying to a prospect.
Setup
A folder for carrier appetite holds markdown items per carrier (accepted risks, declines, underwriting quirks) so the assistant reflects real placement rules.
Result
Prospect replies are shaped by which carriers actually write the risk, avoiding dead-end promises.
Placement answers reflect reality — no promises to prospects about risks carriers won't write.
Folder: carrier appetite
Items: appetite + declines (md)
Guardrail: no coverage promises
Insurance
Coverage guardrails file
A coverage opinion in an email — however casually phrased — is a written record that can be used against you if a claim is denied later.
When
Any reply that risks stating coverage or binding.
Setup
A global guardrails profile enforces: never confirm coverage, never bind over email, always defer to the policy form and a documented conversation. Applied across all client threads.
Result
Compliance posture is baked into every draft and auto-reply, not left to memory.
Coverage guardrails travel with every thread — compliance is never left to memory.
Guardrail: never bind over email
Guardrail: defer to policy form
Scope: all threads
Insurance
Office variables
Office hours, the claims line, and the agency name typed inconsistently across replies makes a small office look disorganized to clients who are already anxious.
When
Replies that reference the office, hours, or claims process.
Setup
Global variables hold {agency_name}, {office_hours}, {claims_line}, and {producer_name} so boilerplate is consistent and always current.
Result
Every message uses the same accurate office details without the agent retyping them.
Office details are always consistent and accurate — no version drift across replies.
Variable: {claims_line} (global)
Variable: {office_hours}
Variable: {agency_name}
Insurance
COI templates folder
Certificate language drafted from scratch or varied between replies creates inconsistency that carriers and vendors push back on.
When
A certificate request comes in and needs standard language.
Setup
A folder holds approved COI language and additional-insured wording as text/markdown items the assistant can reference — but not alter — when drafting.
Result
Certificate replies pull from vetted language, keeping wording consistent and defensible.
Every COI reply uses vetted language — consistent and defensible every time.
Folder: COI templates
Items: approved wording (text)
Guardrail: no unreviewed AI wording
Insurance
Renewal playbook file
Renewal outreach drafted ad-hoc varies in quality, timing, and message — a consistent playbook is what separates a well-run renewal season from a chaotic one.
When
Renewal season outreach across the book.
Setup
An uploaded markdown playbook defines the renewal cadence, review talking points, and cross-sell prompts by line of business, referenced when drafting renewal outreach.
Result
Renewal emails follow a consistent, proven process instead of ad-hoc wording per account.
Every renewal email follows the same proven process — regardless of who drafts it.
Uploaded file: renewal playbook (md)
Profile: renewal date
dontForget: schedule review call
Insurance
Cross-sell tracking
A monoline auto client with a homeowners opportunity gets contacted three renewals later — by which time they've already bundled elsewhere.
When
A monoline client emails and there's an obvious bundle opportunity.
Setup
The profile tags monoline accounts and records dontForget cross-sell openings (e.g. 'auto-only, mention home'); guardrail keeps any pricing off email.
Result
Cross-sell opportunities are remembered per client and surfaced at the next touch, without over-promising savings.
Cross-sell openings are never forgotten — they surface at the next contact automatically.
Profile: tag 'monoline'
dontForget: home cross-sell
Guardrail: no price/discount promises
STR hosts
Property manual folder
Without a single source of truth, the AI answers wifi and parking questions from whatever it can guess — which is how guests get the wrong information.
When
Guests ask about wifi, parking, trash, and appliances all week.
Setup
A Context folder holds the full property manual as a PDF, so every autopilot and copilot reply pulls answers from one source of truth.
Result
House details are answered accurately from day one, no copy-paste.
Every guest answer grounded in your actual property details
Folder: property manual (PDF)
Purpose: answer guest FAQs
Variable: {wifi_password}
STR hosts
Access-code variables
Sending the wrong door code to the wrong unit is a guest-experience failure that no amount of apology fully fixes.
When
Every arriving guest needs the door and gate codes.
Setup
Per-unit variables store the smart-lock code, gate code, and wifi password so replies insert the right credentials by property.
Result
Codes go out correctly per unit, and you update them in one place.
Right codes sent to the right unit — updated in one place when they change
Variable: {door_code} (per-unit)
Variable: {gate_code}
Variable: {wifi_password}
STR hosts
House-rules file
An AI that paraphrases your house rules from memory can accidentally soften a firm policy or omit a critical restriction.
When
Inquiries ask about pets, parties, smoking, and guest limits.
Setup
The signed house-rules document is uploaded as a PDF the agent quotes verbatim when guests ask about policies.
Result
Policy answers are always consistent with what guests actually agreed to.
Policy answers verbatim from what guests signed — no paraphrasing
Uploaded file: house rules (PDF)
Guardrail: quote rules verbatim
Don't-forget: no pets unit 2
STR hosts
Per-property profiles
Managing three units from one inbox without unit-level context is a fast path to giving guest A the details for unit B.
When
You manage three units with different codes, wifi, and quirks.
Setup
Each property is its own Context profile with tier, tags, and unit-specific variables, so routing rules can assign the correct one.
Result
Multi-property mail is answered from the exact right unit's details.
Multi-property hosting handled correctly without manual context-switching
Profile: Beach Condo (tier: premium)
Tags: 2BR, oceanfront
Variables: per-unit codes
STR hosts
Local guidebook
Guests who ask for restaurant and activity recommendations expect something personal — a generic shrug costs you a 5-star mention.
When
Guests ask for restaurant, beach, and grocery recommendations.
Setup
A Context folder holds a Markdown local guide the agent draws from for recommendation questions.
Result
Guests get thoughtful local tips without you retyping them each stay.
Thoughtful local tips in every stay — no retyping each time
Folder: local guide (Markdown)
Purpose: area recommendations
Variable: {nearest_grocery}
STR hosts
Cleaner contact profile
Turnover status living only in your head means one missed message can strand a guest at a unit that isn't ready.
When
Turnover coordination needs the cleaner's details and schedule.
Setup
A Context profile stores the cleaner as a point of contact with open loops for the current turnover, keeping team threads organized.
Result
Turnover status is tracked in one place across every property.
Turnover status visible and current across every property
Profile: Cleaning Co (poc)
Open-loop: unit 2 turnover pending
Variable: {turnover_window}
STR hosts
Guardrails on promises
A well-meaning AI that promises an early check-in or an unapproved discount can cost you the cleaner's window or your margin.
When
Guests push for early check-in, late checkout, or discounts.
Setup
Profile guardrails tell the agent never to promise early check-in, late checkout, or a discount without your approval.
Result
The agent stays helpful without committing you to things you can't honor.
Helpful responses without commitments you didn't approve
Guardrail: no early check-in promise
Guardrail: no unapproved discounts
Don't-forget: cleaner needs the full window
STR hosts
Superhost SLA note
Response time directly drives Airbnb search rank and Superhost status — every slow reply is a compounding cost to your visibility.
When
Your Superhost status depends on a fast, reliable response time.
Setup
A global don't-forget records your under-1-hour response target and books check-in/checkout times as variables the agent respects.
Result
Every reply reinforces the response standard that protects your status.
Response SLA embedded in every automated action — Superhost status defended
Don't-forget: reply within 1 hour
Variable: {check_in_time} = 3pm
Variable: {checkout_time} = 11am
Staffing
Live req profile
Without a single source of truth per search, the agent drafts against whatever it last knew — which is how the wrong rate or the wrong client preference leaks into a reply.
When
Every candidate and client email tied to an open role.
Setup
A profile per hot req holds the client POC, tier, open loops, and the guardrail that the agent never quotes rates.
Result
Drafts and Autopilot actions stay accurate to each search — the model always knows the req.
Every draft grounded in the real req, not a generic guess
Profile: hot req (status, poc, tier)
Open-loop: 3 candidates out
Guardrail: never quote rate
Don't-forget: client wants local only
Staffing
Role spec folder
A screening draft written from memory instead of the actual job description is how candidates who don't fit the spec make it to the client.
When
Any reply that needs the exact job requirements.
Setup
A folder holds the uploaded job description and a text summary of must-haves and nice-to-haves.
Result
Screening and shortlist drafts cite the real spec, not a paraphrase — fewer wrong submissions.
Submissions grounded in the real spec, not a paraphrase
Folder: role spec (PDF)
Item: must-haves (md)
Purpose: fit-check screening replies
Staffing
Rate card file
An agent that can see the rate card but isn't guardrailed from restating it is a compliance problem waiting to land in a client's inbox.
When
Any thread touching bill or pay rate for a client.
Setup
The client's rate card is uploaded as a reference file the agent reads but is guardrailed from ever restating.
Result
The agent stays inside commercial limits without leaking a rate it wasn't told to send.
Commercial limits respected automatically — no accidental rate disclosure
Uploaded file: rate card (DOCX)
Guardrail: don't restate rate
Variable: {bill_rate}
Staffing
Client company brain
A client who prefers video-first rounds and gets a phone-screen proposal reads that as a desk that didn't listen.
When
Any client-facing email for a key account.
Setup
A client profile stores tier, hiring-manager POC, tone preference, and dont-forget notes on their process.
Result
Client mail always reflects that account's preferences — you sound like their embedded recruiter.
Client-facing replies that reflect how they actually like to work
Profile: client company (tier, poc)
Don't-forget: prefers video first round
Tag: vip
Staffing
Screening question set
A desk running at volume will skip screening questions under pressure — consistent bars only hold when they're baked into the tool, not the recruiter's memory.
When
First contact with any new applicant.
Setup
A folder of standard screening questions per role type feeds the copilot's screening drafts.
Result
Every applicant is screened against the same bar; nothing gets skipped in the rush.
Consistent screening bar across every applicant, regardless of how busy the desk is
Folder: screening questions (md)
Purpose: seed screening drafts
Variable: {notice_period}
Staffing
Placement variables
An onboarding email with the wrong start date or work location is the kind of error that erodes a candidate's confidence in the placement before day one.
When
Any onboarding or interview email that needs candidate-specific detail.
Setup
Per-candidate variables hold start date, work location, and the desk owner for merge into drafts.
Result
Onboarding and prep mails auto-fill the right details — no copy-paste, no wrong dates.
Onboarding emails accurate and personalized without manual copy-paste
Variable: {start_date}
Variable: {work_location}
Per-client scope
Staffing
Compliance guardrails
One agent reply that confirms sponsorship it can't deliver, or leaks candidate PII to the wrong party, is a legal and reputational problem no placement fee covers.
When
Any candidate thread touching visa, references, or personal data.
Setup
Global guardrails forbid the agent from confirming sponsorship, sharing candidate PII, or committing terms.
Result
The agent stays compliant by default across every desk and every candidate.
Compliance enforced automatically across every desk, not just when someone remembers
Guardrail: never confirm sponsorship
Guardrail: no candidate PII to third parties
Don't-forget: escalate offers to human
Staffing
Bench pool profile
A bench that isn't actively tracked is just a list of people you'll remember too late, after they've already taken another contract.
When
Any redeployment or availability check.
Setup
A bench profile tracks placeable contractors, their skills, last rate band, and open availability loops.
Result
Redeployment outreach targets the right people fast — your bench is always search-ready.
Bench always search-ready — redeployment starts in seconds, not a manual dig
Profile: bench pool (tags, openLoops)
Open-loop: 2 ending contracts
Variable: {available_from}
Roofing
Service-area guardrail
An agent that offers an inspection date to someone 90 miles outside your radius books a callback your estimator can't keep.
When
Any reply that offers an inspection or install date.
Setup
A global variable holds the service area and a guardrail blocks work outside it.
Result
The agent never books a job the crew can't reach.
Out-of-area commitments blocked before a truck ever rolls out
Variable: {service_area}
Guardrail: decline out-of-area
Don't-forget: no work over 3 stories
Roofing
Warranty terms file
A warranty answer written from memory instead of the actual signed terms is a guess — and a wrong guess becomes a liability when a customer pushes back.
When
A past customer asks what their warranty covers.
Setup
The warranty terms PDF is uploaded so replies quote real coverage, not guesses.
Result
Warranty answers are always grounded in the signed terms.
Warranty answers grounded in the actual terms, not a best guess
Folder: warranty terms (PDF)
Guardrail: don't admit fault
Tier: past-customer
Roofing
Financing options
A financing reply that doesn't match what the office actually offers creates an expectation problem that surfaces at the worst possible moment — when the job is ready to sign.
When
A homeowner asks about payment plans for a replacement.
Setup
The financing-options file lists the real plans the agent can reference.
Result
Financing replies match exactly what the office actually offers.
Financing information accurate every time — no expectation mismatch at signing
Folder: financing options (PDF)
Don't-forget: no interest-rate quotes
Variable: {financing_link}
Roofing
Pricing sheet
A rough range quoted by email that doesn't survive the site visit destroys trust before the real estimate is even delivered.
When
The estimator drafts a ballpark for a common repair.
Setup
A pricing-sheet folder holds per-square and repair ranges as reference-only text.
Result
Rough ranges stay consistent while firm quotes still need a site visit.
Ballpark ranges consistent across the team — no surprises when the real quote arrives
Folder: pricing sheet (MD)
Guardrail: no firm quote by email
Don't-forget: site visit required
Roofing
Adjuster profile
An adjuster who has to re-explain the claim situation on every email thread is an adjuster who thinks you're disorganized.
When
A recurring adjuster emails about an active claim.
Setup
An adjuster profile tracks their carrier, open loops, and preferred contact style.
Result
Every adjuster reply picks up where the last one left off.
Adjuster conversations pick up mid-thread — no re-explaining, no credibility lost
Profile: status + poc + tier
Open-loops: pending claim docs
Tags: insurance
Roofing
Repeat-customer memory
Asking a repeat customer what type of roof you installed for them last time signals that they're a transaction, not a relationship.
When
A homeowner from a prior job emails again.
Setup
Their profile stores the roof installed, materials used, and the completion date.
Result
Follow-ups reference the actual roof — no re-asking what was done.
Repeat customers feel remembered — relationship retained, referrals more likely
Profile: tier + tags
Variables: {roof_type}, {install_date}
Don't-forget: warranty active
Roofing
Brand voice variables
An inconsistent signature or a missing review link in one reply and not another makes a small operation look disorganized to the homeowner reading it.
When
Any homeowner-facing reply the agent drafts.
Setup
Global variables hold the company name, review link, and booking link for consistent signatures.
Result
Every reply signs off the same way with the right links baked in.
Every reply signs off consistently — no missing links, no off-brand signatures
Variable: {company_name}
Variable: {review_link}
Variable: {booking_link}
Roofing
Safety guardrails
An agent that doesn't know the jobs you won't take can book an inspection for a three-story steep-slope torch-down your crew isn't certified or insured to do.
When
A lead asks about steep, multi-story, or metal-roof work.
Setup
Guardrails encode the jobs the crew won't take on so the agent screens them early.
Result
Out-of-scope jobs are flagged before a truck rolls out.
Out-of-scope jobs screened before an estimator is dispatched
Guardrail: no work over 3 stories
Guardrail: no torch-down repairs
Don't-forget: steep-slope surcharge
Med spas
Service-menu file
Without a single source of truth, different staff quote different prices and the inbox becomes a liability.
When
Pricing and treatment questions come in all day.
Setup
The clinic's current service menu is uploaded as a PDF so the agent quotes only real, up-to-date prices.
Result
Every price answer matches the actual menu — no stale numbers, no invented packages.
Consistent, accurate pricing in every reply — one source of truth
Uploaded file: service-menu (PDF)
Variable: {consult_fee}
Guardrail: quote only listed prices
Med spas
Pre-care folder
Ad-libbed pre-care instructions are inconsistent and, in an injectables setting, a patient-safety issue.
When
Booked patients ask how to prepare for injectables or laser.
Setup
A pre-care folder holds the clinic's approved prep sheets so replies use vetted guidance verbatim.
Result
Patients always get the same clinic-approved prep — the agent never improvises medical instructions.
Clinic-approved prep delivered verbatim every time — zero improvisation
Folder: pre-care (text/md)
Guardrail: no medical advice beyond the sheet
Verbatim only
Med spas
Post-care folder
Inconsistent aftercare answers from different staff members undermine patient confidence and create complaint risk.
When
Patients email with aftercare questions in the days after treatment.
Setup
A post-care folder stores approved aftercare sheets, with a guardrail to escalate any reaction wording.
Result
Standard aftercare is answered instantly and consistently; anything clinical routes to a provider.
Consistent aftercare answers — reactions escalated to a provider without delay
Folder: post-care (text/md)
Guardrail: escalate reactions, no diagnosis
Escalate-if: swelling, pain, vision
Med spas
Clinic guardrails
One carelessly worded email reply can expose the clinic to liability that a consultation would have avoided entirely.
When
Any AI-assisted reply could stray into clinical territory.
Setup
A global guardrail forbids diagnosing, promising outcomes, or clearing patients for treatment by email.
Result
No reply ever gives medical advice or guarantees results — clinical calls stay with providers, in consult.
Clinical liability risk in email eliminated across all automated and drafted replies
Guardrail: never diagnose
Guardrail: never promise outcomes
Guardrail: no treatment clearance by email
Med spas
Booking variables
When the fee or booking link changes, every outdated reply costs you a consult or a patient's trust.
When
Replies need the fee, booking link, hours, and location every time.
Setup
Global variables hold the consult fee, booking URL, hours, and address so replies stay accurate and current.
Result
One place to update details; every reply — human or agent — uses the same correct facts.
Update once, every reply accurate — no stale fees or broken links
Variable: {consult_fee}, {booking_link}
Variable: {hours}, {address}
Scope: global
Med spas
VIP patient profile
A regular who has spent thousands at your clinic shouldn't have to re-explain their preference for a specific injector.
When
A returning high-value patient reaches out for maintenance.
Setup
Their profile stores tier, preferred injector, standing preferences, and open loops from prior visits.
Result
Replies feel personal and informed without staff re-reading old threads for every regular.
Personalized replies for high-value regulars, no thread archaeology required
Profile: tier VIP, poc (injector)
openLoops, dontForget
Variable: {preferred_provider}
Med spas
Membership terms
A member told the wrong benefit — even accidentally — becomes a billing dispute that costs more to fix than it was worth.
When
Members ask what their plan covers this cycle.
Setup
Membership benefits and portal link are saved as variables so benefit answers are always accurate.
Result
Members get correct benefit details every time, and billing changes route to a human instead of a wrong promise.
Accurate benefit answers every time — wrong-benefit disputes eliminated
Variable: {membership_benefits}
Variable: {portal_link}
Guardrail: escalate billing changes
Med spas
New-consult profile
A first-time lead handled off-script — wrong fee, wrong tone, wrong link — rarely books.
When
A first-time prospect starts a conversation about a treatment.
Setup
A new-consult context profile sets the tone, offers, and booking flow the agent should follow for cold leads.
Result
Every new lead is greeted with the same warm, on-brand consult flow — nothing improvised, nothing off-message.
Every cold lead receives the same consistent, on-brand consult flow
Profile: status new-lead, tags [cold]
guardrails: no clinical advice
Variable: {promo_details}
Tax prep
Client open loops
Without a live list of what's still outstanding per client, every document-chase email starts with re-reading the file — time you don't have in March.
When
A return is in progress with specific forms still outstanding.
Setup
The client's context profile tracks open loops like 'missing 1099-INT' and 'missing W-2', updated as docs arrive.
Result
Every reply and chase knows exactly what's still needed, without the preparer re-checking the file.
Every chase is precise from the start — no file re-reading, no wrong missing-doc lists
Profile openLoops: missing W-2
Profile openLoops: missing 1099-INT
Guardrail: no tax advice by email
Tax prep
Document checklist folder
Ad-libbed missing-doc lists sent to clients lead to back-and-forth over forms you didn't ask for the first time.
When
The preparer needs the standard intake list for a client type.
Setup
A context folder holds the document checklist as markdown items — W-2, 1099s, receipts, prior-year return.
Result
The agent drafts complete, accurate missing-doc lists straight from the firm's own checklist.
Complete, accurate intake lists sent every time — no ad-libbed or incomplete requests
Folder: doc checklist
Purpose: intake reference
Guardrail: no tax advice by email
Tax prep
No tax advice guardrail
Written tax advice in email — even casually worded — is a professional liability that compounds when volume is too high to review every draft.
When
Any client email that edges toward asking for advice.
Setup
A firm-wide guardrail states advice is never given by email; the agent offers a call or appointment instead.
Result
The whole firm's automated and drafted replies stay safely clear of written tax advice.
Written advice exposure eliminated across every automated and drafted reply firm-wide
Guardrail: no tax advice by email
Guardrail: route advice to a call
dontForget: keep it factual
Tax prep
Engagement-letter file
An outdated engagement letter attached to a welcome email is a scope and liability problem that starts the client relationship on the wrong footing.
When
A client is ready to be onboarded for the year.
Setup
The current engagement letter is uploaded as a PDF the agent attaches when drafting intake replies.
Result
Engagement letters are always the current version, pulled from one source of truth.
Current engagement letter attached every time — no version risk, no manual updates
Uploaded file: engagement letter PDF
Variable: taxYear
Folder: onboarding
Tax prep
Client tier and POC
A business client handed to the wrong preparer or handled at the wrong service level is a relationship problem that surfaces at the worst time.
When
An email arrives from a client the firm handles at a specific service level.
Setup
The profile records tier (e.g. business, individual) and the point of contact so routing and tone fit.
Result
High-tier clients get the right preparer and register in the correct priority lane automatically.
Every client handled at the right tier and routed to the right preparer without manual lookup
Profile tier: business
Profile poc: lead preparer
Profile tags: vip
Tax prep
Season variables
A reply with last year's filing deadline or a wrong tax year is the kind of small error that erodes confidence fast in a compliance-sensitive relationship.
When
Any reply that references dates, deadlines, or the current tax year.
Setup
Global variables hold the filing deadline, extension deadline, and current tax year for the agent to reference.
Result
Every drafted message uses the correct season dates without anyone editing them into each reply.
Correct dates and deadlines in every reply — one update, no per-message editing
Variable: filingDeadline
Variable: extensionDeadline
Variable: taxYear
Tax prep
Organizer on file
An organizer attached from memory or a saved email draft risks being last year's version — a small error that creates confusion before intake even starts.
When
A returning client is being reminded to start their organizer.
Setup
The blank tax organizer is uploaded as a DOCX/PDF the agent attaches to kickoff reminders.
Result
Organizers go out from a single stored template, correct and consistent every send.
Current organizer version sent every time — one upload, consistent all season
Uploaded file: organizer DOCX
Folder: onboarding
Variable: taxYear
Tax prep
Life-event notes
A client who mentions a marriage or new child mid-thread expects you to remember it — and acting on it automatically would be the wrong move.
When
A client mentions a marriage, new child, or home purchase.
Setup
The profile's dontForget notes flag life events so the agent surfaces them to the preparer rather than acting on them.
Result
Material life changes are captured for the human to handle, never answered automatically.
Life events flagged for the preparer every time — never auto-handled or forgotten
Profile dontForget: life event flagged
Guardrail: no tax advice by email
Escalate to preparer
Shopify
Returns policy folder
An agent that invents return windows or conditions contradicts your actual policy — and customers who catch the inconsistency lose trust fast.
When
The agent needs to answer return and exchange questions consistently.
Setup
Upload your shipping & returns policy as Markdown so every reply cites the real window, conditions, and label process.
Result
Return answers are always policy-accurate — no more contradicting yourself across tickets.
Policy-accurate return answers across every ticket — zero contradictions
Folder: returns policy (MD)
Uploaded: shipping-and-returns.md
Guardrail: refunds need approval
Variable: {return_window}
Shopify
Product FAQ file
Without a single source for sizing, materials, and care, pre-sale answers get inconsistent — and an inaccurate claim about materials or durability is a return waiting to happen.
When
Pre-sale and care questions repeat across products.
Setup
Upload a product FAQ (materials, sizing, care, waterproofing) as a Markdown file the agent reads before replying.
Result
Sizing and product questions get instant, on-brand answers that lift conversion.
Consistent, on-brand product answers that build trust and convert pre-sale visitors
Folder: product FAQ (MD)
Uploaded: product-faq.md
Variable: {size_chart_url}
Guardrail: no unverified claims
Shopify
VIP customer profile
A repeat customer who spent thousands with you shouldn't feel like a first-time ticket number when they reach out.
When
A repeat, high-LTV customer contacts support.
Setup
A VIP profile stores their status, tier, order history notes, and a don't-forget on white-glove handling.
Result
Top customers get recognized instantly and handled with the care their loyalty earns.
High-LTV customers recognized immediately and handled with the care their loyalty earns
Profile: VIP customer (tier: VIP)
Don't-forget: offer free expedited reship
Tag: vip
Guardrail: escalate disputes to owner
Shopify
Discount policy variable
When discount answers aren't anchored to a real policy, different replies leak margin in different directions — and there's no consistent story for customers asking.
When
Shoppers keep asking for coupon codes.
Setup
A global variable holds your standing sign-up offer so the agent always points there instead of inventing codes.
Result
Discount replies are consistent and margin-safe across every conversation.
Consistent, margin-safe discount answer across every conversation — no codes invented
Variable: {signup_offer} (global)
Guardrail: never create custom codes
Folder: promo policy (MD)
Don't-forget: mention the newsletter
Shopify
Shipping & ETA rules
An over-promised delivery window is the fastest way to generate a WISMO ticket from a customer who was otherwise happy to wait.
When
WISMO replies need accurate processing and carrier windows.
Setup
Per-region shipping variables and cutoff times let the agent quote honest delivery estimates.
Result
Every order-status answer gives a realistic ETA, cutting anxious follow-ups.
Honest, realistic ETAs in every reply — fewer anxious follow-ups from over-promised windows
Variable: {processing_days}
Variable: {carrier_eta}
Folder: shipping policy (MD)
Guardrail: never over-promise delivery
Shopify
Wholesale line sheet
A B2B lead that asks the right qualifying questions gets a fast, professional reply — one that improvises gets an awkward back-and-forth that stalls the deal.
When
B2B buyers ask about bulk pricing and terms.
Setup
A wholesale folder holds the line sheet PDF, minimums, and qualifying questions the agent uses for B2B leads.
Result
Wholesale inquiries get a professional, complete reply that qualifies the lead up front.
Wholesale leads qualified up front with a professional reply — no improvised back-and-forth
Folder: wholesale (PDF)
Uploaded: line-sheet.pdf
Variable: {min_order_qty}
Guardrail: pricing to owner only
Shopify
Damaged-item playbook
Without a defined resolution ladder, damage claims get handled differently every time — some customers get a full refund while others get asked to wait, and both outcomes feel wrong.
When
Customers report broken or defective goods.
Setup
A resolution playbook sets the goodwill ladder — replacement first, refund with approval — and the photo request script.
Result
Damage claims are handled generously and consistently within the limits you set.
Damage claims handled generously and consistently — resolution policy applied every time
Folder: resolution playbook (MD)
Guardrail: refunds need approval
Don't-forget: always request a photo
Variable: {goodwill_cap}
Shopify
Brand voice guardrails
Automated replies that sound robotic or off-tone erode the brand equity you've spent real money building — customers notice when support sounds like a different company.
When
Every reply needs to sound like your brand.
Setup
A voice profile encodes your friendly-but-honest tone, banned phrases, and open loops the agent must never drop.
Result
Support reads on-brand every time, so automation never feels robotic or off-voice.
On-brand support across every automated and drafted reply — automation that sounds like you
Profile: brand voice
Guardrail: no hype, no false urgency
Don't-forget: sign off with the team name
Variable: {brand_name}
Agencies
Per-client profiles
Handling a dozen clients without a shared source of truth means each reply is only as good as whoever happens to write it that day.
When
You run a dozen clients, each with a different POC, tier, and open loops.
Setup
A context profile per client holds status, POC, tier, tags, open loops, and don't-forget notes that drive every draft and rule.
Result
The agent knows each client's state cold, so replies and routing are always account-accurate.
Every reply account-accurate — regardless of who's handling the inbox
Per-client profile: Acme
POC + tier + status
Open loops tracked
Guardrail: no new scope without PM
Agencies
Brand-guide folders
Drafting in the wrong client's voice — too casual for the enterprise account, too stiff for the DTC brand — damages trust.
When
Each client has distinct voice, terminology, and do-not-say rules.
Setup
A context folder per client stores their brand guide and tone notes as text and uploaded PDFs the agent reads before drafting.
Result
Copilot drafts in each client's exact brand voice because the guidelines live in that client's context.
On-brand drafts for every client, pulled from their own guidelines
Folder: brand guide (PDF)
Purpose: voice + terminology
Per-client scoped
Do-not-say list
Agencies
SOW guardrails
Without a hard boundary in the system, scope commitments creep in through casual replies before the PM ever sees them.
When
You need the agent to refuse anything beyond the signed statement of work.
Setup
The client profile carries a hard guardrail — no scope commitments — backed by the uploaded SOW document.
Result
The agent enforces scope boundaries automatically, escalating anything the SOW doesn't cover.
Scope boundaries enforced at the reply level — before commitments are made
Uploaded file: SOW (DOCX)
Guardrail: no new scope without PM
Per-client profile
Escalate-if: scope, add
Agencies
Billing variables
Billing replies that reference the wrong PO number or payment terms slow down payment and erode professionalism.
When
Clients ask for PO numbers, payment terms, and invoice contacts.
Setup
Per-client variables store billing contact, PO number, and net terms the agent reads to answer FAQs and draft accurately.
Result
Billing questions are answered from stored facts, so numbers are always right and never guessed.
Billing details pulled from one accurate source — no manual lookup
Variables: {poNumber, netTerms}
Per-client scoped
Feeds invoice replies
Guardrail: no fee waivers
Agencies
Open-loop tracking
When you're across five clients at once, the approval that's been waiting three days is the one you forget to nudge.
When
Multiple deliverables and approvals are in flight per client.
Setup
Each client profile's open-loops list captures what's pending — awaiting approval, in review, blocked — feeding status drafts and nudges.
Result
Status updates and follow-ups write themselves from live open loops, so nothing pending slips.
Nothing in flight goes untracked or un-followed-up
Per-client profile: BetaCo
Open loops: pending approvals
Feeds status drafts
Don't forget: renewal date
Agencies
Global agency voice
Without a default style guide in the system, house tone varies by whoever replies — which reads as inconsistency to clients.
When
You want a consistent house style across clients that don't specify their own.
Setup
A global variable set and voice profile define the agency's default tone, used whenever a client has no override.
Result
Every reply defaults to a polished agency house style, with per-client voices layered on top where defined.
Consistent house voice on every reply — per-client overrides win
Variables: global (house voice)
Voice: professional default
Per-client overrides win
Consistent signature
Agencies
Onboarding playbook
A kickoff email written from memory is rarely as complete as one written from the actual onboarding checklist.
When
Every new client needs the same kickoff steps, contacts, and asset requests.
Setup
A context folder holds the onboarding playbook as markdown items the agent uses to draft kickoff and intake emails.
Result
New-client kickoffs are complete and consistent because the playbook drives the draft every time.
Every new client gets the same thorough kickoff — nothing skipped
Folder: onboarding (MD)
Purpose: kickoff steps
Feeds kickoff drafts
Don't forget: asset checklist
Agencies
Tier-based routing
Treating a six-figure retainer client the same as a small one-off project is a service-level mismatch clients notice.
When
Tier-1 retainers deserve faster, higher-touch handling than one-off projects.
Setup
The client profile's tier field drives priority — tier-1 gets vip tagging and escalation, lower tiers route normally.
Result
Attention is allocated by client value automatically, so your best accounts always get the fastest response.
Highest-value clients get the fastest, highest-touch handling — automatically
Per-client profile: tier field
Tier-1: vip + escalate
Feeds rules + Autopilot
Guardrail: tier-1 escalate on delay
Sales teams
Named-account profile
Without a single source of truth for a strategic account, every rep touches the thread differently and consistency evaporates.
When
You start working a strategic account with multiple stakeholders.
Setup
An account profile tracks tier, point-of-contact, open loops, and a discounts-via-deal-desk guardrail.
Result
Every draft to this account stays on-strategy and within pricing policy.
Consistent, on-strategy replies across every account touchpoint
Per-account profile
Profile tier: enterprise
Guardrail: discounts via deal desk
Sales teams
Battlecards folder
A competitor comparison in a live email thread deserves your sharpest rebuttal — not whatever you can improvise under pressure.
When
A prospect raises a competitor comparison mid-thread.
Setup
A context folder holds your markdown battlecards the agent reads while drafting.
Result
Objection replies stay sharp, accurate, and on-message every time.
Every objection handled with the right battlecard, not improvised
Context folder: battlecards
Items: markdown
Purpose: objection handling
Sales teams
Pricing sheet file
Without a single source, pricing answers vary by rep and thread — which plants doubt in the buyer's mind.
When
A buyer asks for list pricing or plan tiers before a call.
Setup
You upload a pricing-sheet PDF into a context folder the agent references while drafting.
Result
Pricing answers stay grounded and consistent across every prospect.
One consistent pricing answer across every rep and thread
Uploaded file: pricing sheet (PDF)
Context folder: Pricing
Guardrail: no unapproved discounts
Sales teams
Security overview file
Security diligence questions come up in every mid-market and enterprise deal, and re-typing the same answers burns time you don't have.
When
A buyer asks about SOC 2, data handling, or your security posture.
Setup
You upload a security-overview PDF the agent reads to answer diligence questions.
Result
Security questions get accurate, consistent answers without a re-type.
Diligence answered instantly, from a single source of truth
Uploaded file: security overview (PDF)
Context folder: Security
Purpose: diligence answers
Sales teams
Follow-up cadence folder
Your follow-up messaging drifts between reps and between busy weeks — and buyers notice the inconsistency.
When
A prospect goes quiet and it's time for the next touch.
Setup
A context folder holds your cadence steps and messaging the agent drafts from.
Result
Follow-ups stay consistent and on-cadence across your whole pipeline.
On-cadence follow-ups, automatically consistent
Context folder: Cadence
Items: markdown steps
Purpose: follow-up drafting
Sales teams
Renewal-date variable
Looking up a renewal date mid-draft breaks the flow and risks a reply that references the wrong timeline.
When
An account asks about timing or their contract anywhere in a thread.
Setup
A per-account variable holds the renewal date so the agent references it while drafting.
Result
Renewal dates stay accurate in every reply without you looking them up.
Accurate renewal dates in every reply, automatically
Variable: {renewal_date}
Per-client scope
Profile status: active
Sales teams
Booking-link variable
Inconsistent booking links in replies — wrong URL, outdated calendar, or missing the link entirely — create friction at the worst moment.
When
Any prospect asks when they can meet.
Setup
A global variable stores your scheduling link so it drops into drafts consistently.
Result
Prospects always get the same working booking link, worded the same way.
Correct booking link, every reply, zero manual lookup
Variable: {booking_link}
Global scope
Purpose: self-scheduling
Sales teams
Deal-desk guardrail
A discount committed in an email thread, before the deal desk is looped in, is a margin problem that's hard to walk back.
When
A buyer pushes for a discount or custom terms mid-thread.
Setup
A profile guardrail instructs the agent to route pricing concessions to the deal desk.
Result
You stay within pricing policy automatically, with concessions handed back to you.
Pricing policy enforced on every thread without manual vigilance
Guardrail: discounts via deal desk
Escalate-if: discount, terms
Route to me
Support
KB article library
Agents answering from memory rather than approved documentation introduce inconsistency that frustrates customers who've already read the docs.
When
Agents and the AI need the current, approved help content to answer accurately.
Setup
Your help docs and how-to guides live in a context folder as Markdown the agent draws from.
Result
Every reply reflects the real documentation, so customers never get outdated steps.
Every answer grounded in the same approved documentation
Folder: KB articles (MD)
Purpose: answer how-to questions
Uploaded files: help docs
Support
Enterprise account profile
An enterprise customer whose contract terms aren't in the system gets a reply that treats them like a standard plan user.
When
An enterprise customer writes in and needs replies aware of their tier and terms.
Setup
A context profile stores their tier, SLA terms, and open loops, with a guardrail on refunds.
Result
Responses match the account's contract and never make commitments above an agent's authority.
Enterprise replies contract-aware — no generic treatment for paying accounts
Profile: enterprise tier
Guardrail: refunds need lead approval
openLoops tracked
Support
Refund policy guardrail
Without a system-level guardrail, refund decisions vary by agent — and customers who compare notes notice.
When
Any reply that touches money must stay inside policy.
Setup
A global guardrail routes refund and credit decisions to a lead before anything is committed.
Result
The AI can draft freely while every money decision still passes through a human.
Consistent refund policy enforced on every thread — no agent discretion drift
Guardrail: refunds need lead approval
Variable: {refund_window}
Scope: global
Support
Canned macro folder
Without a shared macro library, each agent copies from different sources — and the inconsistency reaches the customer.
When
Common tickets deserve consistent, on-brand answers every time.
Setup
A context folder holds your approved reply macros as text snippets the agent reuses.
Result
Routine responses stay consistent across the whole team without copy-paste drift.
One approved macro used consistently by every agent — no drift
Folder: reply macros (text)
Purpose: consistent answers
Reused by all agents
Support
Product spec docs
A technical reply that gets a limit or setting wrong forces a follow-up correction — and the customer loses confidence in both answers.
When
Technical questions require accurate limits, settings, and behavior details.
Setup
Uploaded product specs and integration docs give the agent ground truth for technical replies.
Result
Deep technical answers stay correct instead of guessing at how the product works.
Technical replies grounded in the actual spec — no educated guessing
Uploaded files: product spec (PDF)
Purpose: technical accuracy
Folder: docs
Support
Status URL variable
An incident reply that points to the wrong status URL — or no URL — makes a bad situation harder to manage.
When
During incidents, customers need a single consistent status link.
Setup
A global variable stores the current status page URL for reuse across every reply.
Result
Incident responses point to one source of truth without agents hunting for the link.
Every incident reply points to the same correct status URL
Variable: {status_url} (global)
Purpose: incident consistency
Scope: global
Support
SLA response targets
An agent who doesn't know the customer's SLA tier can't prioritize correctly — and the breach happens before anyone realizes.
When
Different customer tiers carry different response-time commitments.
Setup
A profile records each tier's SLA target and dontForget notes so replies respect the clock.
Result
Agents and the AI stay aware of what each customer is owed and by when.
SLA obligations visible on every ticket — no missed targets
Profile: tier + SLA target
dontForget: SLA clock
Variable: {sla_hours}
Support
Escalation contacts
An escalation that reaches the wrong person — or bounces looking for the right one — delays resolution and strains an already tense situation.
When
Some issues must reach engineering or a lead by name, fast.
Setup
A context folder lists escalation owners and paths so routed tickets go to the right person.
Result
Escalations land with the correct owner instead of bouncing around the team.
Escalations reach the right owner directly — no bouncing
Folder: escalation paths (MD)
Purpose: route to engineering
Variables: {oncall_lead}
Founders
Lead investor profile
Every draft to your lead investor starts with mental re-loading of the relationship, the round status, and what they care about.
When
Any thread with your lead investor is being drafted.
Setup
A Context profile for your lead investor holds their preferences, your live round status, and communication dos and don'ts.
Result
Every draft to your lead reflects the real state of the raise and their preferred style, no re-briefing.
Investor drafts land fully briefed, not reconstructed from memory.
Profile: lead investor
Variable: {round_status}
Don't-forget: prefers Notion over email
Founders
Key-customer brains
Asking a key customer "which plan are you on again?" erases the trust you've built.
When
You reply to one of your top accounts.
Setup
A per-client profile stores each key customer's contract stage, main contact, and open issues as folder items.
Result
Replies land with full account memory: no asking "which plan are you on again?"
Key accounts feel known, every reply.
Profile: key customer
Variable: {contract_stage}
Folder: open issues
Founders
Fundraise variables
Stale or inconsistent metrics across investor emails undermine your credibility at the worst moment.
When
Any investor-facing reply that references the round.
Setup
Global variables hold your current metrics, round terms, and target close so drafts stay accurate everywhere.
Result
Update the numbers once; every future draft uses the current figures instead of a stale copy-paste.
Metrics stay consistent across every investor touchpoint.
Variable: {mrr}
Variable: {round_size}
Variable: {target_close}
Founders
Pitch deck notes
When an investor asks a question the deck already answers, you shouldn't have to dig for the right slide to cite.
When
An investor asks a question the deck already answers.
Setup
Your pitch deck and a notes doc are uploaded to the Context brain (PDF/DOCX) so the agent can cite your real narrative.
Result
Answers stay perfectly on-message with the deck, without you digging up the right slide.
Every deck-answerable question gets a consistent, on-narrative reply.
Uploaded: pitch-deck.pdf
Uploaded: deck-notes.docx
Folder: fundraise
Founders
Company FAQ folder
Repeat questions get improvised answers that drift from your approved messaging over time.
When
A cold lead or customer asks a common question.
Setup
A folder of FAQ text and an uploaded FAQ doc give the agent your standard, approved answers.
Result
Repeat questions get consistent, correct answers every time, in your words, not improvised ones.
Standard answers stay on-message every time, not just when you're paying attention.
Folder: company FAQ
Uploaded: faq.pdf
Don't-forget: never quote roadmap dates
Founders
Hiring context
Inconsistent candidate communication across a fast-moving funnel makes the company look chaotic.
When
Any reply on an open-role thread.
Setup
A Context folder holds the role's comp band, must-haves, and interview loop so candidate replies stay accurate.
Result
Candidate communication is consistent across the pipeline, even when you're moving fast.
The hiring process looks organised even when the company is in full sprint.
Folder: open roles
Variable: {comp_band}
Don't-forget: don't confirm start dates
Founders
Founder voice guide
AI drafts that don't sound like you create a review step that takes longer than writing from scratch.
When
Any Copilot draft written on your behalf.
Setup
A global voice profile captures how you actually write: short sentences, no filler, your signature sign-off.
Result
Drafts sound like you wrote them, not like a template, so approving is a formality.
Approval becomes a quick read, not a full rewrite.
Variable: {sign_off}
Don't-forget: no corporate jargon
Folder: voice samples
Founders
Deep-work profile
Non-urgent mail surfacing during a focus block costs more attention than the mail itself is worth.
When
Non-urgent mail arrives during a focus block.
Setup
A personal context notes your focus hours and priorities so the agent knows what to snooze and what to surface.
Result
Your deep-work time is protected by default; only the genuinely urgent breaks through.
Focus blocks stay unbroken by default.
Variable: {focus_hours}
Don't-forget: protect mornings
Folder: priorities
Assistants
Scheduling preferences
A proposed time slot that violates the exec's standing preferences creates a correction round you could have avoided.
When
Copilot drafts a scheduling reply and needs to know how the exec likes to meet.
Setup
A folder holds the exec's scheduling preferences — no meetings before 10am, 25-minute default, no Fridays — as text items the agent reads before proposing times.
Result
Every proposed slot already respects the exec's rules, so you rarely have to correct a draft.
Scheduling drafts come back correct the first time.
Folder: scheduling preferences (md)
Variable: {exec_calendar_link}
Guardrail: no meetings before 10am
Assistants
Board member profiles
A reply to a board member in the wrong register — too casual, too formal, missing important context — is a mistake that's visible to the exec.
When
Board and investor mail needs replies that reflect each relationship.
Setup
Profiles for each board member and key investor capture role, tone, and history so Copilot drafts land in the right register.
Result
Replies to the board read as informed and appropriately deferential without you rewriting them.
Board replies land in the right register without a rewrite from you.
Profile: board members
Profile: key partners
Guardrail: escalate board to EA + exec
Assistants
Travel prefs on file
Having to re-ask the exec their seat preference for every trip is a detail that should be settled once.
When
Trip coordination needs the exec's flight, hotel, and seating standards.
Setup
An uploaded travel-preferences PDF — airline status, seat, hotel tier, TSA numbers held privately — grounds every travel draft.
Result
Travel replies gather the right details first time, with no back-and-forth to relearn preferences.
Travel coordination is right the first time, every trip.
Folder: travel prefs (PDF)
Guardrail: never share home address
Guardrail: never expose TSA/passport numbers
Assistants
Calendar link variable
Sharing the wrong booking URL — or a raw calendar — in a scheduling reply is a small error with a long tail.
When
Scheduling drafts need to offer a way to book without exposing internals.
Setup
A global variable stores the exec's approved public booking link so every draft points to the same safe URL.
Result
Scheduling replies share one consistent, sanctioned link — never a raw calendar or private detail.
Every scheduling reply uses the right, approved link automatically.
Variable: {exec_calendar_link}
Global scope
Guardrail: only the public link, never the calendar
Assistants
Per-principal voice
Managing two principals whose emails blur together in tone is the kind of mistake that reaches the wrong exec.
When
You run more than one principal's inbox and each writes differently.
Setup
Per-client context profiles carry each exec's voice, signature, and dos/don'ts so drafts never blur between the two.
Result
Each principal's mail sounds like them — one EA, two distinct, consistent voices.
Two principals, two distinct voices — no blurring between inboxes.
Profile: per-principal (per-client)
Variable: {exec_signature} per-client
Guardrail: never cross-reference principals
Assistants
Decline playbook
The exec who declines the same categories of request constantly needs those nos to be consistent and warm every single time.
When
The exec turns down speaking, press, and intro requests constantly.
Setup
A folder of decline templates and standing reasons lets Copilot draft graceful nos that match how the exec actually says no.
Result
Declines are fast, warm, and on-message without you writing each from scratch.
Every decline sounds like the exec, not a generic brush-off.
Folder: decline playbook (md)
Guardrail: always leave the door open
Do: thank the sender
Assistants
Expense routing rules
A receipt that routes to the wrong cost centre or approver creates a correction trail that outlasts the original expense.
When
Receipts and invoices need to reach the right cost center and approver.
Setup
A folder of expense-routing notes — which card, which approver, which project code — informs how receipts get tagged and forwarded.
Result
Receipts route to the correct owner and code every time, cutting the month-end reconciliation.
Every receipt reaches the right approver and code on the first pass.
Folder: expense routing (md)
Variable: {finance_inbox} per-client
Guardrail: never share card numbers
Assistants
Confidential guardrails
One draft that accidentally includes the exec's home address or personal cell is a trust failure you can't walk back.
When
Any draft risks leaking the exec's private details to an outside sender.
Setup
A standing guardrail set forbids sharing home address, personal cell, family details, and financial specifics, applied across every profile.
Result
No draft ever exposes protected personal information, no matter who is asking or how the request is phrased.
Private details are protected by default across every draft, every time.
Guardrail: never share home address
Guardrail: never share personal cell
Guardrail: never share financials
Freelancers
Per-client rate card
Misquoting a client's agreed rate because you had to reconstruct it from memory is a credibility hit you can't easily repair.
When
You reply to a client about pricing or a quote.
Setup
Each client profile stores their agreed hourly rate as a variable, so quotes and proposals pull the right number every time.
Result
You never misquote a client or dig through old emails for their rate.
Every quote pulls from the agreed rate, not from memory.
Per-client profile
Variable: {hourly_rate}
Guardrail: no scope creep without a change order
Tier: retainer / project
Freelancers
Project deadline memory
A deadline answer that doesn't match what you actually committed to is the kind of error that snowballs.
When
A client asks when their work will be ready.
Setup
The client profile holds the current project deadline as a variable and any open loops so replies are accurate.
Result
Deadline answers are always current — no scrolling to reconstruct the timeline.
Deadline replies are always accurate, not reconstructed on the fly.
Per-client profile
Variable: {project_deadline}
Open loops tracked
Don't-forget: deposit before start
Freelancers
Client tone guardrails
Replying in the wrong register to a formal client after a casual one is the kind of slip that's hard to blame on being busy.
When
You draft a reply to a formal versus a casual client.
Setup
Each profile records the client's preferred tone and point of contact so drafts match how they like to be spoken to.
Result
Every client feels like you know them, even when you're juggling ten at once.
Every client gets the tone they expect, every reply.
Per-client profile
POC + preferred tone
Guardrail: match client voice
Tags: formal / casual
Freelancers
Rate-card file
A proposal built from a stale or remembered rate rather than your actual card invites scope and pricing disputes.
When
You need standard pricing for a new proposal.
Setup
Your rate card lives as an uploaded PDF the agent reads, so quotes stay consistent with your published pricing.
Result
Proposals always reflect your real rates, never a stale figure.
Proposals always start from your real, current pricing.
Uploaded file: rate-card.pdf
Global variable: {day_rate}
Guardrail: never quote below floor
Folder: Pricing
Freelancers
SOW template folder
Every statement of work written from a blank document risks missing a clause that protects you later.
When
A lead is ready for a statement of work.
Setup
A folder holds your SOW template and reusable scope clauses as markdown items the agent drafts from.
Result
New SOWs start from your proven boilerplate, not a blank doc.
Every SOW starts from proven boilerplate, not a blank page.
Folder: SOW (purpose: proposals)
Uploaded file: sow-template.docx
Items: scope, terms, revision policy
Per-client variables merged
Freelancers
Payment-terms guardrail
Starting work before the deposit is paid is a boundary that breaks one friendly email at a time.
When
A client asks to start before paying the deposit.
Setup
A global guardrail encodes your terms — 50% deposit, net-15 — so no reply ever agrees to start on spec.
Result
Your payment terms hold on every thread without you policing them.
Payment terms hold automatically; you never agree to start on spec.
Global variable: {deposit_pct}
Guardrail: no work before deposit
Don't-forget: net-15 terms
Folder: Billing
Freelancers
Open-loops per client
Coming back to a client thread after a few days and not remembering what you promised is the thing that quietly erodes trust.
When
You return to a client thread after a few days away.
Setup
Each profile tracks open loops and don't-forget items so nothing pending slips when you context-switch.
Result
Switching between clients stops dropping the small promises that build trust.
Nothing promised to a client slips through a context switch.
Per-client profile
Open loops list
Don't-forget items
Status: active / paused / wrapped
Freelancers
Availability variable
Capacity answers that don't match your actual calendar lead to double-bookings you can't easily undo.
When
Anyone asks whether you can take on new work.
Setup
A global availability variable holds your next open slot, updated as your calendar fills, feeding accurate capacity answers.
Result
Capacity questions get a truthful date every time, across all clients.
Capacity answers are always accurate, not optimistic guesses.
Global variable: {next_open_slot}
Guardrail: don't overbook
Don't-forget: buffer between projects
Folder: Availability
Personal
Family profile
Drafts to family read stiff and generic because the AI has no idea who these people actually are to you.
When
You reply to a sibling or parent and want the tone and details to just fit.
Setup
A family profile holds who's who, nicknames, and the warm, casual voice you use with them.
Result
Drafts to family sound like you, not a template — Copilot already knows the relationship.
Replies to family sound like you wrote them, not a form letter
Profile: family
Voice: warm
Don't-forget: use nicknames
Personal
Landlord profile
Every email to your landlord requires you to look up your unit number, lease dates, or account details from scratch.
When
Anything from your landlord — rent, repairs, lease questions.
Setup
A landlord profile keeps your unit number, lease dates, and a direct, on-record tone in one place.
Result
Replies to your landlord are accurate and businesslike without you re-typing the details.
Landlord replies accurate and on-record without digging for details each time
Profile: landlord
Voice: direct
Variable: {home_address}
Personal
Doctor profile
Medical email replies risk omitting the one health detail that changes everything if the AI doesn't know to surface it.
When
Emails from your clinic, pharmacy, or a specialist's office.
Setup
A doctor profile carries a critical safety note the agent must always surface when relevant.
Result
Medical replies never drop the detail that matters most — it's front of mind, every time.
Critical health context surfaces in every medical reply — never dropped
Profile: doctor
Don't-forget: allergic to penicillin
File: insurance card (PDF)
Personal
Home address variable
You retype your address into emails more often than you'd like, and a fat-fingered digit is easy to miss.
When
A delivery, service, or form email asks where to send or come to.
Setup
A global {home_address} variable lets any draft drop in the right address consistently.
Result
You never re-type your address or fat-finger a digit — it's one saved value everywhere.
Address consistent and correct in every draft — one save, zero re-typing
Variable: {home_address}
Global — reusable in any draft
Don't-forget: apartment number
Personal
Kids' school variable
School coordination emails need specific names, grades, and teacher details you have to remember or look up each time.
When
Any coordination email about pickup, events, or classmates.
Setup
A {kids_school} variable stores the school name, teacher, and grade for quick, correct replies.
Result
Carpool and school notes go out with the right names and times — no second-guessing.
School details always correct in drafts — no second-guessing names or grades
Variable: {kids_school}
Global — reusable in any draft
Don't-forget: teacher's name
Personal
Travel itinerary folder
When someone emails about your trip, replying accurately means hunting down the confirmation PDF you filed three weeks ago.
When
An email that touches your upcoming trip — a change, a question, a check-in.
Setup
A travel folder holds this trip's itinerary PDF and notes so the agent can answer from real details.
Result
Replies about your trip reference the actual flight and hotel, not a vague guess.
Trip replies grounded in real details — no vague guessing about flights or hotels
Folder: travel itinerary (PDF)
Don't-forget: seat preference
Purpose: current trip
Personal
Household folder
Provider emails asking for your policy number or account reference send you on a hunt through old mail or paper files.
When
Emails about utilities, insurance, warranties, or the car.
Setup
A household folder collects account numbers and policy notes as text and markdown items.
Result
The boring-but-important details are one place away when a provider asks for them.
Account numbers and policy details always one lookup away — no paper hunt
Folder: household (text + md)
File: insurance card (PDF)
Don't-forget: policy number
Personal
Preferences memory
You state the same preferences — dietary needs, call times, scheduling constraints — in email after email because nothing remembers them.
When
Any reply where a standing preference of yours should shape the answer.
Setup
A few don't-forget notes capture the things you always say — dietary needs, best times, no-calls.
Result
Your drafts quietly honor your preferences without you restating them in every email.
Standing preferences baked into every draft — never state them again
Don't-forget: vegetarian
Don't-forget: no calls before 9am
Global — applies everywhere
Property mgmt
Per-property guardrails
Your agent sends the wrong emergency contact for a building because the right details live in an email thread from six months ago.
When
Replies about a specific building need the right rules, contacts, and quiet hours.
Setup
A client profile per property stores the POC, tier, open loops, and guardrails the agent must respect.
Result
Every reply reflects that property's specifics without you re-explaining them each time.
Replies are accurate to the property from day one — no re-explaining the same details
Profile: property POC + tier
Guardrails: quiet hours
Open loops
Don't-forget notes
Property mgmt
Lease terms folder
Tenants ask about pet policy or late fees and you're paraphrasing from memory instead of citing the actual signed lease.
When
Tenants ask about pet policy, parking, late fees, or renewal windows.
Setup
A context folder holds each lease and policy doc as PDF and Markdown items the agent can cite.
Result
Policy answers are accurate and consistent, pulled straight from the signed lease.
Policy answers cite the real lease — consistent every time, defensible if challenged
Folder: lease + policies
Items: PDF, Markdown
Purpose: policy answers
Uploaded files
Property mgmt
Property variables
Every templated reply needs the right portal link and after-hours number for each site — and pasting the wrong one erodes trust.
When
Routine replies need the office hours, portal link, and emergency line for each site.
Setup
Per-property variables store the payment portal, after-hours number, and office address as reusable values.
Result
Drafts drop in the correct contact details automatically instead of you copy-pasting them.
Right details in every reply automatically — no copy-paste errors across properties
Variable: {payment_portal_url}
Variable: {after_hours_line}
Per-client scope
Global fallbacks
HVAC
Service-area guardrail
An automated reply that books a job outside your service radius creates a customer problem you have to unwind personally.
When
Any reply that offers a service or install appointment.
Setup
A global variable holds the service area and a guardrail blocks booking outside it.
Result
The agent never dispatches a truck to a job the crew can't reach.
No out-of-area booking slips through to become a customer service problem.
Variable: {service_area}
Guardrail: decline out-of-area
Don't-forget: after-hours surcharge
HVAC
Equipment history memory
Asking a repeat customer what unit they have when you installed it is the kind of thing they remember when choosing someone else next time.
When
A repeat customer emails again about their system.
Setup
Their profile stores the installed brand, model, install date, and warranty status.
Result
Replies reference the actual equipment — no re-asking what's on the pad outside.
Repeat customers get replies that show you know their system, not a blank-slate response.
Profile: tier + tags
Variables: {system_brand}, {install_date}
Don't-forget: warranty status
HVAC
Diagnostic and dispatch fees
If your diagnostic-fee answer varies by who answers the phone, you're setting up disputes before a tech even arrives.
When
A homeowner asks what a service call costs before booking.
Setup
A pricing-sheet folder holds the diagnostic fee, after-hours rate, and common ranges as reference-only text.
Result
Fee answers stay consistent while firm repair quotes still wait for a tech on-site.
Every fee inquiry gets the same accurate number, whoever handles it.
Folder: pricing sheet (MD)
Guardrail: no firm repair quote by email
Variable: {diagnostic_fee}
Plumbing
Commercial-account profile
Sending a quote to a net-30 PO account without a PO number means either a disputed invoice or a conversation you have to restart.
When
A regional property manager emails about a clogged main at one of their buildings.
Setup
Client profile: status active, tier VIP, poc the facilities lead. Variables: net-30 terms, PO required. Guardrails: never quote without a PO number.
Result
Every reply to that account respects net-30 and the PO rule automatically — no re-explaining your terms.
Commercial billing terms are applied correctly every time without anyone having to remember.
tier VIP
poc facilities lead
variables: net-30, PO required
guardrails: no quote without PO
Plumbing
Service-area & rates folder
Quoting a trip charge from memory and getting it wrong sets up a dispute before the tech even knocks on the door.
When
A prospect asks 'do you service my zip, and what's your trip charge?'
Setup
Context folder (Markdown): service-area zip list, standard trip charge, after-hours rate, emergency surcharge. Purpose: pricing reference.
Result
Drafts pull your real service radius and rate card, so quoted numbers match what you actually charge.
Trip-charge and area answers come from your real rate card, not whoever happened to reply.
folder purpose: pricing reference
md: service-area zips
variables: trip charge, after-hours rate
Plumbing
Warranty terms on file
Warranty answers that vary by who replies are the ones that become arguments when the customer quotes something back to you.
When
A customer asks whether last year's fixture install is still covered.
Setup
Uploaded file (PDF): workmanship-warranty terms. Global variables: 1-year labor, manufacturer parts coverage. dontForget: warranty voids if third party altered work.
Result
Warranty replies cite the real coverage window and the voiding conditions — consistent and defensible every time.
Warranty answers are consistent and grounded in the actual terms, every time.
uploaded PDF: warranty terms
variables: 1-year labor
dontForget: voids if altered
Electrical
Emergency guardrail
The one situation where an automated email reply is genuinely dangerous is also the one where it's most likely to fire without a guardrail.
When
Any reply on a thread mentioning sparks, shock, or a burning smell.
Setup
A guardrail blocks any auto-send on safety-hazard threads and pushes a call-the-customer note.
Result
The agent never sends a canned reply where a live electrical hazard is described.
Hazard threads always escalate to a call — no automated reply ever fires on a live risk.
Guardrail: never auto-reply on hazards
Don't-forget: call, don't email, on emergencies
Tags: emergency
Electrical
Permit and code file
Giving a permit answer from memory and getting it wrong puts you in a conversation with an inspector and a customer at the same time.
When
A homeowner asks whether their EV-charger install needs a permit.
Setup
The local permit-and-code reference is uploaded so replies cite real requirements, not guesses.
Result
Permit answers are always grounded in the jurisdiction's actual rules.
Permit replies cite real local requirements, not a best guess from whoever answered.
Folder: permits & code (PDF)
Guardrail: no firm code ruling by email
Variable: {permit_link}
Electrical
Service-area profile
Booking a job an hour outside your zone because someone replied before you checked the address creates a commitment you have to undo or absorb.
When
Any reply that offers a service call or install date.
Setup
A global variable holds the service radius and a guardrail declines jobs outside it.
Result
The agent never books a service call the crew can't reach that day.
No out-of-range booking goes out — the guardrail checks area before any reply commits.
Variable: {service_area}
Guardrail: decline out-of-area
Don't-forget: trip charge past 25 miles
Landscaping
Service-menu file
A homeowner asks exactly what's in a maintenance plan and the reply goes off-menu because nothing's written down.
When
A homeowner asks what's included in a maintenance plan.
Setup
The service-menu PDF is uploaded so replies quote real packages and add-ons, not guesses.
Result
Plan answers are always grounded in the services you actually offer.
Every plan question gets an accurate, on-brand answer.
Folder: service menu (PDF)
Guardrail: no firm quote by email
Don't-forget: site visit for install
Landscaping
Service-area guardrail
A reply accidentally offers a date to someone three towns out of your route, and now you have to back out of it.
When
Any reply that offers a mowing or install date.
Setup
A global variable holds the service radius and a guardrail declines work outside it.
Result
The agent never books a lawn the crew can't reach on route.
Out-of-area leads get a polite decline instead of a scheduling problem later.
Variable: {service_area}
Guardrail: decline out-of-area
Don't-forget: acreage needs a site visit
Landscaping
Recurring-client memory
A returning client emails and the reply asks for their gate code again — the same one they gave you last spring.
When
A season-long client from last year emails again.
Setup
Their profile stores the plan tier, weekly slot, gate code, and renewal date.
Result
Follow-ups reference the real account — no re-asking their plan or property details.
Long-term clients feel remembered, not processed.
Profile: tier + tags
Variables: {plan_tier}, {renewal_date}
Don't-forget: dog in backyard
Cleaning
Recurring-client profile
A weekly client emails about their usual arrangement and the reply asks for details they gave you months ago.
When
A weekly client emails and the agent needs their exact standing arrangement.
Setup
A client profile stores tier, point of contact, day/time, gate code, and pet notes as variables.
Result
Every reply reflects this client's real schedule and quirks — no guessing, no re-asking.
Replies to regulars feel personal, not generic.
profile.tier: recurring-weekly
variables {gate_code, pets}
dontForget: bring extra supplies
guardrails
Cleaning
Service & pricing folder
A quote goes out with last quarter's rates because the agent had no source of truth to check.
When
A lead asks what's included in a standard vs. deep clean and roughly what it costs.
Setup
A folder holds your service menu, add-ons, and rate card as Markdown the agent reads before drafting.
Result
Quotes and answers stay accurate to your current pricing, not a stale copy in someone's head.
Every quote reflects actual, current pricing — not a remembered number.
folder: Services & Rates (md)
purpose: quote grounding
variables (global): {base_rates}
uploaded: rate-card.pdf
Cleaning
Commercial account brain
A property manager references access rules from their contract and you have to dig through a thread from four months ago.
When
A property manager references their contract terms and after-hours access rules.
Setup
A per-client profile tracks contract status, open loops, and building access dos and don'ts.
Result
Replies to big accounts honor the contract and access rules without a scramble through old email.
Commercial account replies are grounded in the contract, not a guess.
profile.status: under-contract
openLoops: renewal in Q3
guardrails: no weekend entry
variables {access_hours}
Dental
Fee schedule file
A patient asks about cleaning costs and gets a number from memory that doesn't match the current fee schedule.
When
Cost questions for cleanings, crowns, and whitening come in all day.
Setup
The practice's current fee schedule is uploaded as a PDF so the agent quotes only real, up-to-date estimates.
Result
Every cost answer matches the actual schedule — no stale numbers, and custom plans defer to a visit.
Fee answers are always grounded in the current schedule, not someone's memory.
Uploaded file: fee-schedule (PDF)
Guardrail: quote only listed fees
Guardrail: custom plans → offer a visit
Dental
Clinical guardrails
An AI-assisted reply inadvertently crosses into clinical advice and the practice is now in an uncomfortable position.
When
Any AI-assisted reply could drift into diagnosing or advising a patient by email.
Setup
A global guardrail forbids diagnosing, advising on treatment, or clearing patients by email — and escalates urgent wording.
Result
No reply ever gives clinical advice; emergencies route to a human to call, keeping the practice HIPAA-mindful and safe.
Every AI-touched reply stays within safe, HIPAA-mindful boundaries.
Guardrail: never diagnose or advise clinically
Guardrail: don't expose patient details
Escalate-if: pain, swelling, emergency
Dental
Practice variables
The practice updated its hours and two different staff members are quoting patients different times all week.
When
Replies need hours, address, booking link, and accepted insurers every time.
Setup
Global variables hold office hours, address, booking URL, and the plans the practice is in-network with.
Result
One place to update details; every reply — human or agent — uses the same correct facts.
One update propagates to every reply — no more conflicting information reaching patients.
Variable: {hours}, {address}, {booking_link}
Variable: {accepted_insurers}
Scope: global
Veterinary
Clinic guardrails
Without a hard constraint, an AI reply could drift into treatment territory — one slip on a drug dose or diagnosis exposes the practice.
When
Any AI-assisted reply could stray into diagnosing or treatment advice.
Setup
A global guardrail forbids diagnosing, recommending treatment, or dosing medication by email, and escalates urgent symptoms to a call.
Result
No reply ever gives medical advice; urgent-sounding messages route to a phone call with a person, every time.
Guardrails are enforced consistently, not dependent on whoever drafted the email that day.
Guardrail: never diagnose or advise treatment
Guardrail: no dosing or med changes by email
Escalate-if: vomiting, not eating, emergency
Veterinary
Booking & rates variables
Stale hours or a wrong boarding rate in a reply erodes trust and creates the very callbacks you were trying to avoid.
When
Replies need hours, the booking link, boarding rates, and address every time.
Setup
Global variables hold hours, booking URL, boarding rates, and address so replies stay accurate and current.
Result
One place to update details; every reply — human or agent — uses the same correct facts.
Every reply quotes the same correct facts, no matter who or what sent it.
Variable: {hours}, {booking_link}
Variable: {boarding_rates}, {address}
Scope: global
Veterinary
Patient profile
When a regular's email gets the same generic reply as a stranger's, it signals that the clinic doesn't remember them.
When
A returning owner reaches out about their pet by name.
Setup
The patient profile stores the pet's name, species, primary vet, standing preferences, and open loops from prior visits.
Result
Replies feel personal and informed without staff re-reading old records for every regular.
Regulars feel recognized from the first line, without staff manually reviewing their history each time.
Profile: poc (primary vet), tier
openLoops, dontForget
Variable: {pet_name}, {species}
Therapy
Clinical guardrails
Without a hard constraint, any AI-assisted reply carries the risk of crossing into clinical advice — a line that can't be uncrossed once sent.
When
Any AI-assisted reply could drift into clinical or crisis territory.
Setup
A global guardrail forbids clinical advice by email and forces immediate escalation of any crisis or self-harm language.
Result
No reply ever counsels, diagnoses, or handles a crisis by email — sensitive moments always reach a clinician.
The boundary between logistics and clinical care is enforced in every reply, automatically.
Guardrail: never give clinical advice by email
Guardrail: escalate any crisis / self-harm at once
Guardrail: discreet, no PHI in previews
Therapy
Intake & policy folder
Policy wording improvised on the fly can conflict with what another staff member told a different client last week.
When
Prospective and new clients ask about fees, cancellation policy, and telehealth.
Setup
An intake folder holds the practice's approved welcome, fee, and cancellation-policy text so replies use vetted wording.
Result
Every new client gets the same accurate, warm onboarding language — nothing improvised or off-policy.
Every new client receives the approved, vetted policy wording rather than a re-worded version.
Folder: intake & policies (text/md)
Verbatim only
Guardrail: no clinical content
Therapy
Scheduling & billing variables
When the booking link or session fee is updated in one place but not everywhere, some clients receive outdated information.
When
Replies need the booking link, session fee, superbill timeline, and crisis line every time.
Setup
Global variables hold the booking URL, fee, superbill timeline, and local crisis resources so replies stay accurate.
Result
One place to update the details; every reply — human or agent — uses the same correct facts and crisis line.
One update propagates everywhere, so no reply contains a stale fee or an outdated booking link.
Variable: {booking_link}, {session_fee}
Variable: {superbill_timeline}, {crisis_line}
Scope: global
Fitness
Membership-tiers file
When the price quoted by email doesn't match what the front desk charges, the sign-up conversation starts with a dispute.
When
Pricing and inclusion questions come in all day.
Setup
The current membership tiers and rates are uploaded as a PDF so replies quote only real, up-to-date pricing.
Result
Every price answer matches the actual menu, with no stale numbers or invented packages.
Pricing in every reply matches what the prospect sees when they show up — no surprises at the desk.
Uploaded file: membership-tiers (PDF)
Variable: {trial_offer}
Guardrail: quote only listed prices
Fitness
Class-schedule variables
Sending a stale schedule link or an outdated class time erodes trust as soon as the member tries to book and finds it wrong.
When
Replies need the schedule link, booking steps, hours, and location every time.
Setup
Global variables hold the schedule URL, app steps, hours, and address so replies stay accurate and current.
Result
One place to update details; every reply, human or agent, uses the same correct facts.
One schedule update propagates to every reply automatically — no manual find-and-replace.
Variable: {schedule_link}, {app_steps}
Variable: {hours}, {address}
Scope: global
Fitness
Injury & liability guardrail
A reply that tells a member with knee pain to try a different exercise class is one email away from a liability problem.
When
Any AI-assisted reply could drift into medical or injury advice.
Setup
A global guardrail forbids giving medical guidance or clearing anyone for exercise, escalating injury mentions instead.
Result
No reply ever gives health advice; anything about pain or injury routes to a human on the record.
Injury and health mentions always reach a human on the record, never receive an improvised AI answer.
Guardrail: no medical or exercise clearance
Escalate-if: injury, pain, pregnancy
Don't-forget: waiver on file
Accounting
Client open loops
Every bookkeeper carries a mental list of what's still missing per client — a list that gets unreliable under deadline pressure.
When
A monthly close is in progress with specific records still outstanding.
Setup
The client's context profile tracks open loops like 'missing Q3 statements' and 'missing payroll register', updated as docs arrive.
Result
Every reply and chase knows exactly what's still needed, without the bookkeeper re-checking the file.
Chase emails and replies are always accurate, even during a busy close with a full book of clients.
Profile openLoops: missing Q3 statements
Profile openLoops: missing payroll register
Guardrail: no accounting advice by email
Accounting
No advice guardrail
Without a firm-wide rule, advice guardrails depend on who's drafting — and that breaks down under deadline pressure.
When
Any client email that edges toward asking for tax or accounting advice.
Setup
A firm-wide guardrail states advice is never given by email; the agent offers an advisory call instead.
Result
The whole firm's automated and drafted replies stay safely clear of written advice.
The no-advice boundary holds consistently across every reply, regardless of who's handling the queue.
Guardrail: no accounting advice by email
Guardrail: route advice to a call
dontForget: keep it factual
Accounting
Document checklist folder
Drafting a missing-document list from memory means items get forgotten, and clients send the wrong things.
When
The bookkeeper needs the standard monthly intake list for a client type.
Setup
A context folder holds the document checklist as markdown items — bank statements, credit-card statements, payroll register, receipts.
Result
The agent drafts complete, accurate missing-record lists straight from the firm's own checklist.
Every document request matches the firm's actual intake requirements, not whoever's memory is sharpest that day.
Folder: doc checklist
Purpose: monthly intake reference
Guardrail: no accounting advice by email
Wealth
Household profile
A reply that ignores what you already know about a household — their open RMD, their pending rollover — signals you're not tracking them.
When
A client from a tracked household emails and the reply needs their full context.
Setup
Context profile stores status, poc, tier, tags, openLoops (pending RMD, rollover in progress), and a guardrail: 'never give specific investment advice or performance promises by email'.
Result
Every draft for that household is grounded in their real open loops and the no-advice guardrail, so replies are accurate and compliant by default.
Drafts are grounded in what's actually open for that household, not a generic template.
Profile: status, poc, tier
openLoops: RMD, rollover
guardrails: no advice by email
tags
Wealth
Compliance folder
When disclosure language varies between replies, inconsistency itself becomes a compliance risk.
When
Any reply that touches disclosures, fees, or process needs approved language.
Setup
A Context folder holds approved disclosure text, the fee schedule, and standard-response language (Markdown) that drafts must draw from.
Result
Drafts reuse pre-approved compliance language instead of improvising, keeping wording consistent and records auditable.
Every reply draws from approved language, so disclosure wording is never improvised.
Folder: approved disclosures
Text/MD: fee schedule
purpose: compliant language
Uploaded ADV brochure
Wealth
RMD and contribution variables
Manually looking up a client's RMD deadline or the current year's IRA limit before every relevant reply is easy to get wrong under pressure.
When
A retiree asks about their required distribution or a client asks about contribution limits.
Setup
Per-client variables store RMD deadline and account type; global variables hold current-year contribution limits, referenced as {rmdDate}, {iraLimit}.
Result
Reminder and answer drafts pull the right dates and limits automatically, so deadlines and figures are consistent without manual lookup.
Date and limit details in drafts are consistent and accurate without a manual reference check each time.
Per-client: {rmdDate}, account type
Global: {iraLimit}
variables key/value
dontForget: RMD deadline
Law firm
Client matter profiles
A reply that doesn't reflect the matter's current status or assigned paralegal signals the firm isn't organised.
When
A client emails and the reply needs their matter number, status, and point of contact.
Setup
Each client has a Context profile: matter status, poc paralegal, tier, open loops, and a guardrail that no advice is emailed.
Result
Every draft is grounded in the real matter and carries the never-advise-by-email guardrail into every reply.
Every draft is grounded in the actual matter status rather than whoever's memory of it.
Profile: status, poc, tier, openLoops
Guardrail: never give legal advice by email
dontForget: no attorney-client relationship by auto-reply
Law firm
Intake form on file
A document request that asks for the wrong items wastes a client's time and slows the matter before it has even started.
When
A drafted reply needs to reference the firm's intake requirements and required documents.
Setup
The intake form and retainer are uploaded as PDF/DOCX to a Context folder the agent reads when drafting requests.
Result
Document requests always match the current intake checklist because the source files live in the agent's context.
Document requests always match the firm's actual current checklist, not a remembered version of it.
Uploaded: intake form (PDF), retainer (DOCX)
Folder purpose: intake requirements
Read-only reference for drafts
Law firm
Firm boilerplate variables
Disclaimer language that varies between replies introduces inconsistency that is hard to defend if challenged.
When
Replies repeatedly need the firm's disclaimer, office hours, and consultation-fee policy.
Setup
Global variables hold the standard disclaimer and hours; per-client variables hold each matter's number and lead attorney.
Result
Standard language stays identical across every draft while client-specific details fill in from the profile.
Disclaimer and boilerplate language is identical in every reply, with no manual copy-pasting required.
Global variable: email disclaimer, office hours
Per-client variable: matter number, lead attorney
Guardrail: disclaimer required on every send
Injury law
Case profiles
When a client emails, whoever picks it up shouldn't have to dig through old threads to understand where the case is.
When
A known client emails and staff need the case file at a glance.
Setup
A profile per case holds status (intake/treating/demand/settlement), the assigned attorney as poc, tier, and variables for {claim_number} and {adjuster_name}. Guardrail: no legal advice or case-value promises by email.
Result
Every reply is grounded in the right case facts, and the no-advice guardrail travels with the client automatically.
Any team member picks up a client thread already oriented on the case.
Profile: status + assigned attorney
Variable: {claim_number}
Guardrail: no legal advice or value promises
Injury law
Open loops per case
Outstanding items on a case — a records request, an unconfirmed lien — are exactly the things that slip when email volume is high.
When
A client or provider with items in flight emails again.
Setup
The profile's openLoops track outstanding items (records pending from a provider, lien to confirm, treatment ongoing) and dontForget notes surface commitments the firm made to the client.
Result
Nothing owed on a case slips — the outstanding record, lien, or promised callback is right there when they write.
Commitments and open items stay visible so nothing silently drops.
Profile: openLoops (records, lien)
dontForget: promised callback
Variable: {provider_name}
Injury law
Compliance guardrails file
One careless reply giving a case value estimate or implying a timeline can create real professional liability — the guardrail has to be automatic, not remembered.
When
Any reply that risks giving advice, promising value, or breaching confidentiality.
Setup
A global guardrails profile enforces: never give legal advice by email, never promise a case value or outcome, escalate substantive and settlement questions to an attorney, and stay confidentiality-careful. Applied across all case threads.
Result
Compliance posture is baked into every draft and auto-reply rather than left to whoever is at the keyboard.
The firm's compliance posture holds across every reply, not just when someone remembers.
Guardrail: no legal advice by email
Guardrail: escalate settlement to attorney
Scope: all threads
Salon & spa
Service-menu file
Without the real menu on hand, the agent can only guess at prices — and a wrong quote erodes trust fast.
When
Pricing, timing, and service questions come in all day.
Setup
The salon's current service menu is uploaded as a PDF so the agent quotes only real, up-to-date prices and durations.
Result
Every price answer matches the actual menu — no stale numbers, no invented packages.
Pricing replies are grounded in the real menu, not improvised.
Uploaded file: service-menu (PDF)
Variable: {consult_fee}
Guardrail: quote only listed prices
Salon & spa
Booking variables
Stale booking links, wrong hours, or an outdated address in a reply wastes the guest's time and reflects poorly on the salon.
When
Replies need the booking link, hours, location, and package details every time.
Setup
Global variables hold the booking URL, hours, address, and gift-card link so replies stay accurate and current.
Result
One place to update details; every reply — human or agent — uses the same correct facts.
Every reply uses current, accurate details — one update propagates everywhere.
Variable: {booking_link}, {giftcard_link}
Variable: {hours}, {address}
Scope: global
Salon & spa
VIP client profile
A VIP who gets a generic reply when their formula and stylist preference are on file will feel like just another appointment.
When
A returning high-value client reaches out for their standing color appointment.
Setup
Their profile stores tier, preferred stylist, color formula notes, and open loops from prior visits.
Result
Replies feel personal and informed without staff re-reading old threads for every regular.
Regulars get a reply that feels personal because it actually is.
Profile: tier VIP, poc (stylist)
openLoops, dontForget
Variable: {preferred_stylist}
Photography
Pricing guide file
Quoting a package price from memory is how stale or wrong numbers end up in client emails.
When
Inquiries about wedding, portrait, and commercial rates come in all week.
Setup
Your current pricing guide is uploaded as a PDF so the agent quotes only real, up-to-date collections and add-ons.
Result
Every price answer matches your actual guide — no stale numbers, and anything bespoke defers to a call with you.
Every price quoted to a client comes from the real guide, not memory.
Uploaded file: pricing-guide (PDF)
Guardrail: quote only listed collections
Guardrail: custom scope → offer a call
Photography
Booked-client profile
Scrolling an old thread to find the wedding date and package before you can reply costs time you don't have mid-edit.
When
A signed couple emails about their upcoming shoot and delivery.
Setup
A client profile holds their status, tier, shoot date, and package as variables, with open loops and don't-forget notes.
Result
Replies already know the wedding date, collection, and what's outstanding — no scrolling the thread to catch up.
You reply fully oriented on the client's details without digging through old threads.
Profile: status booked, tier VIP
Variable: {shoot_date}, {package}
openLoops + dontForget tracked
Photography
Studio variables
If your turnaround changes or your booking link updates, every reply using old variables sends clients the wrong information.
When
Replies need turnaround time, studio address, booking link, and delivery method every time.
Setup
Global variables hold your standard turnaround, studio address, booking URL, and gallery-delivery platform.
Result
One place to update the details; every reply — yours or the agent's — uses the same correct facts.
Update once, and every future reply automatically uses the right details.
Variable: {turnaround}, {studio_address}
Variable: {booking_link}, {gallery_platform}
Scope: global
Auto repair
Vehicle-history memory
Repeat customers shouldn't have to re-explain their vehicle every time they email — and an advisor who already knows feels more trustworthy.
When
A repeat customer emails again about their car.
Setup
Their vehicle profile stores the year, make, model, VIN, and last-service date.
Result
Replies reference the actual vehicle and its history — no re-asking what they drive.
Customers feel recognized, not processed.
Profile: vehicle + tier
Variables: {make_model}, {last_service}
Don't-forget: recurring noise complaint
Auto repair
Estimate-approval guardrail
You need a hard guarantee that the AI will never commit to a repair price or approve work — regardless of how the customer phrases their message.
When
Any reply that touches a repair estimate or additional-work approval.
Setup
A guardrail blocks the agent from authorizing work or committing to a final price by email.
Result
The agent never approves a repair on the customer's behalf — big-ticket work always waits for a human.
The shop is protected from accidental automated commitments on costly repairs.
Guardrail: never authorize work
Guardrail: no firm price by email
Escalate to advisor
Auto repair
Labor rate and fees
Customers ask about diagnostic fees before deciding to book, and an inconsistent answer — or no answer — costs you the appointment.
When
A customer asks about the diagnostic fee or hourly labor rate before booking.
Setup
A pricing folder holds the diagnostic fee, hourly labor rate, and shop-supply policy as reference-only text.
Result
Fee answers stay consistent while firm repair quotes still wait for a tech's diagnosis.
Every pre-booking fee question gets a consistent answer that helps the customer decide to come in.
Folder: pricing sheet (MD)
Variable: {diagnostic_fee}
Guardrail: no firm quote by email
Restaurant
Catering menu folder
Event inquiries ask about menus and pricing all week, and an answer that doesn't match your real packages starts the relationship on a wrong foot.
When
Catering and private-event inquiries ask about menus, per-head pricing, and dietary options all week.
Setup
The catering menu and event packages are uploaded as PDFs into a context folder the agent quotes from.
Result
Every catering answer matches the real packages — no stale pricing, and bespoke menus defer to the events manager.
Catering replies are always grounded in your actual current offerings.
Folder: catering menu (purpose + md)
Uploaded file: event-packages (PDF)
Guardrail: bespoke menus → events manager
Restaurant
Restaurant variables
Hours change, the booking link rotates, and the private-dining minimum gets updated — but every team member still quotes the old details from memory.
When
Replies need hours, address, booking link, and the private-dining minimum every time.
Setup
Global variables hold hours, address, reservation URL, parking notes, and the private-dining spend minimum.
Result
One place to update the details; every reply — human or agent — uses the same correct facts.
Update once and every reply — from any team member or the agent — reflects the right details.
Variable: {hours}, {address}, {booking_link}
Variable: {private_dining_minimum}
Scope: global
Restaurant
Availability guardrails
Without a hard rule, an AI-assisted reply could accidentally confirm a table that isn't available or lock in a price the events team never agreed to.
When
An AI-assisted reply could accidentally confirm a table, a date, or a final catering price.
Setup
A global guardrail forbids confirming availability, dates, or final pricing by email and escalates any allergen or health wording.
Result
No reply ever locks in a booking or a number on its own — those calls stay with the host and events team.
Availability and pricing commitments always require a human — no accidental double-booking by email.
Guardrail: never confirm availability or final price
A couple asking about inclusions at each tier expects a precise answer — a vague or wrong one signals you don't know your own product.
When
A couple asks what's included at each tier and what add-ons cost.
Setup
The packages-and-pricing PDF is uploaded so replies quote real inclusions and add-ons, not guesses.
Result
Package answers are always grounded in the offerings you actually sell.
Package replies are always accurate to what you actually offer, not a best-effort recall.
Folder: packages (PDF)
Guardrail: no custom quote by email
Don't-forget: consult before booking
Events
Per-couple event profile
A booked couple emails a follow-up and getting asked to re-explain their date, venue, or guest count after months of planning signals they're just a transaction to you.
When
A booked couple emails again about a detail from an earlier conversation.
Setup
Their profile stores the event date, venue, guest count, coordinator, and open loops.
Result
Every reply references the real event — no re-asking their date, venue, or vision.
Every reply feels personal because it references the event they've been planning with you.
Profile: status + poc + tier
Variables: {event_date}, {venue}
Open loops + don't-forget
Events
Preferred-vendor list
A couple asks for a photographer recommendation and you need to be sure the name you give is a trusted partner, not someone who'll reflect badly on you.
When
A couple asks for a florist or photographer recommendation.
Setup
A vendor-list folder holds your trusted partners so suggestions stay on your approved roster.
Result
Recommendations always come from your real preferred vendors, never a random name.
Every recommendation comes from your vetted roster, protecting your reputation.
Folder: vendor list (md)
Guardrail: preferred vendors only
Don't-forget: check date availability
SaaS
Onboarding knowledge base
Without a grounded knowledge source, the agent answers onboarding questions generically instead of accurately.
When
A new user asks a common setup or how-to question during activation.
Setup
A context folder holds your onboarding docs in markdown the agent reads while drafting answers.
Result
Onboarding replies stay accurate and consistent across every new account.
Activation answers are specific to your product, not guesswork.
Context folder: onboarding KB
Items: markdown
Purpose: activation answers
SaaS
Account tier profile
A draft that doesn't know this is a strategic enterprise account will read like it was written for a random trial.
When
You start working a strategic enterprise account with several stakeholders.
Setup
An account profile tracks tier, point-of-contact, open loops, and a discounts-via-deal-desk guardrail.
Result
Every draft to this account stays on-strategy and within pricing policy.
Enterprise account replies stay consistent with the deal you're running.
Per-account profile
Profile tier: enterprise
Guardrail: discounts via deal desk
SaaS
Pricing sheet file
A pricing answer that doesn't match your current sheet is worse than no answer at all.
When
A trial user or prospect asks for plan tiers or upgrade pricing.
Setup
You upload a pricing-sheet PDF into a context folder the agent references while drafting.
Result
Pricing answers stay grounded and consistent across every account.
Every pricing reply quotes exactly what you actually charge.
Uploaded file: pricing sheet (PDF)
Context folder: Pricing
Guardrail: no unapproved discounts
IT / MSP
Per-client runbook memory
A reply that asks a client to re-explain their environment tells them you weren't paying attention last time.
When
A recurring client emails again about their environment or a known issue.
Setup
Their profile stores SLA tier, primary contact, and links a runbook folder with their stack and escalation path.
Result
Replies reference the actual environment and correct contact — no re-asking what's already documented.
Clients feel known; techs reply with the right context the first time.
Profile: status + poc + tier
Folder: client runbook (MD)
Variables: {sla_tier}, {escalation_path}
IT / MSP
SLA-tier response guardrail
Promising a response time faster than the client's contracted tier sets an expectation you may not be able to keep.
When
Any reply that commits to a response or resolution time.
Setup
Per-client variables hold the contracted response window and a guardrail blocks promising anything faster.
Result
The agent never quotes a response time tighter than the client's actual SLA tier allows.
SLA commitments in replies always match the actual contract.
Variable: {response_window} per-client
Guardrail: never beat contracted SLA
Don't-forget: after-hours surcharge
IT / MSP
Access & change-control rules
An agent that could grant access from an email alone is a social-engineering attack waiting to happen.
When
A client requests a change, new access, or an admin action by email.
Setup
A guardrail requires the change be logged in the ticketing system and holds any credential handling for a human.
Result
Change requests always route through change control — the agent never grants access from an email alone.
No access or change is granted outside your documented change-control process.
Guardrail: no access grants by email
Guardrail: require ticket for changes
Don't-forget: log to PSA
Tutoring
Per-student profiles
A reply that gets a student's focus area or test date wrong tells the parent you don't actually know their child.
When
Parents ask about their own child's sessions, goals, and progress all week.
Setup
Each student has a profile holding status, subject goals, open loops, and don't-forget notes so replies stay specific to that child.
Result
Every family reply reflects the real student — recent focus, upcoming test, standing reminders — not a generic answer.
Replies feel personal and accurate to the individual student, not templated.
Profile: per-student
Fields: openLoops, dontForget
Variable: {student_goal}
POC: parent
Tutoring
Packages & rates file
A pricing answer that doesn't match your actual packages creates a correction email you'll have to send later.
When
Package, session-count, and pricing questions come in daily.
Setup
Your current packages and rates are uploaded as a PDF so replies quote only real, up-to-date pricing.
Result
Every price answer matches the actual menu, with no stale numbers or invented bundles.
Pricing answers are always grounded in what you actually offer.
Uploaded file: packages-and-rates (PDF)
Variable: {consult_link}
Guardrail: quote only listed prices
Tutoring
Academic-advice guardrail
An AI reply that drifts into learning-disability claims or score guarantees puts your business and your clients at real risk.
When
Any AI-assisted reply could drift into learning-disability or diagnostic claims.
Setup
A global guardrail forbids diagnosing conditions or promising score outcomes, escalating those mentions to a human.
Result
No reply ever makes a clinical or guarantee claim; anything about a diagnosis routes to a person on the record.
Guardrails keep every reply inside safe, honest bounds with no exceptions.
Guardrail: no diagnosis or score guarantees
Escalate-if: IEP, ADHD, dyslexia
Don't-forget: intake form on file
Coaching
Per-student profiles
A reply that ignores where a student is in the program signals you don't know them — eroding trust mid-cohort.
When
An enrolled student emails mid-program with a question about their next step.
Setup
Each student has a context profile — status, tier, tags, open loops, and don't-forget notes — assigned by rule.
Result
Replies land grounded in where that student actually is, so guidance feels personal, not templated.
Every reply reflects the student's actual progress, not a generic answer.
Profile: status, tier, tags
openLoops: current module
dontForget: their stated goal
guardrails: no medical advice
Coaching
Program FAQ folder
Answering a policy question from memory risks quoting the wrong terms — especially after you've updated them.
When
A prospect or student asks a question the syllabus and policies already answer.
Setup
A context folder holds the program FAQ, refund policy, and schedule as markdown the agent reads before drafting.
Result
Answers stay accurate to your actual terms and curriculum, with no stale copy-paste from an old doc.
Policy and curriculum answers are always pulled from the live source.
Folder: program FAQ (md)
Purpose: enrollment + policy
Uploaded: syllabus PDF
Grounds every draft
Coaching
Global voice variables
Sending a reply with last cohort's dates or a stale booking link undermines credibility at a critical moment.
When
Any reply needs your booking link, cohort dates, or the current program price.
Setup
Global variables store your links, next-cohort dates, and pricing so every agent draft pulls the live values.
Result
Links and dates are always current across every reply, and updating one variable fixes them everywhere.
One update propagates correct details to every future reply.
Variable (global): {booking_link}
Variable: {cohort_dates}
Variable: {program_price}
Reused across drafts
Nonprofit
Major-donor profiles
A reply to a major donor that ignores their giving history or naming preference signals they're not known.
When
A board member or major donor emails and the reply needs their giving history in mind.
Setup
Keep a profile per major donor: tier, point of contact, open loops, dontForget notes, and giving guardrails.
Result
Every reply to a key supporter reflects their relationship and open asks — no cold, generic responses.
Major donors are addressed as the individuals they are, not as entries in a list.
Profile: tier + poc
openLoops: pending ask
dontForget: naming preference
guardrails: no solicitation mid-report
Nonprofit
Program info folder
Eligibility answers that vary by who replies undermine trust in your programs and create liability.
When
Inquiries arrive about eligibility, services, and how your programs actually work.
Setup
Store program descriptions and eligibility criteria in a Context folder the agent reads when drafting.
Result
Program replies stay accurate and consistent, pulled from one source instead of staff memory.
Every program inquiry gets an answer grounded in your actual eligibility criteria.
Folder: program info
Purpose: eligibility + services
Markdown criteria
Grounds every draft
Nonprofit
Annual report & grant docs
Funder-facing replies that improvise impact numbers or mission language contradict your official materials.
When
A funder or partner asks about impact numbers, mission language, or your latest outcomes.
Setup
Upload the annual report and grant boilerplate (PDF/DOCX) so drafts cite real figures and approved wording.
Result
Funder-facing replies use vetted mission language and current numbers, not improvised claims.
Impact claims in every reply match your vetted annual report, not staff memory.