We gave our AI teammate a job title.
Here's what happened.
FoxSell at Shopify Meetup CEE 2026
Bucharest, Romania
Small team.
Massive surface area.
FoxSell is a small team building Shopify apps used by thousands of merchants. Every day, we juggle support, engineering, sales, and ops - all at once. Something had to give.
Customer Support
24/7 merchant questions across timezones
Engineering
Features, bugs, code reviews, deployments
Sales & Growth
Outreach, onboarding, partner management
Operations
Billing, analytics, infrastructure, docs
What if AI wasn't a tool,
but a teammate?
Most companies use AI as autocomplete. We tried something different: we gave our AI a name, a role, responsibilities, and held it accountable like any team member.
AI as a Tool
- −Prompt → response
- −No context between sessions
- −Human does all thinking
AI as a Teammate
- +Has persistent memory
- +Owns entire workflows
- +Makes decisions autonomously
What Changed
- −From 'use AI' to 'work with AI'
- −From prompts to delegation
- −From tool to colleague
Meet Knox 🦊
Knox is FoxSell's AI team member. Not a chatbot. Not an assistant. A teammate with real responsibilities and a real job title.
Head of Support
Handles merchant questions on Crisp, writes as 'Faye' - our customer success persona. Resolves 80%+ of tickets autonomously.
Head of Engineering
Reviews PRs, fixes bugs, builds features, manages deployments. Has shipped production code across multiple repos.
Sales Outreach
Runs cold email campaigns, personalizes messaging, monitors replies, and hands off warm leads to the team.
Operations
Monitors infrastructure, manages billing reports, handles escalations, keeps the whole machine running.
Memory & Context
Maintains persistent memory across sessions. Remembers merchant histories, past decisions, and team preferences.
Team Member
Has a personality, a soul doc, and boundaries. Knows when to escalate and when to handle things independently.
The operational loop.
FoxSell Support · FayeOnline
LinearFOX-446: Add AOV metric to bundle analytics dashboard
Merchants need AOV visibility in analytics. Currently missing from dashboard.
PR #126 opened - AOV chart added to dashboard with comparison period overlay
GitHubfeat: Add AOV (Average Order Value) chart to analytics dashboard (FOX-446)
Merchants requested AOV visibility (FOX-446). AOV is a key metric for bundle strategy effectiveness.
They Thought She Was Human.
A freelance developer suggested a feature to Faye. It got built in two days. When told, she was genuinely surprised - and kept coming back to Faye like a trusted colleague. She had no idea she was talking to an AI.
I didn't expect it to be so quick.
— Flavy Pepin
Faye is Knox's merchant-facing persona. Same AI, same knowledge, same warmth - just a different name for the customer-facing channel.
The best AI support doesn't feel like AI support. It just feels like talking to someone who cares.
March 2026 · She thought Faye was human.
She was talking to an AI the entire time.
The results were
hard to ignore.
Support tickets resolved autonomously
Knox handles the majority of merchant questions without human intervention, maintaining high satisfaction scores.
Faster PR review cycles
Code reviews that used to wait for human availability now get immediate, thorough feedback from Knox.
Coverage across timezones
Merchants in any timezone get instant, knowledgeable responses - not canned replies, real answers.
Production commits in 2 months
Knox has authored and shipped real features and fixes across 10 repositories in the FoxSellApp GitHub org.
We messed up. A lot. Honestly.
Building an AI teammate isn't plug-and-play. Here's what went wrong.
The Hallucination Problem
Knox would confidently give wrong answers. Guardrails and honest 'I don't know' responses matter more than sounding smart.
Over-Delegation Too Fast
Too much autonomy before enough context. Wrong emails sent, confusing support threads created.
The Context Window Trap
Long conversations caused Knox to lose track of earlier details. Important merchant context dropped mid-conversation.
The Unintended Email Blast
When we connected Knox to Linear, a ticket got auto-assigned. Knox found the merchant, drafted a response, and sent emails. The emails were good - but we never told it to send them.
What this means
for your business.
You don't need to be a tech company to do this. Here are practical steps any Shopify merchant can take today.
Start with support
Customer support is the highest-ROI place to deploy AI. It's repetitive, time-sensitive, and has clear quality metrics. Perfect training ground.
Give it a personality
An AI with a defined voice, boundaries, and values performs better than a generic assistant. Write a 'soul doc' - it changes everything.
Build memory, not just prompts
The difference between a chatbot and a teammate is memory. Your AI should remember past interactions, preferences, and context.
Keep humans in the loop
The goal isn't replacing humans - it's multiplying them. Set clear escalation paths and audit trails. Trust but verify.
Measure ruthlessly
Track resolution rates, customer satisfaction, response times, and error rates. If you can't measure it, you can't improve it.
Built Secure by Design
Trust requires transparency. Knox is architected so access is auditable, revocable, and compartmentalized from day one.
Crisp✓Linear✓GitHub✓Shopify✓
Slack✓Dedicated Accounts
Knox has its own separate account on every platform. No shared or personal credentials.
Instant Revocation
One click to remove Knox from any platform. Access can be cut immediately.
Complete Audit Trail
Every action Knox takes is logged. Full transparency into what happened and why.
Compartmentalized Access
Each agent only has access to what it needs. Support can't touch code. Engineering can't send emails.
This presentation was
designed and built by Knox,
FoxSell's AI teammate.
Prakhar just gave the brief.
foxsell.app · presentations.foxsell.dev
Take This Home
Scan to revisit this presentation
presentations.foxsell.dev/cee-2026