Creator relationships & outreach
Established relationships across the CapCut UK creator community, including creators working with AI and generative tools; approximately 20–30 creators referred into the ecosystem overall.
Professional / CapCut UK
Community is an operations job.
RoleFreelance Community Manager / creator operations
Experience3+ years
Primary marketUnited Kingdom
International internal teamsCross-market operations
AI / systemsGenerative support · CreatorOps workflow
Creator ↔ internal team
I support UK creators across programmes, challenges, product issues and AI/generative features, turning questions and evidence into actionable internal context and bringing decisions back clearly.
Creator-side perspective
I also work from inside the creator experience itself. That gives the operational role a direct view of the workflows, creative decisions and product behaviours that affect adoption and continued participation.
15.5M+CapCut views
1.97MTemplate uses
1.16MExports
150M+TikTok views via templates
Core responsibilities
AI & generative support
Gather context around generation failures, feature access and product issues, then feed findings back internally.
Creator AI Agent rollout
Configured and supported a CapCut AI Agent rollout in the UK creator community, then provided qualitative feedback on real creator usage.
Challenge operations
Participation questions, winner communication, template requirements and grading.
Creator ↔ internal-team liaison
Move policy, programme, payment and product information clearly between UK creators and international internal teams.
Reporting
Weekly workload, activity, bugs and operational follow-ups.
Creator support
Questions, programme guidance, clarifications and follow-up for UK creators.
Bug escalation
Turn creator-reported product issues into reproducible internal context.
Payments & bonuses
Payment and bonus status, programme requirements and escalations.
Community moderation
Discord moderation, announcements and day-to-day community upkeep.
Multi-market systems
Experience across UK, French and German creator-server systems.
Operational extension / agentic AI
Turn conversation into structured operational memory.
I independently designed and built CreatorOps to turn high-volume Discord support into persistent, searchable cases, evidence-linked history and clear next actions. It has indexed 2,800+ completed case records, including 1,200+ records of support handled by me. Discord ingestion is read-only; outbound creator messages are review-gated in the current deployment, with the action layer designed for further automation.
2,800+Completed case records indexed
1,200+Records of support handled by me
Read-only Discord activity enters the workflow without giving the system outbound control.
Creator conversations are extracted into cases, reconciled against history and checked for duplicates or recurrence.
Issue type, priority, status and next action are classified while relevant knowledge and similar cases are retrieved.
The system prepares monitoring, escalation and response actions. The current deployment routes outbound creator messages through review, while the action layer is designed to support automated responses and status updates in a later implementation.
Open live CreatorOps workspace ↗
Live CreatorOps workspace available during the application period. Recruiters can explore the operational system directly, including its case workflow, evidence history, reporting and live operational scale.
RailwaySupabaseVercel / Next.jsGitHubPersistent case historyEvidence-linked recordsKnowledge retrievalAutonomous QAWeekly reporting
Operational loop
01Listen
Question, payment issue, challenge query or product problem.
02Clarify
Get enough context to decide whether it needs escalation.
03Route
Send it to the right internal contact with the context needed to act.
04Close
Return the update, log the work and carry forward anything unresolved.