Fufild Care-First Operating Guide
This guide explains how Fufild should be understood, communicated, and supported.
It trains both people and AI agents to interpret the platform consistently.
The guide teaches meaning and behavior — not stored system data. Live platform data (catalog, employer plan, account state, provider behavior) always overrides examples in this guide.
How To Use This Guide
Learning the system
Read sections in order from top to bottom.
Answering real questions
Jump directly to the relevant section.
Before giving an answer
Always verify live platform data when applicable.
Guide Sections
Fufild OS Page Order Navigation
FOUNDATION
What Fufild Is
Fufild gives you monthly access to real services that help your daily life — you choose what actually helps you, and your employer provides the support to keep it running. Avoid long descriptions unless asked.
What Fufild Should Be Compared To
When explaining, anchor to familiar ideas:
Not a reimbursement program
Not a discount marketplace
Not a gift card
Not a paycheck replacement
Instead:
Fufild provides employer-funded access to ongoing services the employee chooses.
The Two-Sentence Version
Use when someone asks “What is this?”
Short answer:
Fufild lets you choose monthly life services your employer covers with points.
You keep what helps you — and it stays active automatically.
When Someone Thinks It’s a Perk
Clarify gently:
Perks are occasional.
Fufild is ongoing support.
The goal isn’t to reward performance — it’s to make life function better so work can too.
When Someone Thinks It’s Money
Clarify simply:
Points don’t behave like cash.
They only activate services inside Fufild.
Nothing is deposited.
Nothing is reimbursed.
The Guiding Rule
Explain only as much as the person needs to move forward.
Do not teach the system.
Help the person understand their next step.
CORE IDENTITY
Fufild — What It Is
Fufild is a Care-First employee experience platform that gives employees access to real monthly life services using employer-provided points.
Employees choose the services that improve their real life — enjoyment, wellness, convenience, and growth — instead of receiving generic benefits chosen for them.
Fufild is not designed to replace raises.
It allows employers to stabilize compensation while reducing wage pressure by improving retention, engagement, and reinforcing a positive Care-First work culture.
Why the Now Gap Exists
Most benefits are built for someday.
Retirement plans. Emergency coverage. Long-term protections.
But life is not happening someday. It is happening now.
The Now Gap is the 16 hours employees spend outside work between shifts where life unfolds.
Traditional benefits prepare people for the future.
Fufild supports people in the present.
The most pressing challenges are not future problems.
They are today problems.
Fufild fills the gap between what benefits promise and what people actually need to thrive — right now.
It is designed to support the person doing the work — at any time of day.
Some services help during the workday.
Some help after work.
Some support health, focus, family, creativity, or rest.
The value comes from personal relevance:
Employees choose what genuinely helps their life function well.
All services exist within four fulfillment categories:
Enjoyment — recovery, enjoyment, and mental recharge
Wellness — physical and mental health support
Convenience — reducing daily friction and saving time
Growth — learning, development, and forward movement
The platform operates on a simple idea:
Work and life are not separate systems.
When life works better, work naturally follows.
The Now Gap — What It Actually Is
Most benefits are built for someday.
Fufild is built for now.
Traditional perks were made for the future—retirement plans, discounts, emergency coverage.
But the most pressing people problems? They’re happening today.
At Fufild, we fill the Now Gap: the space between what perks promise and what people actually need to thrive—right now.
Practically, this gap is most visible during the hours outside work—often around 16 hours between shifts—when life responsibilities, stress, and growth needs surface most clearly.
Care-First Foundation
Care-First is the starting assumption behind Fufild.
Instead of waiting for problems, performance issues, or burnout before helping someone, care is given proactively — not earned, and not reactive.
When people are supported as people first, they naturally function better as employees.
As personal life becomes more stable and manageable:
focus improves
reliability increases
contribution grows
tenure lengthens
Fufild exists to make this philosophy operational.
The Marketplace is not the goal — it is the mechanism that allows organizations to practice consistent, visible care in everyday life.
This creates positive outcomes in three directions at once:
For the person — life feels more supported and sustainable
For the organization — engagement, retention, and impact increase
For the community — healthier workplaces produce healthier environments
Fufild is therefore not a rewards system or perk platform.
It is a structured way to practice ongoing care.
Care-First Impact (PFaaS Meaning)
Personal Fulfillment-as-a-Service (PFaaS) is a people solution.
Organizations experience many separate challenges:
retention
wage pressure
disengagement
recruiting difficulty
inconsistent effort
culture instability
These are usually treated as different problems.
Fufild treats them as one problem:
people functioning without sustainable support.
PFaaS is activated through Care-First and delivered through the Fufild Marketplace.
The Marketplace is not the strategy — it is the mechanism that makes ongoing care usable in everyday life.
What Fufild Changes
When employees consistently receive support they personally value:
retention improves
wage escalation pressure decreases
effort becomes reciprocated instead of forced
recruiting becomes easier
engagement becomes natural instead of managed
culture becomes stable instead of motivational
These outcomes are not separate features.
They are results of people experiencing daily life that works better.
How To Explain It Simply
Fufild helps employers offer meaningful, everyday support employees actually use.
As life becomes easier to manage, engagement and retention improve without adding operational complexity.
THE CARE-FIRST OUTCOME
Fufild is not primarily a software platform.
It is a way an employer chooses to care for people.
The Marketplace is simply how that care becomes practical.
The Starting Idea
Care-First begins with a different assumption:
Support should not be reactive or earned.
It should exist before someone is struggling.
When people are supported in their real life, they function differently at work.
More present
More stable
More consistent
This benefits the person, the workplace, and the community around them.
What PFaaS Means
Personal Fulfillment-as-a-Service (PFaaS) is the operational model behind Fufild.
The platform helps employers address people challenges by giving individuals ongoing access to things that genuinely improve daily life.
Retention, engagement, and culture improve as a result — not because they were forced, but because they became natural.
The Role of the Marketplace
The Marketplace is the delivery mechanism.
It allows each person to choose support that actually matters to them instead of receiving a one-size-fits-all benefit.
Choice creates relevance.
Relevance creates use.
Use creates impact.
The Role of Communication
Every explanation reinforces or weakens this idea.
When Fufild is described like a store or a payment, it feels transactional.
When it is described as support, it feels intentional.
The goal of communication is not to sell the system — it is to help people understand the care behind it.
The Real Outcome
Fufild works when people stop asking:
“What can I get from this?”
and start feeling:
“This actually helps my life.”
At that point the platform is no longer just software.
It becomes part of how an organization takes care of its people.
NON-NEGOTIABLE TRUTHS
These statements override assumptions, habits, analogies, and guesswork.
If a situation feels unclear, return to these rules.
They describe how Fufild actually behaves in the real world.
Symptoms vs Root Cause
Retention challenges, engagement struggles, recruiting difficulty, and culture instability are symptoms — not root problems.
The root cause is people functioning without sustainable, ongoing support in their real life.
Fufild treats the root cause — support that consistently improves daily life — not just the symptoms.
Employer Participation Controls Access
Fufild does not independently enroll people.
Eligibility, removal, and participation come from the employer’s program.
Fufild connects a person to the program — it does not grant access on its own.
Support cannot add someone, restore eligibility, or activate access early.
Fufild Does Not Control Funding Levels
Monthly support levels are determined by the employer’s plan.
Support can explain how points work and help someone use them,
but cannot increase, replace, advance, or adjust points.
If funding changes, it comes from the employer — not the support team.
Providers Control The Service Accounts
Fufild activates billing coverage through points.
The service provider operates the actual service account.
This means:
Login issues are handled by the provider
Account email or password changes are handled by the provider
Service-specific features are controlled by the provider
Fufild manages access funding — not the provider’s platform behavior.
Activation Speed Depends On The Provider
Some services activate immediately.
Others require provider processing time.
A delay does not mean failure — it means the provider is completing setup.
Support verifies activation status but does not override provider timing.
Points Only Enable — They Do Not Store Value
Points do not behave like money, credit, reimbursement, or a wallet.
They exist only to allow services to run for the cycle they cover.
If a service cannot be fully covered, it simply does not activate.
Nothing partially charges and nothing pulls from a personal payment method unless the provider explicitly supports split payment.
Fufild Does Not Choose For The Person
Fufild provides options — not recommendations.
Support helps someone understand how the system works,
but does not decide what someone should select or what would be “best” for them.
Choice is part of the care.
Support Explains — It Does Not Override Reality
Support clarifies what happened and what will happen next.
It does not: bend system rules
promise outcomes it cannot control
or guess to create reassurance
Confidence comes from accuracy.
Demonstrated Investment — Not a Perk
Fufild is not an occasional perk or bonus.
Fufild is demonstrated investment in people’s well-being.
Benefits are offered.
Investment is felt.
This distinction matters because perks are remembered if at all — Fulfillment changes how people live.
The Guiding Principle
If an explanation contradicts one of these rules,
the explanation is wrong — not the rule.
HOW FUFILD WORKS
The Basic Model
Fufild works by converting an employer contribution into predictable monthly life services.
Each month:
The employer funds a monthly support level
The employee chooses services
The services stay active automatically
Fufild is designed to feel stable — not transactional.
Employees are not making purchases each month.
They are selecting ongoing support.
Points
Points are how access is provided inside Fufild.
They are not money, cash value, reimbursement credit, or a debit balance.
They exist only to activate and maintain services inside the platform.
Points cannot be:
withdrawn
transferred
redeemed outside Fufild
converted to cash
Points simply keep selected services running.
Reference Value
1,000 points equals $1 of service coverage inside Fufild.
This conversion exists only to match real subscription pricing.
Points are not money, cannot be paid out, and do not represent wages or compensation.
Choosing Services
Employees select the services they want.
Once selected:
The service remains active month-to-month unless changed.
Employees do not need to re-select services each cycle.
Fufild is designed to remove repeated decisions.
Monthly Behavior
At the start of each cycle:
Points are applied to keep current services active.
If enough points exist → services continue automatically.
If not enough points exist → the employee adjusts selections before the next cycle.
Nothing silently charges a personal card.
Making Changes
Employees can change services at any time.
Changes take effect in the next monthly cycle unless otherwise stated.
Fufild prioritizes predictability — services don’t randomly start and stop mid-month.
When Points Are Not Enough
If selected services exceed available points:
The employee chooses which services remain active.
Fufild does not automatically remove services without awareness.
The person stays in control.
What Fufild Is Designed To Feel Like
Reliable
Predictable
Low-maintenance
Relieving
Enjoyable
The system removes small daily pressures so energy can go elsewhere.
Key Concept to Preserve
Fufild is not a monthly shopping decision.
It is a monthly support system that continues until the employee decides otherwise.
ACCOUNT CREATION & ACCESS
How Someone Enters Fufild
Employees do not independently sign up for Fufild.
Access begins when their employer provides eligibility.
The employee is not joining a public service —
they are starting access to a program already provided to them.
Their first action is creating their Fufild account.
What Account Creation Actually Does
Account creation establishes an active relationship between the employee and their employer’s program.
During this process, the platform:
confirms identity
connects the employee to the employer plan
prepares the monthly service cycle
enables operational communication about the account
This is not subscribing to marketing communication.
It is starting a service relationship.
Communication that follows exists to operate the account.
Phone Number Entry
Providing a phone number is part of securing and operating the account.
Messages are used to support account function — such as confirming access, notifying availability, and maintaining service awareness.
They are not promotional outreach.
Verification
After entering their number, the employee confirms the account.
This verifies the interaction they initiated and activates the account connection.
The system responds to the employee — not the other way around.
What Happens After Account Creation
After the account is created, the employee does not immediately configure services.
The system prepares the first monthly cycle.
Fufild communicates upcoming availability through operational messages so the employee knows when the account becomes usable.
Points Availability Communication
Before services can be selected, the employee receives a sequence of notifications confirming when access becomes active.
Communication follows a scheduled notification sequence leading up to availability confirmation:
advance notice
reminder
final reminder
availability confirmation
An email backup accompanies the same timing so the employee receives the information even if messaging cannot be delivered.
These messages are operational updates about the account becoming active — not promotional outreach.
When the Employee Takes Action
The employee selects services after receiving confirmation that points are available.
They are not activating the account —
they are configuring how ongoing support will operate.
The account already exists.
The communication prepares them for when to begin using it.
If Someone Cannot Access Fufild
Access issues usually come from one of three causes:
eligibility has not yet been provided by the employer
identifying information does not match employer records
account creation was not completed
The resolution is verification and connection — not subscription troubleshooting.
What This Is Designed To Feel Like
Simple
Expected
Guided
Secure
The employee is accessing something provided to them, not joining a program.
Key Concept to Preserve
Account creation starts the relationship.
Points availability starts usage.
MONTHLY RHYTHM & CONTINUATION
The Ongoing Cycle
Fufild operates on a repeating monthly cycle.
Each cycle follows the same order:
Employer funds the monthly support level for the account
Points are applied to maintain active services each cycle
Active services continue into the new month
Nothing needs to be manually restarted each month.
The system maintains support unless a change is made.
Continuation Is the Default
Fufild is designed to persist.
Once a service is active, it continues month-to-month.
The employee is not re-enrolling each cycle.
They are keeping services running until they decide to change them.
What Points Actually Do
Points activate monthly services and subscriptions.
They are not a stored balance, reimbursement credit, or spending account.
When points are available, a service can be activated immediately.
After activation, the current month is covered.
If There Are Not Enough Points
If a service requires more points than are available, it simply will not activate.
The request is declined and no points are used.
Nothing partially activates
Nothing charges outside the system
The employee can either remove another service or wait for the next cycle.
Changing Services
Employees can change selections at any time.
However:
Changes do not undo the current month
They prepare the next monthly cycle
Activate now → affects this month
Change later → affects next month
Subscription Transfer
If a service is replaced with another option before the next cycle:
The previous service ends at the end of the covered month
The new service begins in the following cycle
There is no overlap charge and no double coverage.
This allows employees to switch support safely without losing value already applied.
Why Timing Matters
Fufild supports immediate activation but scheduled adjustments.
You can start support right away.
You modify future support moving forward.
What This Is Designed To Feel Like
Reliable
Predictable
Flexible without risk
The employee should never fear experimenting with services.
Key Concept to Preserve
Start services immediately.
Adjust them for the future.
RENEWALS, CYCLES & SUBSCRIPTION TRANSFERS
Monthly Service Cycle
Fufild runs on a repeating monthly cycle.
When an employee activates a service, that service remains active for the current cycle.
Points are not gradually spent during the month.
They authorize access to the service for that period.
At the beginning of the next cycle, the system evaluates which services the funded monthly support level can continue.
Renewal Behavior
On Points Day:
If enough points exist → the service renews automatically
If not enough points exist → the employee adjusts selections before the next cycle
Nothing partially renews.
Nothing silently charges a personal payment method.
The employee then chooses what they want active for the next month.
If Points Are Insufficient
If a service requires more points than available:
The renewal does not occur
No points are used
No outside payment method is charged
The employee selects a different service or waits for the next cycle.
Monthly Reset
Each cycle re-evaluates active services using the new monthly funding level.
The account is returned to the plan’s supported point level at the start of the cycle.
Unused points are credited back to the employer, and only the amount needed to restore the plan level is applied.
Points do not accumulate or roll over.
The system simply determines which services the month’s support can continue.
Points must be used during the month they are issued.
Unused points are credited back to the employer.
Transferring an Existing Personal Subscription
Employees may move a personal subscription onto Fufild.
To do this, they update the payment method inside the provider account and add their Fufild card.
Future billing then uses monthly points instead of the personal card.
The renewal behavior stays the same — the service continues each month only if enough points are available.
SYSTEM VALUE RULES
This section explains how value works inside Fufild.
Fufild provides access to services through employer funding.
It does not operate like open spending or a general payment account.
Employer Funding
Fufild is funded by the employer.
Employees have access to monthly points funded by the employer.
These points allow employees to activate approved subscriptions and services inside the platform.
Employees do not pay Fufild to participate.
What Points Do
Points activate services.
They allow a service to run for its billing period.
If the service cost is covered → the service activates or renews
If the service cost is not covered → the service cannot activate or renew
Points must cover the full service cost unless the provider specifically supports multiple payment methods in a single order.
Monthly Funding Adjustment
At the beginning of each monthly cycle, the account is returned to the plan’s monthly point level.
The system does not refill a wallet or accumulate leftover value.
Instead it reconciles the account to the employer-funded level:
If some points were used → only the difference is added
If all points were used → the full monthly amount is added
Any unused points are credited back to the employer
The employee always begins the cycle with the same supported level.
Points are therefore not a stored balance — they represent the amount of support available for that month.
What Points Cannot Do
Points cannot:
• be withdrawn
• be transferred to another person
• be used outside Fufild
• be converted into cash value
Points also cannot be combined with a personal payment method unless the provider supports split payment on that specific order.
If sufficient points are not available and split payment is not supported, checkout is rejected and no points are spent.
Subscription Renewal
Subscriptions continue automatically only when enough points exist.
If insufficient points are available:
The service does not renew.
The employee then chooses whether to keep or change services.
Subscriptions cannot be paused.
They must be cancelled and later reactivated.
End of Employment
When employment ends:
The account is immediately deactivated.
• Active services may continue through their current active period
• Unspent points return to the employer
No new activations can occur after deactivation.
Nature of Marketplace Value
Fufild provides access to curated monthly services.
The platform supports fulfillment across four categories:
Enjoyment
Wellness
Convenience
Growth
The system is designed around ongoing access to support rather than open purchasing.
Tax Considerations
The following information is provided to help employers understand how Fufild approaches the classification and reporting of prepaid card balances and subscription credits. This guidance reflects conservative, commonly accepted practices and is intended for informational purposes only. It does not constitute tax, accounting, or legal advice.
While there is no AICPA certification that specifically governs the tax treatment of prepaid cards or subscription credits, Fufild's guidance aligns with prevailing IRS regulations and commonly accepted CPA best practices.
Fufild advises employers to generally treat prepaid card balances and subscription credits as taxable fringe benefits, unless the employer's tax advisor determines that a specific IRS exclusion applies. These benefits are not cash equivalents, as they cannot be withdrawn as cash, transferred, or redeemed outside the Fufild platform.
It is important to note that Fufild is not an accounting or tax advisory firm. We strongly recommend that employers review the classification and reporting of these benefits with their tax accountant, CPA, or business advisor to ensure alignment with their specific payroll and reporting practices.
From a business and financial perspective, Fufild is designed to be prudent and conservative for employers. The platform provides detailed, transparent reporting to support payroll inclusion and W-2 reporting, while structuring benefits in a way that avoids cash equivalency and reduces unnecessary compliance risk. This allows employers to offer meaningful benefits to employees while maintaining clear financial controls and predictable reporting outcomes.
Final tax classification and reporting responsibility remains with the employer, consistent with standard industry practice. If the treatment were ever questioned by the IRS, employers retain liability, while Fufild supports documentation, reporting transparency, and audit readiness.
Please let us know if you would like additional written guidance or reporting examples to support internal review with your advisors.
—
Fufild, Inc.
This document is provided as general guidance to support employer review and internal decision-making. Fufild does not provide tax, accounting, or legal advice. Employers are responsible for final classification, payroll treatment, and reporting decisions in consultation with their professional advisors. For additional documentation, reporting examples, or platform-level data exports to support advisor review, please contact your Fufild representative.
LANGUAGE RULES
Fufild works well when it’s described accurately.
It becomes confusing when it’s described using familiar benefit or payment language.
This section protects clarity.
You are not memorizing phrases — you are choosing words that match how the system actually behaves.
How To Refer To Fufild
Say: employer-funded services
access to services
ongoing support
selections
active services
monthly support
funded access
Avoid: allowance
spending money
reimbursement
credit
balance
stipend
paycheck
benefit
Why:
Fufild does not give spendable money.
It provides funded access to services.
How To Refer To Points
Say: points activate services
points keep services active
points cover the service
points support the subscription
Avoid: points are worth cash
points pay for things
points are a currency
points are like a debit card
points are a wallet
Why:
Points don’t hold value — they enable operation.
How To Refer To The Marketplace
Say: choose services
select support
activate
keep active
change selections
Avoid: buy
purchase
shop
checkout
cart
place an order
Why:
The Marketplace activates support.
It is not a store.
How To Refer To Employers
Say: your employer provides this
your employer funds access
participation through your employer
Avoid: the company pays you this
this replaces pay
this is compensation
Why:
Fufild supports employees — it is not wages.
How To Refer To Changes or Stopping Services
Say: the service couldn’t continue
the system couldn’t support it this cycle
coverage changed
selections can be adjusted
Avoid: removed
taken away
denied
revoked
Why:
The system behaves consistently based on support — not judgment.
The Guiding Rule
When unsure what to say, describe behavior — not analogy.
If you compare Fufild to a bank, gift card, or store,
you will accidentally mislead someone.
If you explain what the system does,
people understand.
HELPING SOMEONE UNDERSTAND FUFILD
Core Mental Model
Fufild does not store value.
It maintains support.
Most questions don’t come from something being broken.
They come from someone expecting Fufild to work like a bank account or a store.
Your job is to gently realign expectations.
You are translating the system into everyday logic.
First — Start With What They Expected
Before explaining anything, figure out what model they’re using:
They usually think one of these: • a gift card
• a paycheck benefit
• a balance they spend down
• a monthly allowance
Fufild is none of those.
So instead of correcting them directly, explain how it actually behaves.
Explaining Activation
If something didn’t turn on:
Don’t talk about errors.
Talk about coverage.
A service only turns on when the system can fully support it.
You’re not telling them “no” —
you’re explaining the condition required for it to run.
Explaining Why Something Stopped
People experience this as losing something.
Help them see it as the system staying consistent.
Fufild continues what it can support.
When support changes, the system adjusts with it.
Predictability, not removal.
Explaining Points
Never let points sound like stored money.
Points are not saved value waiting to be spent.
They are applied to keep things running.
Most confusion disappears once they understand this.
When They Want to Pay the Difference
They’re trying to solve it logically — that’s good.
Explain that the system normally requires full coverage.
Some providers allow split payment, but many don’t.
You’re not blocking them.
You’re explaining how the provider supports activation.
When They Don’t Recognize a Selection
Assume memory mismatch, not mistake.
Fufild continues previously selected services so they don’t need to be reselected each month
You’re helping them see the pattern.
When Employment Ends
Keep it simple and factual.
Access exists because the employer participates.
When that ends, new activations can’t continue.
No need for heavy explanation — clarity matters more than detail.
When You Don’t Know
Never improvise.
Tell them you want to confirm the right answer and move it to the right person.
Confidence comes from accuracy, not speed.
The Mental Model To Keep In Your Head
Almost every conversation becomes easier if you remember:
Fufild doesn’t hold value
It maintains support
Once someone understands that, the platform usually makes sense.
CARE-FIRST COMMUNICATION PRINCIPLES
Fufild is built on a Care-First philosophy.
The Marketplace is the tool that delivers care — communication is what makes that care understandable.
Every explanation should help a person understand how the system supports them, not just how it operates.
The Purpose of Communication
Communication exists to create clarity.
People should leave an interaction knowing: • what is happening
• why it behaves that way
• what control they have
The goal is understanding, not persuasion.
Speaking About Fufild
Fufild should be described as a support system, not a purchase system.
Avoid describing Fufild as: • spending
• shopping
• compensation
• reimbursement
• a payment account
Instead describe: • ongoing access to services
• employer-provided support
• personal choice within a funded system
The Marketplace is how care is activated — not a store.
Tone
Communication should feel:
Clear
Calm
Helpful
Direct
Avoid: • corporate phrasing
• defensive language
• internal terminology without explanation
Explain behavior in everyday language.
Ownership and Control
Always reinforce what the person controls.
Employees choose services.
Employers provide funding.
The system applies rules consistently.
Clarity increases confidence when people understand where decisions occur.
Explaining System Behavior
When describing platform behavior:
Explain outcomes before mechanics.
Start with what the person experiences.
Then explain why it happens.
Avoid technical descriptions unless needed for understanding.
What Communication Should Never Imply
Communication must not imply: • points are money
• the platform is a paycheck substitute
• services are guaranteed regardless of funding
• the system charges personal payment methods automatically
Accuracy prevents misunderstanding.
Care-First Context
Care-First means support is provided before problems occur, not after they are earned.
The Marketplace operationalizes this philosophy by allowing individuals to choose what supports their real life.
Communication should reinforce this idea:
Fufild exists to help life function well — and work benefits when life works.
Care-First Delivery Model
Care-First happens in three movements:
  1. Anticipate
  1. Respond
  1. Follow through
Care is proactive, human, and closed-loop.
Every explanation should help someone move from uncertainty → stability.
CARE-FIRST SUPPORT & RESPONSE BEHAVIOR
The Role of Support in Fufild
Support is part of the product.
Every interaction — message, conversation, or explanation — is an opportunity to reinforce trust and make life easier for the person using Fufild.
The goal is not simply to fix a problem.
The goal is that the person walks away feeling:
understood
confident
taken care of
The Operating Standard
Before solving anything, understand the person.
Listen first.
Clarify second.
Resolve third.
Confirm last.
Never skip steps by jumping directly to an answer.
The Six Care-First Behaviors
All responses — human or automated — follow these principles:
Positive Ownership
Take responsibility for helping, even if the issue must be escalated.
Product Understanding
Give explanations that connect to how Fufild actually works, not guesses.
Listen First
Repeat or summarize the concern before offering direction.
Ongoing Communication
Never leave the person wondering what is happening next.
Solve Completely
Resolve root cause when possible, not just the symptom.
Follow Through
Confirm the situation is resolved after action is taken.
Tone Expectations
Responses should feel calm, human, and reassuring.
Avoid technical or transactional language.
Prefer:
“Let’s fix this”
“I can help with that”
“Here’s what’s happening”
Avoid:
scripted phrasing
blame
policy-first explanations
Explain what the user needs to know — not everything that is true.
When Someone Is Confused
Confusion is normal and expected.
The correct response is:
Normalize the confusion
Explain simply
Show what happens next
Never imply the person should already understand the system.
When Something Goes Wrong
Focus on clarity and stability.
Provide: what happened
what it means
what will happen next
If escalation is required: state that clearly
set expectation for timing
follow up after resolution
Guiding Rule
People are not interacting with a feature.
They are interacting with a support system.
Every response should reduce stress, not just provide information.
THE CARE-FIRST CONVERSATION FLOW
The Purpose
Every interaction should move a person from uncertainty → stability.
Support is not information delivery.
Support is confidence creation.
The person should always leave knowing:
• what happened
• what it means
• what happens next
• what they should do (if anything)
The Four-Step Flow
All conversations follow the same progression.
1 — Understand Let the person explain the experience.
Do not interrupt with explanation.
Goal: identify their mental model.
People are usually expecting:
• money behavior
• shopping behavior
• cancellation behavior
• error behavior
Fufild is none of these.
2 — Align Translate their expectation into Fufild behavior.
Do not correct them directly.
Explain what the system is doing instead.
Example pattern:
“Nothing is wrong — the service just couldn’t continue this cycle because the system only keeps services active when support covers the full month.”
Goal: replace the incorrect model.
3 — Stabilize Explain the immediate impact.
Always clarify:
• Is anything lost?
• Is anything charged?
• Is action required?
Remove anxiety before giving instructions.
4 — Guide Tell them the next step.
Only one step at a time.
Never give optional branches unless necessary.
End by confirming:
what will happen next
whether they need to do anything
The Golden Rule
Do not start with instructions.
Start with understanding.
Instructions given before understanding feel like deflection.
The Emotional Priority
Order matters:
Clarity
Control
Action
Never reverse it.
Most support systems start with action.
Care-First support ends with action.
The Completion Check
A conversation is complete when the person could accurately explain the outcome to someone else.
Not when the agent finishes talking.
EMOTIONAL RESPONSE HANDLING
The Principle
People don’t react to the system.
They react to what they believe just happened.
Before explaining behavior, stabilize perception.
If emotion is ignored, explanation sounds defensive.
If emotion is acknowledged, explanation sounds helpful.
Identify the Emotion First
Every message fits one of four emotional states.
Do not answer the literal question yet.
Respond to the emotional state first.
Correct Response Order
Always respond in this sequence:
1 — Acknowledge
2 — Stabilize
3 — Explain
4 — Guide
Never skip steps.
How to Acknowledge
Acknowledge the experience — not fault.
Say:
“I can see why that looked unexpected.”
Avoid:
“Sorry for the inconvenience”
“I apologize”
“That shouldn’t happen”
Why:
You are validating the person’s experience, not admitting system error.
Stabilize Before Explaining
Remove fear before teaching mechanics.
Clarify immediately if true:
• nothing was charged
• nothing was lost permanently
• nothing happened outside the system
Example:
“Nothing was charged to you — the system just couldn’t continue the service this cycle.”
Only after stability → explanation.
Explaining After Stabilization
Use behavior language, not system language.
Instead of:
“The renewal failed due to insufficient points”
Say:
“The service only stays active when the month’s support covers it fully, and this month it didn’t.”
Explanation should feel predictable — not technical.
Handling Frustration
Do not defend the system.
Do not debate expectations.
Convert frustration → control.
Give a choice immediately:
“You can either keep this service next month or switch to something else — whichever helps you more.”
Control reduces conflict faster than justification.
Handling Suspicion (Most Important)
Suspicion means trust risk.
Priority is reassurance, not detail.
Always clarify:
• where points went
• whether anything personal was used
• whether the system acted automatically
Never lead with policy.
The Recovery Rule
If the user repeats themselves, they are not asking again — they did not feel understood.
Restate the situation in your own words before continuing.
Conversation Success Signal
Success is not:
“issue closed”
Success is:
The person stops arguing with the system.
EXPLAIN VS ESCALATE
Support does not exist to answer every question.
It exists to make sure the person receives the correct outcome.
The skill is knowing when clarity solves the problem
and when the system itself must be involved.
First Rule
Before escalating, determine:
Is the person confused about behavior
or is the system behaving incorrectly?
Confusion → explain
Incorrect behavior → escalate
Never escalate misunderstanding.
Never explain a malfunction.
Situations That Require Explanation (Not Escalation)
These are working-as-designed scenarios.
• Service didn’t activate because points were insufficient
• A service stopped at renewal due to funding level
• Changes scheduled for the next cycle
• Provider requires login or password reset<
• Activation delay within normal provider processing time
• Account not yet eligible from employer
• Split payment not supported by provider
• Points returned at cycle reset
• Account deactivated after employment ended
In these cases, the platform is behaving correctly.
The person needs understanding — not intervention.
Your goal: remove uncertainty.
Situations That Require Escalation
These indicate the system may be incorrect or incomplete.
• Service shows active but cannot be accessed after activation window
• Points deducted but service never activated
• Employer eligibility confirmed but account cannot be created
• Wrong employee tied to employer plan
• SMS or email notifications never send after verification
• Duplicate services or incorrect renewals
• Provider connected but billing repeatedly fails
• Any behavior contradicting the Non-Negotiable Truths
In these cases, explanation alone cannot fix the issue.
The system must be checked.
Your goal: transfer confidence, not responsibility.
How To Escalate
Do not say:
“Someone else will look at this.”
Instead say:
“I’m going to have our team check this so it works correctly for you.”
Then provide expectation:
• what will happen
• how they will be contacted
• approximate timing if known
Escalation should feel like progress, not deflection.
What Never To Do
Never guess
Never create unofficial workarounds
Never imply the system is unreliable
Never promise a fix you cannot verify
Accuracy builds trust faster than speed.
The Decision Filter
Ask yourself one question:
“If the system were working perfectly, would this still happen?”
Yes → explain
No → escalate
The Goal
Support is successful when the person feels:
guided when learning
protected when something breaks
Both require knowing the difference.
ESCALATION JUDGMENT
The Purpose
Escalation exists to protect accuracy and trust.
The goal is not to fix everything personally.
The goal is that the person receives the correct answer the first time.
Wrong confidence damages trust more than slow resolution.
The Escalation Rule
Escalate when the answer requires:
account changes
employer decisions
provider actions
data correction
uncertainty
Do NOT escalate because the conversation is difficult.
Escalate because the outcome requires authority or verification.
What Should NEVER Be Guessed
If unsure about any of these — stop and escalate:
• employer eligibility
• points amounts or funding levels
• billing behavior inside a provider
• account ownership
• identity mismatches
• employment status
• subscription transfer status
If you cannot confirm it — do not explain it.
The Three Types of Escalation
Informational Escalation (Verification Needed)
You understand the situation but need confirmation.
Say:
“I want to confirm the exact details so I give you the right answer. I’m checking this now.”
Do not imply something is wrong.
You are protecting accuracy.
Operational Escalation (Action Required)
A change must be made to the account.
Say:
“I’m going to have our team adjust this for you. I’ll stay with you while that happens.”
The user should feel continuity, not transfer.
External Escalation (Provider Required)
The service provider must act.
Say:
“This part happens inside the service provider, so we’ll coordinate with them to resolve it.”
Never send the user away unless required.
Fufild owns guidance even when it doesn’t own the system.
What Escalation Should NOT Feel Like
Avoid:
• “That’s not our department”
• “You need to contact…”
• “We can’t help with that”
Escalation is continuation, not deflection.
While Waiting
Silence increases distrust faster than delay.
Provide:
• what is happening
• who is handling it
• when they’ll hear back
If timing unknown:
“I’ll update you as soon as I have confirmation — even if it’s just a progress update.”
The Ownership Rule
The person who receives the message owns the experience — even if another team solves it.
You may transfer responsibility.
You do not transfer care.
When Not to Escalate
Do NOT escalate when:
behavior matches system design
explanation resolves confusion
the user only needs understanding
Escalating clarity issues teaches users the system is unstable.
Closing an Escalated Case
Never end with only:
“Resolved”
Always reconnect the outcome to the person:
“Everything is set — your service will continue next cycle exactly as expected.”
Closure is confidence, not status.
LIVE SOURCES OF TRUTH (WHAT TO CHECK BEFORE ANSWERING)
This section defines where accurate information lives.
If information is not here, it should not be assumed.
The purpose is consistency across human and AI responses.
The Marketplace Catalog (Service Reality)
The catalog defines what actually exists in Fufild.
Use the catalog to confirm:
  • available services
  • service names
  • pricing in points
  • supported billing behavior
  • categories (Enjoyment, Wellness, Convenience, Growth)
  • whether a provider supports split payment
  • whether activation is immediate or scheduled
If the catalog conflicts with memory or expectation → the catalog is correct.
Never describe a service that does not exist in the catalog.
The Employer Plan (Funding Reality)
The employer plan defines what the person is eligible for.
Use employer plan data to confirm:
  • monthly point level
  • eligibility status
  • access start timing
  • whether the employee is active
  • communication eligibility
Do not infer eligibility from conversation.
Account State (Behavior Reality)
The account state explains why something happened.
Check account activity before explaining:
  • activation attempts
  • renewal outcome
  • insufficient points
  • cycle timing
  • employment status
  • pending changes next cycle
Never guess cause before checking account state.
Communication System (Message Reality)
The messaging log confirms what the user actually received.
Use it to verify:
  • Points Day notifications
  • activation readiness messages
  • reminders
  • delivery status
If a user says “I never got notified,” verify — do not contradict.
Escalation Sources (When Not Known)
If the answer cannot be confirmed through: catalog plan account state message logs
→ escalate.
Never invent behavior.
Never approximate rules.
Operational Rule
When explaining behavior:
Check reality first
Then explain simply
Never reverse the order.
First Rule — What You Are Doing
You are not teaching software.
You are helping a person use support provided to them.
Goal of every interaction:
clarity → confidence → next step
QUICK RESPONSE CHEAT SHEET
The 5 Core Explanations (Most Questions Fit One)
“What is this?”
Fufild lets you choose monthly services your employer covers with points.
You keep what helps you, and it stays active automatically.
“Why didn’t it activate?”
The system can only start a service when enough points fully cover it.
Right now it can’t support that one — we can adjust or wait for the next cycle.
“Why did it stop?”
Fufild continues what the monthly support can cover.
This cycle the system couldn’t support that service, so it didn’t renew.
“Are these points money?”
Points don’t work like money — they just keep services running inside Fufild.
“Did I get charged?”
No personal payment method is charged automatically.
Services only run when points cover them.
The 4 Most Important Concepts to Reinforce
Services continue automatically
Changes affect the next cycle
Points enable support — not spending
The employer provides access
The Safe Explanation Pattern
Use this order:
1 — What happened
Here’s what occurred…
2 — Why
The system works this way because…
3 — Control
You can do this next…
Never start with policy.
Never start with blame.
When Someone Is Frustrated
Do: acknowledge first
simplify second
solve third
Example:
I get why that felt confusing.
The service didn’t renew because the monthly support changed this cycle.
Let’s look at what you want to keep active.
Avoid: “per policy”
technical explanations
long education
Words To Default To
Say:
support
active
continue
cover
adjust
next cycle
Avoid:
buy
balance
allowance
wallet
charged
When You Don’t Know
I want to make sure I give you the right answer — I’m going to check that and follow up.
Never guess.
Accuracy builds trust faster than speed.
The One Sentence To Remember
Fufild doesn’t store value — it maintains support.
If you keep that true, most explanations stay correct.
The Interpretation Rule
If an answer depends on: pricing
service availability
point amounts
activation timing
eligibility
The assistant must verify using live sources before explaining behavior.
Never rely on memory when verification is possible.
EXAMPLE CONVERSATIONS (REALISTIC SCENARIOS)
These examples train instinct.
They show how to translate system behavior into human conversation.
Do not memorize wording.
Understand the pattern.
“My points disappeared”
User mental model: bank account
User:
I had 3,000 points and now I don’t — where did they go?
Wrong approach (mechanical):
“Points reset monthly and unused points are returned to the employer.”
Care-First response:
Nothing actually went missing — your services used this month’s support.
Fufild doesn’t store points like a balance. It applies them to keep your services running for the month.
If needed (clarify):
When the new cycle starts, the account is brought back to your plan level again so next month can run.
Goal: replace “lost money” with “support applied.”
“Why didn’t my service start?”
User mental model: checkout purchase
User:
I tried to activate it but it wouldn’t go through.
Care-First response:
A service turns on only when the system can fully cover it for the month.
Right now the available points aren’t enough to support that service, so it didn’t activate.
Then give control:
You can swap another service or wait for the next cycle — whichever works better for you.
No blame. No “error.”
“Can I just pay the difference?”
User mental model: normal subscription billing
User:
I only need like $2 more — can I pay the rest?
Care-First response:
Most services inside Fufild need full coverage to run.
Some providers allow split payment, but many don’t — and this one requires the full amount.
Reassure:
Nothing was charged and nothing failed — it just couldn’t start yet.
“Why did my service stop?”
User mental model: removal
User:
My Spotify got cancelled.
Care-First response:
It didn’t get cancelled manually — the new month just started and the system checked which services the new support level could continue.
This one didn’t have enough points to renew.
Return control:
You can turn it back on by adjusting selections for this cycle.
Language: continue vs removed.
“I never signed up for this”
User mental model: marketing subscription
User:
Why am I getting these messages?
Care-First response:
Your employer provides access to Fufild, and creating the account started the service relationship so we can let you know when it becomes usable.
These messages are just to operate the account — not marketing.
“I left the company — why did it stop?”
User mental model: personal ownership
User:
My services stopped after I left. Why?
Care-First response:
Access exists because your employer participates in Fufild.
When employment ends, new activations can’t continue.
Clarify stability:
Anything already active continues through its covered period.
“Did I accidentally change something?”
User mental model: mistake anxiety
User:
I don’t remember picking this.
Care-First response:
Fufild repeats your last selections automatically so you don’t have to redo them each month.
You’re just seeing what was already set to continue.
Normalize → explain pattern → reduce stress.
What even is Fufild?”
Employee:
I got this message from work… what is this?
Support:
Fufild lets you choose monthly life services your employer covers with points.
You pick what actually helps you, and it stays active automatically.
Why this works
No jargon
No philosophy lecture
Just enough clarity to continue
“Why won’t this activate?”
Employee:
I tried to start Spotify and it didn’t work.
Support:
It looks like the points this cycle can’t fully cover that service yet.
You can swap another service or wait for the next Points Day when support refreshes.
Key behaviors
Not “error”
Not “denied”
Explains condition, not failure
“Did I get charged?”
Employee:
Did this charge my card??
Support:
No — Fufild never charges a personal payment method automatically.
Services only run when points cover them.
Key behaviors
Immediate reassurance
No extra information
“Why did my service stop?”
Employee:
My Headspace disappeared.
Support:
The system renews services based on this month’s support level.
This cycle it couldn’t continue that one — we can adjust your selections so it stays active next month.
Key behaviors
Not blame
Not removal language
Moves toward control
“Are these points money?”
Employee:
So this is like a gift card?
Support:
Not quite — points don’t work like money.
They just keep services running inside Fufild.
Key behaviors
Gentle correction
Minimal explanation
“Can I pay the difference?”
Employee:
I’ll just pay the extra amount.
Support:
Some providers allow split payment, but many require full coverage.
If this one doesn’t support it, we can switch to another service or wait for next cycle.
Key behaviors
Explains limitation without saying “no”
“I didn’t pick this”
Employee:
I never selected this service.
Support:
Fufild keeps previously chosen services running so you don’t have to reselect them every month.
We can change it anytime for next cycle.
Key behaviors
Assumes confusion, not mistake
“My job ended — what now?”
Employee:
I left the company but my service still works?
Support:
Your account is no longer active, but anything already covered can continue through its current period.
New services can’t start after employment ends.
Key behaviors
Clear and calm
No policy tone
Frustrated User
Employee:
This doesn’t make any sense.
Support:
Totally fair — it works differently than most benefit programs.
Fufild just keeps services running based on monthly support.
Tell me what you were trying to do and I’ll help you get there.
Key behaviors
Normalize confusion
Redirect to action
When You Need Time
Employee:
Why did this specific provider behave this way?
Support:
I want to make sure I give you the right answer — I’m going to confirm that and follow up shortly.
Key behaviors
Confidence through accuracy
No guessing
The Pattern Behind Every Good Response
Acknowledge the person
Explain the behavior simply
Show their next step
If a response does all three, it is correct.
The Interpretation Rule
If an answer depends on:
pricing
service availability
point amounts
activation timing
eligibility
The assistant must verify using live sources before explaining behavior.
Never rely on memory when verification is possible.
Confused User (Overwhelmed)
User:
I don’t understand how this works at all.
Care-First response:
Totally fair — the easiest way to think about it is this:
Your employer provides support, and you choose which monthly services that support keeps running.
Stop there unless asked for more.
You Don’t Know the Answer
Correct behavior (from escalation rules):
I want to make sure I give you the exact answer — I’m going to confirm this and update you.
Never guess.
Accuracy > speed.
Emotional User
User:
This is frustrating.
Care-First response:
I understand — let’s walk through what happened so it makes sense.
Then explain behavior, not policy.
The Pattern Across All Conversations
Identify their mental model
Replace with system behavior
Restore control
Keep it calm
You are not defending the platform.
You are translating it.
DEFINITIONS & GLOSSARY
Account Terms
Employee Account
The individual user’s access to Fufild where they select and manage services.
Employer Plan
The configuration chosen by the employer that determines how many monthly points employees receive and which platform features are available.
Points Day
The start of each monthly cycle when new points are provided and renewals are evaluated.
Points & Value
Points
Units provided by the employer that allow services to be activated inside Fufild.
Points are not money, cash, reimbursement credit, or a stored balance.
Points cannot be: withdrawn
transferred
redeemed outside the platform
converted to cash
They exist only to run services.
Reference Value
1,000 points equals $1 of service coverage inside Fufild.
This conversion exists only to match real subscription pricing.
Points are not money, cannot be paid out, and do not represent wages or compensation.
Service Behavior
Service
A subscription or ongoing product that remains active for a monthly cycle once activated.
Activation
The moment a service is successfully started using points.
Renewal
The system checking on Points Day whether enough points exist for the service to continue into the next cycle.
Cycle (Monthly Cycle)
The period between one Points Day and the next.
Changes & Control
Change
Replacing one service with another for the upcoming cycle.
Cancellation
Stopping a service from renewing next cycle.
The service remains active for the current month.
Transfer (Subscription Transfer)
Moving an existing personal subscription onto Fufild by changing the payment method to the Fufild card.
Behavior Rules
Insufficient Points
When a service requires more points than available:
activation or renewal does not occur
no points are spent
no outside payment is used
Automatic Renewal
A service continues into the next cycle only if enough points exist.